...
- 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
- Cloud Agnostic Intent-based API – Example 1
- Intent: Rack-level Anti-affinity for VMs within a VNF
- Different Realization for different clouds
- OpenStack-based (open source, Wind River, VMware VIO)
- Heat Template – policy-group, anti-affinity policy
- Azure
- Fault-domain
- AWS
- Placement group
- OpenStack-based (open source, Wind River, VMware VIO)
- Cloud Agnostic Intent-based API with networking – Example 2
- Intent: Rack-level Anti-affinity for VMs within a VNF with High Performance intra-DC data plane networking
- Different Placement realization for different clouds
- OpenStack-based (open source, Wind River, VMware VIO)
- Heat Template – policy-group, anti-affinity policy
- Azure
- Fault-domain
- AWS
- Placement group
- OpenStack-based (open source, Wind River, VMware VIO)
- Networking
- Several Realization Options for Networking – not all options may be available in all clouds – the final realization choice could be based on least current resource usage or other criteria
- Overlay in DPDK-based switch/router
- Gateway in DPDK-based switch/router
- Overlay in SmartNIC - implies SR-IOV is enabled in VMs
- Gateway in SmartNIC
- Overlay in ToR - implies SR-IOV is enabled in VMs
- Gateway in ToR
- Gateway in a HW appliance
- The final choice is translated to cloud specific attributes
- Several Realization Options for Networking – not all options may be available in all clouds – the final realization choice could be based on least current resource usage or other criteria
- 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
- Multi-Cloud interprets cloud agnostic intent as Physical DC Endpoint and translates to cloud-specific placement attribute such as Availability Zone
...
- Cloud Agnostic Intent-based API example 1
- Intent: High Performance intra-DC data plane networking with no Host CPU usage
- Several Realization Options – the final realization choice could be based on least current resource usage or other criteriaRealization 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 Agnostic Intent-based API example 2
- Intent: High Performance intra-DC data plane networking
- Several Realization Options – the final realization choice could be based on least current resource usage or other criteriaRealization Possibilities
- Overlay in DPDK-based switch/router
- Gateway in DPDK-based switch/router
- Overlay in ToR
- Gateway in ToR
- Gateway in a HW appliance
- Realizations which are fixed
- Underlay maps to ToR/Network Fabric
- HW-assisted data plane maps to VMs/Containers with SR-IOV support
...