Versions Compared

Old Version 8

changes.mady.by.user Byung-Woo Jun

Saved on

compared with

New Version 9

changes.mady.by.user Byung-Woo Jun

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The content of this template is expected to be fill out for M1 Release Planning Milestone.

Table of Contents
outlinetrue

Overview

Project NameEnter the name of the project
Target Release NameGuilin
Project Lifecycle StateIncubation
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

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = SO AND issuetype = Epic AND fixVersion = "Guilin Release"
serverId425b2b0a-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.

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.


KeySummaryAssigneeTsc PrioritySO Epic(s) / Story(ies)M1 Scope ClarificationsM4
REQ-347CCVPN-Transport Slicing for Guilin ReleaseHenry Yu2

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-347
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Huawei, CMCC, Wipro

Scope and Resource commitment for the non-functional requirement is needed.

NFR:

ttps://jira.onap.org/browse/REQ-323 - Wipro



REQ-342E2E Network Slicing requirements for Guilin releaseSwaminathan S3

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND ("Epic Link" = REQ-342 OR "Epic Name" ~ Slicing ) AND fixVersion = "Guilin Release"
serverId425b2b0a-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

Coding is targeted this week.

ETA:

4th Sept

REQ-325MDONS Extension in Guilin ReleaseXin Miao2

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-325
serverId425b2b0a-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

The change is still pending.

ETA : 

4th Sept


Functional Requirements :

Requirement

SO

SO Epic(s) / Story(ies)M1 Scope and clarificationM4 Status
REQ-339 - Container Network Function Test Platform (CNTP): OVP 2.0 support and Enable Network Service testing TO DOx

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-339
serverId425b2b0a-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
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-324
serverId425b2b0a-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

There is reduced scope is suggested on the vNF part, PNF is in scope.

  • Create/Instantiate/Terminate/Delete NS NBIs
  • Create/Instantiate NS backends
  • Terminate/Delete NS backends are postponed to the next release


REQ-318 - PNF Plug & Play in R7 TO DO

x

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-318
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Nokia

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-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
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-341
serverId425b2b0a-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

In progress, coding is targeted by Monday.

REQ-343 - ONAP SO support Dynamic Orchestration IN PROGRESS

x

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-343
serverId425b2b0a-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

We have encountered issue with the Java 11 on the Camunda and Tomcat, checking it further.

REQ-334 - ETSI-Alignment for Guilin IN PROGRESS

x

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "labels" = ETSI-Alignment
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Ericsson, Verizon

The requirement is presented in the ETSI taskforce meeting and is accepted.

Non-Functional Requirement:

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyREQ-362

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyREQ-361

There will be reduced scope.

The confirmed scope for Guilin is the following:

  • Create/Instantiate/Terminate/Delete NS NBIs
  • Create/Instantiate NS Backends

The following features hav been postponed to the next release

  • Terminate/Delete NS Backends


18 Non functionals :

10 - TSC MUST HAVE (please indicate where you plan to contribute)

Requirement EpicTSC PrioritySO Epic(s) / Story(ies)Committed ContributorsM4

REQ-323 - Each project will update the vulnerable direct dependencies in their code base To Do

RANK #1 - Must Have

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-2915

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

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-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

Need to clarify with Integration team.
REQ-365 - Containers must have no more than one main process To Do
RANK #1 - Must Have

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-3039

OK for SO

M4

Ok

REQ-380 - ONAP container repository (nexus) must not contain upstream docker images To Do
RANK #1 - Must Have

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-3040

License compliance

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

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-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

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


NANA

REQ-362 - All containers must run as non-root user To Do

RANK #1 - Must Have

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-3042

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
REQ-361 - Continue hardcoded passwords removal To Do
RANK #1 - Must Have

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-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.

In Progress
REQ-349 - Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage To Do
RANK #1 - Must Have

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-3038

OK

63% and 66%

Tech Mahindra to support on need basis.  Milind Jalwadi

OK
REQ-351 - ONAP must complete update of the java language (from v8 -> v11) To Do
RANK #1 - Must Have

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-2046

onap/integration-java11:7.0.0 In nexus

Contributors : 

SO   -  Att (base work), Fujitsu (Xin Miao )

So/libs  -   Damian Nowak to get back..


In progress

The changes are awaited on the oom.


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
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-3044

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

Jira
serverONAP JIRA
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-340
serverId425b2b0a-557c-3c0c-b515-579789cceedb

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

Jira
serverONAP JIRA
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-374
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Pattern of the logging to be standardized.

Append the log4j with the appender ( on OOM).

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-3077

To check the status on the latest oom pods of the SO.

In progress.

Discussing with the integration team on the latest results

REQ-369 - Replace nfs share with storage class as a default deployment option To Do

Jira
serverONAP JIRA
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-369
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Gating and daily deployment impact...

(Deployment scripts)

  • Contributors : ?
NA

REQ-364 - Replace NodePorts with ingress controller as a default deployment option To Do

Jira
serverONAP JIRA
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-364
serverId425b2b0a-557c-3c0c-b515-579789cceedb

30227 and 20225 should be

Robot Pod Refactoring

(Oom based)

  • Contributors : Orange

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-3078

In Progress.

Will be handeld as part of the REQ-361.

REQ-360 - Application config should be fully prepared before starting the application container To Do

Jira
serverONAP JIRA
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-360
serverId425b2b0a-557c-3c0c-b515-579789cceedb

spring boot based application  should be ok, will need to re-check with Kryzstof

(Oom based)

  • Contributors : ?

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

Jira
serverONAP JIRA
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-350
serverId425b2b0a-557c-3c0c-b515-579789cceedb

CII badging improvement

  • Contributors : ?
  • Seshu Kumar Mudiganti
  • Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keySO-3079

OK

https part of the badge will be handled in REQ-361.

REQ-359 - Container rootfs must be mounted readOnly To Do

Jira
serverONAP JIRA
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-359
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Springboot startup should take care of this, need to check with Kryzstof.

(Oom based)

  • Contributors : ?


SO Backlog Overview - Not committed for the release (except for stories that have been captured in the above table), best effort

Jira
serverONAP JIRA
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND fixVersion = "Guilin Release"
serverId425b2b0a-557c-3c0c-b515-579789cceedb