ae53c22457
This adds the support for new style volume attachments to the swap volume operation. If the existing volume attachment (old_volume) was created using the new flow, it will have attachment_id set. Based on that the API will create a new volume attachment for the volume being swapped to and then pass that attachment to the compute over RPC. Note that we do not yet create new-style volume attachments so this is all no-op code for now. And when we do start creating new-style volume attachments, that will only be allowed when Cinder is new enough (3.27 microversion) and all compute services are upgraded, so we don't perform any nova-compute service version checks here. Once on the compute, we key off the new_attachment_id being passed from the API to tell if we should use the old or new style calls to Cinder. For example, initialize_connection and terminate_connection are replaced with attachment_update and attachment_delete. Co-Authored-By: Matt Riedemann <mriedem.os@gmail.com> Co-Authored-By: John Griffith <john.griffith8@gmail.com> Depends-On: I23391300468cc5e2f45a12d5ad8617ab48c21e6a Partially Implements: blueprint cinder-new-attach-apis Change-Id: I4b8bd01f1ffe2640fe7313213bf853d2e1bef9dd
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": 21,
|
|
"availability_zone": null,
|
|
"uuid": "fa69c544-906b-4a6a-a9c6-c1f7a8078c73"
|
|
}
|
|
},
|
|
"event_type": "service.update",
|
|
"publisher_id": "nova-compute:host1"
|
|
}
|