| Table of Contents | ||
|---|---|---|
|
Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Honolulu |
| Project Lifecycle State | IncubationMature |
| Participating Company | China Mobile ,ZTE, Huawei, Nokia, Intel |
...
Describe the problem being solved by this release
1. Improve Instance storage function for supporting test environment auto deploy of NFV Testing Automatic Platform2. Improve platform maturity (TSC Muse have)Jira Legacy
| server | System Jira |
|---|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
| key | VFC-1696 |
3. Remove components that are no longer used or maintained2. Fix the bugs left over from the previous version
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
No new use case support planned for Honolulu release.
Minimum Viable Product
Describe the MVP for this release.
...
Minimum VF-C components supporting above functionalities:
NSLCM/GVNFM/Workflow/Vimproxy/EMS driver/vendor VNFM driver
Functionalities
...
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.
Please see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:vfc
Architecture
High level architecture diagram
...
Please fill out the centralized wiki page: https://wiki.onap.org/display/DW/Guilin+Release+Platform+Maturity Honolulu 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) |
|---|---|---|---|---|
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 | MultiCloud API | ||
DCAE VES collector SB API | API to push vnf fcaps data to VES collector | DCAE API Document | ||
A&AI API | API to store inventory | AAI REST API Documentation | ||
| OOF API | API to chose VIM which is used to deploy VNF | OOF API Document |
API Outgoing Dependencies
...
| 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 descriptionhttps://docs.onap.org/projects/onap-vfc-nfvo-lcm/en/latest/platform/APIs/NSLCM_API/index.html | ||
VNFM Driver API Definition | VNFM Driver component northbound APIs | https://docs.onap.org/projects/onap-vfc-nfvo-lcm/en/latest/platform/APIs/VNFMDriver_API/index.html | ||
| VNF LCM API Definition | provide VNF lifecycle management APIs | https://docs.onap.org/projects/onap-vfc-nfvo-lcm/en/latest/platform/APIs/VNFLCM_API/index.html |
Third Party Products Dependencies
...
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.
For Unit Test, all components are required to maintain 55% codecoverage at the minumum.
https://sonarcloud.io/organizations/onap/projects?search=vfc
Functional test plan
VF-C Honolulu Functional Test Plan
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.
...
Please update any risk on the centralized wiki page - Guilin Honolulu Risks
Resources
Fill out the Resources Committed to the Release centralized page.Please see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:vfc
Release Milestone
The milestones are defined at the Release LevelPlanning: Honolulu and all the supporting project agreed to comply with these dates.
...
Please update the following centralized wiki: Guilin Honolulu 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
- ...
...