...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Frankfurt Guilin Release |
| Project Lifecycle State | Incubation.( Refer to ONAP Charter, section 3.3 Project Lifecycle for further information) |
| Participating Company | AT&T, Ericcson, Huawei, .... (TBC) |
...
| 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 | | Jira Legacy | | |||||||||||||
| server | System Jira | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution||||||||||||||||||||
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 | |||||||||||||||||||||
| key | CLAMP-492 | Policy | ||||||||||||||||||||
| Document current upgrade component strategy | high | AT&T |
| |||||||||||||||||||
| SECCOM Password removal from OOM HELM charts TSC Must have | 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 might be supported for the Frankfurt 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 R6 R7 is to have the CLAMP application El AltoFrankfurt(R5R6) features at least running with , the new Operationnal policy-model and the new additional self-serve Control Loop flow workingthe 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.
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=clamp and issuetype in (epic) and fixVersion="Frankfurt Guilin Release" serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | |
|---|---|---|---|---|---|
| Same as previous release | SDC Client(jar library provided by SDC team) used to get service template (describing control loop flow) and blueprint id( to know which blueprint has been distributed to DCAE for this Control Loop template) | Already available | |||
| Same as previous release | API exposed by Policy to create/update guard policies (used for scale out use case operational policies) | Already available | |||
| Same as previous release | API exposed by Policy to create/update policies | Already available | |||
| Same as previous release | API exposed by policy to get a policy-model given the policy-model-id | ongoing | TBDAlready available | ||
| Same as previous release | API exposed by Policy to create polidy pdp group | ongoing | TBDAlready available | ||
| Same as previous release | API exposed by DCAE to start/stop a Closed Loop | Already available | |||
| Same as previous release | API exposed by DCAE to trigger the deployment/undeployment of a Control Loop template | Already available | |||
| Same as previous release | API exposed by DCAE to get status of a CLAMP deployed µS | Already available | |||
| API exposed by DCAE to get status of all µS | ongoing | TBD | |||
| API exposed by DCAE to get the list of Control Loop Flow available to use by CLAMP | ongoing | TBD | |||
| Same as previous release | API exposed by CDS to retriev CDS actors/actions | ongoing | TBDAlready available |
API Outgoing Dependencies
...