anti-affinity policy only honored on boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Sylvain Bauza |
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.
Changed in nova: | |
assignee: | nobody → Russell Bryant (russellb) |
status: | New → Confirmed |
importance: | Undecided → Medium |
no longer affects: | nova/icehouse |
no longer affects: | nova/juno |
Changed in nova: | |
assignee: | Russell Bryant (russellb) → Sylvain Bauza (sylvain-bauza) |
Changed in nova: | |
assignee: | Sylvain Bauza (sylvain-bauza) → Michael Still (mikalstill) |
Changed in nova: | |
assignee: | Michael Still (mikalstill) → Sylvain Bauza (sylvain-bauza) |
Changed in nova: | |
milestone: | none → kilo-1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | kilo-1 → 2015.1.0 |
Related fix proposed to branch: master /review. openstack. org/128054
Review: https:/