...
MORE functional capabilities?
2. CLAMP API definitions
CLAMP provides I was also unsure about the registration interface, whether MC was a provider and consumer there????
I didn't show redfish as its not functionally in dublin (or max a PoC)
2. MultiCloud API definitions
Multi-Cloud provides the following interfaces:
| Interface Name | Interface Definition | Interface Capabilities | ||||
|---|---|---|---|---|---|---|
| MCE-1Control Loop 2 | Cloud FCAPS Interface. Provides the ability to obtain cloud FCAPS data. | What are the main capabilities here - is it VES?? | ||||
| MCE-3 | Resource Lifecycle Management Interface . | A user interface for:
| CLAMPE-2 | Control loop dashboard. User interface to show the status of the control loop | Provides a fine graned resource LCM interface at the VM level | What are the main capabilities here? xxxxx |
| MCE-4 | SDN connect Provides xxxxxxxxxxx | Is this in Dublin or should it be removed. | ||||
| MCE-5 | Atomic Resource LCM Provides a course grain VNF level LCM interface | What are the main capabilities here (instantiate, ....)? | ||||
| MCE-6 | Placement Optimization Interface Provides xyz | What are the main capabilities here | ||||
| MCE-7 | Cloud VIM Registration interface | What are the main capabilities |
Note: xxxI interface is a Component internal interface. xxxxE interface is a 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
CLAMP consumes https://onap.readthedocs.io/en/latest/submodules/multicloud/framework.git/docs/MultiCloud-APIv1-Specification.html
MultiCloud 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. |
| recieve the cloud orchestration artifact from SDC | |
| MCE-2 | Consume the services from the cloud provider. It is specific to each cloud type (by plugin approach) |
3. Component Description:
...
4. known system limitations
Runtime: None
Clamp data redundancy is dependant on kubernetes and the persisten volume.
Clamp appliation redundancy HA reliease on kubernetesto be filled in
5. Used Models
Clamp uses Multi-Cloud 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 Multicloud consists of X containers:
- CLAMP container
- MariaDB container
- Kibana ontainer
- E_Search ontainer
- LogStash container
- Do you have a figure here that?
Drawio border true viewerToolbar true fitWindow false diagramName CLAMP runtime architectrue simpleViewer false width diagramWidth 821 revision 1
7. New Capabilities in this Release
This release, CLAMP Multi-Cloud adds the following Capabilities:
- Introduction of the model driven approach for Control Loops
- add policy-model to the SDC distribution
- automatic rendering of configuration policy UI based on the distributed policy model
- better rending of the display of the control loop flow based on the distributed blueprint
- enhanced internal model to better support model driven approachAdd SDC client to retrieve the workload artifacts from SDC
- Multicloud plugin service for OpenStack StarlingX
- Multicloud plugin service for Lenovo ThinkCloud.
8. References
- CLAMP Overview & User Guide Multicloud interface specification: https://onap.readthedocs.io/en/latest/submodules/multicloud/clampframework.git/docs/indexMultiCloud-APIv1-Specification.html CLAMP internal interfaces
- MultiCloud Architecture: https://docs.onap.readthedocs.ioorg/en/casablanca/latest/_downloads/d3c9f924c6586fe411d40a05ad9b1bb7/swagger.pdfsubmodules/multicloud/framework.git/docs/MultiCloud-Architecture.html