CLAMP videos

AMSTERDAM Videos

What is CLAMP ?

3 min video to showcase what CLAMP purpose is and how it materialize a closed loop within ONAP

CLAMP Holmes Walk through
This video (49min) walks through the setup of an Holmes Closed loop using Amsterdam release

BEIJING Videos

CASABLANCA Videos

Control Dasboard part 1 (preview): ingestion of dmaap events file

CL_dashboard_part_01.mp4

Control Loop Dashboard part 2 (preview): Kibana Dashboard

CL_dashboard_part_02.mp4

vCPE Control Loop Animation

vCPE_closed_loop_ons.mp4

Closed Loop with Spark POC

Clamp deploy on spark cluster

FRANKFURT Videos

In this release CLAMP has been completely changed because of the self-serve feature. The policy UIs are not written in the stone anymore,instead they are generated from the policy TOSCA files.

In a nutshell, these are the CLAMP features:

Get and store the microservice blueprint (DCAE) + Service data (like VNF data, Vfmodules data) from SDC distribution
Get the CDS workflow inputs from CDS during SDC CSAR installation
Store each SDC distribution in "Loop Template", they can be instantiated as a "Loop Instance"
Get and store all TOSCA policy files + PDP groups from the policy engine
Insertion/Removal of policies in the loop instance.
Each policy can be configured according to the TOSCA definition
Read TOSCA metadata section to give possible values to the user when it's possible ( VNF + VFModules data, CDS payload values)

The SDC distribution did not change since Casablanca, please check the previous video to see how to attach a DCAE blueprint defining the micro-services and distribute it to CLAMP.

Clamp-aaf.mp4

Connection to CLAMP UI

Clamp uses AAF to authenticate the user and get the different permissions.

You can either use the default certificate loaded into AAF for CLAMP Admin user or create a new user in AAF and assign the roles "org.onap.clamp.clds.admin.dev", "org.onap.clamp.clds.designer.dev", "org.onap.clamp.clds.vf_filter_all.dev" and "org.onap.clamp.service".

The default certificate can be found here: https://gerrit.onap.org/r/gitweb?p=clamp.git;a=blob;f=src/main/resources/clds/aaf/org.onap.clamp.p12;h=268aa1a3ce56e01448f8043cc0b05b5fceb5a47d;hb=HEAD

The password is: "China in the Spring"

The certificate must be loaded into your favorite browser before trying to load the CLAMP UI.

Create a loop instance from a loop template

When SDC distributes the service information to CLAMP, loop templates are created in CLAMP for each DCAE blueprint found in the CSAR.

Loop instance can be created from a loop template, each template is therefore related to a "service"

Add or Remove the policies in the loop instance

TOSCA based policies can be added or removed from the loop instance.

CLAMP gets periodically the TOSCA based policies available on the policy engine and stores them into the database, so that the user can select what policies he wants to use in the loop instance.

Configure each policy

Each policies in the loop instance must be configured by clicking on each box.

The PDP group must now also be set for the policy engine deployment.

CLAMP gets periodically the available PDP groups from the policy engine per TOSCA based policy

Submit to policy engine

In this video, we show you how to submit all the policies defined in the loop instance to the policy engine.

Deploy microservices to DCAE

In this video, we show you how to deploy the microservices defined in the loop instance (those are initially defined by the DCAE blueprint and distributed from SDC)

Stop/Restart the loop

In this video, we show you how to stop or restart the loop instance, it obviously undeploy or re-deploy all the policies from/to the policy engine.

Undeploy the loop

In this video, we show you how to undeploy the microservices from DCAE