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) |
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
- Constraints used by Optimization Framework (OOF)
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 opaque TLV
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 TLV, besides the Cloud Region
Note 7:
- 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
End-to-end use case: Definition, Creation & Management of Network Slice
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 (hard isolation)
- Burstable (soft isolation)
- Best Effort (no isolation)
Assumption:
- This uses the current Generic VNF workflow in SO
ONAP Component | Life Cycle Phase | Enhancements |
---|---|---|
Policy | Design | |