yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

This is closer to bug 1777591 than bug 1805984.

** Also affects: nova/queens
   Importance: Undecided
       Status: New

** Also affects: nova/stein
   Importance: Undecided
       Status: New

** Also affects: nova/rocky
   Importance: Undecided
       Status: New

** Changed in: nova/queens
       Status: New => Confirmed

** Changed in: nova/rocky
       Status: New => Confirmed

** Changed in: nova/rocky
   Importance: Undecided => Medium

** Changed in: nova/stein
   Importance: Undecided => Medium

** Changed in: nova/stein
       Status: New => Confirmed

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

Title:
  Cannot model affinity (and/or anti) with placement "limits" parameter

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) queens series:
  Confirmed
Status in OpenStack Compute (nova) rocky series:
  Confirmed
Status in OpenStack Compute (nova) stein series:
  Confirmed

Bug description:
  It is currently not possible to use affinity/anti-affinity with the
  placement "limits" parameter since if you want your instance to land
  on a node where another instance lives you cannot rely on what
  placement GET/allocation_candidates would return and this could result
  in a no valid host. Current workaround is to unset the limits
  parameter.

  We already have the same-ish problem for disabled computes
  (https://bugs.launchpad.net/nova/+bug/1805984). We could just do a
  more generic solution that fits both these cases.

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