Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.


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 Blueprint. Blueprint is added to service in SDC during design phase and is distributed with service during distribution phase. Blueprint is not verified by SDC or DCAE. CLAMP checks if blueprint contains specific sections like policy-id however it's not verifying if blueprint will instantiate TCA or not. Clamp assumes it's TCA and draws closed loop flow with TCA as AT. There is no ability to use and configure your own custom analytic. Since usage of custom AT is crucial to manage vnf/pnf instance life-cycle in proper way Closed Loop components should support configuring, deploying and working with custom AT.

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


Business Requirement

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

Changes in components:

SDC

SDC needs to support adding deployment artifact called POLICY_MODEL. Policy model should be yaml file generated from microservice spec by Tosca-lab.

Policy

Now schemas are add to DB manually. Policy should support downloading csar distributed by SDC and extracting POLICY_MODEL.

POLICY should pars POLICY_MODEL artifact and using it create new Config.Micro-Service schema. User should be able to use newly created schema for creating it's own configured Policy.

Clamp

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


Contributions