...
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 | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SO-2915 |
---|
|
| Wipro |
REQ-366 - Containers must crash properly when a failure occurs To Do | RANK #1 - Must Have | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
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 |
REQ-365 - Containers must have no more than one main process To Do | RANK #1 - Must Have | Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SO-3039 |
---|
|
| OK for SO |
REQ-380 - ONAP container repository (nexus) must not contain upstream docker images To Do | RANK #1 - Must Have | Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SO-3040 |
---|
|
| License compliance Huawei Seems OK for SO |
REQ-379 - ONAP projects must use only approved and verified base images for their containers To Do | RANK #1 - Must Have | Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
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 - 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 |
REQ-373 - ONAP must complete update of the Python language (from 2.7 -> 3.8) To Do | RANK #1 - Must Have | | NA |
REQ-362 - All containers must run as non-root user To Do | RANK #1 - Must Have | Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SO-3042 |
---|
|
| 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 | Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SO-3043 |
---|
|
| 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. |
REQ-349 - Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage To Do | RANK #1 - Must Have | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SO-3038 |
---|
|
| OK 63% and 66% Tech Mahindra to support on need basis. Milind Jalwadi (Unlicensed) |
REQ-351 - ONAP must complete update of the java language (from v8 -> v11) To Do | RANK #1 - Must Have | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SO-2046 |
---|
|
| onap/integration-java11:7.0.0 In nexus Contributors : SO - Att (base work), Fujitsu (Xin Miao (Unlicensed)) So/libs - damian.nowak to get back..
|
...
REQ-340 - ONAP to support Multi - tenancy To Do | Jira Legacy |
---|
server | System 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 | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
| |
REQ-374 - ONAP shall use STDOUT for logs collection To Do | Jira Legacy |
---|
server | System 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 |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
| Pattern of the logging to be standardized. Append the log4j with the appender ( on OOM). Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SO-3077 |
---|
|
|
REQ-369 - Replace nfs share with storage class as a default deployment option To Do | Jira Legacy |
---|
server | System 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 | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
| Gating and daily deployment impact... (Deployment scripts) |
REQ-364 - Replace NodePorts with ingress controller as a default deployment option To Do | Jira Legacy |
---|
server | System 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 |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
| 30227 and 20225 should be Robot Pod Refactoring (Oom based) Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SO-3078 |
---|
|
|
REQ-360 - Application config should be fully prepared before starting the application container To Do | Jira Legacy |
---|
server | System 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 | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
| 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 Legacy |
---|
server | System 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 | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
| CII badging improvement - Contributors : ?
- Seshu Kumar Mudiganti
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SO-3079 |
---|
|
|
REQ-359 - Container rootfs must be mounted readOnly To Do | Jira Legacy |
---|
server | System 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 | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
| Springboot startup should take care of this, need to check with Kryzstof. (Oom based) |
...
Jira Legacy |
---|
server | System 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 | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
...
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.
...
List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
...
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.
...