...
- For the 5G Service/VNF placement example in Note 3
- SO passes the Physical DC End Point to Multi-Cloud as a opaque TLV, 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 (e.g. affinity, anti-affinity, specific physical DC) based on Cloud specific SW support
- For the 5G Service/VNF placement example in Note 3
- Multi-Cloud interprets opaque TLV as Physical DC Endpoint as 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 opaque TLV as Physical DC Endpoint as translates to cloud-specific placement attribute such as Availability Zone
...
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)
- Burstable Resource Slice (soft isolation)
- Best Effort Resource Slice (no isolation)
Assumption:
- This uses the current Generic VNF new Network Slicing workflow in SO (todo)
ONAP Component | Life Cycle Phase | Enhancements |
---|---|---|
Policy | Design | Define Distributed Cloud Infrastructure Placement Policies for |