Below is the list of requirements needed for each project to satisfy the Control Loop goals in the Dublin release.
I need help in translating goal #6 into crisp requirements that can be used by project teams.
| Project | Requirement | Commitment | Notes |
|---|---|---|---|
| CLAMP | Automatically render UI for DCAE Analytic 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 an Analytic Model, 2) create a policy for the analytic, and 3) query Policy for available policy models (Is this the same as 1?) | NO DECISION YET | Goal #8 | |
| 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 analytics | NO DECISION YET | Goal #1 |
| DCAE Policy Handler must call the Policy Lifecycle API to retrieve policies for analytics 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 analytic policy models | NO DECISION YET | |
| SDC | Support Policy DCAE Analytic Model in TOSCA-Lab | NO DECISION YET | Goal #2 |
| Support the uploading of the JSON spec for an analytics micro service and create a TOSCA YAML policy model and default blueprint in the SDC Catalog | NO DECISION YET | Goal #3 | |
| DCAE-DS and TOSCA-Lab need to support complex Cloudify Blueprints that can combine multiple analytic micro services | NO DECISION YET | Goal #4 | |
| Analytics and Blueprints need to be added to the service CSAR | NO DECISION YET | Goal #5 |