...
| ONAP Component | Life Cycle Phase | Enhancements |
|---|---|---|
| Policy | Design | Define Distributed Cloud Infrastructure Placement Policies (Note 3)
|
| Multi-Cloud | Deploy | Support Distributed Cloud Infrastructure Capability Discovery (Note 1, Note 2) For workload instantiation, translate cloud-agnostic Opaque TLVs intent from SO into cloud-specific placement attributes (Note 7) |
| A&AI | Deploy | Support Standardized Distributed Cloud Infrastructure Object Hierarchy & Capability Database
|
| OOF | Deploy | Execute Distributed Cloud Infrastructure Placement Policies for Optimized Service/VNF Placement across Cloud Regions (Note 4) |
| SO | Deploy | Extend SO↔OOF API to support opaque TLVs cloud agnostic intent (Note 5) |
Assumption for Policy, SO, OOF:
...
- For the 5G Service/VNF placement example in Note 3
- OOF will pass the Physical DC End Point to SO as a opaque TLVcloud 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 opaque TLVcloud agnostic intent, besides the Cloud Region
...
- 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 opaque TLV cloud agnostic intent as Physical DC Endpoint as 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 opaque TLV cloud agnostic intent as Physical DC Endpoint as and translates to cloud-specific placement attribute such as Availability Zone
Cloud Infrastructure for Distributed Clouds (5G etc.) – Networking Focused (only the unique aspects from the previous section are brought out)
| ONAP Component | Life Cycle Phase | Enhancements |
|---|---|---|
| Policy | Design | Define Distributed Cloud Infrastructure Network Realization Policies Per Cloud Region (Note 1)
|
| Multi-Cloud (MC) | Deploy | MC <-> SDN-DC (Private Cloud) or MC <-> Public Cloud interaction
|
| SO | Deploy | Option 1: (SO -> MC -> Private/Public SDN-DC) -- desired
Option 2: (SO -> SDN-C -> MC → Private/Public SDN-DC)
|
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
...
| ONAP Component | Life cycle phase | Activities |
|---|---|---|
| AAI and ESR | Deploy & Run time |
|
| AAI and ESR | Run time |
|
| Multi-Cloud | Run time |
|