Versions Compared

Old Version 32

changes.mady.by.user Gueyoung Jung

Saved on

compared with

New Version 33

changes.mady.by.user Gueyoung Jung

Saved on

Key

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

...

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 or compute host 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 availabilityAvailability-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 for evaluation in over Dublin).

Owner :

...

 Under OOF (TBD)

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

...

Showcase VNFTest EnvironmentIntegration Team Liaison
Core/Data place VNFs in 5GTBD

OOF

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.

...

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) as policies and VNFD model.
  • HAS: 1) implement new placement constraints and interact with F-GPS, 2) deal with new placement decisions returned from F-GPS.
Multi-VIM/Cloud
 Bin Yang


  • Collect Availability-Zone zone capacity data from Clouds.
  • Open new API to communicate with F-GPS for per Availability-Zone 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
Jimmy Forsyth

  • Open (new) API for F-GPS to obtain Availability-Zone zone information of each Cloud Region.
  • Distributed cloud modelling immediately relevant to F-GPS - a single cloud control plane to be able manage several distributed DC locations/zones. 

...

  • Need end-to-end workflows: Refer to the below Workflows.
  • Modeling
  • Capacity check: Fine grained, per Availability-zone (or DC).

...

View file
nameF-GPS workflows.pdf
height250

VNF Placement workflow

View file
nameF-GPS placement workflow.pdf
height250

Capacity check workflow

View file
nameF-GPS capacity check workflow.pdf
height250
 

...