Overview
The community ask is to be able to design Control Loops based on model.
Which means that you should be able to define model for the Control Loop flow
which implies the modeling of the micro-services and policies that are composing
the flow.
The definition of those models would be done in SDC(DCAE-DS) and somehow distributed to other
components of the control loop ecosystem: Policy, CLAMP, DCAE,....
Business Requirement
The business requirement is make it easier to design and re-use Control Loop
in various services with minimum to development.
Benefits:
- Reduce development cycle when introducing new analytics to Control Loop.
- Reduce development cycle when introducing new policies as part of Control Loop
Participating Companies
Dublin Goals
- Define a Tosca "policy-model" which are models for Configuration policies(policies configuring µS of a Control Loop).
- ability to onboard those policy-model in SDC catalog
- Distribute policy-model to CLAMP, Policy
- Automatic UI rendering of the policy-model so that you can create configuration policies from any components (e.g: Policy Engine, CLAMP)
Contributions