Author: buildbot
Date: Mon Dec 10 20:39:04 2012
New Revision: 841520
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:39:04 2012
@@ -1 +1 @@
-1419737
+1419743
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:39:04 2012
@@ -79,27 +79,27 @@
<div id="content">
<h1 class="title">VMware Configuration</h1>
<h2 id="terminology">Terminology</h2>
-<h4 id="vm-host">VM Host</h4>
+<p><strong>VM Host</strong></p>
<ul>
<li>A VM host is a physical computer running a VMware hypervisor</li>
<li>A VCL computer entry must be added for each VM host (Manage Computers >
Edit Computer Information)</li>
<li>After the computer has been added to VCL, it is designated as a VM host by
changing the computer state to vmhostinuse (Manage Computers > Computer
Utilities)</li>
</ul>
-<h4 id="vm">VM</h4>
+<p><strong>VM</strong></p>
<ul>
<li>A VM is a virtual machine managed by VCL</li>
<li>A computer entry must be added to VCL for each VM (Manage Computers >
Edit Computer Information)</li>
<li>Each VM must be assigned to a VM host (Virtual Hosts > VM Hosts tab
> Configure Host)</li>
<li>VMs do not need to be created manually in VMware, VCL automatically
creates and deletes VMs</li>
</ul>
-<h4 id="vm-host-profile">VM Host Profile</h4>
+<p><strong>VM Host Profile</strong></p>
<ul>
<li>A VM host profile contains several parameters which describe how a VM host
is configured so that VCL knows how to manage it</li>
<li>Each VM host is assigned a VM host profile</li>
<li>A VM host profile may be assigned to multiple VM hosts if they are
configured identically</li>
<li>VM host profiles may be added or modified via Virtual Hosts > VM Host
Profiles tab</li>
</ul>
-<h4 id="vmware-products-supported">VMware Products Supported</h4>
+<p><strong>VMware Products Supported</strong></p>
<ul>
<li>VMware Server 2.x</li>
<li>VMware ESX 3.5 - 4.x</li>
@@ -116,9 +116,9 @@
<p>The vSphere SDK can only be used if management is not restricted due to the
VMware license key installed on the host. This mainly affects hosts running
the free version of ESXi. Remote management using any of the methods supported
by VMware is restricted once a free license key is entered.</p>
<p>If remote management is restricted, the VM host can be managed if SSH is
enabled on it. VCL will execute vim-cmd and other commands on the VM host via
SSH. </p>
<h2 id="how-to-enable-ssh-on-the-vm-host">How to enable SSH on the VM
host:</h2>
-<h4 id="vmware-server-2x">VMware Server 2.x</h4>
+<p><strong>VMware Server 2.x</strong></p>
<p>Enable the SSH daemon and configure identity key authentication according
to the underlying VM host OS</p>
-<h4 id="esxesxi-35-40">ESX/ESXi 3.5 & 4.0</h4>
+<p><strong>ESX/ESXi 3.5 & 4.0</strong></p>
<ul>
<li>Connect to the console of the ESX/ESXi host</li>
<li>Press ALT-F1 - you should see a black screen with the VMware product name
at the top</li>
@@ -132,7 +132,7 @@
<li>You should see a line that looks like: 5065 5065 busybox inetd</li>
<li>Kill the process (enter the PID from the output of the previous command):
kill -HUP 5065</li>
</ul>
-<h4 id="esxi-41">ESXi 4.1</h4>
+<p><strong>ESXi 4.1</strong></p>
<p>Beginning with ESXi 4.1, SSH can be enabled using the vSphere Client:</p>
<ul>
<li>Select the ESXi host</li>
@@ -145,7 +145,7 @@
<li>Click Start</li>
<li>Click OK</li>
</ul>
-<h4 id="esx-50">ESX 5.0</h4>
+<p><strong>ESX 5.0</strong></p>
<p>In the case of ESX 5.0:</p>
<ul>
<li>Select the ESXi host</li>
