Below is the list of requirements needed for each project to satisfy the Control Loop goals in the Dublin release.
...
Goal #10
Stretch Goal
...
| Status |
|---|
| colour | Green |
|---|
| title | COMMITTED |
|---|
|
...
| Status |
|---|
| colour | Green |
|---|
| title | COMMITTED |
|---|
|
...
| Status |
|---|
| colour | Yellow |
|---|
| title | Stretch Goal |
|---|
|
...
| Status |
|---|
| colour | Green |
|---|
| title | COMMITTED |
|---|
|
...
| Status |
|---|
| colour | Green |
|---|
| title | COMMITTED |
|---|
|
...
| Status |
|---|
| colour | Green |
|---|
| title | COMMITTED |
|---|
|
...
...
...
Model
...
...
...
Goal #2.5
...
...
...
Model Driven Control Loop Requirements
| Project | Requirement | Commitment | Notes |
|---|
| CLAMP | Automatically render UI for DCAE Service Component Policy Models to configure an instance of that analytic in a specific Control Loop | | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | COMMITTED |
|---|
|
| Goal #7#5 |
| Create call to Policy Lifecycle API to 1) pull a Service Component Model, and 2) create a concrete policy for the service component. | | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | COMMITTED |
|---|
|
| Goal #8#6 |
| Query Policy Lifecycle API for available Operationtional Policy Templates, Guard Policy Templates, Control Loop Coordination Templates, etc. | | Status |
|---|
| |
|---|
| colour | Red |
|---|
| title | NO COMMITMENTStetch Goal |
|---|
|
| Stretch Goal #7 Not required for Dublin |
| 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) | | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | COMMITTED |
|---|
|
| Goal #9#8 |
| DCAE | Plugin alignment (K8s, Dmaap) | | Status |
|---|
| colour | Green |
|---|
| title | COMMITTED |
|---|
|
| Goal #2.5#15 |
| Blueprint generator and Dashboard contribution | | Status |
|---|
| colour | Green |
|---|
| title | COMMITTED |
|---|
|
| Goal #3.5#17 |
| DCAE Policy Handler must call the Policy Lifecycle API to retrieve policies for service components as they are deployed. | Stretch Goal | Goal #10#9 |
| Integration | Create method for automating tests of generic control loops | | Status |
|---|
| |
|---|
| colour | YellowRed |
|---|
| title | Stretch Goal |
|---|
|
| Goal #12 | Policy#11 Not required for Dublin |
| Policy | Support TOSCA compliant model for DCAE service components | | Status |
|---|
| colour | Green |
|---|
| title | COMMITTED |
|---|
|
| Goal #1 | |
| | Enhance Policy SDC Distribution Application to parse CSAR for DCAE 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. | | Status |
|---|
| colour | Green |
|---|
| title | COMMITTED |
|---|
|
| Goal #6 | Enhance Policy Lifecycle API to allow automated onboarding of DCAE 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 service components to query for a decision on the appropriate configuration policy. | | Status |
|---|
| colour | Green |
|---|
| title | COMMITTED |
|---|
|
| Goal #11#10 |
Self Serve Control Loop
| Project | Requirement | Commitment | Notes |
|---|
| DCAE | ToscaLab (python) alignment with SDC team to align on blueprint generation (k8s) | | Status |
|---|
| |
|---|
| colour | RedYellow |
|---|
| title | NO COMMITMENT |
|---|
|
| Goal #15 |
| Policy | Enhance Policy SDC Distribution Application to parse CSAR for DCAE 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. | | Status |
|---|
| |
|---|
| colour | Yellow |
|---|
| title | Stretch Goal |
|---|
|
| Goal #20 |
SDC | Support TOSCA compliant model for DCAE service components | | Status |
|---|
| |
|---|
| colour | Yellow |
|---|
| title | Stretch Goal |
|---|
|
| Goal #1#12 |
| Support Policy DCAE Service Component Model in TOSCA-Lab | | Status |
|---|
| |
|---|
| colour | Yellow |
|---|
| title | Stretch Goal |
|---|
|
| Goal #2#13 |
| Generate K8S ready Cloudify Blueprints. | | Status |
|---|
| |
|---|
| colour | Yellow |
|---|
| title | Stretch Goal |
|---|
|
| Goal #2.5#14 |
| SDC will need to make changes to the blueprint to reference the Policy DCAE service component Model from #1 | | Status |
|---|
| |
|---|
| colour | Yellow |
|---|
| title | Stretch Goal |
|---|
|
| Goal #2.6#15 |
| 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 | | Status |
|---|
| |
|---|
| colour | YellowRed |
|---|
| title | Stretch GoalNot Committed |
|---|
|
| Goal #3#16 |
| DCAE Service Components and Blueprints need to be added to the service CSAR | | Status |
|---|
| |
|---|
| colour | Yellow |
|---|
| title | Stretch Goal |
|---|
|
| Goal #5#19 |
| Status |
|---|
| colour | Red |
|---|
| title | No Commitment |
|---|
|
| Status |
|---|
| colour | Yellow |
|---|
| title | Partial Commitment |
|---|
|
| Status |
|---|
| colour | Green |
|---|
| title | Committed |
|---|
|
...