Enable migration to rely on nova-scheduler
This patch removes the requirement to specify destination node, for migrate action. There can be some strategies that wants to rely on nova-scheduler for destination node. It will not impact any current strategy behavior. Change-Id: Ia12b2f0b8369e632a7959b28e485d86b6cff83e9 Closes-Bug: #1691056
This commit is contained in:
@@ -117,15 +117,14 @@ class TestMigration(base.TestCase):
|
||||
self.assertRaises(jsonschema.ValidationError,
|
||||
self.action.validate_parameters)
|
||||
|
||||
def test_parameters_exception_destination_node(self):
|
||||
def test_parameters_destination_node_none(self):
|
||||
parameters = {baction.BaseAction.RESOURCE_ID:
|
||||
self.INSTANCE_UUID,
|
||||
'migration_type': 'live',
|
||||
'source_node': 'compute-1',
|
||||
'destination_node': None}
|
||||
self.action.input_parameters = parameters
|
||||
self.assertRaises(jsonschema.ValidationError,
|
||||
self.action.validate_parameters)
|
||||
self.assertTrue(self.action.validate_parameters)
|
||||
|
||||
def test_parameters_exception_resource_id(self):
|
||||
parameters = {baction.BaseAction.RESOURCE_ID: "EFEF",
|
||||
|
||||
Reference in New Issue
Block a user