...

The minimum viable product that we aim to reach within R7 is to have the CLAMP application FrankfurtGuilin (R6R7) features at least running with the TSC must being implemented.

...

Requirement Epic

TSC Priority

SDC Epic(s) and/or SDC 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
columns	key,summary,type,updated,assignee,priority,status
maximumIssues	20
jqlQuery	project = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-323")
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Contributors : AT&T

REQ-366 - Containers must crash properly when a failure occurs To Do

RANK #1 - Must Have

Jira

server	ONAP JIRA
columns	key,summary,type,updated,assignee,priority,status
maximumIssues	20
jqlQuery	project = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-366")
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Contributors : AT&T

REQ-365 - Containers must have no more than one main process To Do

RANK #1 - Must Have

Jira

server	ONAP JIRA
columns	key,summary,type,updated,assignee,priority,status
maximumIssues	20
jqlQuery	project = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-365")
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Contributors : AT&T
already DONE in previous release

REQ-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,updated,assignee,priority,status
maximumIssues	20
jqlQuery	project = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-380")
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Contributors : AT&T
Align all containers to Database, Java, Python, Docker, Kubernetes, and Image Versions

REQ-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,updated,assignee,priority,status
maximumIssues	20
jqlQuery	project = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-379")
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Contributors : AT&T
Align all containers to Database, Java, Python, Docker, Kubernetes, and Image Versions

REQ-373 - ONAP must complete update of the Python language (from 2.7 -> 3.8) To Do

RANK #1 - Must Have

Jira

server	ONAP JIRA
columns	key,summary,type,updated,assignee,priority,status
maximumIssues	20
jqlQuery	project = CLAMP AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-373
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

