Versions Compared

Old Version 22

changes.mady.by.user Seshu Kumar Mudiganti

Saved on

compared with

New Version Current

changes.mady.by.user Seshu Kumar Mudiganti

Saved on

Key

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

...

List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.



Requirements Epics for Guilin, impacting

...

SO

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = SO AND issuetype = Epic AND fixVersion = "Guilin Release"
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

...

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

Jira Legacy
serverSystem 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
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

Huawei, CMCC, Wipro

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


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


REQ-342E2E Network Slicing requirements for Guilin releaseSwaminathan S3

Jira Legacy
serverSystem 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"
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

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-325MDONS Extension in Guilin ReleaseXin Miao2

Jira Legacy
serverSystem 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
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

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 :

318 -?

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 DOx

Jira Legacy
serverSystem 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
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

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 Legacy
serverSystem 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
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

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 Plug & Play in R7 TO DO

x

Jira Legacy
serverSystem 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
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

Nokia

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
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 Legacy
serverSystem 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
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

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 Legacy
serverSystem 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
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

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 Legacy
serverSystem 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
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

Ericsson, Verizon

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

Non-Functional Requirement:

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-362

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-361


18 Non functionals :

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

Requirement EpicTSC PrioritySO 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 Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2915

contributor

?

Reshmasree c

Wipro

Image ModifiedREQ-366 - Containers must crash properly when a failure occurs To Do
RANK #1 - Must Have

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-3037

Need to check for each of the POD

Image RemovedREQ-365 - Containers must have no

SO seems to be ok - TBD on event basis

(OOM and SO)

contributor

Seshu Kumar Mudiganti

Image AddedREQ-365 - Containers must have no more than one main process To Do
RANK #1 - Must Have

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-3039

OK for SO
Image ModifiedREQ-380 - ONAP container repository (nexus) must not contain upstream docker images To Do
RANK #1 - Must Have

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status

maximumIssues20jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-380 serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-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 Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

maximumIssues20jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-379

serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
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

