...
- 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
| 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 |
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)
...
CLAMP is a platform for designing and managing control loops. It is used to design setup a closed control loop, configure it with specific parameters for a particular network service, then deploying and undeploying it. Once deployed, the user can also update the loop with new parameters during runtime, as well as suspending and restarting it.
It interacts with other systems to deploy and execute the closed loop. For example, it pushes the control loop design to the SDC catalogreceives CSAR service package from SDC, associating it with the VF resource. It requests from DCAE the instantiation of microservices to manage the closed loop flow. Further, it creates and updates multiple policies in the Policy Engine that define the closed control loop flow.
The ONAP CLAMP platform abstracts the details of these systems under the concept of a control loop model. The design setup of a control loop and its management is represented by a workflow in which all relevant system interactions take place. This is essential for a self-service model of creating and managing control loops, where no low-level user interaction with other components is required.
...
A Dashboard has been introduced to allow the user to get a quick overview of the status and events of running control loops.
...
| Deliverable Name | Deliverable Description | Deliverable location |
|---|---|---|
| CLAMP Docker container | Docker images available on nexus3 | Nexus3 docker registry |
| Source Code | Code of the Designer and run time of CLAMP | CLAMP git repository |
| Deployment scripts | Scripts that can be used to help with the container instantiation and configuration | CLAMP git repository |
| Property Files | Properties files that can be used to tune the configuration of CLAMP depending on the environment | CLAMP git repository |
| Documentation | Release specific documentation (Release Note, user guide, deployment guide) provided through readthedocs | CLAMP git repositoryreadthedoc ONAP section : https://docs.onap.org/en/latest/index.html |
Sub-Components
....
Architecture
...
- 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, which are both deployed within ONAP portal.
...
•CLAMP is separated in 3 areas, which are currently (in seed code) both supported by a single application:
- 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.
- 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.
...
| Area | Actual level | Targeted level for current release | How, Evidences | Comments | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Performance | 0 | 0 (given CLAMP is design time there is no point to adhere to L2 requirement) | Run performance basic test, depends on performance criteria availability for level 1 - not able to commit to more than what was done on Beijing |
minimum level for Dublin is 0 except for Control Loop projects. | ||||||
| Stability | 1 | 2 | Participate to Stability runs Level 1| Jira Legacy | | ||||||
| server | System Jira | |||||||||
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 | key | CLAMP-2762 | Participate to Stability runs Level 1 Integration Team is responsible to run the platform test to prove level 2. |
minimum level for Dublin:2 see Stability levels | |||||
| Resiliency | 1 | 1 (given CLAMP is design time there is no point to adhere to L2 requirement) Jira Legacy | | |||||||
| server | System Jira | |||||||||
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 | key | CLAMP-83
Minimum Levels (Dublin)
| |||||||
| Security | 1 | 1 | same as in Casablanca, not enough resource to allocate to this effort. | see Security Levels | ||||||
| Scalability | 1 | 1 | Level 1 single site horizontal scaling server | System Jira | serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 | key | CLAMP-102single site horizontal scaling |
Minimum Levels (Dublin)
| |
| Manageability | 1 | 1 (2, if CLAMP can get more resource from the community) |
Minimum Levels (Dublin)
| |||||||
| Usability | 1 | 1 (2, if CLAMP can get more resource from the community) | CLAMP is not anticipating new API at this point, so we are technically compliant with API CVS at this point |
|
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | |
|---|---|---|---|---|---|
| Same as previous release | API exposed by SDC to get list of Alarms and service information's | Date for which the API is reviewed and agreed | Already available | Link toward the detailed API description | |
| Same as Casablancaprevious 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) | ongoing | TBDAlready available | ||
| Same as previous release | API exposed by Policy to create/update policies | Already available | |||
| API exposed by policy to get a policy-model given the policy-model-id | ongoing | TBD(new set of api based on policy-models) | |||
| API exposed by Policy to create polidy pdp group | ongoing | TBD | |||
| Same as Casablancaprevious release | API exposed by DCAE to start/stop a Closed Loop | Already available | |||
| Same as Casablancaprevious release | API exposed by DCAE to trigger the deployment/undeployment of a Control Loop template | Already available | |||
| Same as Casablancaprevious release | API API exposed by DCAE to get status of a CLAMP deployed µS | Already available | |||
| API API exposed by DCAE to get status of all µS | ongoingongoing | TBD | |||
| API exposed by DCAE to get the list of Control Loop Flow available to use by CLAMP | ongoing | TBD | |||
| API exposed by CDS to retriev CDS actors/actions | ongoing | TBD |
API Outgoing Dependencies
API this release of CLAMP is delivering to other ONAP Component(s) releases.
...
CLAMP will invest in CSIT tests to allow further integration testing, CLAMP already provided some tests as part of R1previous 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.
...