CLOUDSTACK-900. DOC. Live storage migration, XenMotion, vMotion.
Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/a2476e93 Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/a2476e93 Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/a2476e93 Branch: refs/heads/ldapplugin Commit: a2476e9346845c0172458855c8837207fea6544d Parents: 6c71131 Author: Jessica <[email protected]> Authored: Wed Aug 28 11:47:10 2013 -0700 Committer: Jessica <[email protected]> Committed: Wed Aug 28 11:47:10 2013 -0700 ---------------------------------------------------------------------- docs/en-US/attaching-volume.xml | 2 +- docs/en-US/detach-move-volumes.xml | 5 +- docs/en-US/manual-live-migration.xml | 13 +++-- ...migrate-datadisk-volume-new-storage-pool.xml | 61 +++++++++++++++++--- ...te-vm-rootvolume-volume-new-storage-pool.xml | 34 +++++++---- docs/en-US/vm-storage-migration.xml | 25 +++++--- 6 files changed, 103 insertions(+), 37 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/cloudstack/blob/a2476e93/docs/en-US/attaching-volume.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/attaching-volume.xml b/docs/en-US/attaching-volume.xml index 7511ec3..bb9196a 100644 --- a/docs/en-US/attaching-volume.xml +++ b/docs/en-US/attaching-volume.xml @@ -37,7 +37,7 @@ <para>In Select View, choose Volumes.</para> </listitem> <listitem> - <para>4. Click the volume name in the Volumes list, then click the Attach Disk button<inlinemediaobject> + <para>Click the volume name in the Volumes list, then click the Attach Disk button<inlinemediaobject> <imageobject> <imagedata fileref="./images/attach-disk-icon.png"/> </imageobject> http://git-wip-us.apache.org/repos/asf/cloudstack/blob/a2476e93/docs/en-US/detach-move-volumes.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/detach-move-volumes.xml b/docs/en-US/detach-move-volumes.xml index 7103c30..8922db1 100644 --- a/docs/en-US/detach-move-volumes.xml +++ b/docs/en-US/detach-move-volumes.xml @@ -24,9 +24,8 @@ <section id="detach-move-volumes"> <title>Detaching and Moving Volumes</title> <note> - <para>This procedure is different from moving disk volumes from one storage pool to another. See - VM Storage Migration </para> - </note> + <para>This procedure is different from moving volumes from one storage pool to another as described in <xref linkend="vm-storage-migration"/>.</para></note> + <para/> <para>A volume can be detached from a guest VM and attached to another guest. Both &PRODUCT; administrators and users can detach volumes from VMs and move them to other VMs.</para> <para>If the two VMs are in different clusters, and the volume is large, it may take several http://git-wip-us.apache.org/repos/asf/cloudstack/blob/a2476e93/docs/en-US/manual-live-migration.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/manual-live-migration.xml b/docs/en-US/manual-live-migration.xml index 225f0ba..1daa6d3 100644 --- a/docs/en-US/manual-live-migration.xml +++ b/docs/en-US/manual-live-migration.xml @@ -26,10 +26,12 @@ <para>The &PRODUCT; administrator can move a running VM from one host to another without interrupting service to users or going into maintenance mode. This is called manual live migration, and can be done under the following conditions:</para> <itemizedlist> <listitem><para>The root administrator is logged in. Domain admins and users can not perform manual live migration of VMs.</para></listitem> - <listitem><para>The VM is running. Stopped VMs can not be live migrated.</para></listitem> - <listitem><para>The destination host must be in the same cluster as the original host.</para></listitem> - <listitem><para>The VM must not be using local disk storage.</para></listitem> + <listitem><para>The VM is running. Stopped VMs can not be live migrated.</para></listitem> <listitem><para>The destination host must have enough available capacity. If not, the VM will remain in the "migrating" state until memory becomes available.</para></listitem> + <listitem><para>(KVM) The VM must not be using local disk storage. (On XenServer and VMware, VM live migration + with local disk is enabled by &PRODUCT; support for XenMotion and vMotion.)</para></listitem> + <listitem><para>(KVM) The destination host must be in the same cluster as the original host. + (On XenServer and VMware, VM live migration from one cluster to another is enabled by &PRODUCT; support for XenMotion and vMotion.)</para></listitem> <!-- <listitem><para>(OVM) If the VM is running on the OVM hypervisor, it must not have an ISO attached. Live migration of a VM with attached ISO is not supported in OVM.</para></listitem> --> </itemizedlist> <para>To manually live migrate a virtual machine</para> @@ -44,7 +46,10 @@ <textobject><phrase>Migrateinstance.png: button to migrate an instance</phrase></textobject> </inlinemediaobject> </para></listitem> - <listitem><para>From the list of hosts, choose the one to which you want to move the VM.</para></listitem> + <listitem><para>From the list of suitable hosts, choose the one to which you want to move the VM.</para> + <note><para>If the VM's storage has to be migrated along with the VM, this will be noted in the host + list. &PRODUCT; will take care of the storage migration for you.</para></note> + <para/></listitem> <listitem><para>Click OK.</para></listitem> </orderedlist> </section> http://git-wip-us.apache.org/repos/asf/cloudstack/blob/a2476e93/docs/en-US/migrate-datadisk-volume-new-storage-pool.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/migrate-datadisk-volume-new-storage-pool.xml b/docs/en-US/migrate-datadisk-volume-new-storage-pool.xml index 552fb31..1ed6bbd 100644 --- a/docs/en-US/migrate-datadisk-volume-new-storage-pool.xml +++ b/docs/en-US/migrate-datadisk-volume-new-storage-pool.xml @@ -23,13 +23,56 @@ --> <section id="migrate-datadisk-volume-new-storage-pool"> - <title>Migrating a Data Disk Volume to a New Storage Pool</title> - <orderedlist> - <listitem><para>Log in to the &PRODUCT; UI as a user or admin.</para></listitem> - <listitem><para>Detach the data disk from the VM. See Detaching and Moving Volumes <xref linkend="detach-move-volumes"/> (but skip the âreattachâ step at the end. You will do that after migrating to new storage).</para></listitem> - <listitem><para>Call the &PRODUCT; API command migrateVolume and pass in the volume ID and the ID of any storage pool in the zone.</para></listitem> - <listitem><para>Watch for the volume status to change to Migrating, then back to Ready.</para></listitem> - <listitem><para>Attach the volume to any desired VM running in the same cluster as the new storage server. See Attaching a Volume <xref linkend="attaching-volume"/> </para></listitem> - </orderedlist> + <title>Migrating a Data Volume to a New Storage Pool</title> + <para>There are two situations when you might want to migrate a disk:</para> + <itemizedlist> + <listitem><para>Move the disk to new storage, but leave it attached to the same running VM.</para></listitem> + <listitem><para>Detach the disk from its current VM, move it to new storage, and attach it to a new VM.</para></listitem> + </itemizedlist> + <section id="migrate-storage-same-vm"> + <title>Migrating Storage For a Running VM</title> + <para>(Supported on XenServer and VMware)</para> + <orderedlist> + <listitem><para>Log in to the &PRODUCT; UI as a user or admin.</para></listitem> + <listitem><para>In the left navigation bar, click Instances, click the VM name, and click View Volumes.</para></listitem> + <listitem><para>Click the volume you want to migrate.</para></listitem> + <listitem><para>Detach the disk from the VM. + See <xref linkend="detach-move-volumes"/> but skip the âreattachâ step at the end. You + will do that after migrating to new storage.</para></listitem> + <listitem><para>Click the Migrate Volume button<inlinemediaobject> + <imageobject> + <imagedata fileref="./images/migrate-instance.png"/> + </imageobject> + <textobject> + <phrase>Migrateinstance.png: button to migrate a volume</phrase> + </textobject> + </inlinemediaobject> + and choose the destination from the dropdown list.</para></listitem> + <listitem><para>Watch for the volume status to change to Migrating, then back to Ready.</para></listitem> + </orderedlist> </section> - + <section id="migrate-storage-change-vm"> + <title>Migrating Storage and Attaching to a Different VM</title> + <orderedlist> + <listitem><para>Log in to the &PRODUCT; UI as a user or admin.</para></listitem> + <listitem><para>Detach the disk from the VM. + See <xref linkend="detach-move-volumes"/> but skip the âreattachâ step at the end. You + will do that after migrating to new storage.</para></listitem> + <listitem><para>Click the Migrate Volume button<inlinemediaobject> + <imageobject> + <imagedata fileref="./images/migrate-instance.png"/> + </imageobject> + <textobject> + <phrase>Migrateinstance.png: button to migrate a volume</phrase> + </textobject> + </inlinemediaobject> + and choose the destination from the dropdown list.</para></listitem> + <listitem><para>Watch for the volume status to change to Migrating, then back to Ready. You can find the + volume by clicking Storage in the left navigation bar. Make sure that Volumes is + displayed at the top of the window, in the Select View dropdown.</para></listitem> + <listitem><para>Attach the volume to any desired VM running in the same cluster as the new storage server. See + <xref linkend="attaching-volume"/> + </para></listitem> + </orderedlist> + </section> +</section> http://git-wip-us.apache.org/repos/asf/cloudstack/blob/a2476e93/docs/en-US/migrate-vm-rootvolume-volume-new-storage-pool.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/migrate-vm-rootvolume-volume-new-storage-pool.xml b/docs/en-US/migrate-vm-rootvolume-volume-new-storage-pool.xml index d615cfe..3bcaff5 100644 --- a/docs/en-US/migrate-vm-rootvolume-volume-new-storage-pool.xml +++ b/docs/en-US/migrate-vm-rootvolume-volume-new-storage-pool.xml @@ -23,15 +23,25 @@ --> <section id="migrate-vm-rootvolume-volume-new-storage-pool"> <title>Migrating a VM Root Volume to a New Storage Pool</title> - <para>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.</para> - <orderedlist> - <listitem><para>Log in to the &PRODUCT; UI as a user or admin.</para></listitem> - <listitem><para>Detach the data disk from the VM. See Detaching and Moving Volumes <xref linkend="detach-move-volumes"/> (but skip the âreattachâ step at the end. You will do that after migrating to new storage).</para></listitem> - <listitem><para>Stop the VM.</para></listitem> - <listitem><para>Use the &PRODUCT; API command, migrateVirtualMachine, with the ID of the VM to migrate and - the IDs of a destination host and destination storage pool in the same zone.</para></listitem> - <listitem><para>Watch for the VM status to change to Migrating, then back to Stopped.</para></listitem> - <listitem><para>Restart the VM.</para></listitem> - </orderedlist> - </section> - + <para>(XenServer, VMware) You can live migrate a VM's root disk from one storage pool to another, without stopping the VM first.</para> + <para>(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.</para> + <orderedlist> + <listitem><para>Log in to the &PRODUCT; UI as a user or admin.</para></listitem> + <listitem><para>In the left navigation bar, click Instances, and click the VM name.</para></listitem> + <listitem><para>(KVM only) Stop the VM.</para></listitem> + <listitem><para>Click the Migrate button <inlinemediaobject> + <imageobject> + <imagedata fileref="./images/migrate-instance.png"/> + </imageobject> + <textobject> + <phrase>Migrateinstance.png: button to migrate a VM or volume</phrase> + </textobject> + </inlinemediaobject> + and choose the destination from the dropdown list.</para> + <note><para>If the VM's storage has to be migrated along with the VM, this will be noted in the host + list. &PRODUCT; will take care of the storage migration for you.</para></note><para/></listitem> + <listitem><para>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.</para></listitem> + <listitem><para>(KVM only) Restart the VM.</para></listitem> + </orderedlist> +</section> \ No newline at end of file http://git-wip-us.apache.org/repos/asf/cloudstack/blob/a2476e93/docs/en-US/vm-storage-migration.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/vm-storage-migration.xml b/docs/en-US/vm-storage-migration.xml index fc18da7..51c6f34 100644 --- a/docs/en-US/vm-storage-migration.xml +++ b/docs/en-US/vm-storage-migration.xml @@ -24,14 +24,23 @@ <section id="vm-storage-migration"> <title>VM Storage Migration</title> <para>Supported in XenServer, KVM, and VMware.</para> - <note> - <para>This procedure is different from moving disk volumes from one VM to another. See <xref linkend="detach-move-volumes"/>.</para> - </note> - <para>You can migrate a virtual machineâs root disk volume or any additional data disk volume from - one storage pool to another in the same zone.</para> - <para>You can use the storage migration feature to achieve some commonly desired administration - goals, such as balancing the load on storage pools and increasing the reliability of virtual - machines by moving them away from any storage pool that is experiencing issues.</para> + <note><para>This procedure is different from moving disk volumes from one VM to another as described in + <xref linkend="detach-move-volumes"/>.</para></note> + <para/> + <para>You can migrate a virtual machineâs root disk volume or any additional data disk volume from one storage pool to another in the same zone.</para> + <para>You can use the storage migration feature to achieve some commonly desired administration goals, such as balancing the load on storage pools and increasing the reliability of virtual machines by moving them away from any storage pool that is experiencing issues.</para> + <para>On XenServer and VMware, live migration of VM storage is enabled through &PRODUCT; + support for XenMotion and vMotion. + Live storage migration allows VMs to be moved from one host to another, where the VMs are + not located on storage shared between the two hosts. It provides the option to live + migrate a VMâs disks along with the VM itself. It is possible to migrate a VM from one + XenServer resource pool / VMware cluster to another, or to migrate a VM whose disks are on + local storage, or even to migrate a VMâs disks from one storage repository to another, all + while the VM is running.</para> + <note><para>Because of a limitation in VMware, live migration of storage for a VM is allowed only + if the source and target storage pool are accessible to the source host; that is, the host + where the VM is running when the live migration operation is requested.</para></note> + <para/> <xi:include href="migrate-datadisk-volume-new-storage-pool.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/> <xi:include href="migrate-vm-rootvolume-volume-new-storage-pool.xml"
