Table of Contents maxLevel 2
...
3rd Party Analytics Application - Dublin Scope
- Register VMware VIO (OpenStack-based) edge cloud region(s) in ONAP Central (Note: These Edge Cloud Regions support K8S)
- Deploy VMware vROps 3rd party infra analytics framework/application in target edge cloud region to monitor multiple edge cloud regions
- References:
- https://docs.vmware.com/en/VMware-vCloud-NFV-OpenStack-Edition/3.0/rn/vCloud-NFV-OpenStack-Edition-30-Release-Notes.html
- https://docs.vmware.com/en/vRealize-Operations-Manager/6.7/vrealize-operations-manager-67-reference-architecture-guide.pdf
- In vrops reference architecture this is known as multiple data centers with remote collectors.
- ONAP project impact: None
- Note: 3rd party infra analytics application configuration is out of scope for Dublin
- References:
- Deploy microservice in target edge cloud region for cloud infra Event/Alert/Alarm/Fault Normalization & Dispatching to ONAP Central
- Note: This microservice uses the Multi-VIM/Cloud project repository for development
- ONAP project impact:
- Multi Cloud project impact
- Cloud infra Event/Alert/Alarm/Fault Normalization & Dispatching microservice development
- Integrate DMaaP (Kafka) client for communication to ONAP Central
- Receive Event/Alert/Alarm/Fault from 3rd party infra analytics application
- Normalize from cloud specific Event/Alert/Alarm/Fault format to cloud agnostic (ONAP internal) Event/Alert/Alarm/Fault format
- ONAP internal format references
- Control Loop Design
- Questions: Does each control loop need a separate policy component?
Alert examples (Note: Cluster Host CPU Threshold & Memory Contention Threshold in a cloud region are defined separately)
Exemplary Alert Definition: Cluster
Standalone host has memory contention
Cluster has memory contention caused by less than half of the virtual machines
- Cluster has unexpected high CPU workload
due to overpopulation of virtual machines.
- Symptoms include the following:
- Host memory workload at warning/immediate/critical level
- Host memory contention at warning/immediate/critical level
- > 50% of child virtual machines have Virtual machine memory workload at warning /immediate/critical level
Exemplary Alert Action:
- Scale out VNF
...
- ONAP internal format references
- Dispatch Event/Alert/Alarm/Fault to ONAP central using DMaaP (Kafka) client
- Cloud infra Event/Alert/Alarm/Fault Normalization & Dispatching microservice deployment
- Develop K8S Helm chart
- Note:
- This microservice is focussed on operational workflow & and independent of the current deployment focused micoservices in multi vim/cloud.
- Cloud infra Event/Alert/Alarm/Fault Normalization & Dispatching microservice development
- Multi Cloud project impact
- Register 3rd party infra analytics application in ONAP Central (Stretch Goal)
- ONAP project impact:
- Multi Cloud impact - Below
Populate Intent in A&AI
Infra Analytics as service exemplary intent -- “Infrastructure Analytics as service for Alerts at Cluster Level and Host Level for a Cloud Region”
- Capabilities (not exhaustive) corresponding to intent in A&AI (Note: Cluster CPU Threshold & Memory Threshold are defined separately)
Cluster has memory contention caused by more than half of the virtual machines
Cluster has memory contention caused by less than half of the virtual machines
Cluster has unexpected high CPU workload
- ...
- Capabilities (not exhaustive) corresponding to intent in A&AI (Note: Cluster CPU Threshold & Memory Threshold are defined separately)
- Populate Cloud Region List in A&AI corresponding to Intent
- A&AI: Leverage existing HPA/Intent key-value pair schema
- Multi Cloud impact - Below
- ONAP project impact:
...