...
| | | | SO Epic(s) / Story(ies) | M1 Scope Clarifications |
---|
REQ-347 | CCVPN-Transport Slicing for Guilin Release | Henry Yu | 2 | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
maximumIssues | 20 |
---|
jqlQuery | project = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-347 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| Huawei, CMCC, Wipro Scope and Resource commitment for the non-functional requirement is needed.
ttps://jira.onap.org/browse/REQ-323 - Wipro
|
REQ-342 | E2E Network Slicing requirements for Guilin release | Swaminathan S | 3 | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
maximumIssues | 20 |
---|
jqlQuery | project = SO AND issuetype in (Epic, Story, Task, bug) AND ("Epic Link" = REQ-342 OR "Epic Name" ~ Slicing ) AND fixVersion = "Guilin Release" |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| 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 | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
maximumIssues | 20 |
---|
jqlQuery | project = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-325 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| Fujitsu Need clarifications on the new scope | ,. We will have a meeting scheduled next week. Resource commitment for the non-functional requirement REQ-351 |
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 | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
maximumIssues | 20 |
---|
jqlQuery | project = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-339 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| Huawei Requirement is presented in the CNF task force and is accepted Stories to be updated for the requirement. Non functional requirement Identified: REQ-362 |
REQ-324 - Support xNF Software Upgrade in association to schema updates IN PROGRESS | x | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
maximumIssues | 20 |
---|
jqlQuery | project = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-324 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| Ericsson, Orange This is already reviewed in the SO weekly and is accepted. commitment on the Non functional requirement is required. REQ-364 - Orange |
REQ-318 - PNF 318 - PNF Plug & Play in R7 TO DO | x | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
maximumIssues | 20 |
---|
jqlQuery | project = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-318 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| Nokia Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2785 |
---|
|
Scope and Resource commitment and the non functional requirement need clarifications. SO-2046 - TBC
Lukasz Muszkieta Damian Nowak
|
REQ-341 - ONAP CNF orchestration - Enhancements TO DO | x | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
maximumIssues | 20 |
---|
jqlQuery | project = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-341 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| Lumina, Huawei, Att The requirement is presented in the CNF task force meeting and is accepted. Non Functional requirement, REQ-361 |
REQ-343 - ONAP SO support Dynamic Orchestration IN PROGRESS | x | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
maximumIssues | 20 |
---|
jqlQuery | project = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-343 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| Huawei, (Nokia - initial support in the design) The requirement is presented in the SO weekly meeting and is accepted. Non-Functional Requirement. REQ-362 |
REQ-334 - ETSI-Alignment for Guilin IN PROGRESS | x | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
maximumIssues | 20 |
---|
jqlQuery | project = SO AND issuetype in (Epic, Story, Task, bug) AND "labels" = ETSI-Alignment |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| Ericsson, Verizon The requirement is presented in the ETSI taskforce meeting and is accepted. Non-Functional Requirement: Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | REQ-362 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | REQ-361 |
---|
|
|
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 |
---|
Image ModifiedREQ-323 - Each project will update the vulnerable direct dependencies in their code base To Do
| RANK #1 - Must Have | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2915 |
---|
|
| |
?Wipro |
Image ModifiedREQ-366 - Containers must crash properly when a failure occurs To Do | RANK #1 - Must Have | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-3037 |
---|
|
| Need to check for each of the POD SO seems to be ok - TBD on event basis (OOM and SO) contributor Seshu Kumar Mudiganti |
Image ModifiedREQ-365 - Containers must have no more than one main process To Do | RANK #1 - Must Have | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-3039 |
---|
|
| OK for SO |
Image ModifiedREQ-380 - ONAP container repository (nexus) must not contain upstream docker images To Do | RANK #1 - Must Have | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-3040 |
---|
|
| License compliance Huawei Seems OK for SO |
Image ModifiedREQ-379 - ONAP projects must use only approved and verified base images for their containers To Do | RANK #1 - Must Have | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-3041 |
---|
|
| 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 |
Image RemovedREQ-373 - - to be sure all the containers Contributors : Nokia : SO : Java part (REQ-351) TBC, Fujitsu. Xin Miao so/libs: Nokia (TBC) Orange - Docker part |
Image AddedREQ-373 - ONAP must complete update of the Python |
ONAP must complete update of the Python language (from 2.7 -> 3.8) To Do | RANK #1 - Must Have | | NA |
Image ModifiedREQ-362 - All containers must run as non-root user To Do
| RANK #1 - Must Have | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-3042 |
---|
|
| Wrapping the dockers on the deployment scripts (Oom based) OK Contributors : Orange |
and Huawei. Sylvain Desbureaux , Ericsson Byung-Woo Jun and Huawei Mukesh Paliwal . New pods should be taken care - K8s Adapter, SO-NFVO. |
Image ModifiedREQ-361 - Continue hardcoded passwords removal To Do | RANK #1 - Must Have | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-3043 |
---|
|
| |
ingress (Oom based)
Orange |
Image ModifiedREQ-349 - Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage To Do | RANK #1 - Must Have | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-3038 |
---|
|
| OK 63% and 66% Tech Mahindra to support on need basis. Milind Jalwadi |
Image ModifiedREQ-351 - ONAP must complete update of the java language (from v8 -> v11) To Do | RANK #1 - Must Have | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2046 |
---|
|
| |
-java11:7.0.0 In nexus-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 indicate where you plan to contribute)
REQ-358 - No root (superuser) access to database from application container To Do | RANK #2 – Continuity | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-3044 |
---|
|
| 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)
Image ModifiedREQ-340 - ONAP to support Multi - tenancy To Do
| Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,updated,assignee,priority,status |
---|
maximumIssues | 20 |
---|
jqlQuery | project = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-340 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| |
Yopp Networks |
Image ModifiedREQ-374 - ONAP shall use STDOUT for logs collection To Do | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,updated,assignee,priority,status |
---|
maximumIssues | 20 |
---|
jqlQuery | project = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ |
---|
|
|
-374 -374 | serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| Pattern of the logging to be standardized. Append the log4j with the appender ( on OOM). Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
Pattern of the logging to be standardized. Append the log4j with the appender ( on OOM) | |
Image ModifiedREQ-369 - Replace nfs share with storage class as a default deployment option To Do | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,updated,assignee,priority,status |
---|
maximumIssues | 20 |
---|
jqlQuery | project = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-369 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| Gating and daily deployment impact... (Deployment scripts) |
Image ModifiedREQ-364 - Replace NodePorts with ingress controller as a default deployment option To Do
| Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,updated,assignee,priority,status |
---|
maximumIssues | 20 |
---|
jqlQuery | project = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = |
---|
|
|
REQ-364 REQ-364 | serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| 30227 and 20225 should be Robot Pod Refactoring (Oom based) Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
30227 and 20225 should be Robot Pod Refactoring (Oom based) | |
Image ModifiedREQ-360 - Application config should be fully prepared before starting the application container To Do | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,updated,assignee,priority,status |
---|
maximumIssues | 20 |
---|
jqlQuery | project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-360 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| spring boot based application should be ok, will need to re-check with Kryzstof (Oom based) |
Image ModifiedREQ-350 - Each ONAP project shall improve its CII Badging score by improving input validation and documenting it in their CII Badging site. To Do
| Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,updated,assignee,priority,status |
---|
maximumIssues | 20 |
---|
jqlQuery | project = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-350 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| CII badging improvement - Contributors : ?
- Seshu Kumar Mudiganti
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-3079 |
---|
|
|
Image ModifiedREQ-359 - Container rootfs must be mounted readOnly To Do | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,updated,assignee,priority,status |
---|
maximumIssues | 20 |
---|
jqlQuery | project = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-359 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| 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.
...
Please update any risk on the centralized wiki page - Frankfurt Risks – To be updated when avail
Fill out the Resources Committed to the Release centralized page.
...