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
..
__init__.py	move all tests to nova/tests/unit	2014-11-12 15:31:08 -05:00
test_base.py	Create class hierarchy for tasks in conductor	2015-07-30 17:35:56 +03:00
test_live_migrate.py	Reject forced move with nested source allocation	2018-10-25 15:44:59 +02:00
test_migrate.py	Reject forced move with nested source allocation	2018-10-25 15:44:59 +02:00