Page Comparison

Summary: Edge Scoping 

...

• 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 to be fixed to a specific physical DC based on 5G DU, bounded by a max distance from 5G DU

  • Optimization Policy used by OOF

    • Choose optimized cloud region (or instance) for the placement of 5G CU UP for subscriber group based on the above constraints

Note 4:

• For the 5G Service/VNF placement example in Note 3
  • 5G CU-UP VNF preferably maps to a specific Cloud region & Physical DC End Point 

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 data

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 data, besides the Cloud Region

Cloud-agnostic Placement/Networking & Homing Policies (Phase 1 - Casablanca MVP, Phase 2 - Stretch Goal)

...

• Deployment-Intent 
  • 1. "Infrastructure Resource Isolation for VNF" – { "qosProperty": { {"Burstable QoS": "TRUE", "Burstable QoS Oversubscription Percentage": "25"} } }
    
    • Casablanca Plan
      • Only certain pre-defined over-subscription values are allowed to reflect practical deployment and simplify implementation 
    • Dublin & Beyond Potential Plan
      
      • Creating instance types on demand for private clouds - to study
  • 2. Cloud-agnostic Workload Deployment Policy (Intent) 
    
    • Casablanca Plan
      • Cloud-Agnostic Workload Deployment Policy (Intent) can be directly mapped to specific realization (e.g. OpenStack Flavor, Azure Instance Type) to simplify implementation.  
    • Dublin & Beyond Potential Plan
      • VIM Capability Discovery to populate Intent in A&AI (similar aligning taking into account Cloud selection policy based on cost specific to Intent (leverage similarities to HPA label discovery supported since R2)
        • VIM selection – Intent to be populated in A&AI for capability matching 
        • VIM Deployment realization - Intent(s) to specific realization mapping (e.g. OpenStack Flavor, Azure Instance Type) to be populated in A&AI 
• Policy-based & cloud-selection
  • 3. Tenant Information is not passed in the OOF → MC API
    • Casablanca Plan
      • The tenant information is derived from a simple mapping function per <cloud owner, cloud region>
        • A simple mapping would be a tenant per <cloud owner, cloud region> as part of Multi-VIM plugin configuration.
        • Need to make sure that this scheme is synchronous with the SO → MC API path
    • Dublin & Beyond Potential Plan
      
      • Pass Tenant Information per <cloud owner, cloud region> in the OOF → MC API
  • 4. VM Instance type/VM Feature Group dollar-cost-based cloud selection 

    • Casablanca Plan

      • By default, the workload deployment cost is computed as a fixed cost per plugin

        • VM Instance type/VM Feature Group dollar-cost-based cloud selection is optional for all Multi-Cloud Plugins

    • Dublin & Beyond Potential Plan

      • Deep dive further on dollar-cost-based cloud selection models/implementation for public/private clouds 
        
        

...

ONAP Edge Analytics with DCAE/DMaaP independent of closed loop (Beyond Casablanca)

Value

• 5G Analytics
  
  

...