OOF Valet 2 Goal of This Presentation Introducing our proposal ONAPOOFplacementoptimization Codename Valet Possible required implementation in MultiCloud for the placementoptimization ID: 1018727
Download Presentation The PPT/PDF document "VNF Placement Optimization in ONAP" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
1. VNF Placement Optimization in ONAPOOF - Valet
2. 2Goal of This PresentationIntroducing our proposal: ONAP-OOF/placement-optimization (Codename, Valet)Possible required implementation in MultiCloud for the placement-optimization
3. 3What is the Placement Optimization?Homing for given VNF instanceSelect a cloud site (or a region)Implemented in OOF-HAS as a policy-driven homing servicePlacement for virtual servers (e.g., VMs) in each VF module of the VNF instancePrecisely check capacities & Select nodes in the cloud siteHere, a node is either a cluster of hosts (e.g., AZ, Host-Aggregate) or a compute host
4. 4VNFs Placement RequirementsBased on our experience with real VNFs, richer placement capabilities are requiredGrouping rule: affinity, anti-affinity (diversity), exclusivity, quorumEach group rule is about multiple virtual servers togetherEach virtual server can be involved in multiple grouping rulesScope of grouping rule: e.g., datacenters, AZ, power domain (rack), hostScope of application: Within a VF module, within a VNF instance, or across VNFs
5. 5VNFs Placement RequirementsRack1Host1Host2ToRRack2Host1Host2ToRRack3Host1Host2ToRCoreVM3VM5AZ1AZ2HA1HA2VM1VolVM2VM3VM4VM5VM6Anti-affinity (or Quorum) across power domainExclusivitywithina HostAffinity withinan AZValetPlacement Policies/Rules Resource data (OpenStack Nova)Example in OpenStack CloudVM1VM2VM3VM5VM6VolVM4VF Module (Heat Template)
6. 6VNFs Placement RequirementsA real VNF placement requirement:Placing a set of VNFs, each of which consists of 3 VMs, in a way of anti-affinity among VNFs, affinity among 3 VMs of each VNF, and exclusivityVMVMVMExclusivityAffinityVMVMVMAffinityVMVMVMAffinityAnti-affinityAnti-affinityAnti-affinityVNF-1VNF-2VNF-3
7. 7Why a Placement Optimization in ONAP?Consistently deal with different underlying clouds for VNFs with high-level policies/requirementsprivate, public, or hybrid cloudsdifferent platforms such as OpenStack, variant of OpenStack, Kubernetes, etc.Smoothly combining Placement with Homing
8. 8Why a Placement Optimization in ONAP?VNFs placements contains Multiple virtual servers (e.g., VMs, containers, volumes, NW Bandwidth)Their dependencies (e.g., affinity, anti-affinity, exclusivity, quorum, networking)Various scope (e.g., AZ, compute host)VM1VolVM2VM3VM4VM5VM6Anti-affinity across (AZs, power domains, or hosts)Exclusivity in a (dedicated) hostAffinity in (an AZ, a power domain, or a host)
9. 9Goals of the Placement Optimization (Valet)To connect high-level VNF placement requests into underlying cloud resources with …Translating universal requirement specification into native cloud specificatione.g., Rack-level Diversity -> Azure: Fault-Domain, AWS: Placement-Group, Exclusivity -> Azure: Isolated VM, AWS: Dedicated HostMeeting such placement requirements/policiesConstraints SolvingOptimizing the cloud resource usagesProviding precise capacity/quota check (and reservation capability)
10. 10Homing & Placement FlowSOOOF/HASFor HomingMultiCloudOpenStackPlugInOOF/ValetFor placementPolicyA&AISDNCHoming flowPlacement of VF moduleAzurePlugIn…Capacity check