Balazs Gibizer fd351903a1 Reject forced move with nested source allocation ... Both os-migrateLive and evacuate server API actions support a force flag. If force is set to True in the request then nova does not call the scheduler but instead tries to blindly copy the source host allocation to the desitnation host. If the source host allocation contains resources from more than the root RP then such blind copy cannot be done properly. Therefore this patch detects such situation and rejects the forced move operation if the server has complex allocations on the source host. There is a separate bluperint remove-force-flag-from-live-migrate-and-evacuate that will remove the force flag in a new API microversion. Note that before the force flag was added to these APIs Nova bypassed the scheduler when the target host was specified. Blueprint: use-nested-allocation-candidates Change-Id: I7cbd5d9fb875ebf72995362e0b6693492ce32051		2018-10-25 15:44:59 +02:00
..
client	Consider allocations invovling child providers during allocation cleanup	2018-10-24 17:38:06 +02:00
filters	Remove the CachingScheduler	2018-10-18 17:55:36 -04:00
weights	Change deprecated policies to policy	2018-07-27 02:20:30 +00:00
__init__.py	Improve hacking rule to avoid author markers	2014-05-05 14:35:20 +02:00
driver.py	Remove the CachingScheduler	2018-10-18 17:55:36 -04:00
filter_scheduler.py	Update RequestSpec.instance_uuid during scheduling	2018-07-19 14:50:09 -04:00
host_manager.py	Revert "Make host_aggregate_map dictionary case-insensitive"	2018-09-25 19:04:27 -04:00
manager.py	Use INFO for logging no allocation candidates	2018-09-27 10:58:30 -04:00
request_filter.py	Honor availability_zone hint via placement	2018-05-22 08:56:50 -07:00
rpcapi.py	Modify select_destinations() to return objects and alts	2017-12-07 15:01:13 +00:00
utils.py	Reject forced move with nested source allocation	2018-10-25 15:44:59 +02:00