| Table of Contents | ||
|---|---|---|
|
Overview
...
2. Improve platform maturity (TSC Muse have)
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
|
3. Remove components that are no longer used or maintained
4. Support use cases identified by ONAP and integration: vCPE
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.
...
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 fill out the centralized wiki page: https://wikilf-onap.onapatlassian.orgnet/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.
...
| 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 - Guilin Risks
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...