...

Table of Contents
outline true

Overview

...

• Support TSC must have ONAP requirements Guilin Release Requirements 
• implements as much TSC must feature as possible
  

  
  

  Scope	Priority	Committer Lead	Resources Committed	Epic	Dependencies
  TSC Must have	high	Adrian OSullivan	Adrian O'Sullivan, Priyadharshini B	Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key EXTAPI-465

  
  

• E2E Network Slicing -   EXTAPI-449 - E2E Network Slicing: Lifecycle management operations – standard interface OPEN  Enhancements for Service activation, deactivation, termination (based on TMF 641) 
  • Slides presented covering the NBI requirement for E2E External API Framework: 5GNetworkSlicing_ExtAPI_20200610_v1.0.pptx
    
    • Implementation of TMF 641 APIs for service activation/deactivation/termination. We will go ahead with the proposed approach based on last week's discussion to use ServiceState of Service object as part of EXTAPI-449
    • Specification work on (modernized) TMF 628 for "On Demand" PM collection and future mapping to DES API's

• Macromode for Guilin,  EXTAPI-258 - "Macro" mode OPEN   Former user (Deleted) - Support for when SDC instantiationType = macro

...

• Slides presented covering the NBI requirement for E2E External API Framework: 5GNetworkSlicing_ExtAPI_20200610_v1.0.pptx
• Only Specification aspects of the mapping to be covered during Guilin Release, with implementation of new API tentatively planned for Honolulu Release   

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key EXTAPI-450

   

...

Contributors : AT&T

Align all containers to Database, Java, Python, Docker, Kubernetes, and Image Versions

Requirement Epic	TSC Priority	EXTAPI Epic(s) and/or EXTAPI Story(ies)	Committed Contributors
REQ-323 - Each project will update the vulnerable direct dependencies in their code base TO DO	RANK #1 - Must Have	Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key EXTAPI-446	Contributors : Huawei
REQ-366 - Containers must crash properly when a failure occurs TO DO	RANK #1 - Must Have	Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key EXTAPI-466	Contributors : Huawei, Wipro, Orange
REQ-365 - Containers must have no more than one main process TO DO	RANK #1 - Must Have	Key Summary T Updated Assignee P Status No issues found  Refresh	Contributors : Huawei already DONE in previous release
REQ-380 - ONAP container repository (nexus) must not contain upstream docker images TO DO	RANK #1 - Must Have	Key Summary T Updated Assignee P Status No issues found  Refresh	Contributors : Huawei already DONE in previous release
REQ-379 - ONAP projects must use only approved and verified base images for their containers TO DO	RANK #1 - Must Have	Key Summary T Updated Assignee P Status CLAMP-883 CLAMP containers must use only approved base image Image Removed Jun 26, 2020 Gervais-Martial Ngueko Image Removed OPEN 1 issueNo issues found  Refresh	Contributors : AT&TAlign all containers to Database, Java, Python, Docker, Kubernetes, and Image VersionsHuawei already DONE in previous release - use of standard base java 11 image for nbi
REQ-373 - ONAP must complete update of the Python language (from 2.7 -> 3.8) TO DO	RANK #1 - Must Have	Key Summary T Updated Assignee P Status No issues found  Refresh	N/A for CLAMP EXTAPI (CLAMP EXTAPI doesn't use python)
REQ-362 - All containers must run as non-root user TO DO	RANK #1 - Must Have	Key Summary T Updated Assignee P Status No issues found  Refresh	Contributors : AT&THuawei already DONE in previous release
REQ-361 - Continue hardcoded passwords removal TO DO	RANK #1 - Must Have	Key Summary T Updated Assignee P Status CLAMP-884 CLAMP continue removal of hardcoded pwd Image Removed Jun 26, 2020 Gervais-Martial Ngueko Image Removed OPEN 1 issueNo issues found  Refresh	Contributors : AT&TRemove certificates from containersHuawei already DONE in previous release
REQ-349 - Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage TO DO	RANK #1 - Must Have	Key Summary T Updated Assignee P Status CLAMP-844 Improve test coverage Image Removed Jun 26, 2020 Xue Gao Image Removed SUBMITTED 1 issueNo issues found  Refresh	Contributors : All (currently at 73%65%) Will plan to keep 65%+
REQ-351 - ONAP must complete update of the java language (from v8 -> v11) TO DO	RANK #1 - Must Have	Key Summary T Updated Assignee P Status No issues found  Refresh	Contributors : AT&THuawei already DONE in previous release

...

REQ-358 - No root (superuser) access to database from application container TO DO

RANK #2 – Continuity

Key Summary T Updated Assignee P Status No issues found  Refresh

Contributors : AT&THuawei already DONE in previous release

...

REQ-340 - ONAP to support Multi - tenancy TO DO		Key Summary T Updated Assignee P Status No issues found  Refresh	Contributors : ?
REQ-374 - ONAP shall use STDOUT for logs collection TO DO		Key Summary T Updated Assignee P Status No issues found  Refresh	Contributors : ?
REQ-369 - Replace nfs share with storage class as a default deployment option TO DO		Key Summary T Updated Assignee P Status No issues found  Refresh	Contributors : ?
REQ-364 - Replace NodePorts with ingress controller as a default deployment option TO DO		Key Summary T Updated Assignee P Status No issues found  Refresh	Contributors : ?
REQ-360 - Application config should be fully prepared before starting the application container TO DO		Key Summary T Updated Assignee P Status No issues found  Refresh	Contributors : ?
REQ-350 - Each ONAP project shall improve its CII Badging score by improving input validation and documenting it in their CII Badging site. TO DO		Key Summary T Updated Assignee P Status No issues found  Refresh	Contributors : ?
REQ-359 - Container rootfs must be mounted readOnly TO DO		Key Summary T Updated Assignee P Status No issues found  Refresh	Contributors : ?

...

Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.

...

Platform Maturity

Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.

...

List the API this release is expecting from other releases.
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.

...

Resources

Fill out the Resources Committed to the Release centralized page.

Release Milestone

The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.

...

Each project must edit its project table available at Project FOSS.

Charter Compliance

The project team comply with the ONAP Charter.