Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/soft-affinity-for-server-group. Description: As a tenant I would like to schedule instances on the same host if possible, so that I can achieve colocation. However if it is not possible to schedule some instance to the same host then I still want that the subsequent instances are scheduled together on another host. In this way I can express a good-to-have relationship between a group of instances. End User might want to have a less strict affinity rule than what is today available in server-group API extension. With the proposed good-to-have affinity rule the End User can request nova to schedule the instance to the same host if possible. However if it is not possible (e.g. due to resource limitations) then End User still wants to keep the instances on a small amount of different host. This change would extend the existing server-group API extension with a new policy soft-affinity. When a instance is booted into a group with soft-affintiy policy the scheduler will use a new weight AffinityWeight to sort the available hosts according to the number of instances running on them from the same server-group. This new soft-affinity policy is mutually exclusive with the other existing server-group policies. Specification URL (additional information): None
*** Bug 1241864 has been marked as a duplicate of this bug. ***
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-1761.html