Summary: Edge Scoping
Cloud Infrastructure for Distributed Clouds
...
– ONAP R3+ Cloud Infrastructure Modeling; Cloud Infrastructure Aggregate Representation Classes
| 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 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 (Note 5) |
...
- 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
...
Cloud Infrastructure Impact – Definition, Creation & Management of Network Slice
...
for 5G
Edge Automation Requirement:
...