Skip to content

Commit 820ca37

Browse files
harikrishna-patnalakiranchavalaDaanHooglandshwstpprbradh
authored
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]>
1 parent 5304e92 commit 820ca37

File tree

2 files changed

+50
-12
lines changed

2 files changed

+50
-12
lines changed

source/adminguide/storage.rst

Lines changed: 17 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -557,34 +557,39 @@ Migrating Storage and Attaching to a Different VM
557557
Volume” <#attaching-a-volume>`_
558558

559559

560-
Migrating a VM Root Volume to a New Storage Pool
561-
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
560+
Migrating a Instance Root Volume to a New Storage Pool
561+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
562562

563-
(XenServer, VMware) You can live migrate a VM's root disk from one
564-
storage pool to another, without stopping the VM first.
563+
(XenServer, VMware) You can live migrate a instance's root disk from one
564+
storage pool to another, without stopping the instance first.
565565

566-
(KVM) When migrating the root disk volume, the VM must first be stopped,
567-
and users can not access the VM. After migration is complete, the VM can
568-
be restarted.
566+
(KVM) When migrating the root disk volume, the instance must first be stopped,
567+
and users can not access the instance. After migration is complete, the instance
568+
can be restarted.
569569

570570
#. Log in to the CloudStack UI as a user or admin.
571571

572-
#. In the left navigation bar, click Instances, and click the VM name.
572+
#. In the left navigation bar, click Instances, and click the instance name.
573573

574-
#. (KVM only) Stop the VM.
574+
#. (KVM only) Stop the instance.
575575

576576
#. Click the Migrate button |Migrateinstance.png| and choose the
577577
destination from the dropdown list.
578578

579579
.. note::
580-
If the VM's storage has to be migrated along with the VM, this will
581-
be noted in the host list. CloudStack will take care of the storage
580+
If the instance's storage has to be migrated along with the instance,
581+
this will be noted in the host list. CloudStack will take care of the storage
582582
migration for you.
583583

584584
#. Watch for the volume status to change to Migrating, then back to
585585
Running (or Stopped, in the case of KVM). This can take some time.
586586

587-
#. (KVM only) Restart the VM.
587+
#. (KVM only) Restart the instance.
588+
589+
.. note::
590+
In case of KVM and PowerFlex/ScaleIO storage, live migration of
591+
instance's root disk is allowed from one PowerFlex/ScaleIO storage pool
592+
to another, without stopping the instance.
588593

589594

590595
Resizing Volumes

source/adminguide/virtual_machines.rst

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -584,7 +584,40 @@ To manually live migrate a virtual machine
584584

585585
where i in [0,..,N] and N = number of volumes of the virtual machine
586586

587+
Moving Instance's Volumes Between Storage Pools (offline volume Migration)
588+
--------------------------------------------------------------------
587589

590+
The CloudStack administrator can move a stopped instance's volumes from one
591+
storage pool to another within the cluster. This is called offline volume
592+
migration, and can be done under the following conditions:
593+
594+
- The root administrator is logged in. Domain admins and users can not
595+
perform offline volume migration of instances.
596+
597+
- The instance is stopped.
598+
599+
- The destination storage pool must have enough available capacity.
600+
601+
- UI operation allows only migrating the root volume upon selecting the
602+
storage pool. To migrate all volumes to the desired storage pools
603+
the 'migrateVirtualMachineWithVolume' API has to be used by providing
604+
'migrateto' map parameter.
605+
606+
607+
To perform stopped instance's volumes migration
608+
609+
#. Log in to the CloudStack UI as root administrator.
610+
611+
#. In the left navigation, click Instances.
612+
613+
#. Choose the instance that you want to migrate.
614+
615+
#. Click the Migrate Instance button. |Migrateinstance.png|
616+
617+
#. From the list of suitable storage pools, choose the one to which you want to
618+
move the instance root volume.
619+
620+
#. Click OK.
588621

589622
Assigning VMs to Hosts
590623
----------------------

0 commit comments

Comments
 (0)