Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Main purpose of F-GPS (a.k.a. Valet) is, with considering placement rules,  (1) to precisely check capacity & capability of target DC or edge site Cloud Region and then, (2) to determine VNF placements (i.e., target zone or compute host for each workload of VNF).

  • Placement rules include Affinity and Anti-affinity.
  • Scopes of placement rules are, in a target DC or edge siteCloud Region, across availability-zones and optionally, across compute hosts.
  • Applications of placement rules are workloads within a VNF or workloads across VNFs.
  • Opportunity to standardize many other placement rules (e.g., Exclusivity, Quorum-Diversity) in VNFD and Policy.
  • Integrated into OOF/HAS (maybe initially as dark mode for evaluation in Dublin).

Owner :  TBD

Participating Companies: Intel, VMware, AT&T

...

Showcase VNFTest EnvironmentIntegration Team Liaison
5G VNF teaming (TBD)TBD

TBDOOF

5G VNFs teaming use case: A VNF instance has 2 workloads (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 DC Cloud Region because of the high-reliability requirements for the VNF.

...

  • Seed code for placement decisions in for OpenStack cloud and evaluate in an OpenStack testbed for this version. Later, extend to the other clouds including Azure and AWS.
  • Capacity & Capability checking for an OpenStack cloud: 1) Checking the number of zones of the target DC Cloud Region to solve the Anti-affinity rules, 2) Checking available capacity of each zone to solve Affinity rule, 3) Checking available host profiles of each zone to solve flavor matching (i.e., Host-Aggregates).
  • Placement decisions for Affinity and Anti-Affinity among zones of target DCCloud 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.

...

ProjectPTLJIRA Epic / User Story*Requirements
OOFSarat Puthenpura
  • OSDF: support new homing/placement constraints (Affinity, Anti-affinity, and resources per workload (e.g., VM) of VNF).
  • HAS: 1) implement new placement constraints and interact with F-GPS, 2) deal with new placement decisions returned from F-GPS.
Multi-VIM/Cloud


  • Collect Availability-Zone capacity data from Clouds.
  • Open new API to communicate with F-GPS for per Availability-Zone capacity checking.
  • Enable the placement decisions (e.g., update Heat env in OpenStack case) to send them to Cloud orchestrator (e.g., OpenStack) via plugins.
A&AI
  • Open (new) API for F-GPS to obtain Availability-Zone information of each Cloud Region.
PolicyPamela Dragosh
  • Support new type of homing/placement policies regarding Affinity, Anti-affinity, required resources of each workload (e.g., VM) on top of the current interaction with OOF/OSDF.


Testing

Current Status