Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

Model Driven Control Loop Requirements

CLAMP  DCAE analytic policy models
ProjectRequirementCommitmentNotes
CLAMP   Automatically render UI for DCAE Analytic Service Component Policy Models to configure an instance of that analytic in a specific Control Loop

Status
colourGreen
titleCOMMITTED

Goal #7#5
Create call to Policy Lifecycle API to 1) pull an Analytic a Service Component Model,  2and 2) create a concrete policy for the analytic, and 3) query Policy for available policy models (Is this the same as 1?)Goal #8
DCAESupport TOSCA Compliant model for DCAE analyticsGoal #1
service component.

Status
colourGreen
titleCOMMITTED

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

Status
colourRed
titleStetch 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)

Status
colourGreen
titleCOMMITTED

Goal #8
DCAE   Plugin alignment (K8s, Dmaap)

Status
colourGreen
titleCOMMITTED

Goal #15
Blueprint generator and Dashboard contribution

Status
colourGreen
titleCOMMITTED

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

Status
colourYellow
titleAT&T Committed

Goal #9

IntegrationCreate method for automating tests of generic control loops

Status
colourRed
titleStretch Goal

Goal #11

Not required for Dublin

 Policy  Support TOSCA compliant model for DCAE service components

Status
colourGreen
titleCOMMITTED

Goal #1
PolicyEnhance 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
colourGreen
titleCOMMITTED

Goal #10


Self Serve Control Loop

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

Status
colourYellow
titleStretch Goal

Goal #15
PolicyEnhance 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
colourYellow
titleStretch Goal

Goal #20

SDC

    
Support TOSCA compliant model for DCAE service components

Status
colourYellow
titleStretch Goal

Goal #12
Support Policy DCAE Service Component Model in TOSCA-Lab

Status
colourYellow
titleStretch Goal

Goal #13
Generate K8S ready Cloudify Blueprints. 

Status
colourYellow
titleStretch Goal

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

Status
colourYellow
titleStretch Goal

Goal #15SDC Support Policy DCAE Analytic Model in TOSCA-LabGoal #2
Support the uploading of the JSON spec for an analytics a micro service component and create a TOSCA YAML policy model and default blueprint in the SDC CatalogGoal #3
DCAE-DS and TOSCA-Lab need to support complex Cloudify Blueprints that can combine multiple analytic micro servicesGoal #4 

Status
colourRed
titleNot Committed

Goal #16
DCAE Service Components Analytics and Blueprints need to be added to the service CSARGoal #5

Status
colourYellow
titleStretch Goal

Goal #19

Status
colourRed
titleNo Commitment
 
Status
colourYellow
titlePartial Commitment
 
Status
colourGreen
titleCommitted