Page Comparison

...

Deploy Edge Analytics App in Edge CloudApp
Create Kafka topic “edge-analytics-central-<id>” in DMaaP (Kafka) broker for publishing alarm from normalization microservice in ONAP format
Program DMaaP (Kafka) client in normalization microservice to publish on “edge-analytics-central-<id>”
Program DMaaP (Kafka) client in Policy to subscribe to “edge-analytics-central-<id>”

...

Develop basic service assurance microservice supporting ONAP Threshold Crossing Alert (TCA) format
- TCA application
  - TCA format explained in "Table 1: Format of the Output Alert from the cdap-tca-hi-lo Microservice"
- Policy R3 Casablanca - Control Loop Operational Policy
Supported service assurance policies on VMware product
- Host CPU usage exceeded a programmed threshold in the edge cloud
- Host Memory usage exceeded a programmed threshold in the edge cloud
- Host CPU & Memory usage exceeded a programmed thresholds in the edge cloud
- Alert reporting format
  - Will report VMs which are part of the affected host
Hardcoding of various parameters acceptable

...

Helm Chart and Dockerfile for "service-assurance" Normalization Microservice - Ramki - mostly complete
VMware Service Assurance Product Analytics API investigation for TCA w/ future proofing for Smarts - Girish/Ramki - in progress
Service Assurance repo creation - Ramki - in progress
Code development for "service-assurance" Normalization Microservice - TBD (expected to be 2 weeks or less)
- Receive TCA Alert using VMware Service Assurance Product API and publish on “edge-analytics-central-<id>”
  - Receive Alert on Kafka interface from VMware Service Assurance product
- Map from VM to relevant VNF by querying A&AI
- Program DMaaP (Kafka) client in normalization microservice to publish on “edge-analytics-central-<id>”Receive TCA Alert using VMware Service Assurance Product API and publish on “edge-analytics-central-<id>”<id>”

VMware Service Assurance Product References

...

Versions Compared