Service Orchestrator Guilin Release M1
The content of this template is expected to be fill out for M1 Release Planning Milestone.
Overview
Project Name | Enter the name of the project |
|---|---|
Target Release Name | Guilin |
Project Lifecycle State | Incubation |
Participating Company | AT&T, Amdocs, Bell Canada, CMCC, DT, Ericsson, Fujitsu, Huawei, Intel, Lumina Networks, Nokia, Orange, Samsung, Tech Mahindra, Verizon |
Scope
What is this release trying to address?
Support Guilin use cases, Features and Non Functional requirements.
Requirements
Explained in detail in the below sections.
Minimum Viable Product
Deliver all the need dockers and DB needed to support SO core functionality and the needed scripts for deploying it in OOM.
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.
Requirements Epics for Guilin, impacting SO
Use Cases :
Greetings, As per the new process set in place, we need to have the TSC must have requirements also to be completed for us to qualify for the release.
Hence, Please confirm the contributions in SO.
1. the resource commitment for this requirement for Guilin release
2. the non-functional requirement that would be contributed by them.
Thanks in advance.
Key | Summary | Assignee | Tsc Priority | SO Epic(s) / Story(ies) | M1 Scope Clarifications |
|---|---|---|---|---|---|
Henry Yu | 2 | Huawei, CMCC, Wipro Scope and Resource commitment for the non-functional requirement is needed. ttps://jira.onap.org/browse/REQ-323 - Wipro | |||
Swaminathan S | 3 | CMCC, Wipro, Huawei Requirement is presented in the 5G slicing weekly meeting and is accepted. Need resource commitment for the non-functional requirement. ttps://jira.onap.org/browse/REQ-358 - Wipro 374 - Tech M 349 - Tech M | |||
Xin Miao | 2 | Fujitsu Need clarifications on the new scope. We will have a meeting scheduled next week. Resource commitment for the non-functional requirement |
Functional Requirements :
Requirement | SO | SO Epic(s) / Story(ies) | M1 Scope and clarification |
x | Huawei Requirement is presented in the CNF task force and is accepted Stories to be updated for the requirement. Non functional requirement Identified: | ||
REQ-324 - Support xNF Software Upgrade in association to schema updates IN PROGRESS | x | Ericsson, Orange This is already reviewed in the SO weekly and is accepted. commitment on the Non functional requirement is required. REQ-364 - Orange | |
x | Nokia https://lf-onap.atlassian.net/browse/SO-2785 Scope and Resource commitment and the non functional requirement need clarifications. SO-2046 - TBC @Lukasz Muszkieta @damian.nowak | ||
x | Lumina, Huawei, Att The requirement is presented in the CNF task force meeting and is accepted. Non Functional requirement, | ||
x | Huawei, (Nokia - initial support in the design) The requirement is presented in the SO weekly meeting and is accepted. Non-Functional Requirement. | ||
x | Ericsson, Verizon The requirement is presented in the ETSI taskforce meeting and is accepted. Non-Functional Requirement: |
18 Non functionals :
10 - TSC MUST HAVE (please indicate where you plan to contribute)
Requirement Epic | TSC Priority | SO Epic(s) / Story(ies) | Committed Contributors |
|---|---|---|---|
| RANK #1 - Must Have | contributor @Reshmasree c Wipro | |
| RANK #1 - Must Have | Need to check for each of the POD SO seems to be ok - TBD on event basis (OOM and SO) contributor @Seshu Kumar Mudiganti | |
| RANK #1 - Must Have | OK for SO | |
| RANK #1 - Must Have | Huawei Seems OK for SO | |
| RANK #1 - Must Have | Java 11 upgrade is the pending item at the moment for SO. onap/integration-java11:7.0.0 image In nexus to be used. License compliance - to be sure all the containers Contributors : Nokia : SO : Java part (REQ-351) TBC, Fujitsu. @Xin Miao (Unlicensed) so/libs: Nokia (TBC) Orange - Docker part | |
| RANK #1 - Must Have | NA | |
| RANK #1 - Must Have | Wrapping the dockers on the deployment scripts (Oom based) OK Contributors : Orange @Sylvain Desbureaux , Ericsson @Byung-Woo Jun and Huawei @Mukesh Paliwal . New pods should be taken care - K8s Adapter, SO-NFVO. | |
| RANK #1 - Must Have | Certificate and ingress (Oom based) passwords and certificates to be cleaned in the oom. Certificate : Https solution will be done through Ingress. (REQ-364) - Orange @Sylvain Desbureaux Password : Att (30225 @Ramesh Parthasarathy , Ericsson (30227 @Byung-Woo Jun Orange, Att, Ericsson and Huawei. | |
| RANK #1 - Must Have | OK 63% and 66% Tech Mahindra to support on need basis. @Milind Jalwadi (Unlicensed) | |
| RANK #1 - Must Have | onap/integration-java11:7.0.0 In nexus Contributors : SO - Att (base work), Fujitsu (@Xin Miao (Unlicensed)) So/libs - @damian.nowak to get back.. |
1 - TSC PRIORITY 2 Continuity (please indicate where you plan to contribute)
| RANK #2 – Continuity | This should be OK, Need to check it further with Security (Oom based)
|
7- TSC PRIORITY 3 PTL GO/NO GO (please indicate where you plan to contribute)
| Multi Tenancy
| |
| Pattern of the logging to be standardized. Append the log4j with the appender ( on OOM).
| |
| Gating and daily deployment impact... (Deployment scripts)
| |
| 30227 and 20225 should be (Oom based)
| |
| spring boot based application should be ok, will need to re-check with Kryzstof (Oom based)
| |
| CII badging improvement
| |
| Springboot startup should take care of this, need to check with Kryzstof. (Oom based)
|
SO Backlog Overview - Not committed for the release (except for stories that have been captured in the above table), best effort
Longer term roadmap
SO aims to highest level of orchestration which is model driven and generic enough to both traditional and Cloud Native scenarios alike.
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this release.
Deliverable Name | Deliverable Description |
|---|---|
SO Docker Images | Docker Images, details can be found below |
SO libs | libs |
Sub-Components
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall 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.
onap/so/api-handler-infra
onap/so/bpmn-infra
onap/so/catalog-db-adapter
onap/so/openstack-adapter
onap/so/request-db-adapter
onap/so/sdc-controller
onap/so/sdnc-adapter
onap/so/so-monitoring
onap/so/vfc-adapter
onap/so/sol003-adapter
onap/so/sol02-adapter
onap/so/nssmf-adapter
onap/so/appc-orchestrator
onap/so/k8s-adapter
Architecture
High level architecture diagram
Platform Maturity
Please fill out the centralized wiki page: Guilin Release Platform Maturity
Team Internal Milestone (Tentative)
Milestone | Description | Date | Comments |
|---|---|---|---|
M2/M3 | Functionality Freeze / API Freeze | ||
| July 3, 2020 | Last day to submit Guilin swagger / Yang changes to Gerrit | |
| Aug 3, 2020 | Release manager reviews worksheets to assess readiness for M2/M3 milestone | |
| Aug 6, 2020 | ||
M4 | Code Freeze | ||
|