Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »


Design


Step 1: Design the Control Loop Flow in SDC (DCAE-Design Studio)

What will be the scope of control loop flows in Casablanca:

  • Which microservices will be used?
  • Will flows contain more than one microservice node?
  • Will microservices be capable of receiving more than one configuration policy?
  • Will the singleton vs. dynamically deployed distrinction be described in the TOSCA?
  • Will collectors be deployed dynamically or statically?
  • Will DCAE Design Studio allow for the piecing together of flows in Casablanca?


Step 2: Generate artifacts

  • Cloudify TOSCA is different from standard TOSCA
  • Many details of deployment are not relevant to CLAMP
  • For these reasons, there should be parallel artifacts: Service Template and Blueprint
    • Service Template is for use by CLAMP and is not Cloudify-specific
    • Based on Service Template, any deployment of the parallel Blueprint should be possible from CLAMP
    • Service Template and Blueprint must define the same inputs
  • Will DMaaP topics be provisioned at deploy time?
    • If a new topic is created, this would require CLAMP dashboard awareness in order to monitor the messages on that topic
    • How will credentials for DMaaP be provisioned?


Example Service Template
 
Example Blueprint
 
Example Policy TOSCA Model
 


Step 3: Distribute artifacts


Step 4: CLAMP Processes artifact

Assumptions of how parsing will be done

Getting TOSCA model of Policy through Policy API


Configure


How will this be affected by changes in Policy Lifecycle APIs?  https://wiki.onap.org/display/DW/Policy+Platform+API

Deploy


Update


Suspend


  • No labels