DRAFT PROPOSAL FOR COMMENTS
The content of this template is expected to be fill out for M1 Release Planning Milestone.
| Table of Contents | ||
|---|---|---|
|
Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Casablanca |
| Project Lifecycle State | Incubation, |
| Participating Company | Amdocs, AT&T, China Mobile, Huawei, Orange, Tech Mahindra, |
Scope
What is this release trying to address?
- For the Casablanca release, the vvp project adds no new tool 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 packages.
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.
Epics
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=VVP and issuetype in (epic) serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
Stories
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox and issuetype in (story) serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
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.
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 |
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.
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.
Indicate where your project fit within the ONAP Archiecture diagram.
The VNF Validation Program provides a stand alone tool and supporting procedures for validation of VNF Packages ( HEAT templates) .
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
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 |
|---|---|---|
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
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
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 |
Known Defects and Issues
Provide a link toward the list of all known project bugs.
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
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 |
|---|---|---|
| To fill out | To fill out | To fill out |
Resources
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.
It is not expected to have a detailed project plan.
| Date | Project | Deliverable |
|---|---|---|
| To fill out | To fill out | To fill out |
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
- ...
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 Project FOSS.
Charter Compliance
The project team comply with the ONAP Charter.