yahoo-eng-team team mailing list archive

[Surya Seetharaman <1827628@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: nova
     Importance: Medium
         Status: Confirmed


** Tags: placement scheduler

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

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

-- 
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):
  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