Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Dublin and Beyond

Deployment Automation Workflow:

  • Init
    1. Deploy Normalization Microservice as part of ONAP Central
  • On Demand
    1. Deploy Edge Analytics App in Edge Cloud
    2. Create Kafka topic “edge-analytics-central-<id>” in DMaaP (Kafka) broker for publishing alarm from normalization microservice in ONAP format
    3. Program DMaaP (Kafka) client in normalization microservice to publish on “edge-analytics-central-<id>”
    4. Program DMaaP (Kafka) client in Policy to subscribe to “edge-analytics-central-<id>”

 Operational Workflow:

  • Support the following alerts
    • Host Aggregate/Cluster CPU usage exceeded a programmed threshold in the edge cloud
    • Host Aggregate/Cluster Memory usage exceeded a programmed threshold in the edge cloud
    • Host Aggregate/Cluster CPU & Memory usage exceeded a programmed thresholds in the edge cloud
  • ONAP Central normalization microservice receives alerts from Edge Analytics App through REST interface
  • ONAP Central normalization microservice publishes the above alerts on “edge-analytics-central-<id>” DMaaP (kafka) topic in ONAP format mapping from VM to relevant VNF by querying A&AI
  • Policy receives alerts on “edge-analytics-central-<id>” DMaaP (kafka) topic in ONAP format (leverage the current format between DCAE TCA App and Policy -- https://wiki.onap.org/display/DW/TCA+application)
    • Policy to perform VNF scale out

 Assumptions:

  • Edge Cloud supports OpenStack and K8S
  • Edge Analytics App is manually configured – configuration automation involves APP-C and out of scope for this effort
  • ONAP Central Normalization microservice is a separate repo in multi-cloud

Dublin Scope

Goal

Stretch Goals

  • vRops integration testing
  • ONAP Lab Integration 
  • Create Kafka topic “edge-analytics-central-<id>” in DMaaP (Kafka) broker for publishing alert from "multicloud-service-assurance" normalization microservice in ONAP TCA format 

Key Work Items

  • Helm Chart and Dockerfile for "multicloud-service-assurance" Normalization Microservice  - Ramki
  • vRops Analytics API investigation for TCA w/ future proofing for Smarts - Girish/Ramki
  • Code development for "multicloud-service-assurance" Normalization Microservice - TBD
    • Program DMaaP (Kafka) client in normalization microservice to publish on “edge-analytics-central-<id>”
    • Receive TCA Alert using vROps API and publish on “edge-analytics-central-<id>”


  • No labels