There is no mechanism in place for automated triggering of DCAE service assurance deployment, i.e. DCAE microservice instantiation and configuration will be driven by CLAMP
The DCAE Design Studio will not generate any policies in Beijing
CLAMP expects DCAE Design Studio to:
- Onboard any necessary microservices for the flows (together with input from DCAE, Policy and CLAMP)
- Generate TOSCA Service Template describing the different parts of the flow: source, collector, analytics, operational policy reference/placeholder
- Generate Cloudify Blueprint
- Store both service template and blueprint in SDC catalog as part of Service/Resource instance
- Distribute these service assurance artifacts for consumption by DCAE and CLAMP

Definitions

Single (shared) deployment flow
- Example: Holmes
Multiple (dedicated) deployment flow
- Example: TCA
For Holmes, as a shared deployment, do we deploy it from CLAMP or pre-deploy it together with DCAE
- If pre-deployed, is there any way that CLAMP can know its status?

Full Flow

...