Versions Compared

Old Version 7

changes.mady.by.user Ron Shacham

Saved on

compared with

New Version Current

changes.mady.by.user Lusheng Ji

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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
    • State synchronization between different replica instances (for auto-scaling support) and state resiliency
    • Policy spec/model creation Support Configuartion and policy fetch from CBS
    • Responsible for enforcing Policy Decisions 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
    • Retrieval of configuration policy and policy updates from Policy PDP and making available in Consul
    • Service component deployment (and undeploy) support through CLAMP and other triggers, e.g. initialization.
      • Registration (deregistration) of components in Consul and/or Kubernetes platform for healtcheck and application state
      • Service registration (deregistration) with MSB when applicable
    • DMaaP resource provisioning when applicable
    • Provides configuration api and policy configuration via CBS
    • Scaling of components
  • 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.
    • 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

...