Versions Compared

Old Version 21

changes.mady.by.user Gervais-Martial Ngueko

Saved on

compared with

New Version Current

changes.mady.by.user Stephen terrill

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

STATUS: Draft

...

Project Approved, ArchCom approved (note to add the links in red below).

CLAMP (Closed loop Automation Platform):

1 High Level Component Definition and

...

Architectural Relationships 


Drawio
bordertrue
viewerToolbartrue
fitWindowfalse
diagramNameCLAMP System Context View
simpleViewerfalse
width
diagramWidth624
revision59


The clamp CLAMP functional entity provides the capability to manage runtime control loops.  It provides the capaiblity to

...

capability to

  • Create control loop from DCAE blueprint sent by SDC
  • Create configuration policy from the policy Tosca sent by SDC
  •  Configure DCAE applications of the control loop
  • Associate µService configuration policies to the DCAE application
  • Configure the oprations operations to be taken by the cotnrol control loop (by creating/updating/deleting operational policies)
  • Deploy/un-deploy control loop flow (blueprints) to DCAE
  • Control loop visulizationvisualization. 

Clamp Relise CLAMP relies on Policy to communite communicate to App-C/VF-C/SDN-C/SO in runtime, hence these are not part of CLAMP 

2.

...

 API definitions

CLAMP provides the following interfaces: (add the link to the interfaces)

Interface NameInterface Definition Interface Capabilities
CLAMPE-1Control Loop Lifecycle Management Interface.   A user interface for:
  • Selecting the control loop flow
  • entering Entering configuration policy paramatersparameters
  • entering Entering operational policy parameters
  • Managing lifecycle life cycle of DCAE conrol DCAE control 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 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

  • Events received and actions taken on the control loop.

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

...

Interface NamePurpose Reason For Use
SDCE-6To Recieve receive the Control Loop Blueprint from SDCTo recievereceive
PolicyE-2To create and configure the closed Loop Operational Policies and Confguration Configuration policies(DCAE Aps. Config.)
DCAEE-x Retrieve DCAE appplication status
DCAEE-y Deploy/remove DCAE application. 

...

A more detailed figure and description of the component.

<< For later inclusion >><< link to readthe docs >>

4. known system limitations

Runtime: None

Clamp data redundancy is dependant dependent on kubernetes Kubernetes and the persisten persistent volume.

Clamp appliation application redundancy HA reliease relies on kubernetesKubernetes

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 >>
  •  
  • Service model (received from SDC)
  • VNF model (received from SDC)
  • Policy Model.


6. System Deployment Architecture

Clamp consists of 4 containers:

  • CLAMP container
  • MariaDB container
  • Kibana ontainer
  • E_Search ontainer
  • LogStash container 


DrawiobordertrueviewerToolbartruefitWindowfalsediagramNameCLAMP runtime architectruesimpleViewerfalsewidthdiagramWidth821revision2FFS

7. New Capabilities in this Release

This release, CLAMP adds the following Capabilities:

...

-

...

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 

...