Image RemovedREQ-373 - ONAP must complete update of the Python language (from 2.7 -serverSystem Jira

 - 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

Image AddedREQ-373 - ONAP must complete update of the Python language (from 2.7 -> 3.8) To Do
RANK #1 - Must Have
Jira Legacy


NA

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

RANK #1 - Must Have

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status

maximumIssues20jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-373

,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

NARANK #1 -

key

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

serverId4733707d-

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.

Image AddedREQ-361 - Continue hardcoded passwords removal To Do
RANK #1 - Must Have

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

maximumIssues20jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-362

serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

Wrapping the dockers on the deployment scriptsImage RemovedREQ-361 - Continue hardcoded passwords removal

keySO-3043

Certificate and ingress 

(Oom based)

OK

Orange and Huawei.

serverId4733707d

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.

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

Jira Legacy
serverSystem Jira

columnskey,summary,type,updated,assignee,priority,statusmaximumIssues20jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-361 Image RemovedREQ-349 - Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage

serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

Certificate and ingress 

(Oom based)

Orange and Huawei.

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

keySO-3038

OK

63% and 66%

Tech Mahindra to support on need basis.  Milind Jalwadi (Unlicensed)

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

Jira Legacy
serverSystem Jira

columnskey,summary,type,updated,assignee,priority,statusmaximumIssues20jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-349 serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-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..


1 - TSC PRIORITY 2 Continuity (please indicate where you plan to contribute)

serverId4733707d-
Image AddedREQ-358 - No root (superuser) access to database from application container To Do
RANK #2 – Continuity 

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

maximumIssues20jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-351

serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
key

onap/integration-java11:7.0.0 In nexus

...

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-

358 - No root (superuser) access to database from application container To DoRANK #2 – Continuity 

340 - ONAP to support Multi - tenancy To Do

Jira Legacy
serverSystem Jira
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-

358 (Oom based)

340
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

This should be OK, Need to check it further with Security

Multi Tenancy

  • Contributors :
?

...

Image ModifiedREQ-
340
374 - ONAP
to support Multi - tenancy
shall use STDOUT for logs collection To Do

Jira Legacy
serverSystem Jira
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-

340

374
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

Multi Tenancy

Pattern of the logging to be standardized.

Append the log4j with the appender ( on OOM).

  • Contributors :
Bell, Yopp NetworksImage RemovedREQ-374 - ONAP shall use STDOUT for logs collection

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-3077

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

Jira Legacy
serverSystem Jira
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-

374 Append the log4j with the appender ( on OOM

369
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

Pattern of the logging to be standardized.

Gating and daily deployment impact...

(Deployment scripts)

  • Contributors : ?
 

Image ModifiedREQ-

369

364 - Replace

nfs share with storage class

NodePorts with ingress controller as a default deployment option To Do

Jira Legacy
serverSystem Jira
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-

369

364
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

Gating and daily deployment impact...

(Deployment scripts

30227 and 20225 should be

Robot Pod Refactoring

(Oom based)

  • Contributors :
?

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

serverId4733707d-2057-
  • Orange

Jira Legacy
serverSystem Jira

columnskey,summary,type,updated,assignee,priority,statusmaximumIssues20jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-364

serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

30227 and 20225 should be

Robot Pod Refactoring

(Oom based)

  • Contributors : ?

keySO-3078

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

Jira Legacy
serverSystem Jira
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-360
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

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

(Oom based)

  • Contributors : ?

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
serverSystem Jira
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-350
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

CII badging improvement

  • Contributors : ?
Image Removed
Image AddedREQ-359 - Container rootfs must be mounted readOnly To Do

Jira Legacy
serverSystem Jira
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-359
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

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 Legacy
serverSystem Jira
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = SDC SO AND issuetype in (Epic, Story, Task, bug) AND fixVersion = "Guilin Release"
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

...

Deliverable NameDeliverable Description
SO Docker ImagesTo fill outDocker Images, details  can be found below
SO libslibs


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.

  • onap/so/api-handler-infra
  • onap/so/bpmn-infra
  • onap/so/catalog-db-adapter
  • onap/so/openstack-adapter
  • onap/so/request-db-adapter
  • onap/so/sdc-controller
  • onap/so/sdnc-adapter
  • onap/so/so-monitoring
  • onap/so/vfc-adapter
  • onap/so/sol003-adapter
  • onap/so/sol02-adapter
  • onap/so/nssmf-adapter
  • onap/so/appc-orchestrator
  • onap/so/k8s-adapter

Architecture

High level architecture diagram

Image Removed

Platform Maturity

...

  • onap/so/nssmf-adapter
  • onap/so/appc-orchestrator
  • onap/so/k8s-adapter

Architecture

High level architecture diagram

Image Added

Platform Maturity

Please fill out the centralized wiki page: Guilin Release Platform Maturity


Team Internal Milestone (Tentative)

MilestoneDescription DateComments
M2/M3Functionality Freeze / API Freeze


  • Final API definitions (swagger, Yang) due
July 3, 2020Last day to submit Guilin swagger / Yang changes to Gerrit

  • M2/M3 Jiras ready for review
Aug 3, 2020Release manager reviews worksheets to assess readiness for M2/M3 milestone

  • M2/M3 Milestone
Aug 6, 2020


M4Code Freeze


  • Code due for Frankfurt user stories
Sept 4, 2020Last day to submit Frankfurt code changes to Gerrit

  • M4 worksheets ready for review
Sept 7, 2020

Release manager reviews worksheets to assess readiness for M4 milestone, including the following checks:

  • All repos must have >= 55% code (line) coverage in Sonar
  • No failed Jenkins jobs
  • All CSIT tests pass
  • Healthchecks pass

  • M4 release builds available
Sept 7, 2020

  • M4 Milestone
Sept 10, 2020


RC0Release Candidate 0


  • Code due for RC0 fixes
Sept 25, 2020Last date to submit code fixes for release candidate 0

  • RC0 release artifacts available
Sept 28, 2020

  • RC0 Jiras ready for review
Sept 28, 2020

  • TSC RC0 approval vote
Oct 1, 2020


RC1Release Candidate 1


  • Code due for RC1 fixes
Oct 9, 2020Last date to submit code fixes for Frankfurt release candidate 1

  • RC1 release artifacts available
Oct 12, 2020

  • RC1 Jiras ready for review
Oct 12, 2020

  • TSC RC1
Oct 15, 2020


RC2Release Candidate 2


  • Code due for final Frankfurt fixes
Oct 23, 2020Last date to submit code fixes for final Frankfurt release (RC2)

  • RC2 release artifacts available
Oct 26, 2020

  • RC2 Jiras ready for review
Oct 26, 2020

  • TSC RC2
Oct 29, 2020


Release Sign-OffFinal TSC Sign-OffMay 7, 2020
Frankfurt Release Sign-Off


  • API Incoming Dependencies

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.

...

Base docker images with approved set of License to be used to construct SDC base SO base images.


  • Testing and Integration Plans

...

  • validate uses cases and pairwise testing of SDC with SO with other components
  • enhance CSIT to include more tests

...

Please update any risk on the centralized wiki page - Frankfurt Risks – To be updated when avail

  • Resources

Fill out the Resources Committed to the Release centralized page.

  • Release Milestone

...