| Table of Contents | ||
|---|---|---|
|
Overview
...
2. Improve platform maturity (TSC Muse have)
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
3. Remove components that are no longer used or maintained
...
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://wiki.onap.org/display/DW/Guilin+Release+Platform+Maturity Honolulu Release Platform Maturity
API Incoming Dependencies
...
Please update any risk on the centralized wiki page - Guilin Honolulu Risks
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...
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
- ...
...