...
In addition to individual infrastructure level telemetry, the infrastructure cloud platform presents aggregate view as a provider of resources including available, used, and step-size; allocations assigned including reservations, limits, and share; and utilization to represent current resource consumptions.
Key Business Requirements
To support latency-sensitive, high-bandwidth network functions and applications driven by 5G, Edge Computing, VoLTE use cases some of the key requirements from a Cloud Infrastructure perspective are
1) A single Cloud Region needs to be able to manage multiple distributed (typically Edge) physical DCs
2) Standardized representation of Multi-vendor Cloud Object Hierarchy
- Aggregate objects (Cloud Region, Tenants, DCI Overlay etc.)
- Atomic objects (VMs, Containers etc.)
- Resource (CPU, Memory, Network etc.) allocation statistics and resource utilization metrics
3) Standardized representation of Multi-vendor Cloud Analytics
- Events (E.g. VM Power On/Off),
- Alerts (E.g. Cloud Region CPU Usage exceeds threshold) and
- Faults (E.g. Loss of Redundancy from a Host NIC perspective)
- Policies for correlating between various Events, Alerts, Faults
4) Near-real-time Streaming Data Management
- Resource (CPU, Memory, Network etc.) Utilization Metrics
- Analytics (Events/Alerts/Faults)
5) Inter-Cloud (typically Edge) Workload (especially Data Plane) Placement/Scheduling/Change Management decisions to leverage metrics and analytics information at an aggregate object level
Infrastructure Domains
As a general convention, infrastructure (NFV etc.) is partitioned into high level domains to represent various infrastructure resources metrics such as cpu, memory, disk, network, and various hardware and technology capability extensions.
...