...
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
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project = SO AND issuetype = Epic AND fixVersion = "Guilin Release" serverId 425b2b0a-557c-3c0c-b515-579789cceedb
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.
...
Key | Summary | Assignee | Tsc Priority | SO Epic(s) / Story(ies) | M1 Scope Clarifications | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
REQ-347 | CCVPN-Transport Slicing for Guilin Release | 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 | ||||||||||||||
REQ-REQ-342 | E2E Network Slicing requirements for Guilin release | 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 | ||||||||||||||
REQ-325 | MDONS Extension in Guilin Release | Xin Miao | 2 |
| Fujitsu Need clarifications on the new scope | ,. We will have a meeting scheduled next week. Resource commitment | Resource commitment for the non-functional requirement |
Functional Requirements :
Requirement | SO | SO Epic(s) / Story(ies) | M1 Scope and clarification | ||||||||||||||||||||||||||||
REQ-339 - Container Network Function Test Platform (CNTP): OVP 2.0 support and Enable Network Service testing TO DO | 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 | ?
Scope and Resource commitment and the non functional requirement need clarifications.
| ||||||||||||||||||||||||||||
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 | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
REQ-323 - Each project will update the vulnerable direct dependencies in their code base To Do | RANK #1 - Must Have |
| contributor |
Wipro | |||||||||||
RANK #1 - Must Have |
| Need to check for each of the POD |
RANK #1 - Must Have |
|
|
|
| OK for SO | ||||
container repository (nexus) must not contain upstream docker images To Do | RANK #1 - Must Have |
|
|
Java 11 upgrade is the pending item at the moment for SO.
|
Huawei Seems OK for SO |
projects must use only approved and verified base images for their containers To Do | 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 so/libs: Nokia (TBC) Orange - Docker part | |||||
RANK #1 - Must Have | NA | |||||
362 - All containers must run as non-root user To Do | RANK #1 - Must Have |
|
| Wrapping the dockers on the deployment scripts (Oom based) OK |
Orange and Huawei.
Contributors : Orange Sylvain Desbureaux , Ericsson Byung-Woo Jun and Huawei Mukesh Paliwal . New pods should be taken care - K8s Adapter, SO-NFVO. |
REQ-361 - |
Continue hardcoded passwords removal To Do | RANK #1 - Must Have |
|
| Certificate and ingress (Oom based) |
Orange and Huawei.
REQ-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. | ||||||
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 |
|
|
| onap/integration-java11:7.0.0 In nexus Contributors : SO - Att (base work), Fujitsu (Xin Miao ) So/libs - Damian Nowak to get back.. |
1 - TSC PRIORITY 2 Continuity (please 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)
REQ-340 - ONAP to support Multi - tenancy To Do |
| Multi Tenancy
|
| ||||||||||||||
| Pattern of the logging to be standardized. Append the log4j with the appender ( on OOM).
|
| ||||||||||||||
| Gating and daily deployment impact... (Deployment scripts)
| |||||||||||||
REQ-364 - Replace NodePorts with ingress controller as a default deployment option To Do |
|
| ||||||||
config should be fully prepared before starting the application container To Do |
| spring boot based application should be ok, will need to re-check with Kryzstof (Oom based)
| ||||||||||||||||||||
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 |
| 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
Jira server ONAP JIRA columns key,summary,type,updated,assignee,priority,status maximumIssues 20 jqlQuery project = SDC SO AND issuetype in (Epic, Story, Task, bug) AND fixVersion = "Guilin Release" serverId 425b2b0a-557c-3c0c-b515-579789cceedb
...
Deliverable Name | Deliverable Description |
---|---|
SO Docker ImagesTo fill out | 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
...
- 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 | ||
| Sept 4, 2020 | Last day to submit Frankfurt code changes to Gerrit | |
| Sept 7, 2020 | Release manager reviews worksheets to assess readiness for M4 milestone, including the following checks:
| |
| Sept 7, 2020 | ||
| Sept 10, 2020 | ||
RC0 | Release Candidate 0 | ||
| Sept 25, 2020 | Last date to submit code fixes for release candidate 0 | |
| Sept 28, 2020 | ||
| Sept 28, 2020 | ||
| Oct 1, 2020 | ||
RC1 | Release Candidate 1 | ||
| Oct 9, 2020 | Last date to submit code fixes for Frankfurt release candidate 1 | |
| Oct 12, 2020 | ||
| Oct 12, 2020 | ||
| Oct 15, 2020 | ||
RC2 | Release Candidate 2 | ||
| Oct 23, 2020 | Last date to submit code fixes for final Frankfurt release (RC2) | |
| Oct 26, 2020 | ||
| Oct 26, 2020 | ||
| Oct 29, 2020 | ||
Release Sign-Off | Final TSC Sign-Off | May 7, 2020 | Frankfurt Release Sign-Off |
API Incoming Dependencies
...
Base docker images with approved set of License to be used to construct SDC base SO base images.
Testing and Integration Plans
...
- validate uses cases and pairwise testing of SDC with SO with other components
- enhance CSIT to include more tests
...
Please update any risk on the centralized wiki page - Frankfurt Risks – To be updated when avail
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...