Day 0: On-Boarding DCAE Micro Services

DCAE Micro Service On-Boarding UML

@startuml
title This is the flow for onboarding DCAE components. All components get onboarded and made available to DCAE template designer.
box "DCAE Development"
	actor DCAE_Developer
	entity DCAE_Comp_JSON
	participant DCAE_TOSCA_Tool
	entity DCAE_TOSCA
end box
box "SDC GUI" #f4c69f
	participant SDC
	database SDC_Catalog
	end box
autonumber
loop for all DCAE Components
DCAE_Developer -> DCAE_Comp_JSON : Offline creates JSON schema\nspecifying the metadata\nrequired by this component.\nInputs\nOutputs\nConfiguration
DCAE_Comp_JSON -> DCAE_TOSCA_Tool : Uses TOSCA tool to\ncreate artifact.
DCAE_TOSCA_Tool -> DCAE_TOSCA : TOSCA Artifact created.
DCAE_TOSCA -> SDC : Imports into SDC\nto onboard their\nDCAE component
SDC -> SDC_Catalog : Saved into catalog
end
@enduml

TODO: change UML for terminology

DCAE Component-spec

The DCAE component specification is a JSON file that is used to describe and configure a DCAE Micro Service component.

For a complete description, examples and details of on-boarding of DCAE Micro Services, please refer to MicroServices Onboarding.

Day 0: DCAE Design Studio Creation of Service Assurance Flows

For Beijing, the creation of Service Assurance flows are being done out-of-band using the command line tool TOSCA Lab. The service assurance flows will be pre-loaded into the SDC Catalog for Beijing. SDC is currently integrating the DCAE Design Studio as part of Beijing development.

Day 0: Importing DCAE Micro Service Policy Model

For Beijing, the DCAE Micro Service Policy Models will be pre-loaded. For development purposes, the following screen shots can be used to demonstrate how to load a model.

flow diagram/screen shots

example of a policy model

Day 1: SDC/CLAMP Create a Control Loop in a Service

flow diagram

example of policies, blueprints, api calls. etc.

Day N: Runtime Monitoring of a Control Loop