STATUS: Project Approved, ArchCom approved (note to add the links in red below).
CLAMP (Closed loop Automation Platform):
1
This is a working wiki to capture the ONAP architecture component descriptions
CLAMP:
...
High Level Component Definition and
...
Architectural Relationships
draw.io Diagram | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
2. CLAMP API definitions
|
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
- Create configuration policy from the policy Tosca sent by SDC
- 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.
CLAMP relies on Policy to communicate to App-C/VF-C/SDN-C/SO in runtime, hence these are not part of CLAMP
2. API definitions
CLAMP provides the following interfaces: (add the link to the interfaces)SDC provides the following interfaces:
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:
|
Note: xxxI interface is a CLMAP a Component internal interface. xxxxE interface is a SDCE component external interface
The current API documents can be found at:
The provided UI interfaces are found at: CLAMP latest user guide
- CLAMP internal APIs can be found: clamp swagger pdf<< Link to documents >>
CLAMP consumes the following Interfaces:
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.) |
DCAEE-x |
Retrieve DCAE appplication status | |
DCAEE-y | Deploy/remove DCAE application. |
3.
...
Component Description:
A more detailed figure and description of the component.
<< link to readthe docs >>
4.
...
4 <<XXXX>> Target Functional Architecture
A Description of the target functional architecture
5. The XXX dublin view :
<< Functional Dublin View>>
6 SDC Architecture Evolution (optional item)
optional description of the SDC Architectural Evolution
7 SDC Overall ONAP Architecture Principle Compliance
8 XXXX near term focus on architecture deficincies are (optional):
<<Represenation of the architectural compliance >>
9 XXXXX - Current System Deployment Architecture
xxxxxx
known system limitations
Runtime: None
Clamp data redundancy is dependent on Kubernetes and the persistent volume.
Clamp application redundancy HA relies on Kubernetes
5. Used Models
Clamp uses the following models:
- Service model (received from SDC)
- VNF model (received from SDC)
- Policy Model.
6. System Deployment Architecture
FFS
7. New Capabilities in this Release
-
8. References
- CLAMP Overview & User Guide: https://onap.readthedocs.io/en/latest/submodules/clamp.git/docs/index.html
- CLAMP internal interfaces: https://onap.readthedocs.io/en/latest/_downloads/d3c9f924c6586fe411d40a05ad9b1bb7/swagger.pdf
...