Sylvain Bauza 446d15568e 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: I03c22ff757d0ee1da9d69fa48cc4bdd036e6b13f Closes-Bug: #1561357		2016-03-24 23:07:54 +01:00
..
tasks	Stop providing force_hosts to the scheduler for move ops	2016-03-24 23:07:54 +01:00
__init__.py	Config options: centralize options in conductor api	2016-02-09 14:06:51 +00:00
api.py	Fix conductor to *really* pass the Spec obj	2016-02-24 10:20:32 +01:00
manager.py	Stop providing force_hosts to the scheduler for move ops	2016-03-24 23:07:54 +01:00
rpcapi.py	Set RPC version aliases for Mitaka	2016-03-16 09:54:49 -07:00