990a26ef1f
1. Claim allocations from placement first, then claim specific
resources in Resource Tracker on destination to populate
migration_context.new_resources
3. cleanup specific resources when live migration succeeds/fails
Because we store specific resources in migration_context during
live migration, to ensure cleanup correctly we can't drop
migration_context before cleanup is complete:
a) when post live migration, we move source host cleanup before
destination cleanup(post_live_migration_at_destination will
apply migration_context and drop it)
b) when rollback live migration, we drop migration_context after
rollback operations are complete
For different specific resource, we might need driver specific support,
such as vpmem. This change just ensures that new claimed specific
resources are populated to migration_context and migration_context is not
droped before cleanup is complete.
Change-Id: I44ad826f0edb39d770bb3201c675dff78154cbf3
Implements: blueprint support-live-migration-with-virtual-persistent-memory
13 lines
336 B
JSON
13 lines
336 B
JSON
{
|
|
"event_type":"instance.live_migration_rollback.start",
|
|
"payload":{
|
|
"$ref":"common_payloads/InstanceActionPayload.json#",
|
|
"nova_object.data":{
|
|
"action_initiator_user": "admin",
|
|
"task_state": "migrating"
|
|
}
|
|
},
|
|
"priority":"INFO",
|
|
"publisher_id":"nova-compute:compute"
|
|
}
|