...

Scope

What is this release trying to address

...

...

...

...

• 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,  Image RemovedEXTAPI-258 - "Macro" mode OPEN   Former user (Deleted) - Support for when SDC instantiationType = macro

Use Cases

The existing use cases are still going to be supported ( BBS, CCVPN ) in the Guilin Release

5G E2E Network Slicing Use case have plans to use External API Service Order APIs to Create, Delete and modify ( activate / deactivate) Communication Services. There is minor changes to reuse the existing Service Order APIs to activate and deactivate Service Instances via ServiceState. 

The major impact is for the catering Performance Management and the possible inclusion of a subset of the TMF 628 API. See 

• 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

   

Platform Maturity

 Platform Maturity (i.e., S3P items)  Guilin Release Platform Maturity 

Minimum Viable Product

• Documentation of User Stories; Use Cases and Interactions (e.g., swagger ); Data Models (e.g., JSON); Interface Profiles and Functional Definition; 
• ONAP Component Mapping and Functional Analysis; 
• Code contribution for External API Framework functionality.

Functionalities

List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.

Table of Contents
outline true

Overview

Scope

What is this release trying to address

• 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 -   Image AddedEXTAPI-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,  Image AddedEXTAPI-258 - "Macro" mode OPEN   Former user (Deleted) - Support for when SDC instantiationType = macro

Use Cases

The existing use cases are still going to be supported ( BBS, CCVPN ) in the Guilin Release

5G E2E Network Slicing Use case have plans to use External API Service Order APIs to Create, Delete and modify ( activate / deactivate) Communication Services. There is minor changes to reuse the existing Service Order APIs to activate and deactivate Service Instances via ServiceState. 

The major impact is for the catering Performance Management and the possible inclusion of a subset of the TMF 628 API. See 

• 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

   

Platform Maturity

 Platform Maturity (i.e., S3P items)  Guilin Release Platform Maturity 

Minimum Viable Product

• Documentation of User Stories; Use Cases and Interactions (e.g., swagger ); Data Models (e.g., JSON); Interface Profiles and Functional Definition; 
• ONAP Component Mapping and Functional Analysis; 
• Code contribution for External API Framework functionality.

Functionalities

List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.

18 Non functionals :

10 - TSC MUST HAVE (please indicate where you plan to contribute)

Requirement Epic	TSC Priority	SDC Epic(s) and/or SDC Story(ies)	Committed Contributors
Image AddedREQ-323 - Each project will update the vulnerable direct dependencies in their code base TO DO	RANK #1 - Must Have	Key Summary T Updated Assignee P Status https://jira.onap.org/projects/EXTAPI/issues/EXTAPI-446 Upgrade Vulnerable Direct Dependencies Image Added Jun 26, 2020 Gervais-Martial Ngueko Image Added OPEN 1 issue  Refresh	Contributors : Huawei
Image AddedREQ-366 - Containers must crash properly when a failure occurs TO DO	RANK #1 - Must Have	Key Summary T Updated Assignee P Status CLAMP-881 CLAMP containers must crash properly when a failure occurs Image Added Jun 26, 2020 Gervais-Martial Ngueko Image Added OPEN 1 issue  Refresh	Contributors : AT&T
Image AddedREQ-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 : AT&T already DONE in previous release
Image AddedREQ-380 - ONAP container repository (nexus) must not contain upstream docker images TO DO	RANK #1 - Must Have	Key Summary T Updated Assignee P Status CLAMP-882 CLAMP containers in nexus muist not contain upstream docker images Image Added Jun 26, 2020 Gervais-Martial Ngueko Image Added OPEN CLAMP-855 download mariadb-galera image from original source and not from nexus3 Image Added Jul 02, 2020 Gervais-Martial Ngueko Image Added OPEN 2 issues  Refresh	Contributors : AT&T Align all containers to Database, Java, Python, Docker, Kubernetes, and Image Versions
Image AddedREQ-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 Added Jun 26, 2020 Gervais-Martial Ngueko Image Added OPEN 1 issue  Refresh	Contributors : AT&T Align all containers to Database, Java, Python, Docker, Kubernetes, and Image Versions
Image AddedREQ-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 (CLAMP doesn't use python)
Image AddedREQ-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&T already DONE in previous release
Image AddedREQ-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 Added Jun 26, 2020 Gervais-Martial Ngueko Image Added OPEN 1 issue  Refresh	Contributors : AT&T Remove certificates from containers
Image AddedREQ-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 Added Jun 26, 2020 Xue Gao Image Added SUBMITTED 1 issue  Refresh	Contributors : All (currently at 73%)
Image AddedREQ-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&T already DONE in previous release

1 - TSC PRIORITY 2 Continuity (please indicate where you plan to contribute)

Image AddedREQ-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&T already DONE in previous release

7- TSC PRIORITY 3 PTL GO/NO GO (please indicate where you plan to contribute)

Image AddedREQ-340 - ONAP to support Multi - tenancy TO DO		Key Summary T Updated Assignee P Status No issues found  Refresh	Contributors : ?
Image AddedREQ-374 - ONAP shall use STDOUT for logs collection TO DO		Key Summary T Updated Assignee P Status No issues found  Refresh	Contributors : ?
Image AddedREQ-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 : ?
Image AddedREQ-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 : ?
Image AddedREQ-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 : ?
Image AddedREQ-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 : ?
Image AddedREQ-359 - Container rootfs must be mounted readOnly TO DO		Key Summary T Updated Assignee P Status No issues found  Refresh	Contributors : ?

Epics

...