...
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 O'Sullivan, Priyadharshini BJira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key EXTAPI-465 - E2E Network Slicing - EXTAPI-449 - E2E Network Slicing - two Jira opened EXTAPI-449 - E2E Network Slicing: Lifecycle management operations – standard interface OPEN Enhancements for Service activation, deactivation, termination (based on TMF 641) and EXTAPI-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:
- Slides presented covering the NBI requirement for E2E External API Framework: 5GNetworkSlicing_ExtAPI_20200610_v1.0.pptx
Actions/updates:- Briefly discussed reg. the use 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 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:
- Macromode for Guilin, EXTAPI-258 - "Macro" mode OPEN Sanchita Pathak - 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
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
...
- and future mapping to DES API's
- Macromode for Guilin, EXTAPI-258 - "Macro" mode OPEN Sanchita Pathak - 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 server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb 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 | 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 |
|
| ||||||||||
RANK #1 - Must Have |
|
| |||||||||||
RANK #1 - Must Have |
| ||||||||||||
RANK #1 - Must Have |
| ||||||||||||
RANK #1 - Must Have |
| ||||||||||||
RANK #1 - Must Have |
| ||||||||||||
RANK #1 - Must Have |
| ||||||||||||
RANK #1 - Must Have |
| ||||||||||||
REQ-349 - Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage TO DO | RANK #1 - Must Have |
| |||||||||||
RANK #1 - Must Have |
|
1 - TSC PRIORITY 2 Continuity (please indicate where you plan to contribute)
RANK #2 – Continuity |
|
7- TSC PRIORITY 3 PTL GO/NO GO (please indicate where you plan to contribute)
| |||
| |||
| |||
| |||
REQ-360 - Application config should be fully prepared before starting the application container TO DO |
| ||
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 |
| ||
|
Epics
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...