Edge Scoping MVP for Casablanca - ONAP Enhancements

Summary: Edge Scoping 

Cloud Infrastructure for Distributed Clouds (5G etc.) – ONAP R3+ Cloud Infrastructure Modeling; Cloud Infrastructure Aggregate Representation Classes 

Assumption for Policy, SO, OOF:

• This uses the current Generic VNF workflow in SO

Note 1: 

• Configured Capacity and Utilized (or Currently Used) Capacity are managed by the specific cloud.

Note 2:

• Cloud SW Capability example 
  • Cloud region "x" with SR-IOV, GPU, Min-guarantee support
  • Cloud region "y" with SR-IOV support
• Cloud HW Capability example 
  • Resource cluster "xa" in Cloud region "x" with SR-IOV and GPU support 
  • Resource cluster "xb" in Cloud region "x" with GPU support
  • Resource cluster "ya" in Cloud region "y" with SR-IOV support

Note 3:

• 5G Service/VNF placement example
  • Constraints used by Optimization Framework (OOF)

    • 5G CU-UP VNF location is fixed to a specific physical DC based based on subscriber group

    • 5G CU-CP VNF to 5G CU-UP VNF Data Center connectivity latency cannot exceed certain value

  • Optimization Policy used by OOF

    • Choose optimized cloud region (or instance) for the placement of 5G CU UP/CP for subscriber group based on the above constraints

Note 4:

• For the 5G Service/VNF placement example in Note 3
  • 5G CU-UP VNF maps to a specific Cloud region & Physical DC End Point
  • 5G CU-UP VNF maps to one or more Cloud region(s) 

Note 5:

• For the 5G Service/VNF placement example in Note 3
  • OOF will pass the Physical DC End Point to SO as a cloud agnostic intent

Note 6:

• For the 5G Service/VNF placement example in Note 3
  
  • SO passes the Physical DC End Point to Multi-Cloud as a cloud agnostic intent, besides the Cloud Region

Note 7:

• Cloud agnostic placement attributes are targeted to abstract the following cloud specific placement attributes
  • HPA attributes (e.g. Smart NIC Family, GPU Family) based on Cloud specific HW/SW support
  • Normalized CPU capacity for VMs/Containers based on Cloud specific HW support
    
    • Reference for CPU Normalization:  https://d1.awsstatic.com/whitepapers/Demystifying_vCPUs.df200b766578b75009ad8d15c72e493d6408c68a.pdf
  • Fine-grained Placement attributes based on Cloud specific SW support
    • e.g., Rack-level Anti-affinity-> Azure: Fault-Domain, AWS: Placement-Group 
    • e.g., Exclusivity ->                   Azure: Isolated VM, AWS: Dedicated Host 
    • e.g., Fine grained QoS ->       VMware Minimum guarantee, Kubernetes Burstable Class
• For the 5G Service/VNF placement example in Note 3
  
  • Multi-Cloud interprets cloud agnostic intent as Physical DC Endpoint and translates to cloud-specific placement attribute such as Availability Zone
    • For this example, each distributed physical DC is in a separate Availability Zone for a OpenStack-based Cloud

Cloud Infrastructure for Distributed Clouds (5G etc.) – Networking Focused (only the unique aspects from the previous section are brought out)

Note 1:

• Intent-based API example 1
  • Intent: High Performance intra-DC data plane networking with no Host CPU usage

•Realization Possibilities
•Overlay in SmartNIC
•Gateway in SmartNIC
•Overlay in ToR
•Gateway in a ToR
•Gateway in a HW appliance
•Realizations which are fixed
•Underlay maps to ToR/Network Fabric
•No CPU usage for data plane networking maps to VMs/Containers with SR-IOV support
•

Cloud Infrastructure Impact – Definition, Creation & Management of Network Slice for 5G

Edge Automation Requirement:

Support three types of slices in the Cloud Infrastructure (Definition Reference: https://kubernetes.io/docs/tasks/configure-pod-container/quality-service-pod/)

• Guaranteed Resource Slice (hard isolation) for various infra Resources (CPU/Memory/Network)
  • Max (limit), Min (request) are the same; resource guarantee is "Max"
  • Maps to 5G Applications such as Connected Car which fall in the category of ultra-reliable machine-type communications (ref. 1)
• Burstable Resource Slice (soft isolation) for various infra Resources
  • Min (request) <= Max (limit); resource guarantee is "Min"
  • Maps to Burstable Network Slice such > 1Gbps broadband which fall in the category of extreme mobile broadband (ref. 1)
• Best Effort Resource Slice (no isolation) for various infra Resources
  • No Min (request) ; resource guarantee is "None"
  • Maps to 5G Applications such as IoT which fall in the category of massive machine-type communications (ref. 1)

References:

• 1 https://metis-ii.5g-ppp.eu/wp-content/uploads/white_papers/5G-RAN-Architecture-and-Functional-Design.pdf

Note:

• Any VMs/Containers which are part of a resource slice will adhere to the specs of the resource slice

Assumption:

• This uses the new Network Slicing workflow in SO (todo confirm)

Aggregation Service

ONAP, as in R2, collects the statistics/alarms/events from workloads (VMs) and take any close loop control actions such as Heal a process, scale-out, restart etc.. In R3, infrastructure related statistics/alarms/events will be collected, generate actionable insights and take life cycle actions on the workloads.  Infrastructure statistics normally include performance counters, NIC counters, IPMI information on per physical server node basis.  To reduce the load on the ONAP, it is necessary that aggregated (summarized) information is sent to the ONAP from edge-clouds. 

As part of this activity, intention is to create aggregation micro-service that collects the data from physical nodes (over collected and other mechanisms), aggregate the information (time based aggregation, threshold based aggregation, silencing etc.,..) based on the configurable rules and export the aggregate data to DCAE.  This micro service can be instantiated by ONAP itself - one or more instances for edge-clouds at the ONAP-central itself using OOM, it could be instantiated at the edge-cloud using their own deployment tools or it could be deployed edge service providers at the regional site level.  

Impacted projects (development activities)

Life Cycle stages related functions