Purpose:

Main purpose of F-GPS (a.k.a. ONAP-Valet) is, with considering new placement policies,  (1) to precisely check capacity & capability of target Cloud Region and then, (2) to determine VNF placements (i.e., target zone for each workload (VDU) of VNF).

• New placement policies include Affinity and Anti-affinity.
• Scopes of Affinity/Anti-affinity are, in a target Cloud Region, across Availability-zones and optionally, across compute hosts.
• Applications of Affinity/Anti-affinity are workloads (VDUs) within a VNF or workloads across VNFs.
• Opportunity to standardize many other placement policies (e.g., Beside Affinity/Anti-affinity, include Exclusivity, Quorum-Diversity, etc.) in VNFD and Policy.
• Integrated into OOF/HAS (maybe initially as dark mode (PoC) for evaluation over Dublin).

Owner :  Under OOF

Participating Companies: VMware (Architecture/Modelling), Intel (Architecture), IBM, AT&T

Operator Support: OOF/HAS, 5G Use Case (TBD)

Parent page: TBD

Use Case Name

5G Data Plane Performance use case:

A VNF instance has 2 workloads (e.g., 2 VM instances) that must be placed in a same zone (or compute host) because of the high throughput requirement between workloads. Meanwhile, 2 more replicas of the VNF instance must be placed in different zones (or different compute hosts) of the same Cloud Region because of the high-reliability requirements for the VNF.

To meet these requirements, each VNF instance must specify an Affinity rule for its 2 workloads. Meanwhile, the same type of workloads in those 3 VNF instances must specify an Anti-affinity rule.

5G VNF user(s) aware Placement:

Place 5G VNF in a specific DC location/zone in a distributed cloud for user(s) proximity. A single cloud control plane (Cloud Region) is managing several distributed DC locations/zones. 

Dublin Focus:

• Seed code for OpenStack cloud and evaluate in an OpenStack testbed. Later, extend to the other clouds including Azure.
• Capacity & Capability checking for an OpenStack cloud: 
  • Checking the number of zones of the target Cloud Region to solve the Anti-affinity rules.
  • Checking available capacity of each zone to solve Affinity rule.
  • Checking available host profiles of each zone to solve flavor matching (i.e., Host-Aggregates) (Stretch Goal).
• Placement decisions for Affinity and Anti-Affinity among zones of target Cloud Region. Optionally, decisions go into compute hosts (for private cloud case).
• Defining Affinity and Anti-affinity rules in Policy (Stretch Goal). Until this is ready, evaluate with a manual/hard-coded policy.
• Specifying Affinity and Anti-affinity rules in homing/placement request (Stretch Goal). Until this is ready, evaluate with a manual/hard-coded specification.
• Distributed cloud modelling immediately relevant to F-GPS - a single cloud control plane (Cloud Region) to be able manage several distributed DC locations/zones. 

• Leverage capacity alerts (significant change in capacity) from Model-driven Distributed Analytics work.

Impacted Projects 

Architecture committee suggestions

On Dec. 4, 2018

• Need end-to-end workflows: Refer to the below Workflows.
• Modeling
  • Affinity/Anti-affinity: Investigated ETSI NFV-IFA (See section 7.1.8.11 and 7.1.8.12 in  https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/011/03.01.01_60/gs_NFV-IFA011v030101p.pdf) and turns out that VNFD includes Affinity/Anti-affinity specification per DC (NFVI-PoP), Zone (Availability-zone), and compute server (NFVI-node). 
  • Distributed cloud: Each Cloud Region has multiple Availability-zones (and DCs)
• Capacity check: Fine grained, per Availability-zone (or DC).

Workflows

Flow architecture

Capacity check workflow: This can be requested in design time to determine available Availability-zones for VNF.

VNF Placement workflow

Presentation for Edge Automation Use Case