yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => kilo-1

-- 
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/1379451

Title:
  anti-affinity policy only honored on boot

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  If you create a server group with an anti-affinity policy, it is only
  honored during the initial boot.  If you do a cold migrate, live
  migrate, or evacuate where the scheduler is picking the destination,
  it seems reasonable to expect that the scheduler will continue to
  honor that policy.  However, it does not.

  The reason for this has to do with an implementation optimization in
  the scheduler.  It skips all of the group checking if the 'group' hint
  is not present.  Since scheduler hints are only kept around for the
  initial boot, this doesn't work.  One solution would be to persist
  scheduler hints.  However, a shorter term fix specifically for server
  groups is to always check the database for group membership when the
  server group filters are enabled.

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