Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 3 Next »

STATUS: Draft

Multi-Cloud:


1 High Level Component Definition and Architecteral Relationships 



The multi-cloud function provides mediation capabilities to connect to different infrastructure providers.

  • Connect to VM based infrastructure such as openstack
  • Contains container based Orchestration engine and infra structure levelLCM of VNFs for container based VNFs
  • Discovery and registration of resource information. 

MORE functional capabilities?

2. CLAMP API definitions

CLAMP provides the following interfaces:

Interface NameInterface Definition Interface Capabilities
MCE-1Control Loop Lifecycle Management Interface.   A user interface for:
  • Selecting the control loop flow
  • entering configuration policy paramaters
  • entering operational policy parameters
  • Managing lifecycle of DCAE conrol flow blueprint 
CLAMPE-2Control loop dashboard.  User interface to show the status of the control loop

 Display and update:

xxxxx

Note:   xxxI interface is a Component internal interface.  xxxxE interface is a component external interface

The current API documents can be found at:

CLAMP consumes the following Interfaces:

Interface NamePurpose Reason For Use
SDCE-6To Recieve the Control Loop Blueprint from SDCTo recieve
PolicyE-2To 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 

7. New Capabilities in this Release

This release, CLAMP 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 approach. 

8. References

  1.  CLAMP Overview & User Guide: https://onap.readthedocs.io/en/latest/submodules/clamp.git/docs/index.html 
  2. CLAMP internal interfaces:  https://onap.readthedocs.io/en/latest/_downloads/d3c9f924c6586fe411d40a05ad9b1bb7/swagger.pdf 


  • No labels