Day 1: SDC/CLAMP Create a Control Loop in a Service
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
@startuml title This is the flow for designing, configuring and deploying Control Loops actor Service_Designer participant SDC participant CLAMP actor Operator participant DCAE_SCH participant DCAE_Deployment participant DCAE_Inventory participant Policy participant CDS participant DCAE_Policy_Handler autonumber CLAMP -> Policy : Every 5 min. Get available policy models(Ops and Config). note left This Step is done asynchronously end note Service_Designer -> SDC : Create/Test/Certify service, \nwith control loop DCAE flow SDC -> CLAMP : CSAR distribution CLAMP -> DCAE_Inventory : Get DCAE Service Id based on Distributed Parameters DCAE_Inventory -> CLAMP : Rcv DCAE Service Id based on Distributed Parameters SDC -> DCAE_SCH : Blueprint distribution DCAE_SCH -> DCAE_Inventory : Save blueprint Operator -> CLAMP : Configuration of control loop note left During this Step, the Operator can opt to upload manually a policy model instead of using an existing one (periodically downloaded) end note CLAMP -> CDS: Get Actor/Actions for Operational list of Actions and payloads \nfor Operational Policies(ifif CDS CDS is the « Actor ») CLAMP -> Policy : Create Configuration and Operational Policies Policy -> DCAE_Policy_Handler : Configuration Policy(mS config.) CLAMP -> DCAE_Deployment : Trigger Deployment note left This StepStep is is involved when therethe ismicroservices noare not pre pre-deploymentdeployed ofin controlDCAE(which loopis inthe DCAEnormal case) end note @enduml |
TODO: Update UML with correct terminology. Update UML to add SDC Service Distribution
...