Debian Codegraph @

releasenotes/notes/add-volume-re-image-api-6f02dcefd4975a66.yaml

raw
1 ---
2 features:
3 - |
4 Add microversion 3.68 to support the ability to re-image a volume with a
5 specific image. Specify the ``os-reimage`` action in the request body.
6
7 A volume in ``available`` or ``error`` status can be re-imaged directly.
8 To re-image a volume in ``reserved`` status, you must include the
9 ``reimage_reserved`` parameter set to ``true``. When reimaging a volume,
10 the volume state will be changed to ``downloading`` first.
11
12 Note that this is a destructive action, that is, all data currently
13 contained in a volume is destroyed when the volume is re-imaged.
14
15 Two new policies are introduced to govern this functionality:
16
17 * ``volume:reimage`` - users who satisfy this policy may re-image a volume
18 in status ``available`` or ``error``
19 * ``volume:reimage_reserved`` - users who satisfy this policy may re-image
20 a volume in status ``reserved``
21
22 The default setting for both policies allow an administrator or the volume
23 owner to perform the associated action. See the `Policy configuration
24 <https://docs.openstack.org/cinder/yoga/configuration/block-storage/policy.html>`_
25 documentation in the `Cinder Service Configuration` guide for details.
26
27 upgrade:
28 - |
29 Two new policies are introduced to govern the volume reimage functionality
30 introduced with microversion 3.68:
31
32 * ``volume:reimage`` - users who satisfy this policy may re-image a volume
33 in status ``available`` or ``error``
34 * ``volume:reimage_reserved`` - users who satisfy this policy may re-image
35 a volume in status ``reserved``
36
37 The default setting for both policies allow an administrator or the volume
38 owner to perform the associated action. See the `Policy configuration
39 <https://docs.openstack.org/cinder/yoga/configuration/block-storage/policy.html>`_
40 documentation in the `Cinder Service Configuration` guide for details.