Versions Compared

Old Version 13

changes.mady.by.user Gueyoung Jung

Saved on

compared with

New Version 14

changes.mady.by.user Gueyoung Jung

Saved on

Key

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

...

  • Seed code for placement decisions in 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 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 DC. 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.
  • HAS: 1) implement new placement constraints and interact with F-GPS, 2) deal with new placement
result data
  • decisions returned from F-GPS.
Multi-VIM/Cloud
 Bin Yang


  • 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
Jimmy Forsyth

Open new API to communicate with for F-GPS for sending to obtain Availability-Zone information of each Cloud Region.

PolicyPamela Dragosh
New Support new type of homing/placement policy policies regarding Affinity, Anti-affinity, required resources is supported in of each workload (e.g., VM) on top of the current interaction with OOF/OSDF.

...