Doc note warning about retyping unencrypted/encrypted volume

As suggested in 662b8210aa and
discussed at Victoria PTG[1] it would be nice to have a notes
warning users to don’t try this.

[1] https://wiki.openstack.org/wiki/CinderVictoriaPTGSummary#Sizing_encrypted_volumes

Change-Id: I3fd514126dbdf56d4d4d8e423e98e462238c683f
Partial-Bug: #1687880
This commit is contained in:
Sofia Enriquez 2020-08-06 18:13:24 +00:00
parent b204df52cc
commit 09ad89b7ee
3 changed files with 19 additions and 0 deletions

View File

@ -405,6 +405,11 @@ Policy defaults enable only users with the administrative role or the owner of
the volume to perform this operation. Cloud providers can change these
permissions through the policy configuration file.
Retyping an unencrypted volume to the same size encrypted volume will most
likely fail. Even though the volume is the same size as the source volume, the
encrypted volume needs to store additional encryption information overhead.
This results in the new volume not being large enough to hold all data.
Response codes
--------------

View File

@ -461,6 +461,11 @@ Policy defaults enable only users with the administrative role or the owner of
the volume to perform this operation. Cloud providers can change these
permissions through the policy configuration file.
Retyping an unencrypted volume to the same size encrypted volume will most
likely fail. Even though the volume is the same size as the source volume, the
encrypted volume needs to store additional encryption information overhead.
This results in the new volume not being large enough to hold all data.
Response codes
--------------

View File

@ -218,3 +218,12 @@ sections.
In the above example you see that the search returns the string
written to the unencrypted volume, but not the encrypted one.
Known Issues
~~~~~~~~~~~~
Retyping an unencrypted volume to the same size encrypted volume will
most likely fail. Even though the volume is the same size as the source
volume, the encrypted volume needs to store additional encryption
information overhead. This results in the new volume not being large
enough to hold all data.