You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Summary: Edge Scoping 

Cloud Infrastructure for Distributed Clouds: ONAP R3+ Cloud Infrastructure Modeling; Cloud Infrastructure Aggregate Representation Classes 


ONAP ComponentLife Cycle PhaseEnhancements
PolicyDesign

Define Distributed Cloud Infrastructure Placement Policies (Note 3)

  • Leverage Standardized Distributed Cloud Infrastructure Object Hierarchy & Capabilities from A&AI
Multi-CloudDeployImplement Distributed Cloud Infrastructure Capability Discovery (Note 1, Note 2)
A&AIDeploy

Implement Standardized Distributed Cloud Infrastructure Object Hierarchy & Capability Database

  • Loose coupling between HW objects (private cloud) and SW objects (private and public clouds)
  • Includes Standardized Capabilities across clouds & Capabilities unique to certain clouds

The Multi-Cloud Distributed Cloud Infrastructure Capability Discovery process will populate the aforementioned database

OOFDeployExecute Distributed Cloud Infrastructure Placement Policies for Optimized Service/VNF Placement across Cloud Regions (Note 4)

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

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) 

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 ComponentLife Cycle PhaseEnhancements
PolicyDesign













































  • No labels