CLAMP project proposal

Project Name:

• Proposed name for the project: CLAMP
• Proposed name for the repository: (org.onap.)clamp

Project description:

• CLAMP is a platform for designing and managing control loops.  It is used to design a closed loop, configure it with specific parameters for a particular network service, then deploying and undeploying it.  Once deployed, the user can also update the loop with new parameters during runtime, as well as suspending and restarting it.

  
  

  It interacts with other systems to deploy and execute the closed loop.  For example, it pushes the control loop design to the SDC catalog, associating it with the VF resource.  It requests from DCAE the instantiation of microservices to manage the closed loop flow.  Further, it creates and updates multiple policies in the Policy Engine that define the closed loop flow.  

  
  

  The OpenCLAMP platform abstracts the details of these systems under the concept of a control loop model.  The design of a control loop and its management is represented by a workflow in which all relevant system interactions take place.  This is essential for a self-service model of creating and managing control loops, where no low-level user interaction with other components is required.

Scope

Functionality:

1. Designing the Control Loop:
   1. Model based (based on templates)
   2. Re-usable designs
2. Configuring the Control Loop:
   1. VNF driven, future should be SERVICE driven
   2. Defining threshold values…
3. Deploying the Control Loop:
   1. Sending template towards DCAE, Policy, …
4. Lifecycle Management of the Control Loop:
1. Stopping/re-starting/updating
2. Monitoring (visualization of the Loop)(future not in R1)
3. Trial mode, production mode, ….(future not in R1)
4. Activation (manually and/or triggered by a policy(future not in R1) and/or tied to the vnf startup(future not in R1))

End to End Flows:

Since CLAMP is an end-to-end application, the project will, early on, develop documents describing detailed call-flows and message formats between ONAP components to support

control loop. 

These documents will be developed for the three use cases: vFW/vDNS, vVoLTE, and vCPE.

Use-cases:

CLAMP will support the vFW/vDNS ONAP Use case in R1. 

For the vVoLTE and vCPE use cases, CLAMP will tentatively plan to support them, and at the very least develop requirements for supporting in R2.

      vFW Control Loop design will consist of:

• 1. create the blueprint for DCAE to capture traffic level .
  2. create the policy that will define theshold signature that DCAE will use.
     1. DCAE team provides model to Policy team to built the Configuration policy
  3. create the policy that will trigger traffic gen to lower traffic.

      vDNS Control Loop design will consist of:

• 1. create the blueprint for DCAE to capture traffic level.
  2. create the policy that will define theshold signature that DCAE will use.
     1. DCAE team provides model to Policy team to built the Configuration policy
  3. create the policy that will trigger SO to spun up a new vDNS vm.

Interfaces:

The following interfaces will be implemented by other components but used for CLAMP.  Therefore, CLAMP has these as dependencies:

• Query and update services in SDC
• Query and update control loop templates in SDC (future not in R1)
• Policy interfaces for creating/updating configuration and operational policies
• DCAE interfaces for deploying/undeploying control loops
• Runtime messaging interface between DCAE and Policy

 Architecture Alignment

CLAMP depends upon the following open source projects:

1. 1. AJSC 6.0 (container framework based on Spring and developed by "AT&T Common platform" Team)
   2. AJSC-Camunda 6.0 (Camunda Workflow integration to AJSC container developed by "AT&T Common platform" Team)

Resources