bbe0f313bd
Allow Cinder to use external events to signal a volume extension. 1) Nova will then call os-brick to perform the volume extension so the host can detect its new size. 2) Compute driver will resize the device in QEMU so instance can detect the new disk size without rebooting. This change: * Adds the 'volume-extended' external event. The event tag needs to be the extended volume id. * Bumps the latest microversion to 2.51. * Exposes non-traceback instance action event details for non-admins on the microversion. This is needed for the non-admin API user that initiated the volume extend operation to be able to tell when the nova-compute side is complete. Co-Authored-By: Matt Riedemann <mriedem.os@gmail.com> Blueprint: nova-support-attached-volume-extend Change-Id: If10cffd0dc4c9879f6754ce39bee5fae1d04f474
18 lines
860 B
YAML
18 lines
860 B
YAML
---
|
|
features:
|
|
- |
|
|
It is now possible to signal and perform an online volume size change
|
|
as of the 2.51 microversion using the ``volume-extended`` external event.
|
|
Nova will perform the volume extension so the host can detect its new size.
|
|
It will also resize the device in QEMU so instance can detect
|
|
the new disk size without rebooting.
|
|
|
|
Currently only the libvirt compute driver with iSCSI and FC volumes
|
|
supports the online volume size change.
|
|
- |
|
|
The 2.51 microversion exposes the ``events`` field in the response body for
|
|
the ``GET /servers/{server_id}/os-instance-actions/{request_id}`` API. This
|
|
is useful for API users to monitor when a volume extend operation completes
|
|
for the given server instance. By default only users with the administrator
|
|
role will be able to see event ``traceback`` details.
|