...
The content of this template is expected to be fill out for M1 Release Planning Milestone.
| Info | ||
|---|---|---|
| ||
Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki. |
| Table of Contents | ||
|---|---|---|
|
Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Enter the name of the release you are targeting to deliverBeijing |
| Project Lifecycle State | Either Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company List the company participating in this release. At least 3-4 organizations, including an operator are recommended. | Amdocs, AT&T, China Mobile, Huawei, Orange, Tech Mahindra, |
Scope
What is this release trying to address?
Describe the problem being solved by this releaseFor 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.
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
Describe the MVP for this releaseThe 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.
Functionalities
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.
Epics
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox vvp and issuetype in (epic=epic and (fixVersion=EMPTY or fixVersion=Beijing) serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox vvp and issuetype in (story) and (fixVersion=EMPTY or fixVersion=Beijing) serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
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.
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description | |
|---|---|---|
| To fill out | To fill outrelease notes | no new functionality beyond current code base expected |
Sub-Components
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.
...
| 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 |
|
...
API Incoming Dependencies
List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
...
API Outgoing Dependencies
API this project is delivering to other projects.
...
VVP does not have APIs with other ONAP components.
API Outgoing Dependencies
VVP does not have APIs with other ONAP components.
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 | ||
|---|---|---|---|---|
| Postgresql | object database | To fill out | To fill out | 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.
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.
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.
...
The vvp project has been developed as a containerized service for stand alone operation.
This is being integrated for instanciation by the OOM project
Gaps
Known Defects and Issues
Provide a link toward the list of all known project bugs.
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| To fill out | To fill out | To fill out |
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.
| 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 |
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.
No additional functionality is expected in Beijing release.
| Date | Project | Deliverable |
|---|---|---|
| To fill out | To fill out | To fill out |
...