Versions Compared

Old Version 17

changes.mady.by.user cl664y@att.com

Saved on

compared with

New Version Current

changes.mady.by.user Gervais-Martial Ngueko

Saved on

Key

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

...

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 EpicTSC PrioritySDC Epic(s) and/or SDC 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
serverSystem Jira
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-323")
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

  • Contributors : AT&T
REQ-366 - Containers must crash properly when a failure occurs To Do
RANK #1 - Must Have

Jira Legacy
serverSystem Jira
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-366")
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

  • Contributors : AT&T
REQ-365 - Containers must have no more than one main process To Do
RANK #1 - Must Have

Jira Legacy
serverSystem Jira
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-365")
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

  • 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 Legacy
serverSystem Jira
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-380")
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

REQ-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,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-379")
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

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

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

  • 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 Legacy
serverSystem Jira
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-362")
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

  • Contributors : AT&T
  • already DONE in previous release
REQ-361 - Continue hardcoded passwords removal To Do
RANK #1 - Must Have

Jira Legacy
serverSystem Jira
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-361")
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

  • 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 Legacy
serverSystem Jira
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-349")
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

  • 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 Legacy
serverSystem Jira
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = CLAMP AND labels !=relman AND issuetype in (Epic, Story, Task, bug) AND issueFunction in linkedIssuesOf( "issue = REQ-351")
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

  • Contributors : AT&T
  • already DONE in previous release

...

  1. Design/Setup Time(Cockpit/UI to Configure the received templates)
    1.  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.
    2. 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. 
    3. 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 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)
    4. 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
  2. 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)
  3. 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. 

...

List the API this release is expecting from other ONAP component(s) releases.
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 - Guilin Risks

Resources

Link toward the Resources Committed to the Release centralized page.

Release Milestone

...

Each project must edit its project table available at Project FOSS

Charter Compliance

The project team comply with the ONAP Charter.

Release Key Facts

Fill out and provide a link toward the centralized Release Artifacts.