...
Requirement | SO | SO Epic(s) / Story(ies) | M1 Scope and clarification | M4 Status | ||||||||||||||||||||||||||||
| 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 | There is reduced scope is suggested on the vNF part, PNF is in scope.
| ||||||||||||||||||||||||||||
| x |
| Nokia
Scope and Resource commitment and the non functional requirement need clarifications.
| 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 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| RANK #1 - Must Have |
| contributor Wipro | Delivered Security Subcommitte feedback is awaited. | ||||||||||
| 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 | Need to clarify with Integration team. | |||||||||||
| RANK #1 - Must Have |
| OK for SO | M4 Ok | |||||||||||
| RANK #1 - Must Have |
| Huawei Seems OK for SO | M4 OK | |||||||||||
| 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 | In progress The changes are awaited on the oom. 1.7,1 image are released. Has issues on the gating side. | |||||||||||
| RANK #1 - Must Have | NA | NA | ||||||||||||
| 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. | OK | ||||||||||
| 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. | In ProgressSecrets 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 | |||||||||||
| RANK #1 - Must Have |
| onap/integration-java11:7.0.0 In nexus Contributors : SO - Att (base work), Fujitsu (Xin Miao (Unlicensed))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)
...
7- TSC PRIORITY 3 PTL GO/NO GO (please indicate where you plan to contribute)
|
| Multi Tenancy
| OK The scope is reduced with AAI, no SDC is involved in G release. | |||||||||||||||||||
| Pattern of the logging to be standardized. Append the log4j with the appender ( on OOM).
To check the status on the latest oom pods of the SO. |
In progress.
Discussing with the integration team on the latest results
Changes are done and merged in the spring. | |||||||||||||||||||||||
| Gating and daily deployment impact... (Deployment scripts)
| NA | |||||||||||||||||||||
|
| 30227 and 20225 should be (Oom based)
| 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)
| |||||||||||||||||||||
|
| CII badging improvement
| OK https part of the badge will be handled in REQ-361. | ||||||||||||||||||||
| 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
...