...
Responsibilities of Projects
Any microservice Team
TODO component spec, etc.
DCAE - Data Collection, Analytics, and Events
Component Developer (Microservice Owner)
- Responsible for overall microservice functionality and containerization
- Creation of component_spec (json spec) and validation through dcae_cli utility
- Syncronization between different stateful instances (for auto-scaling support
- Policy spec/model creation Support Configuartion and policy fetch from CBS.
- Responsible for enforcing Policy Decisions
- 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)
DCAE Platform (controller)
- Platform Deployment of platform components based on ONAP deployment strategy
- Retrieval of blueprint via SDC distribution and store in DCAE inventory
- Service component deployment (and undeploy) support through CLAMP
- Registration of components in Consul for healtcheck and application state
- Provides configuration api and policy configuration via CBS
- Auto scaling of components
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.
- Generating artifacts for DCAE deployment of control loop, namely blueprint, and distributing to DCAE
- Generating artifact for CLAMP visualization and configuration of control loop, namely service template and policy TOSCA model and distributing to CLAMP
...