You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@vcl.apache.org by bu...@apache.org on 2012/12/10 21:42:10 UTC
svn commit: r841521 - in /websites/staging/vcl/trunk/content: ./
docs/vmwareconfiguration.html
Author: buildbot
Date: Mon Dec 10 20:42:10 2012
New Revision: 841521
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 20:42:10 2012
@@ -1 +1 @@
-1419743
+1419744
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 20:42:10 2012
@@ -227,16 +227,16 @@ bootstate=0
</li>
</ul>
<h2 id="vm-host-profile-parameters">VM Host Profile Parameters</h2>
-<h3 id="general-parameters">General Parameters</h3>
-<h4 id="name">Name</h4>
+<p><strong>General Parameters</strong></p>
+<p><strong>Name</strong></p>
<ul>
<li>Descriptive name of the VM host profile</li>
</ul>
-<h4 id="type-deprecated">Type (deprecated)</h4>
+<p><strong>Type (deprecated)</strong></p>
<ul>
<li>Removed in VCL 2.3</li>
</ul>
-<h4 id="image-optional">Image (optional)</h4>
+<p><strong>Image (optional)</strong></p>
<ul>
<li>VCL hypervisor image installed on VM host computers using xCAT
<div class="docnote">
@@ -245,14 +245,14 @@ bootstate=0
<li>If xCAT is not used, select "No Image"</li>
<li>VCL has the ability to install a hypervisor image on bare-metal computers using xCAT. If the image property is configured, the image is installed when a computer's state is changed to vmhostinuse via Manage Computers > Computer Utilities</li>
</ul>
-<h4 id="usernamepassword-optional">Username/Password (optional)</h4>
+<p><strong>Username/Password (optional)</strong></p>
<ul>
<li>Name and password of the administrative or root user residing on the VM host</li>
<li>This account is used to manage the VM host and VMs assigned to the host</li>
<li>The username and password are currently only used if the vSphere SDK is used to manage the VM host and VMs</li>
</ul>
<h3 id="storage-parameters">Storage Parameters</h3>
-<h4 id="resource-path-optional">Resource Path (optional)</h4>
+<p><strong>Resource Path (optional)</strong></p>
<p>Resource Path only needs to be configured if VMware vCenter is used. It defines the location where VMs will be created in the vCenter inventory tree. The inventory tree contains at least one Datacenter, and may also contain Folders, Clusters, and Resource Pools.
Example: /DatacenterA/Folder1/Cluster2/ResourcePool3</p>
<ul>
@@ -274,9 +274,9 @@ Example: /DatacenterA/Folder1/Cluster2/R
<li>The size of the vmdk files will approximately be equal to the amount of actual data saved in the image regardless of the size of the VM's hard drive</li>
<li>Storing images in the 2 GB sparse format is necessary to allow images to be transferred via SCP without having to transfer data equal to the entire size of the VM's hard drive</li>
</ul>
-<h4 id="repository-image-type">Repository Image Type</h4>
+<p><strong>Repository Image Type</strong></p>
<p>Virtual disk file format for images stored in the repository.</p>
-<h4 id="virtual-disk-path-previously-datastore-path">Virtual Disk Path (previously Datastore Path)</h4>
+<p><strong>Virtual Disk Path (previously Datastore Path)</strong></p>
<ul>
<li>Location where master copies of images are stored which are used by running VMs</li>
<li>Example: /vmfs/volumes/nfs-datastore1
@@ -298,9 +298,9 @@ Example: /DatacenterA/Folder1/Cluster2/R
</ul>
</li>
</ul>
-<h4 id="virtual-disk-image-type">Virtual Disk Image Type</h4>
+<p><strong>Virtual Disk Image Type</strong></p>
<p>Virtual disk file format for images stored in the virtual disk path.</p>
-<h4 id="virtual-disk-mode-previously-vm-disk">Virtual Disk Mode (previously VM Disk)</h4>
+<p><strong>Virtual Disk Mode (previously VM Disk)</strong></p>
<ul>
<li>Defines whether the storage where the VM host's Virtual Disk Path resides is dedicated to a single host or shared among multiple hosts:</li>
<li>dedicated (previously localdisk)<ul>
@@ -323,7 +323,7 @@ Example: /DatacenterA/Folder1/Cluster2/R
</div></p>
</li>
</ul>
-<h4 id="vm-working-directory-path-optional-previously-vm-path">VM Working Directory Path (optional) (previously VM Path)</h4>
+<p><strong>VM Working Directory Path (optional) (previously VM Path)</strong></p>
<ul>
<li>Defines path on VM host where VM working directories will reside (contains .vmx, delta, .vswp, nvram files)</li>
<li>If not configured, the Virtual Disk Path location will be used</li>
@@ -341,7 +341,7 @@ Example: /DatacenterA/Folder1/Cluster2/R
<li>Storage where the VM Working Directory Path is located should be optimized for read-write performance</li>
</ul>
<h3 id="networking-parameters">Networking Parameters</h3>
-<h4 id="vm-network-previously-virtual-switch">VM Network (previously Virtual Switch)</h4>
+<p><strong>VM Network (previously Virtual Switch)</strong></p>
<ul>
<li>VM Network 0 (previously Virtual Switch 0) - private VCL management network</li>
<li>
@@ -362,13 +362,13 @@ Example: /DatacenterA/Folder1/Cluster2/R
<ul>
<li>For VMware Server 2.x, the VM Network parameters must match the Network Names configured by running vmware-config.pl</li>
</ul>
-<h5 id="generate-eth0eth1-mac">Generate eth0/eth1 MAC</h5>
+<p><strong>Generate eth0/eth1 MAC</strong></p>
<ul>
<li>New in VCL 2.3</li>
<li>Determines whether VMs are assigned MAC addresses defined in the VCL database or if random MAC addresses should be assigned</li>
</ul>
<h3 id="configuration-examples">Configuration Examples</h3>
-<h4 id="local-disk-only-repository-mounted-via-nfs">Local Disk Only - Repository Mounted via NFS</h4>
+<p><strong>Local Disk Only - Repository Mounted via NFS</strong></p>
<p>The diagram above shows a simple VCL configuration with 1 management node and 2 VMware ESXi hosts. Network storage is not used.</p>
<p><img alt="local-only-nfs" src="local-only-nfs.gif" /></p>
<p>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>
@@ -376,12 +376,12 @@ Example: /DatacenterA/Folder1/Cluster2/R
<p>If an image is to be loaded on a VM host and that image does not already exist in the VM host's local datastore (Virtual Disk Path), it is automatically copied from the repository to the VM host's local datastore (Virtual Disk Path) at the beginning of the load process.</p>
<p>During image capture, images are automatically copied to from the VM host's local datastore (Virtual Disk Path) to the repository. This allows images captured on a VM host to be loaded on any other VM host.</p>
<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>
+<p><strong>Local Disk Only - Repository Not Available via NFS</strong></p>
<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.</p>
<p><img alt="local-only-scp" src="local-only-scp.gif" /></p>
<p>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.</p>
<p>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>
+<p><strong>Network Storage Only - No Repository</strong></p>
<p>This is an example of a simple configuration where the network storage is used.</p>
<p><img alt="network-only-no-repo" src="network-only-no-repo.gif" /></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>