This is an automated email from the ASF dual-hosted git repository.
rohit pushed a commit to branch 4.18
in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git
The following commit(s) were added to refs/heads/4.18 by this push:
new 820ca37 ScaleIO volume migration documentation (#321)
820ca37 is described below
commit 820ca37c3e7132dc480e02e2ef1c79fb5a595cad
Author: Harikrishna <[email protected]>
AuthorDate: Thu Sep 14 16:08:27 2023 +0530
ScaleIO volume migration documentation (#321)
* Update service offering section with new compute offering and disk
offering changes (#238)
* Added sample ssh commands to connect to Control and Worker node (#304)
Co-authored-by: dahn <[email protected]>
Co-authored-by: Abhishek Kumar <[email protected]>
* Trivial editing (#305)
* volume migration docs for PowerFlex/ScaleIO storage pool
* Rename VM to Instance
* Update storage.rst package update limitation
* revert changes, as it's not needed storage.rst
---------
Co-authored-by: kiranchavala <[email protected]>
Co-authored-by: dahn <[email protected]>
Co-authored-by: Abhishek Kumar <[email protected]>
Co-authored-by: Brad Hards <[email protected]>
Co-authored-by: Boris Stoyanov - a.k.a Bobby <[email protected]>
---
source/adminguide/storage.rst | 29 +++++++++++++++++------------
source/adminguide/virtual_machines.rst | 33 +++++++++++++++++++++++++++++++++
2 files changed, 50 insertions(+), 12 deletions(-)
diff --git a/source/adminguide/storage.rst b/source/adminguide/storage.rst
index 617938c..14dba38 100644
--- a/source/adminguide/storage.rst
+++ b/source/adminguide/storage.rst
@@ -557,34 +557,39 @@ Migrating Storage and Attaching to a Different VM
Volume” <#attaching-a-volume>`_
-Migrating a VM Root Volume to a New Storage Pool
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Migrating a Instance Root Volume to a New Storage Pool
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-(XenServer, VMware) You can live migrate a VM's root disk from one
-storage pool to another, without stopping the VM first.
+(XenServer, VMware) You can live migrate a instance's root disk from one
+storage pool to another, without stopping the instance first.
-(KVM) When migrating the root disk volume, the VM must first be stopped,
-and users can not access the VM. After migration is complete, the VM can
-be restarted.
+(KVM) When migrating the root disk volume, the instance must first be stopped,
+and users can not access the instance. After migration is complete, the
instance
+can be restarted.
#. Log in to the CloudStack UI as a user or admin.
-#. In the left navigation bar, click Instances, and click the VM name.
+#. In the left navigation bar, click Instances, and click the instance name.
-#. (KVM only) Stop the VM.
+#. (KVM only) Stop the instance.
#. Click the Migrate button |Migrateinstance.png| and choose the
destination from the dropdown list.
.. note::
- If the VM's storage has to be migrated along with the VM, this will
- be noted in the host list. CloudStack will take care of the storage
+ If the instance's storage has to be migrated along with the instance,
+ this will be noted in the host list. CloudStack will take care of the
storage
migration for you.
#. Watch for the volume status to change to Migrating, then back to
Running (or Stopped, in the case of KVM). This can take some time.
-#. (KVM only) Restart the VM.
+#. (KVM only) Restart the instance.
+
+ .. note::
+ In case of KVM and PowerFlex/ScaleIO storage, live migration of
+ instance's root disk is allowed from one PowerFlex/ScaleIO storage pool
+ to another, without stopping the instance.
Resizing Volumes
diff --git a/source/adminguide/virtual_machines.rst
b/source/adminguide/virtual_machines.rst
index 3c37641..1b4bb30 100644
--- a/source/adminguide/virtual_machines.rst
+++ b/source/adminguide/virtual_machines.rst
@@ -584,7 +584,40 @@ To manually live migrate a virtual machine
where i in [0,..,N] and N = number of volumes of the virtual machine
+Moving Instance's Volumes Between Storage Pools (offline volume Migration)
+--------------------------------------------------------------------
+The CloudStack administrator can move a stopped instance's volumes from one
+storage pool to another within the cluster. This is called offline volume
+migration, and can be done under the following conditions:
+
+- The root administrator is logged in. Domain admins and users can not
+ perform offline volume migration of instances.
+
+- The instance is stopped.
+
+- The destination storage pool must have enough available capacity.
+
+- UI operation allows only migrating the root volume upon selecting the
+ storage pool. To migrate all volumes to the desired storage pools
+ the 'migrateVirtualMachineWithVolume' API has to be used by providing
+ 'migrateto' map parameter.
+
+
+To perform stopped instance's volumes migration
+
+#. Log in to the CloudStack UI as root administrator.
+
+#. In the left navigation, click Instances.
+
+#. Choose the instance that you want to migrate.
+
+#. Click the Migrate Instance button. |Migrateinstance.png|
+
+#. From the list of suitable storage pools, choose the one to which you want to
+ move the instance root volume.
+
+#. Click OK.
Assigning VMs to Hosts
----------------------
