STATUS: Draft
CLAMP:
1
...
High Level Component Definition and Architecteral Relationships
| Drawio | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The clamp functional entity provides the capability to manage runtime control loops. It provides the capaiblity to
- configure DCAE applications of the control loop
- Associate policies to the DCAE application
- Configure the oprations to be taken by the cotnrol loop (by creating/updating/deleting operational policies)
- Deploy/un-deploy control loop flow (blueprints) to DCAE
- Control loop visulization.
Clamp Relise on Policy to communite to App-C/VF-C/SDN-C/SO in runtime, hence these are not part of CLAMP
2. CLAMP API definitions
CLAMP 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 status of the control loop |
Note: xxxI interface is a CLMAP internal interface. xxxxE interface is a SDCE external interface
...
CLAMP consumes the following Interfaces:
| Interface Name | Purpose Reason For Use |
|---|---|
| SDCE-6 | To Recieve the Control Loop Blueprint from SDCTo recieve |
| PolicyE-2 | To create and configure the closed Loop Operational Policies |
| DCAEE-x | Activate or de activate the DCAE applications for the control loop |
| DCAEE-y |
3.
...
Component Description:
A more detailed figure and description of the component.
<< For later inclusion >>
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
...
known system limitations
Runtime: None
Clamp data redundancy is dependant on kubernetes and the persisten volume.
Clamp appliation redundancy HA reliease on kubernetes
5. Used Models
Clamp uses the following models:
- please fill in (and references if possible)
6. System Deployment Architecture
Clamp consists of 4 containers:
- CLAMP container
- MariaDB container
- Kibana ontainer
- E_Search ontainer
- LogStash container
Drawio border true viewerToolbar true fitWindow false diagramName CLAMP runtime architectrue simpleViewer false width diagramWidth 821 revision 1
7. 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