Author: buildbot
Date: Mon Dec 10 19:41:43 2012
New Revision: 841506
Log:
Staging update by buildbot for vcl
Modified:
websites/staging/vcl/trunk/content/ (props changed)
websites/staging/vcl/trunk/content/docs/vmwareconfiguration.html
Propchange: websites/staging/vcl/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Dec 10 19:41:43 2012
@@ -1 +1 @@
-1419695
+1419701
Modified: websites/staging/vcl/trunk/content/docs/vmwareconfiguration.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/vmwareconfiguration.html (original)
+++ websites/staging/vcl/trunk/content/docs/vmwareconfiguration.html Mon Dec 10
19:41:43 2012
@@ -359,10 +359,8 @@ These are determined by whether or not R
<ul>
<li>For ESXi, the VM Network parameters must match the Virtual Machine Port
Group Network Labels configured in the vSphere Client, example:<ul>
<li>VM Network 0: Public</li>
-<li>VM Network 1: Private<ul>
-<li>INSERT IMAGE</li>
-</ul>
-</li>
+<li>VM Network 1: Private
+ <img alt="vmware-network-labels" src="vmware-network-labels.gif" /></li>
</ul>
</li>
</ul>
@@ -379,7 +377,7 @@ These are determined by whether or not R
<h3 id="configuration-examples">Configuration Examples</h3>
<h4 id="local-disk-only-repository-mounted-via-nfs">Local Disk Only -
Repository Mounted via NFS</h4>
<ul>
-<li>INSERT IMAGE</li>
+<li><img alt="local-only-nfs" src="local-only-nfs.gif" /></li>
</ul>
<p>The diagram above shows a simple VCL configuration with 1 management node
and 2 VMware ESXi hosts. Network storage is not used.
The local disks on the VM hosts are used to store all of the files used by
running VMs including the VM's working directory and the master vmdk image.</p>
@@ -389,13 +387,13 @@ The local disks on the VM hosts are used
<p>The VM host profile Virtual Disk Mode parameter is set to dedicated. This
indicates to the load process that the VM host's Virtual Disk Path is dedicated
to the VM host and not shared by other VM hosts. This allows images to be
deleted from the VM host's local datastore (Virtual Disk Path) if another image
must be copied from the repository and not enough space is available.</p>
<h4 id="local-disk-only-repository-not-available-via-nfs">Local Disk Only -
Repository Not Available via NFS</h4>
<ul>
-<li>INSERT IMAGE</li>
+<li><img alt="local-only-scp" src="local-only-scp.gif" /></li>
</ul>
<p>This example is identical to the one above except that the repository
located on the management node's local disk is not exported via NFS. Because
of this, images must be transferred using SCP instead of vmkfstools. This is
less desirable than mounting the repository directly on the VM hosts because
images cannot be copied and converted in a single step. Images are stored in
the repository in the 2GB sparse format. This allows the images to be copied
via SCP while only transferring the data stored in the image, not the entire
size of the hard drive stored in the image. VMware ESXi cannot run VMs using
vmdk images stored in the 2GB sparse format. Images are converted to the vmfs
thin format so that they can be loaded on VMware ESXi. This adds extra time to
the load process if an image does not exist in the VM's local datastore
(Virtual Disk Path) and must be copied from the repository. It also requires
additional space in the VM host's local datastore (Virtual Disk
Path) becuase 2 copies of the image exist while it is being converted.
Note that the VM host profile Repository Path parameter is set to the path on
the management node's hard drive. The code first checks if the path exists on
the VM host. If not, it assumes the repository is not mounted directly on the
VM host and the Repository Path value refers to a location on the management
node.</p>
<h4 id="network-storage-only-no-repository">Network Storage Only - No
Repository</h4>
<ul>
-<li>INSERT IMAGE</li>
+<li><img alt="network-only-no-repo" src="network-only-no-repo.gif" /></li>
</ul>
<p>This is an example of a simple configuration where the network storage is
used.</p>
<p>A repository is not used in this configuration. This implies that all VM
hosts which will ever be added to this VCL environment will need to be able to
connect to the network storage.</p>
