Page History

...

Phase 1 (Casablanca MVP) Summary:

• Multi-Cloud Policy Framework
  • Assist OOF in target cloud region selection for VNF placement (aka homing) by summarizing cloud-specific capability, capacity & cost metrics (e.g. VMs could have different cost in different clouds, Infra High Availability (HA) for VMs in a VNF could have different cost in different clouds)

    • Cloud Agnostic Intent (Policy) Execution Workflow  - Steps 1- 6

  • Dynamically modify the cloud specific VNF deployment template based on cloud-specific realization of the specified intent (e.g. Infra HA for VMs within a VNF could have different realizations across different clouds)

    • Cloud Agnostic Intent (Policy) Execution Workflow  - Step 7

• Intent Support

  • Single realization option per Cloud Region for the specified Intent

• Major Impact Projects:
  • Multi-Cloud (Highest), OOF
  Minor Impact Projects:
  • A&AI, SO
• End-to-end use case demonstration:
  • vCPE, vDNS

Phase 2 (Casablanca Stretch Goal) Summary (Build on Phase 1 Work):

• Multi-Cloud Policy Framework
  
  • Dynamically modify the cloud specific VNF deployment template based on cloud-specific realization of the specified intent – Impact to VNF configuration 
    • E.g. High performance Intra-DC data plane networking with several realization choices
• Intent Support
  • Multiple realization options per Cloud Region for the specified Intent
• Major Impact Projects:
  • Multi-Cloud
• Minor Impact Projects:
  
  • SO, OOF, GNF Controller

References: 

 The sequence diagram below expands "Multi-Cloud/VNFM Deploy Apps" in Edge Scoping Sequence Diagram

Cloud Agnostic Intent (Policy) Workflow Summary (Phase 1 - Casablanca MVP):

Cloud Agnostic Intent (Policy) Workflow Details (Phase 1 - Casablanca MVP):

Private Cloud Setup - OpenStack-based

...

• For R3, Cloud-Agnostic Workload Deployment Policy (Intent) can be stored in the form of configuration file(s) in the OOM K8S Persistent Volumes to simplify implementation.
  • For R4 and beyond, this policy (optionally with specific realization options) will be passed from SO → MC. This is captured in the R4 and beyond workflow (Edge Scoping - Casablanca Stretch Goal/Beyond Casablanca).
• This policy is exactly the same as the policies with "deployment-intent" in the Enhanced Capacity Check & Cloud Selection Policy for Homing described in Section 2.
• An exemplary policy is depicted below.

...

• 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) is not passed in the OOF → SO API & SO → MC API
    
    • Casablanca Plan
      • Cloud-Agnostic Workload Deployment Policy (Intent) can be stored in the form of Multi-Cloud configuration file(s) in OOM K8S Persistent Volumes to simplify implementation.
    • Dublin & Beyond Potential Plan
      • Pass this policy (optionally with specific realization options) from OOF → SO. SO passes the policy and associated information transparently from SO → MC. This is captured in the R4 and beyond workflow (Edge Scoping - Casablanca Stretch Goal/Beyond Casablanca). 
• Policy-based capacity check & 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. Capacity Check for Public Clouds is not supported
    • Casablanca Plan
      • Public Clouds always pass the capacity check
    • Dublin & Beyond Potential Plan
      
      • Quota in Public Clouds - to study

  • 5. VM Instance type/VM Feature Group dollar-cost-based cloud selection 

    • Casablanca Plan

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

      • If a Multi-Cloud Plugin does not support cost based on "dollarCostEvaluationVM-Type" and/or "dollarCostEvaluationVM-FeatureGroup"

        • The workload deployment cost is computed as a fixed cost per plugin

    • Dublin & Beyond Potential Plan

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

  • 6.  The workload instance type model (Note 1 below) is not passed from OOF → MC. Rationale below.

    • Currently, the VNFC model supports only compute/memory/local storage. A comprehensive VNFC model needs to include HW generation (Intel Broadwell/Haswell, ARM etc.), HPA details (SR-IOV etc.) and more.  

    • Casablanca Plan

      • Since the VNFC model standardization is in progress, VNFC mapping to VM Instance Type (OpenStack Flavor, Azure M4 etc.) happens in the Multi-Cloud plugin through configuration. 

      • Note 1: An exception to the rule is a simple capacity check based on VM compute/memory/local storage which can be supported by the current instance type model.
    • Dublin & Beyond Potential Plan
      
      • Align with the modeling work and make progress

...