...
- 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
- Policies can now be added or removed from 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
...