DRAFT
The following functional requirements are in place for Beijing Release:
- There is no mechanism in place for automated triggering of DCAE service assurance deployment, i.e. DCAE microservice instantiation will be driven by CLAMP or be pre-deployed with the DCAE platform
- The DCAE Design Studio will not generate any policies
- CLAMP expects DCAE Design Studio to:
- Onboard any necessary microservices for the flows (together with DCAE team)
- Generate TOSCA Service Template describing the flow
- 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
- Flow type 1: Single (shared) deployment flow
- Microservice is deployed once together with DCAE, and provided with multiple configuration policies to support multiple usages.
- Example: Correlation Holmes flow
- Flow type 2: Multiple (dedicated) deployment flow
- Microservice is deployed for every usage by CLAMP
- Example: Threshold TCA flow
- In both of the above cases, the VES collector is a shared resource that is used by any downstream microservices
Terminology - TODO a separate page?
service assurance vs control loop