Onboarding steps for DCAE MS through SDC/Policy/CLAMP (Dublin)

With Model Driven Control Loop feature, Policy is migrating toward new design/architecture in Dublin. This requires interfacing clients (CLAMP, DCAE) to use new LC API’s and onboarding MS to use new tosca policy model. As automated generation of models and distribution between SDC and Policy is deferred to next release, certain manual steps will be required in Dublin. The steps below should be followed by any DCAE MS targeted under CL flows deployed through CLAMP.

Policy Model Creation (Development phase)

1. Create the MS specific blueprint, component_spec and associated data_format based on DCAE team specification (refer to details under DCAE wiki page - Dublin Deployment Strategy).
   Note: For components with dynamic configuration, the component spec MUST include policy schema definition (policy_editable set for required parameter exposed via policy with corresponding policy_schema defined)
2. Use SDC/ToscaLab tool as documented here to create the base policy model
   Note: If the policy model does not get generated, change the "component_type" from "docker" to "cdap" in the componentspec and retry policy model creation.

The base policy model created by the tool is not complaint to R4 model expected by Policy; following updates will be required.

Load Policy Model into SDC repo (Development phase)

The policy model will need to included part SDC deployment hence these artifacts must be added into SDC gerrit repository.

This is required for the artifacts to included in CSAR, which CLAMP will be utilizing.

The following gerrit commits were done in Dublin to load the policy types:

https://gerrit.onap.org/r/#/c/sdc/+/82846/

https://gerrit.onap.org/r/#/c/sdc/jtosca/+/84690/

https://gerrit.onap.org/r/#/c/sdc/+/86161/

https://gerrit.onap.org/r/#/c/sdc/+/86301/

Load Policy Model into Policy api repo (Development phase)

The policy type needs to be available in the policy api in order for CLAMP to be able to create policies during Control Loop creation.

https://gerrit.onap.org/r/gitweb?p=policy/api.git;a=blob;f=main/src/main/java/org/onap/policy/api/main/startstop/ApiDatabaseInitializer.java;h=27fc83a8d64c6188ac3b498a11168e9c2f15e44f;hb=refs/heads/master

Load Blueprint into SDC (post ONAP instantiation)

This will follow the same process as done in Casablanca for blueprint to be loaded, service design created and distributed to DCAE/CLAMP.

Example TCA Blueprint - https://nexus.onap.org/content/repositories/raw/org.onap.dcaegen2.platform.blueprints/R4/blueprints/k8s-tca-clampnode.yaml

Deployment from CLAMP

Details to be provided