Overview
DRAFT PROPOSAL FOR COMMENTS
The content of this template is expected to be fill out for M1 Release Planning Milestone.
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Beijing |
| Project Lifecycle State | Incubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company | Amdocs, AT&T, China Mobile, Huawei, Orange, Tech Mahindra, |
For the Beijing release, the vvp project adds no new functionality, but the code delivered late in the Amsterdam release is integrated into the Beijing release plan.
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.
List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.
For the Beijing release, the vvp project adds no new functionality, but the code delivered late in the Amsterdam release is integrated into the Beijing release plan.
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.
The test scripts in vvp/test-scripts are used to validate compliance with VNF Requirments. Currently these are focussed on VNFs packaged in HEAT templates. These need to expand in future releases to accommodate changes in VNF Requirments and adoption of TOSCA formatted VNFs.
The other repos provide a tool for standalone validation of VNF packages. these same tests are likely to be also made available through VNF SDK and SDC projects in future.
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description |
|---|---|
| release notes | no new functionality beyond current code base expected |
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.
Indicate where your project fit within the ONAP Archiecture diagram.
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.
Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|---|---|---|---|
| Performance | NA | NA | vvp is a stand alone tool not a platform component |
|
| Stability | NA | NA | vvp is a stand alone tool not a platform component |
|
| Resiliency | NA | NA | vvp is a stand alone tool not a platform component |
|
| Security | 0 | 1 | vvp is a stand alone tool not a platform component |
|
| Scalability | NA | NA | vvp is a stand alone tool not a platform component |
|
| Manageability | NA | NA | vvp is a stand alone tool not a platform component |
|
| Usability | NA | NA | vvp is a stand alone tool not a platform component |
|
VVP does not have APIs with other ONAP components.
VVP does not have APIs with other ONAP components.
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 |
|---|---|---|
| Postgresql | object database | To fill out |
| git | repository | |
| jenkins | Ci/CD tool |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
The vvp project has been developed as a containerized service for stand alone operation.
This is being integrated for instanciation by the OOM project
Provide a link toward the list of all known project bugs.
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 |
|---|---|---|
| To fill out | To fill out | To fill out |
Fill out the Resources Committed to the Release centralized page.
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
| 11/16/18 | M0 | Kickoff |
| 1/18/18 | M1 | Planning process Complete |
| 2/12/18 | M2 | Functionality Freeze |
| 3/8/18 | M3 | API/Data Model Freeze |
| 3/29/18 | M4 | Code Freeze |
| 4/19/18 | RC0 | Release Candidate 0 |
| 5/23/18 | RC1 | Release Candidiate 1 |
| 5/17/18 | RC2 | Release Candidiate 2 |
| 5/24/18 | Release Delivery | Target Release Date |
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.
No additional functionality is expected in Beijing release.
| Date | Project | Deliverable |
|---|---|---|
| To fill out | To fill out | To fill out |
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset. |
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.
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 Project FOSS.
Charter Compliance
The project team comply with the ONAP Charter.