Dublin Control Loop Impacts

Below is the list of requirements needed for each project to satisfy the Control Loop goals in the Dublin release.

Model Driven Control Loop Requirements

Project

Requirement

Commitment

Notes

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

COMMITTED

Goal #5

Create call to Policy Lifecycle API to 1) pull a Service Component Model, and 2) create a concrete policy for the service component.

COMMITTED

Goal #6

Query Policy Lifecycle API for available Operationtional Policy Templates, Guard Policy Templates, Control Loop Coordination Templates, etc.

Stetch Goal

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)

COMMITTED

Goal #8

DCAE   

Plugin alignment (K8s, Dmaap)

COMMITTED

Goal #15

Blueprint generator and Dashboard contribution

COMMITTED

Goal #17

DCAE Policy Handler must call the Policy Lifecycle API to retrieve policies for service components as they are deployed.

AT&T Committed

Goal #9

Integration

Create method for automating tests of generic control loops

Stretch Goal

Goal #11

Not required for Dublin

 Policy 

 Support TOSCA compliant model for DCAE service components

COMMITTED

Goal #1

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.

COMMITTED

Goal #10



Self Serve Control Loop

Project

Requirement

Commitment

Notes

Project

Requirement

Commitment

Notes

DCAE

ToscaLab (python) alignment with SDC team to align on blueprint generation (k8s)

Stretch Goal

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.

Stretch Goal

Goal #20

SDC

    

Support TOSCA compliant model for DCAE service components

Stretch Goal

Goal #12

Support Policy DCAE Service Component Model in TOSCA-Lab

Stretch Goal

Goal #13

Generate K8S ready Cloudify Blueprints. 

Stretch Goal

Goal #14

SDC will need to make changes to the blueprint to reference the Policy DCAE service component Model from #1

Stretch Goal

Goal #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

Not Committed

Goal #16

DCAE Service Components and Blueprints need to be added to the service CSAR

Stretch Goal

Goal #19

No Commitment Partial Commitment Committed