...
CLAMP want to enhance the flexibility and ease of introducing new Control loop by:
- implemnting a new Control Loop creation flow: Self Serve Control Loop .
- Add Tosca policy-model support for Operationnal Policies definbitions.
- 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
...
- Solve bugs coming during this release
- implements as much TSC must feature as possible
| Scope | Priority | Committer Lead | Resources Committed | Epic | Dependencies | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CLAMP Self Serve Control Loop | high | TSC Must have | high | ATAT&T, Ericscson |
| DCAE | Document current upgrade component strategy | high | AT&T | |||||||||||||
| Jira Legacy | ||||||||||||||||||||||
| server | System Jira |
Use Cases
The existing use cases are still going to be supported and additional use cases might be supported for the Guilin Release (as defined by the Control loop sub committee and TSC) depending on available resources.
Minimum Viable Product
The minimum viable product that we aim to reach within R7 is to have the CLAMP application Guilin (R7) features at least running with the TSC must being implemented.
Functionalities
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, Code mpacting CLAMP
Use Case : None
Functional Requirements : None
18 Non functionals :
10 - TSC MUST HAVE (please indicate where you plan to contribute)
| Requirement Epic | TSC Priority | SDC Epic(s) and/or SDC Story(ies) | Committed Contributors | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| RANK #1 - Must Have |
|
| ||||||||||||
| RANK #1 - Must Have |
|
| |||||||||||||
| RANK #1 - Must Have |
|
| |||||||||||||
| RANK #1 - Must Have |
|
| |||||||||||||
| RANK #1 - Must Have |
|
| |||||||||||||
| RANK #1 - Must Have |
|
| |||||||||||||
| RANK #1 - Must Have |
|
| |||||||||||||
| RANK #1 - Must Have |
|
| |||||||||||||
 REQ-349 - Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage To Do | RANK #1 - Must Have |
|
| ||||||||||||
| RANK #1 - Must Have |
|
|
1 - TSC PRIORITY 2 Continuity (please indicate where you plan to contribute)
| RANK #2 – Continuity |
|
|
7- TSC PRIORITY 3 PTL GO/NO GO (please indicate where you plan to contribute)
|
| |||||||||||||||||||
|
| |||||||||||||||||||
|
| |||||||||||||||||||
|
| |||||||||||||||||||
| REQ-360 - Application config should be fully prepared before starting the application container To Do |
|
| ||||||||||||||||||
| 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 |
| |||||||||||||||||||
| key | CLAMP-546 | TSC Must have | high | AT&T |
| |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ,created
| ,due
| ,reporter
| ,resolution|||||||||||||||||
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 | |||||||||||||||||||
| key | CLAMP-880 |
Use Cases
The existing use cases are still going to be supported and additional use cases might be supported for the Guilin Release (as defined by the Control loop sub committee and TSC) depending on available resources.
Minimum Viable Product
The minimum viable product that we aim to reach within R7 is to have the CLAMP application Frankfurt(R6) features at least running with the TSC must being implemented.
Functionalities
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.
...
|
|
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 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 Legacy server System 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 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
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 Legacy server System 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 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
- 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:
- 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.
- 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).
- 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):
- design control loop flow (sequences of µS)
- 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):
- 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)
- 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.
- The CLAMP cockpit will support the following action at runtime:
- start (start the provisioned Closed Loop on DCAE)
- stop (stop a provisioned Closed loop on DCAE)
- Dashboard (ELK based)
- 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.
...
| Name | Description | Version |
|---|---|---|
| Camel | framework to define routing and mediation rules | 2.24.0 |
| Docker | Container engine | 1.17 |
| MariaDB | database container | 10.3.12 |
| Spring boot | Spring boot Framework dependencies | 2.1.5 |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
Testing and Integration Plans
Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.
Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.
CLAMP will invest in CSIT tests to allow further integration testing, CLAMP already provided some tests as part of previous releases.
Gaps
This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.
...
Known Defects and Issues
...
| 10.3.12 | ||
| Spring boot | Spring boot Framework dependencies | 2.1.5 |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
Testing and Integration Plans
Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.
Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.
CLAMP will invest in CSIT tests to allow further integration testing, CLAMP already provided some tests as part of previous releases.
Gaps
This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.
| Gaps identified | Impact |
|---|---|
| Testing/Integration | limited testing of final product |
Known Defects and Issues
Jira Legacy server System 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 4733707d-2057-3a0f-ae5e-4fd8aff50176
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
...
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.