Service Orchestrator Guilin Release M4
- Seshu Kumar Mudiganti
- Byung-Woo Jun
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 |
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 | M4 |
|---|---|---|---|---|---|---|
Henry Yu | 2 | Huawei, CMCC, Wipro Scope and Resource commitment for the non-functional requirement is needed. NFR: 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 | Coding is targeted this week. ETA: 4th Sept | |||
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 | The change is still pending. ETA : 4th Sept |
Functional Requirements :
Requirement | SO | SO Epic(s) / Story(ies) | M1 Scope and clarification | M4 Status |
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 | There is reduced scope is suggested on the vNF part, PNF is in scope.
| |
x | Nokia SO-2785: Migrate PNF PNP workflow to Building Blocks (Guilin enhancements)Closed Scope and Resource commitment and the non functional requirement need clarifications. SO-2046 - TBC @Lukasz Muszkieta @damian.nowak | On Going config - Deploy is open (May be for Honolulu). config - Assign is in progress. ETA : 10-09 (Yet to be confirmed) | ||
x | Lumina, Huawei, Att The requirement is presented in the CNF task force meeting and is accepted. Non Functional requirement, | In progress, coding is targeted by Monday. | ||
x | Huawei, (Nokia - initial support in the design) The requirement is presented in the SO weekly meeting and is accepted. Non-Functional Requirement. | We have encountered issue with the Java 11 on the Camunda and Tomcat, checking it further.\\ Deferred for H release. | ||
x | Ericsson, Verizon The requirement is presented in the ETSI taskforce meeting and is accepted. Non-Functional Requirement: | There will be reduced scope. The confirmed scope for Guilin is the following:
The following features hav been postponed to the next release
MSB based cert issues needs to be checked. Trsutstore needs to be updated. |
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 | M4 |
|---|---|---|---|---|
REQ-323 - Each project will update the vulnerable direct dependencies in their code base To Do | RANK #1 - Must Have | contributor @Reshmasree c Wipro | Delivered Security Subcommitte feedback is awaited. | |
REQ-366 - Containers must crash properly when a failure occurs To Do | RANK #1 - Must Have | SO-3037: Containers must crash properly when a failure occurs Open | Need to check for each of the POD SO seems to be ok - TBD on event basis (OOM and SO) contributor @Seshu Kumar Mudiganti | Need to clarify with Integration team. |
REQ-365 - Containers must have no more than one main process To Do | RANK #1 - Must Have | SO-3039: Containers must crash properly when a failure occurs Closed | OK for SO | M4 Ok |
REQ-380 - ONAP container repository (nexus) must not contain upstream docker images To Do | RANK #1 - Must Have | SO-3040: ONAP container repository (nexus) must not contain upstream docker imagesClosed | Huawei Seems OK for SO | M4 OK |
REQ-379 - ONAP projects must use only approved and verified base images for their containers To Do | RANK #1 - Must Have | SO-3041: ONAP projects must use only approved and verified base images for their containersOpen | 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 | In progress The changes are awaited on the oom. 1.7,1 image are released. Has issues on the gating side. |
REQ-373 - ONAP must complete update of the Python language (from 2.7 -> 3.8) To Do | RANK #1 - Must Have | NA | NA | |
REQ-362 - All containers must run as non-root user To Do | RANK #1 - Must Have | M4: OK 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. |
| |
REQ-361 - Continue hardcoded passwords removal To Do | 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. | Secrets based implementation. | |
REQ-349 - Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage To Do | RANK #1 - Must Have | OK 63% and 66% Tech Mahindra to support on need basis. @Milind Jalwadi (Unlicensed) | OK | |
REQ-351 - ONAP must complete update of the java language (from v8 -> v11) To Do | RANK #1 - Must Have | onap/integration-java11:7.0.0 In nexus Contributors : SO - huawei So/libs - @damian.nowak to get back.. | In progress The changes are awaited on the oom gating. |
1 - TSC PRIORITY 2 Continuity (please indicate where you plan to contribute)
REQ-358 - No root (superuser) access to database from application container To Do | RANK #2 – Continuity | SO-3044: No root (superuser) access to database from application containerOpen | This should be OK, Need to check it further with Security (Oom based)
| OK |
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
| OK The scope is reduced with AAI, no SDC is involved in G release. | |
REQ-374 - ONAP shall use STDOUT for logs collection To Do | Pattern of the logging to be standardized. Append the log4j with the appender ( on OOM).
SO-3077: ONAP shall use STDOUT for logs collection - REQ-374Closed To check the status on the latest oom pods of the SO. | Changes are done and merged in the spring. | |
REQ-369 - Replace nfs share with storage class as a default deployment option To Do | Gating and daily deployment impact... (Deployment scripts)
| NA | |
REQ-364 - Replace NodePorts with ingress controller as a default deployment option To Do | 30227 and 20225 should be (Oom based)
SO-3078: REQ-364 Replace NodePorts with ingress controller as a default deployment optionSubmitted | In Progress. Will be handed as part of the REQ-361. | |
REQ-360 - Application 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
| OK https part of the badge will be handled in REQ-361. | |
REQ-359 - Container rootfs must be mounted readOnly To Do | Springboot startup should take care of this, need to check with Kryzstof. (Oom based)
|