...
This is a working wiki to capture the ONAP architecture component descriptions
<< Component Name >>:
...
STATUS: Draft
<<Functional component name >>:
1 High Level Component Definition and Architecteral Relationships
draw.io Diagram | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
2. <<XXXX>> Component Description:
A more detailed figure and description of the component.
3 <<XXXX>> Target Functional Architecture
A Description of the target functional architecture
4. SDC Current Release API definitions
<< Figure to show the interfaces >>
|
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. xxxx API definitions
xxxxxx provides SDC provides the following interfaces:
Interface Name | Interface |
---|
Definition | Interface Capabilities |
---|---|
xxxxxE |
-1 | External |
interface defintion. | capabilies |
xxxxI- |
2 | Internal |
SDCE-2
Service designer creates a service model from Design Catalog items
SDCI-2
Designer Studio stores and retrieves Design Catalog items
SDCE-3
Ops designer creates monitoring templates with mS data flows
SDCI-3
DCAE Designer Studio stores and retrieves monitoring flow with mS elements
SDCE-4
Service tester certifies service models for distribution
SDCE-5
Service tester distributes service models
SDCE-6
Distribution Engine publishes service notification to DMaaP.
ONAP components subscribe to service notification from DMaaP
SDCE-7
interface definition | Display and update: xxxxx |
Note: xxxI interface is
...
a CLMAP internal interface. xxxxE interface is a SDCE external interface
The current API documents can be found at:
The provided UI interfaces are found at:
...
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
...
- CLAMP internal APIs can be found: clamp swagger pdf
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 | Retrieve DCAE appplication status |
DCAEE-y | Deploy/remove DCAE application. |
3. Component Description:
A more detailed figure and description of the component.
<< For later inclusion >>
4. 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)
- << include model that you recieve from SDC >>
- << Include the model that you configure in the policy >>
6. System Deployment Architecture
Clamp consists of 4 containers:
- CLAMP container
- MariaDB container
- Kibana ontainer
- E_Search ontainer
- LogStash container
draw.io Diagram border true viewerToolbar true fitWindow false diagramName CLAMP runtime architectrue simpleViewer false width diagramWidth 821 revision 2
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