Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Support SDC direct interface
  • Support ETSI package APIs and storage for ETSI packages in runtime
  • Update version of Python as well as Django and djangorestframework
  • TSC must have items 
    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyMODELING-386
    Improve platform maturity (TSC must have items)

 Modelspec for modleing subcommittee:

  • Create UML models for new model proposals or enhancements in Guilin release
  • Document approved models as model specs

Requirements

Describe the use case this release is targeted for (better if reference to customer requirements).

etsicatalog will contribute to the following functional requirements: 

Functional requirements:

TSC must have items:

Image AddedREQ-373 - ONAP must complete update of the Python language (from 2.7 -> 3.8) TO DO

Image AddedREQ-380 - ONAP container repository (nexus) must not contain upstream docker images TO DO

Image AddedREQ-379 - ONAP projects must use only approved and verified base images for their containers TO DO

Image AddedREQ-370 - Components may use HTTP as server and client TO DO

Image AddedREQ-366 - Containers must crash properly when a failure occurs TO DO

Image AddedREQ-365 - Containers must have no more than one main process TO DO

Image AddedREQ-362 - All containers must run as non-root user TO DO

Image AddedREQ-361 - Continue hardcoded passwords removal TO DO

Image AddedREQ-323 - Each project will update the vulnerable direct dependencies in their code base TO DO

Image AddedREQ-349 - Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage TO DO

Requirement with risk:

Image AddedREQ-323 - Each project will update the vulnerable direct dependencies in their code base TO DO

Image AddedREQ-363 - ONAP components should be able to run without AAF and MSB TO DO

Image AddedREQ-349 - Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage TO DO


modelspec will address the following modeling requirements:


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.

...

Gaps identifiedImpact
To fill outTo 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
    • ...

...