Below is the list of requirements needed for each project to satisfy the Control Loop goals in the Dublin release.
| Project | Requirement | Commitment | Notes |
|---|---|---|---|
| CLAMP | Automatically render UI for DCAE Micro Service Component Policy Models to configure an instance of that analytic in a specific Control Loop | NO DECISION YET | Goal #7 |
| Create call to Policy Lifecycle API to 1) pull a Micro Service Component Model, 2) create a concrete policy for the micro service component, and 3) query Policy for available policy models (Is this the same as 1?) | NO DECISION YET | Goal #8 | |
| Query Policy Lifecycle API for available Operationtional Policy Templates, Guard Policy Templates, Control Loop Coordination Templates, etc. | NO DECISION YET | Stretch Goal | |
| Use the Lifecycle API to deploy/undeploy all policies for Control Loops as they are deployed and undeployed (happens at same time as deployment of blueprints to DCAE-C) | NO DECISION YET | Goal #9 | |
| DCAE | Support TOSCA Compliant model for DCAE micro service component | NO DECISION YET | Goal #1 |
| DCAE Policy Handler must call the Policy Lifecycle API to retrieve policies for micro service components as they are deployed. | NO DECISION YET | Goal #10 | |
| Integration | Create method for automating tests of generic control loops | NO DECISION YET | |
| Policy | Enhance Policy Lifecycle API to allow automated onboarding of DCAE micro service component policy models, querying of policy models, creation of concrete policies from these models, deploy/undeploy API for the concrete policies and decision API for DCAE micro service components to query for a decision on the appropriate configuration policy. | NO DECISION YET | |
| Enhance Policy SDC Distribution Application to parse CSAR for DCAE micro service component policy models. If the model is new, the application will call the Policy Lifecycle API to create a Policy Model for that model. | NO DECISION YET | Goal #6 | |
| SDC | Support Policy DCAE Micro Service Component Model in TOSCA-Lab | NO DECISION YET | Goal #2 |
| Generate K8S ready Cloudify Blueprints. | NO DECISION YET | Goal #2.5 | |
| Support the uploading of the JSON spec for a micro service component and create a TOSCA YAML policy model and default blueprint in the SDC Catalog | NO DECISION YET | Goal #3 | |
| Micro Service Components and Blueprints need to be added to the service CSAR | NO DECISION YET | Goal #5 |