...
| draw.io Diagram | |||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The CLAMP functional entity provides the capability to manage runtime control loops. It provides the capability to
- Create control loop from DCAE blueprint sent by SDC, those blueprint are either:
- sent by SDC to DCAE(inventory) via SDC distribution.
- or sent by DCAE-MOD to DCAE(inventory)
- Create configuration policy from the policy Tosca sent by SDC-model Tosca, the tosca policy-model are either:
- sent by SDC via SDC distribution to everyone
- or query by CLAMP to Policy. in this case the policy-model is either pre-provison in Policy
or separately provision to Policy via the REST API exposed by Policy.
- Configure DCAE applications of the control loop
- Associate µService configuration policies to the DCAE application
- Configure the operations to be taken by the control loop (by creating/updating/deleting operational policies)
- Deploy/un-deploy control loop flow (blueprints) to DCAE
- Control loop visualization.
...
| Interface Name | Interface Definition | Interface Capabilities |
|---|---|---|
| CLAMPE-1 | Control Loop Lifecycle Management Interface. | A user interface for:
|
| CLAMPE-2 | Control loop dashboard. User interface to show the overall status of the control loop through DMAAP events | Display and update:
|
...
| Interface Name | Purpose Reason For Use |
|---|---|
| SDCE-6 | To receive the Control Loop Blueprint from SDCTo receive |
| PolicyE-2 | To create and configure the closed Loop Operational Policies and Configuration policies(DCAE Aps. Config.) |
| PolicyE-1 | To query policy-model based on a policy-model id. used for Configuration policy-model and Operational Policy-model |
| DCAEE-x |
|
| DCAEE-y | Deploy/remove DCAE application. |
...