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
...
Describe the problem being solved by this release
...
1. Improve Instance storage function for supporting test environment auto deploy of NFV Testing Automatic Platform
2. Improve platform maturity (TSC Muse have)
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
3. Remove components that are no longer used or maintained
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
Use Case: Residential Broadband vCPE (Approved)
Requirements
Support for Test Environment Auto Deploy（NFV Testing Automatic Platform）
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Non-functional requirements (TSC must have)
REQ-373 - ONAP must complete update of the Python language (from 2.7 -> 3.8) TO DO
REQ-380 - ONAP container repository (nexus) must not contain upstream docker images TO DO
REQ-379 - ONAP projects must use only approved and verified base images for their containers TO DO
REQ-374 - ONAP shall use STDOUT for logs collection TO DO
REQ-370 - Components may use HTTP as server and client TO DO
REQ-366 - Containers must crash properly when a failure occurs TO DO
REQ-365 - Containers must have no more than one main process TO DO
REQ-362 - All containers must run as non-root user TO DO
REQ-361 - Continue hardcoded passwords removal TO DO
REQ-349 - Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage TO DO
Requirement with risk:
REQ-323 - Each project will update the vulnerable direct dependencies in their code base TO DO
REQ-363 - ONAP components should be able to run without AAF and MSB TO DO
REQ-351 - ONAP must complete update of the java language (from v8 -> v11) TO DO
Minimum Viable Product
Describe the MVP for this release.
VF-C will include the necessary sub-components supporting the primary objectives: meeting platform maturity goals and supporting the use cases.
LCM(instantiate/terminate/heal/scaling) for NS and Vendor VNFs
FCAPS for vendor VNFs
LCM(instantiate/terminate) for open source VNFs
Minimum VF-C components supporting above functionalities:
NSLCM/GVNFM/Workflow/Vimproxy/EMS driver/vendor VNFM driver
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.
...
| Deliverable Name | Deliverable Description | To fill out | To fill out|
|---|---|---|---|
| Source Code | Source code for all VF-C components | ||
| Maven Artifacts | Maven Artifacts for all VF-C components | ||
| Docker Containers | Docker container associated with VF-C components | ||
| Documentation | VF-C detailed documentation |
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.
...
Indicate where your project fit within the ONAP Architecture 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.
Platform Maturity
Please fill out the centralized wiki page: Frankfurt Release Platform https://lf-onap.atlassian.net/wiki/display/DW/Guilin+Release+Platform+Maturity
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 Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description
|---|---|---|---|---|---|---|---|---|
Parser API(Modeling) | API for parsering TOSCA file | Etsicatalog API Document | ||||||
Micro-services bus API | API for registration and use of micro-services bus | Microservice Bus API Documentation | ||||||
Multi-vim API | API to allocate resource to VIM | |||||||
DCAE VES collector SB API | API to push vnf fcaps data to VES collector | |||||||
A&AI API | API to store inventory | AAI REST API Documentation | ||||||
| OOF API | API to chose VIM which is used to deploy VNF |
API Outgoing Dependencies
API this project is delivering to other projects.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|
NSLCM API Definition | Network services lifecycle management APIs | Link toward the detailed API description | ||
VNFM Driver API Definition | VNFM Driver component northbound APIs | |||
| VNF LCM API Definition | provide VNF lifecycle management APIs |
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|
|---|---|---|---|---|---|
| Django | https://www.djangoproject.com/ | 2.1.10 | |||
| djangorestframework | https://www.django-rest-framework.org/ | 3.10.3 |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
...
| Gaps identified | Impact |
|---|---|
| To fill out | To fill out |
Known Defects and Issues
Please refer to Frankfurt Defect StatusN/A
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).
Please update any risk on the centralized wiki page - Frankfurt Guilin Risks
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...
Please update the following centralized wiki: Frankfurt Guilin Documentation
That includes
- Team contributions to the specific document related to he project (Config guide, installation guide...).
- 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
- ...
...