ScaleIO volume migration documentation #321
Conversation
…he#304) Co-authored-by: dahn <daan.hoogland@gmail.com> Co-authored-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
harikrishna-patnala
force-pushed
the
ScaleIOvolumeMigration
branch
from
6b854b6 to
d8ddec0
Compare
|
@blueorangutan docbuild |
|
@harikrishna-patnala a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. |
|
QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/321. (QA-JID 82) |
|
@blueorangutan docbuild |
|
@harikrishna-patnala a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. |
|
QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/321. (QA-JID 83) |
|
Added a new section here: and added a note for ScaleIO storage for live migration here: |
|
@blueorangutan docbuild |
|
@borisstoyanov a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. |
|
QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/321. (QA-JID 84) |
… the ScaleIO storage pools of the same and different ScaleIO storage clusters. Previously this operation was blocked and now we are allowing it from API/UI. The volume migration within the same storage cluster is performed using ScaleIO’s native V-Tree migration operation where the volume will be live migrated to another storage pool. The volume migration across the different storage cluster is performed using libvirt’s live blockcopy operation which will first copy the volume to the destination storage pool and after a successful copy, the source volume will be deleted. Upon any failures during the block copy, source volume will remain to continue and other blockcopy operations will be reverted. A document PR is added here apache/cloudstack-documentation#321
7 participants
This is related to the feature introduced here apache/cloudstack#7408 to introduce volume migrations for Powerflex/ScaleIO storage