openstack/openstack-manuals
Code Issues Proposed changes

Add note about vmware_linked_clone when spawning with ISO

Browse Source 
On refacrctoring on image user function for spawn(), adding reason why
and condition where vmware_linked_clone property is ignored when
spawning with ISO image.

Closes-Bug: #1366325

Change-Id: Icde3817189b64215d8203bd32217439c7a11403a
Signed-off-by: Masaki Furuta <masaki.furuta@gmail.com>
This commit is contained in:
Masaki Furuta 2015-10-26 16:27:41 +09:00
parent 9e6a7a6945
commit 13032de299
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/config-reference/compute/section_hypervisor_vmware.xml
View File

@ -860,7 +860,12 @@ trusty-server-cloudimg-amd64-disk1.vmdk</userinput></screen>
<note><para>You can also use
the <code>vmware_linked_clone</code> property in the OpenStack
Image service to
override the linked_clone mode on a per-image basis.</para></note>
override the linked_clone mode on a per-image basis.</para>
<para>If spawning a virtual machine image from ISO with
a VMDK disk, the image is created and attached to
the virtual machine as a blank disk.
In that case <code>vmware_linked_clone</code> property
for the image is just ignored.</para></note>
<para>If multiple compute nodes are running on the same host,
or have a shared file system, you can enable them to use the