openstack/cinder
Code Issues Proposed changes

Fix example of failed migrarion for LVM->RBD

Browse Source 
Migration from and to RBD devices works for in-use volumes since
Ussuri release. Also as of now a migration of in-use volumes for
non-active VMs is prohibited for any backends.

Related-Bug: #1673090
Related-Bug: #1868996
Closes-Bug: #1969913
Change-Id: Id639c412a6f5ad24ab9c80416c56c1d99b3f104c
This commit is contained in:
Vladislav Belogrudov 2022-04-29 10:45:37 +03:00
parent 983f62ed50
commit 7ee223837e
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/source/contributor/migration.rst
View File

@ -33,8 +33,11 @@ the migration of 'in-use' volumes is driver dependent. It depends on
different drivers involved in the operation. It may fail depending on
the source or destination driver of the volume.
For example, from RBD to LVM, the migration of 'in-use' volume will
succeed, but from LVM to RBD, it will fail.
For example, for older releases (before Ussuri), the migration of
'in-use' volume from RBD to LVM will succeed, but from LVM to RBD,
it will fail. Currently, migration of 'in-use' volumes will not succeed
for any backend when they are attached to an instance in any of these
states: SHUTOFF, SUSPENDED, or SOFT-DELETED.
There are two major scenarios, which volume migration supports
in Cinder: