Skip to end of metadata
Go to start of metadata

NOTE: This functional requirement is combined with the parent page for Model Driven Control Loop Design. It is moved as a sub-page for reference.


The community ask is to make it easier to design and on-board custom DCAE analytics. Currently, AT (analytic tools) are deployed by DCAE using Cloudify Blueprints. A Blueprint is added to a service in SDC during the design phase and can then be distributed with the service during the distribution phase.

Blueprints are not verified by SDC or DCAE. CLAMP checks if a blueprint contains specific sections, like policy-id, however it is not verifying if the Blueprint will instantiate TCA or not. CLAMP assumes it is TCA and draws a closed loop flow with TCA as the AT. There is no ability to use and configure your own custom AT. Since usage of a custom AT is crucial to manage the VNF/PNF instance life-cycle in a proper way, closed loop components should support configuring, deploying and working with a custom AT.

The main problem that has to be faced is of how other components (CLAMP, Policy) should know how to configure an AT. Currently, Policy supports creating various types of policies. Policies relevant to TCA have the type Config.Micro-Service. Using it as a type of policy lets you choose the field Micro Service. This field decides about parameters that can be defined for policy and by using them Policy creates a configuration form for the user.

Business Requirement

The business requirement is to prepare ONAP Closed Loop components for configuring, deploying and working with a custom analytic tool.

Changes in components:


SDC needs to support adding a deployment artifact called POLICY_MODEL. Policy model should be a YAML file generated from the microservice spec by TOSCA-lab.


Currently, schemas are added to the DB manually. Policy should support downloading a CSAR distributed by SDC and extracting POLICY_MODEL.

POLICY should parse the POLICY_MODEL artifact and use it to create a new Config.Micro-Service schema. The user should then be able to use the newly created schema for creating their own configured Policy.


Clamp should support creating any type of Microservice Configuration Policy using the Policy Model downloaded from Policy.


  • No labels