Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 23 Next »

STATUS: Draft

CLAMP:

1 High Level Component Definition and Architecteral Relationships 



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 NameInterface Definition Interface Capabilities
CLAMPE-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 overall status of the control loop through DMAAP events

 Display and update:

 Show key control loops kpi's computed via Control Loop Dmaap Events from DCAE/Policy/APPC.
  those kpi's are organized inside a Kibana dashboard, the dashboard can be updated by the user.

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 and Confguration 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.

<< 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