Page Comparison

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

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)
   3. Trial mode, production mode, ….(future)
   4. Activation (manually and/or triggered by a policy(future) and/or tied to the vnf startup(future))

 Architecture Alignment

1. Design Time(Cockpit/UI to define the templates)
1. Templates are pushed to SDC. The template format is TOSCA blueprint, those blueprints will be pushed/provisioned, by SDC, to DCAE orchestration engine.
2. policies(operational policies) are pushed/provisioned towards the Policy Component of ONAP. (those policies will be triggered by DCAE during Closed Loop operations).
2. Run time(DCAE-Policy, grabbing events and triggering policies based actions)
   1. In the first release of CLAMP, the triggering to deploy(and then effectively start the closed loop)  a blueprint will be manual (via CLAMP cockpit)
      an automatic deployment based on an event will come in future release.
   2. The CLAMP cockpit will support the following action at runtime:
      1. start (start the provisioned Closed Loop on DCAE)
      2. stop (stop a provisioned Closed loop on DCAE)

Image Removed

Image Removed

Resources

  NGUEKO Gervais-Martial (AT&T - gn422w@intl.att.com)

Other Contact/Contributor Person:

• SHACHAM Ron (AT&T - rshacham@research.att.com)
• BHATNAGAR Aayush (Reliance Jio)
• NGUYEN Trung (Amdocs)

Committers/Maintainers:

• Christophe Closset (AT&T - cc697w@intl.att.com)
• Sebastien Determe (AT&T - sd378r@intl.att.com)
• Pierre Close (AT&T - pc457b@intl.att.com)
• Eddy Hautot (AT&T - eh552t@intl.att.com)
• Xue Gao (AT&T - xg353y@intl.att.com)

Other Information's