...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Casablanca |
| Project Lifecycle State | Incubation, |
| 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 release
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
Minimum Viable Product
- For the Casablanca release, the vvp project adds no new functionality, but the code integrated into the Beijing release plan is maintained.
- The HEAT test suite of validation scripts is updated to align with published VNF Requirements
- Discussion Forum to support the LFN Certification programs.
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 VVP should be able to be installed and booted as a standalone tool, and the HEAT validation scripts run against VNF packagesDescribe the MVP for this release.
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.
...
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox VVP and issuetype in (epic) serverId 425b2b0a-557c-3c0c-b515-579789cceedb
...
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox and issuetype in (story) serverId 425b2b0a-557c-3c0c-b515-579789cceedb
Longer term roadmap
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 at a high level the longer term roadmap. This is to put things into the big perspective.
Release Deliverables
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 | To fill out | To fill out |
Sub-Components
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
...
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.
The VNF Validation Program provides a stand alone tool and supporting procedures for validation of VNF Packages ( HEAT templates) .
Anyone reading this section should have a good understanding of all the interacting modules.
Platform Maturity
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 | vvp is a stand alone tool not a platform component |
| |
| Stability | NA | vvp is a stand alone tool not a platform component |
| |
| Resiliency | NA | vvp is a stand alone tool not a platform component |
| |
| Security | 1 | 1 |
| |
| Scalability | NA | vvp is a stand alone tool not a platform component |
| |
| Manageability | NA | vvp is a stand alone tool not a platform component |
| |
| Usability | 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.
...
VVP does not have APIs with other ONAP components.
API Outgoing Dependencies
VVP does not have APIs with other ONAP components.
API Outgoing Dependencies
API this project is delivering to other projects.
...
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 |
|---|---|---|
Name | Description | Version |
| git | repository | |
| jenkins | Ci/CD tool | |
| Postgresql | object database |
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.
The vvp project has been developed as a containerized service for stand alone operation.
This is being integrated for instanciation by the OOM projectDescribe 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.
| Gaps identified | Impact | ||
|---|---|---|---|
| validation scripts for TOSCA formatted VNF Packages | current VVP only supports HEAT templates | To fill out | To fill out |
Known Defects and Issues
Provide a link toward the list of all known project bugs.
...
Fill out the Resources Committed to the Release centralized page.
Release Milestone
Milestone | Deliverable | Date |
|---|---|---|
Milestone |
...
Deliverable | Date | |
|---|---|---|
| M0 | Intent to Participate | June 14, 2018 |
| M1 | Release Plan M1 Checklist | June 28, 2018 |
| M2 | M2 Checklist | July 26, 2018 |
| M3 | M3 Checklist | August 23, 2018 |
| M4 | M4Checklist | September 20, 2018 |
| RC0 | RC0 Checklist | October 11, 2018 |
| RC1 | RC1Checklist | October 25, 2018 |
| RC2 | RC2 Checklist | November 8, 2018 |
| Signoff | Signoff Checklist | November 15, 2018 |
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.
...
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
- ...
...
| title | Note |
|---|
...
- .
Other Information
Vendor Neutral
...