Draft

Overall Architecture of Control Loops

DCAE - Data Collection, Analytics, and Events

DCAE is responsible for the heavy lifting of capturing alarms, traps, events, etc. for performing collection, analytics, correlation etc.
DCAE is responsible for developing a general architecture for any type of collector (eg VES), analytic (eg. Threshold Crossing), correlation engine (eg. Holmes) to be on-boarded into the platform
DCAE is responsible for deploying all DCAE Micro Services
DCAE Micro Services are responsible for enforcing Policy Decisions (see below) for configuration of those micro services for a particular Control Loop(s)

SDC

SDC is responsible for design time elements such as:
- On-boarding DCAE Micro Services
- DCAE Design Studio - implementing the design to create a generic service assurance flow to be reused when designing a service.

CLAMP

CLAMP is responsible for configuring generic service assurance flows for a specific control loop in a service
CLAMP is responsible for deploying Control Loops to the DCAE Controller
CLAMP is responsible for run-time monitoring of Control Loops
- Updating of Configuration/Operational Policies

Policy

Policy is responsible for run time decisions and enforcement for Control Loops
- Policy Decisions for the configuration of DCAE Micro Services in a control loop (enforced by DCAE Micro Services)
- Policy Decision and Enforcement of Control Loop Actions to take in response to a Control Loop Event

Controller/Orchestrators (APPC/SO/VFC)

Controllers and Orchestrators are responsible for implement a North Bound API in order for Policy to enforce a Control Loop Action