Enable anti-affinity check for instance reservation

Bug #1737676 reported by Hiroaki Kobayashi on 2017-12-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Tetsuro Nakamura

Bug Description

The affinity/anti-affinity checks of Nova do not work correctly since Pike [1] because upcalls from the computes to the scheduler (or other control services) cannot occur in deployments with multiple (v2) cells [2]. These affinity/anti-affinity checks have to be enabled for instance reservation.

[1] https://docs.openstack.org/releasenotes/nova/pike.html#id10
[2] https://docs.openstack.org/nova/latest/user/cellsv2-layout.html#operations-requiring-upcalls

description: updated
Masahito Muroi (muroi-masahito) wrote :

Need a design to fix the problem though the use of placement API in Blazar is still under the discussion.

Changed in blazar:
importance: Undecided → Medium
milestone: none → rocky-3
Pierre Riteau (priteau) on 2018-09-10
Changed in blazar:
assignee: nobody → Tetsuro Nakamura (tetsuro0907)
milestone: rocky-3 → stein-2
Pierre Riteau (priteau) on 2019-01-10
Changed in blazar:
milestone: stein-2 → stein-3
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers