| 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 |
| 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 |
| Query Policy Lifecycle API for available Operationtional Policy Templates, Guard Policy Templates, Control Loop Coordination Templates, etc. | | Status |
|---|
| |
|---|
| colour | Red |
|---|
| title | NO COMMITMENT |
|---|
|
| 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) | | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | COMMITTED |
|---|
|
| Goal #9 |
| DCAE | DCAE Policy Handler must call the Policy Lifecycle API to retrieve policies for service components as they are deployed. | | Status |
|---|
| |
|---|
| colour | Yellow |
|---|
| title | Pending commit (Resource) |
|---|
|
| Goal #10 Stretch Goal |
| | ToscaLab (python) alignment with SDC team to align on blueprint generation (k8s) | | Status |
|---|
| |
|---|
| colour | Yellow |
|---|
| title | Pending commit (Resource) |
|---|
|
| Goal#2.5 |
| | Plugin alignment (K8s, Dmaap) | | Status |
|---|
| |
|---|
| colour | Yellow |
|---|
| title | Pending commit (Resource) |
|---|
|
| Goal#2.5 |
| | Blueprint generator and Dashboard contribution | | Status |
|---|
| |
|---|
| colour | Yellow |
|---|
| title | Pending commit (Resource) |
|---|
|
| Goal#3.5 |
| Integration | Create method for automating tests of generic control loops | | Goal #12 |
| Policy | 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 |
| 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 |
| Support TOSCA compliant model for DCAE service components | | Status |
|---|
| colour | Green |
|---|
| title | COMMITTED |
|---|
|
| Goal #1 |
| SDC | Support TOSCA compliant model for DCAE service components | | Goal #1 |
| Support Policy DCAE Service Component Model in TOSCA-Lab | | Goal #2 |
| SDC will need to make changes to the blueprint to reference the Policy DCAE service component Model from #1 | | Goal #2.6 |
| Generate K8S ready Cloudify Blueprints. | | 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 | | Goal #3 |
| DCAE Service Components and Blueprints need to be added to the service CSAR | | Goal #5 |