yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

This is working as designed. The underlying issues that require CERN to
set max_placement_results to such a low number (10 when there are ~200
hosts per cell, and ~14K hosts total in the deployment) are what we need
to focus on, like bug 1805984 for example.

** Changed in: nova
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1805989

Title:
  Weight policy to stack/spread instances and "max_placement_results"

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Weights are applyed by the scheduler.
  This means that if using "max_placement_results" with a number bellow to the existing resources,
  the weight policy will only be applied to the subset of allocation candidates retrieved by placement.

  As consequence we lose the policy to stack/spread instances.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1805989/+subscriptions