| 1 |
--- |
| 2 |
features: |
| 3 |
- | |
| 4 |
Added a new configuration option ``image_conversion_disable`` to disallow |
| 5 |
conversion between image disk format and volume format when doing |
| 6 |
certain operations. This can prevent performance problems on a |
| 7 |
cinder-volume node due to the large amount of system resources |
| 8 |
consumed during image conversion. The default value is ``False``, |
| 9 |
which corresponds to Cinder's current behavior to always attempt |
| 10 |
image conversion. |
| 11 |
|
| 12 |
This option affects three Block Storage API calls: |
| 13 |
|
| 14 |
* Upload volume to image: |
| 15 |
``POST /v3/volumes/{volume_id}/action`` with the |
| 16 |
``os-volume_upload_image`` action. This call will result in a |
| 17 |
400 (Bad Request) response when an image ``disk_format`` |
| 18 |
that would require conversion is requested. |
| 19 |
* Create a volume: |
| 20 |
``POST /v3/volumes`` with an ``imageRef`` attribute in the request |
| 21 |
body. This will result in a 202 (Accepted) response, but if the |
| 22 |
image's ``disk_format`` would require conversion to be written to |
| 23 |
the volume, the volume will go to ``error`` status. |
| 24 |
* Reimage a volume: |
| 25 |
``POST /v3/volumes/{volume_id}/action`` with the ``os-reimage`` |
| 26 |
action. This call will result in a 202 (Accepted) response, but |
| 27 |
if the image's ``disk_format`` would require conversion to be written |
| 28 |
to the volume, the volume will go to ``error`` status. |
| 29 |
|
| 30 |
In the latter two cases, an end user can determine what happened |
| 31 |
by using the `Messages API |
| 32 |
<https://docs.openstack.org/api-ref/block-storage/v3/#messages-messages>`_, |
| 33 |
which can be accessed using the `cinderclient |
| 34 |
<https://docs.openstack.org/python-cinderclient/latest/cli/details.html#cinder-message-list>`_ |
| 35 |
or `openstackclient |
| 36 |
<https://docs.openstack.org/python-openstackclient/latest/cli/decoder.html>`_. |