Skip to end of metadata
Go to start of metadata

This is the project welcome page for CLAMP (Closed Loop Automation Management Platform)

Below are the links to the CLAMP project sub wiki pages


What is CLAMP?

How to create a Control loop  :  3 min video


Initial Project Proposal

The CLAMP project was proposed as a new initiative as part of ONAP on 5/11/17 :

Approved Project Proposal


Releases

  1. R1 Amsterdam Release  RELEASED  Q4 2017

  2. R2 Beijing Release  RELEASED    Q2 2018

  3. R3 Casablanca Release IN PROGRESS Q4 2018




Weekly Call Meetings

A Team meeting is organized every Wednesday

Weekly calls meeting minutes, agenda and schedule can be found here


Resources


Useful links and resources for the CLAMP team :


Amsterdam Integration Testing 

status :

CLAMP - SDC: tested 100%

CLAMP - policy: tested 100% (TCA model need to be updated in policy to finalize the testing)

CLAMP - UI (design of CL): 100% tested

CLAMP - DCAE: Tested successfully with latest changes in RC2 in SB01 lab during the first weekend of November (4-5)

vCPE : TCA closed loop provisionning 100% reached - Deployed status

vVOLTE : Holmes integration provisionning : Cancelled as Policy↔DCAE interface is not ready. - Deferred to Beijing R2 Release

  • No labels

5 Comments

  1. Hi Gervais-Martial Ngueko, could you highlight major differences in closed loop automation use case support between CLAMP and the proposed OOF project ?

    1. Hi, can you tell me where is the description of the OOF project, is it a R2 project ?

      1. Yes; it is in R2 proposal as part of 5G RAN deployment and optimization use cases. We could have a discussion with the lead to figure out how CLAMP and OOF fit together or expected to be independent. OOF is being discussed in the context of network slice (I presume it would be realized as a service in ONAP) optimization as well. It would be good to get a matrix identifying levels of closed loop automation. i.e. VNF level (which CLAMP addresses today...), Service level (OOF ?).

        1. My view is: OOF would provide mS on DCAE, those mS would then be available to be included in a control loop designed and managed using CLAMP. Those OOF control loop would obviously trigger appropriate optimization policy (this would be part of the control loop designed and managed via CLAMP).

          Note that currently control loop are triggered by event coming from VNF, so (automatic)scheduled trigger are not yet part of the solution.

          So the link between OOF and CLAMP for me:

          1) micro-service on DCAE dedicated to OOF usable in Control Loop

          2) specific OOF policies that would be used in OOF Control loop.


          But of course we can have discussion with OOF lead (and other people involved) to dig deeper.

  2. Hi Clamp team , Can you post the Video/Document of End-to-End Closed loop demo using CLAMP ? . It will be very much helpful .

    Thanks a lot !

    Regards,

    Karthik