N/A for CLAMP (CLAMP doesn't use python)

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

RANK #1 - Must Have

Jira

server	ONAP JIRA
columns	key,summary,type,updated,assignee,priority,status
maximumIssues	20
jqlQuery	project = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-362")
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Contributors : AT&T
already DONE in previous release

REQ-361 - Continue hardcoded passwords removal To Do

RANK #1 - Must Have

Jira

server	ONAP JIRA
columns	key,summary,type,updated,assignee,priority,status
maximumIssues	20
jqlQuery	project = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-361")
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Contributors : AT&T
Remove certificates from containers

REQ-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
columns	key,summary,type,updated,assignee,priority,status
maximumIssues	20
jqlQuery	project = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-349")
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Contributors : All (currently at 73%)

REQ-351 - ONAP must complete update of the java language (from v8 -> v11) To Do

RANK #1 - Must Have

Jira

server	ONAP JIRA
columns	key,summary,type,updated,assignee,priority,status
maximumIssues	20
jqlQuery	project = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-351")
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Contributors : AT&T
already DONE in previous release

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,updated,assignee,priority,status
maximumIssues	20
jqlQuery	project = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-358")
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Contributors : AT&T
already DONE in previous release

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

server	ONAP JIRA
columns	key,summary,type,updated,assignee,priority,status
maximumIssues	20
jqlQuery	project = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-340")
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Contributors : ?

REQ-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 = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-374")
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Contributors : ?

REQ-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 = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-369")
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Contributors : ?

REQ-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 = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-364")
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Contributors : ?

REQ-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 = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-360")
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

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

server	ONAP JIRA
columns	key,summary,type,updated,assignee,priority,status
maximumIssues	20
jqlQuery	project = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-350")
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Contributors : ?

REQ-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 = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-359")
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Contributors : ?

CLAMP Guilin Backlog Overview - Not committed for the release (except for stories and Epics that have been captured in the table in the above

...

sections:"Use Case","Functionals" and "Non-Functionals" ), best effort

Epics

Epics (Epics in the table below which doesn't appears in the tables(section Use Case, Functionals and Non functionals) above are not committed for this release !!)

Jira

server	ONAP JIRA
columns	key,summary,

Jira

server	ONAP JIRA
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	project=clamp and labels!=relman and issuetype in (epic) and fixVersion="Guilin Release"
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Stories

...

/Tasks (Stories/Tasks in the table below which doesn't appears in the tables(section Use Case, Functionals and Non functionals) above are not committed for this release !!)

Jira

server	ONAP JIRA
columns	key,summary,type

Jira

server	ONAP JIRA
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	25
jqlQuery	project=clamp and labels!=relman and issuetype in (storyStory, task, bug) and fixVersion="Guilin Release"
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

...

Design/Setup Time(Cockpit/UI to Configure the received templates)

SDC will distribute a CSAR, for a service, the part of the CSAR that CLAMP will use are:
1. the Control Loop flow Templates(e.g: blueprint) are defined in DCAE-D(sub-component of SDC) and distributed to CLAMP by SDC. The templates format is TOSCA. The blueprint is also pushed, by SDC, to DCAE platform orchestration engine.
2. The policy-models defining the DCAE µS used inside the blueprint. note that policy-engine will also receive this SDC distribution and so should be also aware of those policy-models.
policies (configuration and operational policies) are pushed/provisioned towards the Policy Component of ONAP. (those policies will be triggered by DCAE during Closed Loop operations).
1. The DCAE team needs to provide models to Policy team in order for the Configuration policy to be built.
DCAE (in Frankfurt release), plan to introduce the DCAE-DESIGNER to(this is part of the new Self Serve Control Loop initiative)::
1. design control loop flow (sequences of µS)
2. expose an API for CLAMP to retrieve the
3. design control loop flow (sequences of µS)
4. expose an API for CLAMP to retrieve the list of existing flow, so that CLAMP can use it to create new Control Loop's instance(also using a DCAE API for this creation)
CDS (in starting from Frankfurt release):
1. expose by an API (or through CSAR distribution via SDC), the list of actors and corresponding actions, that CLAMP can then configure as part of an Operationnal Operational policy configuration

Run time(DCAE-Policy, grabbing events and triggering policies based actions)
1. the triggering to deploy(and then effectively start the closed loop) a blueprint will be manual (via CLAMP cockpit) an automatic deployment based on an event will come in future release.
2. The CLAMP cockpit will support the following action at runtime:
  1. start (start the provisioned Closed Loop on DCAE)
  2. stop (stop a provisioned Closed loop on DCAE)
Dashboard (ELK based)
1. CLAMP also provides (as a separate components) an ELK stack (with specific configurations for the elk components) that listen to Control Loop events published on DMAAP on specific dmaap topics.

...

Gaps identified	Impact
Testing/Integration	limited testing of final product

Known Defects and Issues

Jira

server	ONAP JIRA
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	status != Closed AND status != Done AND project != "Sandbox Project" AND issuetype = Bug AND project = CLAMP ORDER BY priority DESC, updated DESC
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Please refer toGuilin Defect Status (TBC)

Risks

List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).

Please update any risk on the centralized wiki page - Guilin Risks

Resources

Link toward the Resources Committed to the Release centralized page.

Release Milestone

...

Space shortcuts

Page tree

Versions Compared

Old Version 10

New Version Current

Key

CLAMP Guilin Backlog Overview - Not committed for the release (except for stories and Epics that have been captured in the table in the above

sections:"Use Case","Functionals" and "Non-Functionals" ), best effort

Epics

Epics (Epics in the table below which doesn't appears in the tables(section Use Case, Functionals and Non functionals) above are not committed for this release !!)

Stories

/Tasks (Stories/Tasks in the table below which doesn't appears in the tables(section Use Case, Functionals and Non functionals) above are not committed for this release !!)

Known Defects and Issues

Risks

Resources

Release Milestone

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 10

New Version Current

Key

CLAMP Guilin Backlog Overview - Not committed for the release (except for stories and Epics that have been captured in the table in the above

sections:"Use Case","Functionals" and "Non-Functionals" ), best effort

Epics

Epics (Epics in the table below which doesn't appears in the tables(section Use Case, Functionals and Non functionals) above are not committed for this release !!)

Stories

/Tasks (Stories/Tasks in the table below which doesn't appears in the tables(section Use Case, Functionals and Non functionals) above are not committed for this release !!)

Known Defects and Issues

Risks

Resources

Release Milestone