Versions Compared

Key

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

...

  1. implemnting a new Control Loop creation flow: Self Serve Control Loop .
  2. Add Tosca policy-model support for Operationnal Policies definbitions.
  3. Add integration to CDS for Actor/Action selection.
  4. Move from SearchGuard to OpenDistro
  5. Document current upgrade component strategy (TSC must havve)
  6. SECCOM Perform Software Composition Analysis - Vulnerability tables (TSC must have)
  7. SECCOM Password removal from OOM HELM charts (TSC must have)
  8. SECCOM HTTPS communication vs. HTTP (TSC must have) - CLAMP has already moved to to HTTPS so no work is required here
ScopePriorityCommitter LeadResources CommittedEpic Dependencies 
 CLAMP Self Serve Control Loop high AT&T, Ericscson

 

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

 DCAE
CLAMP use policy model for Ops PolicyhighAT&T, Ericcsson

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

Policy
CLAMP - CDS integrationhighvidyashree.ramaAT&T, Huawei

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

CDS
SearchGuard to OpenDistro movehighAT&T

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLAMP-483


Document current upgrade component strategyhighAT&T

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLAMP-546


SECCOM Password removal from OOM HELM charts highAT&T

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLAMP-547


SECCOM Perform Software Composition Analysis - Vulnerability tableshighAT&T

...

Please check the centralized wiki page: Frankfurt Release Platform Maturity v1

API Incoming Dependencies

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.

...

NameDescriptionVersion
Camelframework to define routing and mediation rules2.2224.10
DockerContainer engine1.1217
MariaDBdatabase container10.13.1112
Spring bootSpring boot Framework dependencies2.1.4.15

In case there are specific dependencies  (Centos 7 vs Ubuntu 16. Etc.) list them as well.

...

Known Defects and Issues

Please refer to Frankfurt Defect Status

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 - Frankfurt 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.