Stop providing force_hosts to the scheduler for move ops
Since now we provide the original RequestSpec for move operations (unshelve,
live-migrate and evacuate), it can also provide the original force_hosts/nodes
to the scheduler.
In that case, it means that if an admin was asking to boot an instance forcing
to an host, a later move operation could then give again the forced value and
then wouldn't permit to get a different destination which is an issue.
TBH, that is not a problem for live-migrate and evacuate that do provide an
optional host value (which bypasses then the scheduler) but since unshelve
is not having this optional value, it would mean that we could only unshelve
an forced instance to the same host.
Reviewed: https:/ /review. openstack. org/297387 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=446d15568e0 0a483d909dc5c56 5d70baf29179ad
Committed: https:/
Submitter: Jenkins
Branch: master
commit 446d15568e00a48 3d909dc5c565d70 baf29179ad
Author: Sylvain Bauza <email address hidden>
Date: Thu Mar 24 23:07:54 2016 +0100
Stop providing force_hosts to the scheduler for move ops
Since now we provide the original RequestSpec for move operations (unshelve,
live-migrate and evacuate), it can also provide the original force_hosts/nodes
to the scheduler.
In that case, it means that if an admin was asking to boot an instance forcing
to an host, a later move operation could then give again the forced value and
then wouldn't permit to get a different destination which is an issue.
TBH, that is not a problem for live-migrate and evacuate that do provide an
optional host value (which bypasses then the scheduler) but since unshelve
is not having this optional value, it would mean that we could only unshelve
an forced instance to the same host.
Change-Id: I03c22ff757d0ee 1da9d69fa48cc4b dd036e6b13f
Closes-Bug: #1561357