9868a4d9c1
We need to do this so we can have a migration uuid at the time we call to scheduler to allocate for the new host. This just does the plumbing through the RPC layers. The compute-side code can already tolerate a migration having been already created for things like live migration, so we just have to plumb it through. Related to blueprint migration-allocations Change-Id: I6bc6d28655368084f08fed9c4f56a285b7063338
24 lines
709 B
JSON
24 lines
709 B
JSON
{
|
|
"priority": "INFO",
|
|
"payload": {
|
|
"nova_object.namespace": "nova",
|
|
"nova_object.name": "ServiceStatusPayload",
|
|
"nova_object.version": "1.1",
|
|
"nova_object.data": {
|
|
"host": "host1",
|
|
"disabled": false,
|
|
"last_seen_up": "2012-10-29T13:42:05Z",
|
|
"binary": "nova-compute",
|
|
"topic": "compute",
|
|
"disabled_reason": null,
|
|
"report_count": 1,
|
|
"forced_down": false,
|
|
"version": 23,
|
|
"availability_zone": null,
|
|
"uuid": "fa69c544-906b-4a6a-a9c6-c1f7a8078c73"
|
|
}
|
|
},
|
|
"event_type": "service.update",
|
|
"publisher_id": "nova-compute:host1"
|
|
}
|