Draft

Overall Architecture of Control Loops

  • TODO use Beijing ref arch to highlight projects

Responsibilities of Projects


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

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

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


  • No labels