The content of this template is expected to be fill out for M1 Release Planning Milestone.
Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Amsterdam |
| Project Lifecycle State | Incubation |
| Participating Company | AT&T, Huawei, Techmahindra, China Mobile, Amdocs |
Scope
What is this release trying to address?
- Develop a mechanism for a 3rd party to be approved to validate VNFs to allow them to obtain an ONAP Compatible Label
- Align with the VNF SDK project and VNF Requirements
- Develop and define a long-term strategy for the ONAP Compatible Label
Use Cases
- We will not target any specific use case as the VNF Validation Program is focused on developing a mechanism for any VNF to obtain a ONAP Compatible Label
Minimum Viable Product
The MVP for Amsterdam will create the necessary framework and guidance to allow any 3rd party to acquire the ability to obtain an ONAP Compatible Label. The key here is to provide the necessary tracking and mechanisms to both carryout the validations and also to manage which 3rd parties have been approved to carry out such validations.
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description |
|---|---|
| Validation Tracking & Reporting | Django Project with associated components. This includes the mechanism to provide documentation, steps to take to make the VNF valid and report back on the validation status |
| Validation Tools | Pytest framework and/or any other tools relevant here from the VNF SDK Project |
| Documentation | Documentation of all aspects necessary to run a validation program including the steps to take to become an approved validation entity |
| Validation Entity Tracking | The nature of how this will be tracked will be defined during the project |
Sub-Components
List all sub-components part of this release.
Activities related to sub-component must be in sync with the overall release.
Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.
ONAP Dependencies
- VNF SDK: Develop
- VNF Requirement: responsible for documenting VNF guidelines and requirements. It will produce requirements documents
Architecture
High level architecture diagram
At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
Anyone reading this section should have a good understanding of all the interacting modules.
Third Party Products Dependencies
Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).
| Name | Description | Version |
|---|---|---|
| To fill out | To fill out | To fill out |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
Testing and Integration Plans
Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.
Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.
We will provide unit tests and CSIT tests for validation tools, packaging tools, and certification tools.
Gaps
This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.
| Gaps identified | Impact |
|---|---|
| To fill out | To fill out |
Known Defects and Issues
Provide a link toward the list of all known project bugs.
Risks
List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| code to be scrubbed for release to ONAP | additional resources assigned | include in Beijing release |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
Team Internal Milestone
This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.
It is not expected to have a detailed project plan.
| Date | Project | Deliverable |
|---|---|---|
| 5/4/17 | M0 | Kickoff |
| 6/29/17 | M1 | Planning process Complete |
| 8/3/17 | M2 | Functionality Freeze |
| 8/24/17 | M3 | API/Data Model Freeze |
| 8/31/17 | Sprint 1 | sprint-1 created |
| 9/14/17 | M4 Sprint 2 | Code Freeze Sprint 1 complete, Sprint 2 created |
| 9/28/17 | RC0 Sprint 3 | Release Candidate 0 Sprint 2 complete, Sprint 3 created |
| 10/12/17 | RC1 Sprint 4 | Release Candidiate 1 Sprint 3 complete, Sprint 4 created |
| 10/26/17 | RC2 Sprint 5 | Release Candidiate 2 Sprint 4 complete, Sprint 5 created |
| 11/2/17 | Release Delivery | Target Release Date |
Documentation, Training
- Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
- Highlight the team contributions to the overall Release Documentation and training asset
- High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
- Documentation includes items such as:
- Installation instructions
- Configuration instructions
- Developer guide
- End User guide
- Admin guide
- ...
Note
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset.
Other Information
Vendor Neutral
If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.
Free and Open Source Software
FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.
Each project must edit its project table available at FOSS VNF SDK.
Charter Compliance
The project team comply with the ONAP Charter.