Versions Compared

Old Version 5

changes.mady.by.user Adrian OSullivan

Saved on

compared with

New Version Current

changes.mady.by.user Adrian OSullivan

Saved on

Key

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


Table of Contents
outlinetrue

...

Scope

What is this release trying to address

  • E2E Network Slicing - two Jira opened  Image RemovedEXTAPI-449 - E2E Network Slicing: Lifecycle management operations – standard interface OPEN  Enhancements for Service activation, deactivation, termination (based on TMF 641) and  Image RemovedEXTAPI-450 - E2E Network Slicing: KPI monitoring OPEN  KPI Monitoring e.g., based on TMF 628. Discussion on the requirements for Guilin with Priyadharshini B Swaminathan Seetharaman Guobiao Mo
    • Slides presented covering the NBI requirement for E2E External API Framework: 5GNetworkSlicing_ExtAPI_20200610_v1.0.pptx
    • Actions/updates:
      • Briefly discussed reg. the use 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
      • Discussed with @Jack Pugaczewski reg. use of (modernized) TMF 628 for "On Demand" PM collection.
      • Share DES APIs (that would have been invoked from UUI), as well as the typical response from DES for a KPI monitoring request – can be the draft version. Guobiao Mo LUKAI
      • Get the draft updated TMF 628 swagger from Jack. Adrian OSullivan
      • Try to map the request from UUI to TMF 628 onDemandCollection Priyadharshini B Adrian OSullivan Swaminathan Seetharaman
      • If the mapping looks reasonable, make a simple start w.r.to implementation in Guilin release – this will have impact in UUI and ExTAPI. LIN MENG Swaminathan Seetharaman to confirm resources.
      • Update the ppt with relevant details. Priyadharshini B/ Swaminathan Seetharaman/Guobiao Mo
      • Last week Items:

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 

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
outlinetrue

Overview

Project NameEnter the name of the project
Target Release NameGuilin Release
Project Lifecycle StateIncubation.( Refer to ONAP Charter, section 3.3 Project Lifecycle for further information)
Participating Company AT&T, CenturyLink, China Mobile, Huawei, Orange, Verizon, Amdocs, Ciena, Wipro, HCL, Tech Mahindra, Netcracker, MEF, TMF

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


    ScopePriorityCommitter LeadResources CommittedEpic Dependencies 
    TSC Must have
    		high
    Adrian OSullivan
    Adrian O'Sullivan, Priyadharshini B

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyEXTAPI-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


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
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyEXTAPI-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

EXTAPI Epic(s) and/or EXTAPI 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

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyEXTAPI-446

  • Contributors : Huawei
Image AddedREQ-366 - Containers must crash properly when a failure occurs TO DO
RANK #1 - Must Have

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyEXTAPI-466

  • Contributors : Huawei, Wipro, Orange
Image AddedREQ-365 - Containers must have no more than one main process TO DO
RANK #1 - Must Have



KeySummaryTUpdatedAssigneePStatus

No issues found  Refresh




  • Contributors : Huawei
  • already DONE in previous release
Image AddedREQ-380 - ONAP container repository (nexus) must not contain upstream docker images TO DO
RANK #1 - Must Have



KeySummaryTUpdatedAssigneePStatus

No issues found  Refresh




  • Contributors : Huawei
  • already DONE in previous release
Image AddedREQ-379 - ONAP projects must use only approved and verified base images for their containers TO DO
RANK #1 - Must Have



KeySummaryTUpdatedAssigneePStatus

No issues found  Refresh




  • Contributors : Huawei
  • already DONE in previous release - use of standard base java 11 image for nbi
Image AddedREQ-373 - ONAP must complete update of the Python language (from 2.7 -> 3.8) TO DO
RANK #1 - Must Have



KeySummaryTUpdatedAssigneePStatus

No issues found  Refresh




  • N/A for EXTAPI (EXTAPI doesn't use python)
Image AddedREQ-362 - All containers must run as non-root user TO DO
RANK #1 - Must Have



KeySummaryTUpdatedAssigneePStatus

No issues found  Refresh




  • Contributors : Huawei
  • already DONE in previous release
Image AddedREQ-361 - Continue hardcoded passwords removal TO DO
RANK #1 - Must Have



KeySummaryTUpdatedAssigneePStatus

No issues found  Refresh




  • Contributors : Huawei
  • already DONE in previous release
Image AddedREQ-349 - Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage TO DO
RANK #1 - Must Have



KeySummaryTUpdatedAssigneePStatus

No issues found  Refresh




  • Contributors : All (currently at 65%)
  • Will plan to keep 65%+
Image AddedREQ-351 - ONAP must complete update of the java language (from v8 -> v11) TO DO
RANK #1 - Must Have



KeySummaryTUpdatedAssigneePStatus

No issues found  Refresh




  • Contributors : Huawei
  • 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 



KeySummaryTUpdatedAssigneePStatus

No issues found  Refresh




  • Contributors : Huawei
  • 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



KeySummaryTUpdatedAssigneePStatus

No issues found  Refresh




  • Contributors : ?
Image AddedREQ-374 - ONAP shall use STDOUT for logs collection TO DO



KeySummaryTUpdatedAssigneePStatus

No issues found  Refresh




  • Contributors : ?
Image AddedREQ-369 - Replace nfs share with storage class as a default deployment option TO DO



KeySummaryTUpdatedAssigneePStatus

No issues found  Refresh




  • Contributors : ?
Image AddedREQ-364 - Replace NodePorts with ingress controller as a default deployment option TO DO



KeySummaryTUpdatedAssigneePStatus

No issues found  Refresh




  • Contributors : ?
Image AddedREQ-360 - Application config should be fully prepared before starting the application container TO DO



KeySummaryTUpdatedAssigneePStatus

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



KeySummaryTUpdatedAssigneePStatus

No issues found  Refresh




  • Contributors : ?
Image AddedREQ-359 - Container rootfs must be mounted readOnly TO DO



KeySummaryTUpdatedAssigneePStatus

No issues found  Refresh




  • Contributors : ?


Epics

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = EXTAPI AND fixVersion = "Guilin Release" AND type = Epic
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

...

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.

API Name

API Description

API Definition Date

API Delivery date

API Definition link (i.e.swagger)

SDC: Catalog APIExposes Service CatalogTBDTBDhttps://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/SDC+API
SO: Service Instantiation APIRequests for Service InstantiationTBDTBD
AAI: Service Inventory APIQuery for Service InventoryTBDTBD
DMaaP: Events APIQuery for AAI_EVENTS and SDC Distribution EventsTBDTBD

...

Risk identified

Mitigation Plan

Contingency Plan

TBDTBDTBD

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.