You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by jt...@apache.org on 2013/08/20 23:52:57 UTC
git commit: updated refs/heads/4.2 to a6d7651
Updated Branches:
refs/heads/4.2 da0816487 -> a6d765141
CLOUDSTACK-871. DOC. Incorporate review comments in VM base image update.
Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo
Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/a6d76514
Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/a6d76514
Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/a6d76514
Branch: refs/heads/4.2
Commit: a6d765141bfd18e063b8028df6074a978a22308d
Parents: da08164
Author: Jessica <je...@citrix.com>
Authored: Tue Aug 20 14:52:34 2013 -0700
Committer: Jessica <je...@citrix.com>
Committed: Tue Aug 20 14:52:43 2013 -0700
----------------------------------------------------------------------
docs/en-US/update-iso-vm.xml | 30 ++++++++++++++++++------------
1 file changed, 18 insertions(+), 12 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cloudstack/blob/a6d76514/docs/en-US/update-iso-vm.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/update-iso-vm.xml b/docs/en-US/update-iso-vm.xml
index 8aa9b25..98105f5 100644
--- a/docs/en-US/update-iso-vm.xml
+++ b/docs/en-US/update-iso-vm.xml
@@ -24,18 +24,24 @@
<section id="update-iso-vm">
<!-- CLOUDSTACK-667 -->
<title>Changing a VM's Base Image</title>
- <para>Every VM is created from a base image, which is a template or ISO which has been
- created and stored in &PRODUCT;. Both cloud administrators and end users can create and
- modify templates, ISOs, and VMs.</para>
- <para>In &PRODUCT;, you can change an
- existing VM's base image. For example, suppose there is a template based
- on a particular operating system, and the OS vendor releases a software patch. The
- administrator or user naturally wants to apply the patch and then make sure existing VMs
+ <para>Every VM is created from a base image, which is a template or ISO which has been created and
+ stored in &PRODUCT;. Both cloud administrators and end users can create and modify templates,
+ ISOs, and VMs.</para>
+ <para>In &PRODUCT;, you can change an existing VM's base image from one template to another,
+ or from one ISO to another. (You can not change from an ISO to a template, or from a
+ template to an ISO).</para>
+ <para>For example, suppose there is a
+ template based on a particular operating system, and the OS vendor releases a software patch.
+ The administrator or user naturally wants to apply the patch and then make sure existing VMs
start using it. Whether a software update is involved or not, it's also possible to simply
switch a VM from its current template to any other desired template.</para>
- <para>To change a VM's base image, call the restoreVirtualMachine API command and pass in the virtual machine
- ID and a new template ID. The template ID parameter may refer to either a template or an
- ISO. When this call occurs, the VM's root disk is first destroyed, then a new root disk is
- created from the source designated in the template ID parameter. The new root disk is
- attached to the VM, and now the VM is based on the new template.</para>
+ <para>To change a VM's base image, call the restoreVirtualMachine API command and pass in the
+ virtual machine ID and a new template ID. The template ID parameter may refer to either a
+ template or an ISO, depending on which type of base image the VM was already using (it must
+ match the previous type of image). When this call occurs, the VM's root disk is first destroyed,
+ then a new root disk is created from the source designated in the template ID parameter. The new
+ root disk is attached to the VM, and now the VM is based on the new template.</para>
+ <para>You can also omit the template ID parameter from the restoreVirtualMachine call. In this
+ case, the VM's root disk is destroyed and recreated, but from the same template or ISO that was
+ already in use by the VM.</para>
</section>
\ No newline at end of file