...
- implemnting a new Control Loop creation flow: Self Serve Control Loop .
- Add Tosca policy-model support for Operationnal Policies definbitions.
- Add integration to CDS for Actor/Action selection.
- Move from SearchGuard to OpenDistro
- Document current upgrade component strategy (TSC must havve)
- SECCOM Perform Software Composition Analysis - Vulnerability tables (TSC must have)
- SECCOM Password removal from OOM HELM charts (TSC must have)
- SECCOM HTTPS communication vs. HTTP (TSC must have) - CLAMP has already moved to to HTTPS so no work is required here
| Scope | Priority | Committer Lead | Resources Committed | Epic | Dependencies | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CLAMP Self Serve Control Loop | high | AT&T, Ericscson |
| DCAE | |||||||||||
| CLAMP use policy model for Ops Policy | high | AT&T, Ericcsson |
| Policy | |||||||||||
| CLAMP - CDS integration | high | vidyashree.rama | AT&T, Huawei |
| CDS | ||||||||||
| SearchGuard to OpenDistro move | high | AT&T |
| ||||||||||||
| Document current upgrade component strategy | high | AT&T |
| ||||||||||||
| SECCOM Password removal from OOM HELM charts | high | AT&T |
| ||||||||||||
| SECCOM Perform Software Composition Analysis - Vulnerability tables | high | AT&T |
Use Cases
The existing use cases are still going to be supported and additional use cases will be supported for the Frankfurt Release (as defined by the Control loop sub committee and TSC)
...
- Below we show how the CLAMP application fits into ONAP. The red figure below shows the CLAMP application components. There is a design portion and an operations component.
•CLAMP is separated in 3 areas, which are currently (in seed code) both supported by a single application:
...
CLAMP will thus control the typical following control loop flow within ONAP :
Platform Maturity
Please fill out 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.
...
| Name | Description | Version |
|---|---|---|
| Camel | framework to define routing and mediation rules | 2.2224.10 |
| Docker | Container engine | 1.1217 |
| MariaDB | database container | 10.13.1112 |
| Spring boot | Spring boot Framework dependencies | 2.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.