NOTE: This functional requirement is combined with the parent page for Model driven Driven Control Loop Design. It is moved as a sub-page for reference.
Overview
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 BlueprintBlueprints. A Blueprint is added to a service in SDC during the design phase and is can then be distributed with the service during the distribution phase.
Blueprints are Blueprint is not verified by SDC or DCAE. CLAMP checks if a blueprint contains specific sections, like policy-id, however it 's is not verifying if blueprint the Blueprint will instantiate TCA or not. Clamp CLAMP assumes it 's is TCA and draws a closed loop flow with TCA as the AT. There is no ability to use and configure your own custom analyticAT. Since usage of a custom AT is crucial to manage vnfthe VNF/pnf PNF instance life-cycle in a proper way Closed Loop , closed loop components should support configuring, deploying and working with a custom AT.
The main problem that has to be faced is of how does other components (ClampCLAMP, Policy) should know how to configure an AT. Currently, Policy supports creating various types of policies. Policies relevant with 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
SDC needs to support adding a deployment artifact called POLICY_MODEL. Policy model should be yaml a YAML file generated from the microservice spec by ToscaTOSCA-lab.
Policy
Now Currently, schemas are add added to the DB manually. Policy should support downloading csar a CSAR distributed by SDC and extracting POLICY_MODEL.
POLICY should pars parse the POLICY_MODEL artifact and using use it to create a new Config.Micro-Service schema. User The user should then be able to use the newly created schema for creating it's their own configured Policy.
Clamp
Clamp should support creating any type of Microservice Configuration Policy using the Policy Model downloaded from Policy.