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
- 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) - 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 and blueprint into SDC repo (Development phase)
The policy model (and blueprint?) will need to included part SDC deployment hence these artifacts must be added into SDC gerrit repository (Details to be provided)
This is required for the artifacts to included in CSAR, which CLAMP will be utilizing.
Load Policy Model into Policy (post ONAP instantiation)
Steps to be done before MS instantiation is done from CLAMP
Details to be provided
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.
Deployment from CLAMP
Details to be provided