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
Design part in SDC
Step2-SDC_Push_Service_To_Test.mp4
Step3-SDC_Approve_Service_In_Test.mp4
Distribution to CLAMP
Step4-SDC_Distribute_Service.mp4
Step5-CLAMP_Check_Distribution.mp4
Configure Closed loop in CLAMP UI
Step6-CLAMP_Configure_ClosedLoop.mp4
Submit Configuration and Operational Policies to Policy Engine
Step7-CLAMP_Submit_ClosedLoop.mp4
Step8-POLICY_Check_Policies.mp4
Deploy/Control the Closed Loop on DCAE
Step9-CLAMP_Deploy_ClosedLoop.mp4
Step10-CLAMP_Deployment_Operations.mp4
CASABLANCA Videos
Control Dasboard part 1 (preview): ingestion of dmaap events file
Control Loop Dashboard part 2 (preview): Kibana Dashboard
vCPE Control Loop Animation
Closed Loop with Spark POC
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.
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 reach the CLAMP UI.
Create a loop from a loop template
In this video, we show you how to see the loop templates distributed from SDC to CLAMP.
You can create a loop instance from a loop template, it always related to a "service"
Create loop from loop template
Add/remove the policies wanted in the loop
In this video, we show you how to add or remove tosca based policies.
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.
Add/remove operatinal policies
Edit each policy settings
In this video, we show you how to edit the policy settings for each policy defined in the loop instance.
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 policy type
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