vcl-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1019714 [8/13] - in /websites/staging/vcl/trunk/content: ./ comm/ comm/boardreports/ comm/commprojects/ confluence_export/ dev/ docs/ docs/UpgradePreviousVersions/ docs/archives/old-releases/ docs/authorization/ downloads/ info/
Date Wed, 18 Oct 2017 19:55:33 GMT
Modified: websites/staging/vcl/trunk/content/confluence_export/vmware-configuration.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/vmware-configuration.html (original)
+++ websites/staging/vcl/trunk/content/confluence_export/vmware-configuration.html Wed Oct 18 19:55:31 2017
@@ -36,7 +36,18 @@
   </div>
 
   <div id="navigation"> 
-  <ul>
+  <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
 <li><a href="/index.html">Information</a><ul>
 <li><a href="/info/features.html">Features</a></li>
 <li><a href="/info/architecture.html">Architecture</a></li>
@@ -53,7 +64,7 @@
 <li><a href="/comm/index.html">Community</a><ul>
 <li><a href="/comm/index.html#getInvolved">Getting Involved</a></li>
 <li><a href="/comm/index.html#mail-list">Mailing Lists</a></li>
-<li><a href="/comm/wiki.html">Wiki</a></li>
+<li><a href="https://cwiki.apache.org/confluence/display/VCL/Apache+VCL" target="_blank">Wiki</a></li>
 <li><a href="/dev/index.html">Development</a><ul>
 <li><a href="/dev/jira.html">Issue Tracking</a></li>
 <li><a href="/dev/code-documentation.html">Code Documentation</a></li>
@@ -72,32 +83,43 @@
   
   <div id="content">
     <h1 class="title">VMware Configuration</h1>
-    <p><a name="VMwareConfiguration-Terminology"></a></p>
-<h2 id="terminology">Terminology</h2>
+    <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p><a name="VMwareConfiguration-Terminology"></a></p>
+<h2 id="terminology">Terminology<a class="headerlink" href="#terminology" title="Permanent link">&para;</a></h2>
 <p><a name="VMwareConfiguration-VMHost"></a></p>
-<h4 id="vm-host">VM Host</h4>
+<h4 id="vm-host">VM Host<a class="headerlink" href="#vm-host" title="Permanent link">&para;</a></h4>
 <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&nbsp;({color:#000000}{<em>}Manage Computers &gt; Edit Computer
-Information)</em>{color}</li>
+host&nbsp;({color:#000000}{<em color="color">}Manage Computers &gt; Edit Computer
+Information)</em></li>
 <li>{color:#000000}After the computer has been added to VCL, it is designated
 as a VM host by changing the computer state to vmhostinuse{color}
-{color:#000000}<em>(Manage Computers &gt; Computer Utilities)</em>{color}</li>
+{color:#000000}<em color="color">(Manage Computers &gt; Computer Utilities)</em></li>
 </ul>
 <p><a name="VMwareConfiguration-VM"></a></p>
-<h4 id="vm">VM</h4>
+<h4 id="vm">VM<a class="headerlink" href="#vm" title="Permanent link">&para;</a></h4>
 <ul>
 <li>A VM is a virtual machine managed by VCL</li>
 <li>A computer entry must be added to VCL for each VM
-({color:#000000}{<em>}Manage Computers &gt; Edit Computer Information)</em>{color}</li>
+({color:#000000}{<em color="color">}Manage Computers &gt; Edit Computer Information)</em></li>
 <li>{color:#000000}Each VM must be assigned to a VM host{color}
-{color:#000000}<em>(Virtual Hosts &gt; VM Hosts tab &gt; Configure Host)</em>{color}</li>
+{color:#000000}<em color="color">(Virtual Hosts &gt; VM Hosts tab &gt; Configure Host)</em></li>
 <li>VMs do not need to be created manually in VMware, VCL automatically
 creates and deletes VMs</li>
 </ul>
 <p><a name="VMwareConfiguration-VMHostProfile"></a></p>
-<h4 id="vm-host-profile">VM Host Profile</h4>
+<h4 id="vm-host-profile">VM Host Profile<a class="headerlink" href="#vm-host-profile" title="Permanent link">&para;</a></h4>
 <ul>
 <li>A VM host profile contains&nbsp;several parameters which describe how a
 VM host is configured so that VCL knows how to manage it</li>
@@ -108,7 +130,7 @@ configured identically</li>
 Profiles tab</em></li>
 </ul>
 <p><a name="VMwareConfiguration-VMwareProductsSupported"></a></p>
-<h2 id="vmware-products-supported">VMware Products Supported</h2>
+<h2 id="vmware-products-supported">VMware Products Supported<a class="headerlink" href="#vmware-products-supported" title="Permanent link">&para;</a></h2>
 <ul>
 <li>VMware Server 2.x</li>
 <li>VMware ESX 3.5 - 4.x</li>
@@ -116,7 +138,7 @@ Profiles tab</em></li>
 <li>VMware ESXi 5.x</li>
 </ul>
 <p><a name="VMwareConfiguration-VMHost&nbsp;ManagementOptions"></a></p>
-<h3 id="vm-hostwzxhzdk12management-options">VM Host&nbsp;Management Options</h3>
+<h3 id="vm-hostmanagement-options">VM Host&nbsp;Management Options<a class="headerlink" href="#vm-hostmanagement-options" title="Permanent link">&para;</a></h3>
 <p>&nbsp;The VCL&nbsp;management node must be able to control the VM host and
 the VMs running on it.&nbsp; VMware provides several different&nbsp;ways of
 doing this.&nbsp; VCL currently supports the following methods for remote
@@ -133,13 +155,13 @@ free license key is entered.</p>
 enabled on it.&nbsp; VCL will execute vim-cmd and other commands on the VM
 host via SSH.&nbsp;</p>
 <p><a name="VMwareConfiguration-HowtoenableSSHontheVMhost:"></a></p>
-<h4 id="how-to-enable-ssh-on-the-vm-host">How to enable SSH on the VM host:</h4>
+<h4 id="how-to-enable-ssh-on-the-vm-host">How to enable SSH on the VM host:<a class="headerlink" href="#how-to-enable-ssh-on-the-vm-host" title="Permanent link">&para;</a></h4>
 <p><a name="VMwareConfiguration-VMwareServer2.x"></a></p>
-<h5 id="vmware-server-2x">VMware Server 2.x</h5>
+<h5 id="vmware-server-2x">VMware Server 2.x<a class="headerlink" href="#vmware-server-2x" title="Permanent link">&para;</a></h5>
 <p>Enable the SSH daemon and configure identity key authentication according
 to the underlying VM host OS</p>
 <p><a name="VMwareConfiguration-ESX/ESXi3.5&4.0"></a></p>
-<h5 id="esxesxi-35-40">ESX/ESXi 3.5 &amp; 4.0</h5>
+<h5 id="esxesxi-35-40">ESX/ESXi 3.5 &amp; 4.0<a class="headerlink" href="#esxesxi-35-40" title="Permanent link">&para;</a></h5>
 <ul>
 <li>Connect to the console of the ESX/ESXi host</li>
 <li>Press <em>ALT-F1</em> - you should see a black screen with the VMware product
@@ -158,7 +180,7 @@ You should see a line that looks like: <
 command): <em>kill -HUP 5065</em></li>
 </ul>
 <p><a name="VMwareConfiguration-ESXi4.1"></a></p>
-<h5 id="esxi-41">ESXi 4.1</h5>
+<h5 id="esxi-41">ESXi 4.1<a class="headerlink" href="#esxi-41" title="Permanent link">&para;</a></h5>
 <p>Beginning with <em>ESXi 4.1</em>, SSH&nbsp;can be enabled using the vSphere
 Client:
 <em> Select the ESXi host
@@ -171,7 +193,7 @@ Client:
 </em> Click <em>Start</em>
 <em> Click </em>OK*</p>
 <p><a name="VMwareConfiguration-ESX5.0"></a></p>
-<h5 id="esx-50">ESX 5.0</h5>
+<h5 id="esx-50">ESX 5.0<a class="headerlink" href="#esx-50" title="Permanent link">&para;</a></h5>
 <p>In the case of <em>ESX 5.0</em>:
 <em> Select the ESXi host
 </em> Select the <em>Configuration</em> tab
@@ -182,8 +204,8 @@ Client:
 <em> Confirm that </em>Start automatically<em> is selected
 </em> Click <em>OK</em></p>
 <p><a name="VMwareConfiguration-HowtoconfigureESX/ESXitouseSSHidentitykeyauthentication:"></a></p>
-<h4 id="how-to-configure-esxesxi-to-use-ssh-identity-key-authentication">How to configure ESX/ESXi to use SSH identity key authentication:</h4>
-<p>SSH identity key authentication&nbsp;must be configured if SSH is used to
+<h4 id="how-to-configure-esxesxi-to-use-ssh-identity-key-authentication">How to configure ESX/ESXi to use SSH identity key authentication:<a class="headerlink" href="#how-to-configure-esxesxi-to-use-ssh-identity-key-authentication" title="Permanent link">&para;</a></h4>
+<p tip="tip">SSH identity key authentication&nbsp;must be configured if SSH is used to
 manage the VM host.
 <em> Create an SSH key pair on the management node (or use a key you
 previously created):
@@ -207,19 +229,17 @@ scp /etc/vcl/vcl.key.pub <ESXi host>:/et
 {tip}
 </em> Test making an SSH connection using the key:
 {tip}
-ssh -i /etc/vcl/vcl.key <ESXi host>
-{tip}</p>
-<p>{color:#ff0000}{<em>}IMPORTANT:</em>{color} Under ESXi 4.x, the authorized_keys
+ssh -i /etc/vcl/vcl.key <ESXi host></p>
+<p>{color:#ff0000}{<em color="color">}IMPORTANT:</em> Under ESXi 4.x, the authorized_keys
 file is erased when the ESXi VM host is rebooted.&nbsp;Complete the
 following steps to&nbsp;make&nbsp;the authorized_keys file&nbsp;persistent:</p>
 <p><em>Note: VCL will perform these steps automatically when the 1st reservation
 assigned to the host is processed.</em></p>
 <ul>
-<li>Create a compressed tarball file containing the /.ssh directory:
+<li tip="tip">Create a compressed tarball file containing the /.ssh directory:
 {tip}
-tar -C / -czf bootbank/vcl.tgz .ssh
-{tip}</li>
-<li>Edit the /bootbank/boot.cfg file and append <em><em>' --- vcl.tgz'</em></em> to
+tar -C / -czf bootbank/vcl.tgz .ssh</li>
+<li tip="tip">Edit the /bootbank/boot.cfg file and append <em><em>' --- vcl.tgz'</em></em> to
 modules line as shown in the following example:
 {panel}
 kernel=b.z
@@ -233,31 +253,30 @@ bootstate=0
 {tip}
 Optionally you can run the following two commands:
 tar -C / -czf vcl.tgz .ssh
-BootModuleConfig.sh --add=vcl.tgz --verbose
-{tip}</li>
+BootModuleConfig.sh --add=vcl.tgz --verbose</li>
 </ul>
 <p><a name="VMwareConfiguration-VMHostProfileParameters"></a></p>
-<h2 id="vm-host-profile-parameters">VM Host Profile Parameters</h2>
+<h2 id="vm-host-profile-parameters">VM Host Profile Parameters<a class="headerlink" href="#vm-host-profile-parameters" title="Permanent link">&para;</a></h2>
 <p><a name="VMwareConfiguration-GeneralParameters"></a></p>
-<h3 id="general-parameters">General Parameters</h3>
+<h3 id="general-parameters">General Parameters<a class="headerlink" href="#general-parameters" title="Permanent link">&para;</a></h3>
 <p><a name="VMwareConfiguration-"></a></p>
-<h4></h4>
+<h4 id="_1"><a class="headerlink" href="#_1" title="Permanent link">&para;</a></h4>
 <p><a name="VMwareConfiguration-*Name*"></a></p>
-<h5 id="name"><em>Name</em></h5>
+<h5 id="name"><em>Name</em><a class="headerlink" href="#name" title="Permanent link">&para;</a></h5>
 <ul>
 <li>Descriptive name of the VM host&nbsp;profile</li>
 </ul>
 <p><a name="VMwareConfiguration-*Type*_(deprecated)_"></a></p>
-<h5 id="type-deprecated"><em>Type</em> <em>(deprecated)</em></h5>
+<h5 id="type-deprecated"><em>Type</em> <em>(deprecated)</em><a class="headerlink" href="#type-deprecated" title="Permanent link">&para;</a></h5>
 <ul>
 <li>Removed in VCL 2.3</li>
 </ul>
 <p><a name="VMwareConfiguration-*Image*_(optional)_"></a></p>
-<h5 id="image-optional"><em>Image</em> <em>(optional)</em></h5>
+<h5 id="image-optional"><em>Image</em> <em>(optional)</em><a class="headerlink" href="#image-optional" title="Permanent link">&para;</a></h5>
 <ul>
 <li>VCL hypervisor image installed on VM host computers using xCAT
-{info}{<em>}xCAT is not required. &nbsp;VM host computers may be installed
-manually or by some other means.</em>{info}</li>
+{info}{<em info="info">}xCAT is not required. &nbsp;VM host computers may be installed
+manually or by some other means.</em></li>
 <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. &nbsp;If the image property is configured, the image is
@@ -265,7 +284,7 @@ installed when a computer's state is cha
 Computers &gt; Computer Utilities</em></li>
 </ul>
 <p><a name="VMwareConfiguration-*Username/Password*_(optional)_"></a></p>
-<h5 id="usernamepassword-optional"><em>Username/Password</em> <em>(optional)</em></h5>
+<h5 id="usernamepassword-optional"><em>Username/Password</em> <em>(optional)</em><a class="headerlink" href="#usernamepassword-optional" title="Permanent link">&para;</a></h5>
 <ul>
 <li>Name and password&nbsp;of the&nbsp;administrative or root user residing
 on the VM host</li>
@@ -274,10 +293,10 @@ on the VM host</li>
 used to manage the VM host and VMs</li>
 </ul>
 <p><a name="VMwareConfiguration-StorageParameters"></a></p>
-<h3 id="storage-parameters">Storage Parameters</h3>
+<h3 id="storage-parameters">Storage Parameters<a class="headerlink" href="#storage-parameters" title="Permanent link">&para;</a></h3>
 <p>{anchor:resource}</p>
 <p><a name="VMwareConfiguration-ResourcePath_(optional)_"></a></p>
-<h5 id="resource-path-optional">Resource Path <em>(optional)</em></h5>
+<h5 id="resource-path-optional">Resource Path <em>(optional)</em><a class="headerlink" href="#resource-path-optional" title="Permanent link">&para;</a></h5>
 <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
@@ -285,7 +304,7 @@ contain Folders, Clusters, and Resource
 Example: /DatacenterA/Folder1/Cluster2/ResourcePool3</p>
 <p>{anchor:repository}</p>
 <p><a name="VMwareConfiguration-*RepositoryPath*_(optional)_"></a></p>
-<h5 id="repository-path-optional"><em>Repository Path</em> <em>(optional)</em></h5>
+<h5 id="repository-path-optional"><em>Repository Path</em> <em>(optional)</em><a class="headerlink" href="#repository-path-optional" title="Permanent link">&para;</a></h5>
 <ul>
 <li>Path where master copies of images are stored which are&nbsp;used to
 transfer images to VM host datastores or to other repositories:
@@ -322,11 +341,10 @@ to be transferred via SCP without having
 entire size of the VM's hard drive</li>
 </ul>
 <p><a name="VMwareConfiguration-RepositoryImageType"></a></p>
-<h5 id="repository-image-type">Repository Image Type</h5>
-<p>Virtual disk file format for images stored in the repository.
-{anchor:datastore}</p>
+<h5 id="repository-image-type">Repository Image Type<a class="headerlink" href="#repository-image-type" title="Permanent link">&para;</a></h5>
+<p anchor:datastore="anchor:datastore">Virtual disk file format for images stored in the repository.</p>
 <p><a name="VMwareConfiguration-*VirtualDiskPath(previouslyDatastorePath)*"></a></p>
-<h5 id="virtual-disk-path-previously-datastore-path"><em>Virtual Disk Path (previously Datastore Path)</em></h5>
+<h5 id="virtual-disk-path-previously-datastore-path"><em>Virtual Disk Path (previously Datastore Path)</em><a class="headerlink" href="#virtual-disk-path-previously-datastore-path" title="Permanent link">&para;</a></h5>
 <ul>
 <li>Location where master copies of images are stored which are used by
 running VMs</li>
@@ -355,10 +373,10 @@ read-only mode
 in the VM Working Directory Path dedicated for the VM</li>
 </ul>
 <p><a name="VMwareConfiguration-VirtualDiskImageType"></a></p>
-<h5 id="virtual-disk-image-type">Virtual Disk Image Type</h5>
+<h5 id="virtual-disk-image-type">Virtual Disk Image Type<a class="headerlink" href="#virtual-disk-image-type" title="Permanent link">&para;</a></h5>
 <p>Virtual disk file format for images stored in the virtual disk path.</p>
 <p><a name="VMwareConfiguration-VirtualDiskMode(previously*VMDisk)*"></a></p>
-<h5 id="virtual-disk-mode-previously-vm-disk">Virtual Disk Mode (previously <em>VM Disk)</em></h5>
+<h5 id="virtual-disk-mode-previously-vm-disk">Virtual Disk Mode (previously <em>VM Disk)</em><a class="headerlink" href="#virtual-disk-mode-previously-vm-disk" title="Permanent link">&para;</a></h5>
 <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:
@@ -367,23 +385,20 @@ resides is dedicated to a single host or
 dedicated network storage
 </em></strong> The VM host is the only host which accesses the Virtual Disk Path
 <strong><em> Repository Path must be configured
-** shared (previously networkdisk)
-</em></strong> The VM host's Virtual Disk Path&nbsp;is located on network storage
-which is shared by other VM hosts
-</strong>* Repository Path is optional</li>
+</em>* shared (previously networkdisk)</strong>* The VM host's Virtual Disk Path&nbsp;is located on network storage
+which is shared by other VM hosts</strong>* Repository Path is optional</li>
 </ul>
-<p>{note}
+<p note="note">{note}
 The Virtual Disk Mode (VM Disk) parameter does <em>not</em> determine whether or
 not:
 ...images are copied from the datastore to the repository during image
 capture
 ...images are copied from the repository to the datastore during image load
 These are determined by whether or not Repository Path is configured in the
-profile
-{note}</p>
+profile</p>
 <p>{anchor:vmpath}</p>
 <p><a name="VMwareConfiguration-VMWorkingDirectoryPath_(optional)_(previously*VMPath*)"></a></p>
-<h5 id="vm-working-directory-path-optional-previously-vm-path">VM Working Directory Path <em>(optional)</em> (previously <em>VM Path</em>)</h5>
+<h5 id="vm-working-directory-path-optional-previously-vm-path">VM Working Directory Path <em>(optional)</em> (previously <em>VM Path</em>)<a class="headerlink" href="#vm-working-directory-path-optional-previously-vm-path" title="Permanent link">&para;</a></h5>
 <ul>
 <li>Defines path on VM host where VM working directories will reside
 (contains .vmx, delta, .vswp, nvram files)</li>
@@ -403,11 +418,11 @@ volume but a subdirectory should be crea
 optimized for read-write performance</li>
 </ul>
 <p><a name="VMwareConfiguration-"></a></p>
-<h5></h5>
+<h5 id="_2"><a class="headerlink" href="#_2" title="Permanent link">&para;</a></h5>
 <p><a name="VMwareConfiguration-NetworkingParameters"></a></p>
-<h4 id="networking-parameters">Networking Parameters</h4>
+<h4 id="networking-parameters">Networking Parameters<a class="headerlink" href="#networking-parameters" title="Permanent link">&para;</a></h4>
 <p><a name="VMwareConfiguration-*VMNetwork(previouslyVirtualSwitch)*"></a></p>
-<h5 id="vm-network-previously-virtual-switch"><em>VM Network (previously Virtual Switch)</em></h5>
+<h5 id="vm-network-previously-virtual-switch"><em>VM Network (previously Virtual Switch)</em><a class="headerlink" href="#vm-network-previously-virtual-switch" title="Permanent link">&para;</a></h5>
 <ul>
 <li>VM Network 0 (previously Virtual Switch 0) - private VCL
 management&nbsp;network</li>
@@ -430,18 +445,18 @@ Port Group Network Labels</em> configure
 </li>
 </ul>
 <p><a name="VMwareConfiguration-*Generateeth0/eth1MAC*"></a></p>
-<h5 id="generate-eth0eth1-mac"><em>Generate eth0/eth1 MAC</em></h5>
+<h5 id="generate-eth0eth1-mac"><em>Generate eth0/eth1 MAC</em><a class="headerlink" href="#generate-eth0eth1-mac" title="Permanent link">&para;</a></h5>
 <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>
 <p><a name="VMwareConfiguration-ConfigurationExamples"></a></p>
-<h2 id="configuration-examples">Configuration Examples</h2>
+<h2 id="configuration-examples">Configuration Examples<a class="headerlink" href="#configuration-examples" title="Permanent link">&para;</a></h2>
 <p><a name="VMwareConfiguration-LocalDiskOnly-RepositoryMountedviaNFS"></a></p>
-<h3 id="local-disk-only-repository-mounted-via-nfs">Local Disk Only - Repository Mounted via NFS</h3>
+<h3 id="local-disk-only-repository-mounted-via-nfs">Local Disk Only - Repository Mounted via NFS<a class="headerlink" href="#local-disk-only-repository-mounted-via-nfs" title="Permanent link">&para;</a></h3>
 <p><a name="VMwareConfiguration-!local-only-nfs.gif!"></a></p>
-<h3 id="local-only-nfsgif">!local-only-nfs.gif!</h3>
+<h3 id="local-only-nfsgif">!local-only-nfs.gif!<a class="headerlink" href="#local-only-nfsgif" title="Permanent link">&para;</a></h3>
 <p>The diagram above shows a simple VCL configuration with 1 management node
 and 2 VMware ESXi hosts.&nbsp; Network storage is not used.
 The local disks on the VM hosts are used to store all of the files used by
@@ -466,7 +481,7 @@ allows images to be deleted from the VM
 Disk Path) if another image must be copied from the repository and not
 enough space is available.</p>
 <p><a name="VMwareConfiguration-LocalDiskOnly-RepositoryNotAvailableviaNFS"></a></p>
-<h3 id="local-disk-only-repository-not-available-via-nfs">Local Disk Only - Repository Not Available via NFS</h3>
+<h3 id="local-disk-only-repository-not-available-via-nfs">Local Disk Only - Repository Not Available via NFS<a class="headerlink" href="#local-disk-only-repository-not-available-via-nfs" title="Permanent link">&para;</a></h3>
 <p>!local-only-scp.gif!</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.&nbsp;
@@ -489,7 +504,7 @@ path exists on the VM host.&nbsp; If not
 mounted directly on the VM host and the Repository Path value refers to a
 location on the management node.</p>
 <p><a name="VMwareConfiguration-NetworkStorageOnly-NoRepository"></a></p>
-<h3 id="network-storage-only-no-repository">Network Storage Only - No Repository</h3>
+<h3 id="network-storage-only-no-repository">Network Storage Only - No Repository<a class="headerlink" href="#network-storage-only-no-repository" title="Permanent link">&para;</a></h3>
 <p>!network-only-no-repo.gif!</p>
 <p>This is an example of a simple configuration where the network storage is
 used.</p>

Modified: websites/staging/vcl/trunk/content/confluence_export/vmware-provisioning-module-information.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/vmware-provisioning-module-information.html (original)
+++ websites/staging/vcl/trunk/content/confluence_export/vmware-provisioning-module-information.html Wed Oct 18 19:55:31 2017
@@ -36,7 +36,18 @@
   </div>
 
   <div id="navigation"> 
-  <ul>
+  <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
 <li><a href="/index.html">Information</a><ul>
 <li><a href="/info/features.html">Features</a></li>
 <li><a href="/info/architecture.html">Architecture</a></li>
@@ -53,7 +64,7 @@
 <li><a href="/comm/index.html">Community</a><ul>
 <li><a href="/comm/index.html#getInvolved">Getting Involved</a></li>
 <li><a href="/comm/index.html#mail-list">Mailing Lists</a></li>
-<li><a href="/comm/wiki.html">Wiki</a></li>
+<li><a href="https://cwiki.apache.org/confluence/display/VCL/Apache+VCL" target="_blank">Wiki</a></li>
 <li><a href="/dev/index.html">Development</a><ul>
 <li><a href="/dev/jira.html">Issue Tracking</a></li>
 <li><a href="/dev/code-documentation.html">Code Documentation</a></li>
@@ -72,20 +83,31 @@
   
   <div id="content">
     <h1 class="title">VMware Provisioning Module Information</h1>
-    <p><a name="VMwareProvisioningModuleInformation-VMwareProvisioningModule"></a></p>
-<h2 id="vmware-provisioning-module">VMware Provisioning Module</h2>
+    <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p><a name="VMwareProvisioningModuleInformation-VMwareProvisioningModule"></a></p>
+<h2 id="vmware-provisioning-module">VMware Provisioning Module<a class="headerlink" href="#vmware-provisioning-module" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Source file: managementnode/lib/VCL/Module/Provisioning/VMware/VMware.pm</li>
 </ul>
 <p><a name="VMwareProvisioningModuleInformation-SupportedVMwareProducts"></a></p>
-<h4 id="supported-vmware-products">Supported VMware Products</h4>
+<h4 id="supported-vmware-products">Supported VMware Products<a class="headerlink" href="#supported-vmware-products" title="Permanent link">&para;</a></h4>
 <ul>
 <li>VMware Server 2.0</li>
 <li>VMware ESX/ESXi 3.5</li>
 <li>VMware ESX/ESXi 4.0</li>
 </ul>
 <p><a name="VMwareProvisioningModuleInformation-SupportedVMware&nbsp;APIs,SDKs,&CLIs"></a></p>
-<h4 id="supported-vmwarewzxhzdk6apis-sdks-clis">Supported VMware&nbsp;APIs, SDKs, &amp; CLIs</h4>
+<h4 id="supported-vmwareapis-sdks-clis">Supported VMware&nbsp;APIs, SDKs, &amp; CLIs<a class="headerlink" href="#supported-vmwareapis-sdks-clis" title="Permanent link">&para;</a></h4>
 <p>There are several different methods to control VMware hosts and virtual
 machines.&nbsp; The main VMware.pm module should remain as
 SDK/API/CLI-agnostic as possible.&nbsp; All code which interacts with a
@@ -119,7 +141,7 @@ restricted license-
 system
 ** Can be used if the the VMware host is running with a restricted license</p>
 <p><a name="VMwareProvisioningModuleInformation-RequiredUtilityModuleSubroutines"></a></p>
-<h3 id="required-utility-module-subroutines">Required Utility Module Subroutines</h3>
+<h3 id="required-utility-module-subroutines">Required Utility Module Subroutines<a class="headerlink" href="#required-utility-module-subroutines" title="Permanent link">&para;</a></h3>
 <ul>
 <li>get_registered_vms</li>
 <li>vm_register</li>
@@ -134,7 +156,7 @@ system
 <li>get_virtual_disk_type</li>
 </ul>
 <p><a name="VMwareProvisioningModuleInformation-RequiredOSModuleSubroutines"></a></p>
-<h3 id="required-os-module-subroutines">Required OS Module Subroutines</h3>
+<h3 id="required-os-module-subroutines">Required OS Module Subroutines<a class="headerlink" href="#required-os-module-subroutines" title="Permanent link">&para;</a></h3>
 <ul>
 <li>find_files</li>
 <li>copy_file</li>

Modified: websites/staging/vcl/trunk/content/confluence_export/web-code-installation.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/web-code-installation.html (original)
+++ websites/staging/vcl/trunk/content/confluence_export/web-code-installation.html Wed Oct 18 19:55:31 2017
@@ -36,7 +36,18 @@
   </div>
 
   <div id="navigation"> 
-  <ul>
+  <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
 <li><a href="/index.html">Information</a><ul>
 <li><a href="/info/features.html">Features</a></li>
 <li><a href="/info/architecture.html">Architecture</a></li>
@@ -53,7 +64,7 @@
 <li><a href="/comm/index.html">Community</a><ul>
 <li><a href="/comm/index.html#getInvolved">Getting Involved</a></li>
 <li><a href="/comm/index.html#mail-list">Mailing Lists</a></li>
-<li><a href="/comm/wiki.html">Wiki</a></li>
+<li><a href="https://cwiki.apache.org/confluence/display/VCL/Apache+VCL" target="_blank">Wiki</a></li>
 <li><a href="/dev/index.html">Development</a><ul>
 <li><a href="/dev/jira.html">Issue Tracking</a></li>
 <li><a href="/dev/code-documentation.html">Code Documentation</a></li>
@@ -72,12 +83,23 @@
   
   <div id="content">
     <h1 class="title">Web Code Installation</h1>
-    <p>{excerpt}This page describes how to install and configure the frontend VCL
+    <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>{excerpt}This page describes how to install and configure the frontend VCL
 web code components including the web server prerequisites and frontend VCL
 web code. It also describes how to add local web accounts, configure LDAP
 authentication, and set the timezone correctly.{excerpt}</p>
 <p><a name="WebCodeInstallation-*Prerequisites*"></a></p>
-<h2 id="prerequisites"><em>Prerequisites</em></h2>
+<h2 id="prerequisites"><em>Prerequisites</em><a class="headerlink" href="#prerequisites" title="Permanent link">&para;</a></h2>
 <p>Your web server should meet the following criteria before installing the
 frontend VCL code:
 <em> Apache HTTP Server v1.3 or v2.x with SSL enabled - while VCL may run
@@ -99,7 +121,7 @@ module):
 * php-mcrypt requires libmcrypt and mcrypt libraries as dependencies. 
 These may need to be installed first.</p>
 <p><a name="WebCodeInstallation-*InstallingVCLFrontendWebCode*"></a></p>
-<h2 id="installing-vcl-frontend-web-code"><em>Installing VCL Frontend Web Code</em></h2>
+<h2 id="installing-vcl-frontend-web-code"><em>Installing VCL Frontend Web Code</em><a class="headerlink" href="#installing-vcl-frontend-web-code" title="Permanent link">&para;</a></h2>
 <ol>
 <li>If you haven't already done so, download and extract a copy of the latest
 release. There is a link to it under the Project Resources section on our
@@ -211,7 +233,7 @@ isn't listed after clicking Submit)</li>
 started checking in, you should be able to make a reservation</li>
 </ol>
 <p><a name="WebCodeInstallation-*Addingextralocalaccounts*"></a></p>
-<h2 id="adding-extra-local-accounts"><em>Adding extra local accounts</em></h2>
+<h2 id="adding-extra-local-accounts"><em>Adding extra local accounts</em><a class="headerlink" href="#adding-extra-local-accounts" title="Permanent link">&para;</a></h2>
 <p>There's not currently a tool for this.  You will need to add entries
 directly to the database.
 1. add entry to user table</p>
@@ -240,7 +262,7 @@ echo -n 'thedog11111111' \| sha1sum
 Once a user has been added, the user can go to User Preferences to change
 his/her password</p>
 <p><a name="WebCodeInstallation-*AddingLDAPauthentication*"></a></p>
-<h2 id="adding-ldap-authentication"><em>Adding LDAP authentication</em></h2>
+<h2 id="adding-ldap-authentication"><em>Adding LDAP authentication</em><a class="headerlink" href="#adding-ldap-authentication" title="Permanent link">&para;</a></h2>
 <ol>
 <li>fill in the necessary information in vcl/.ht-inc/conf.php</li>
 <li>add an entry to the affiliation table and use the id for that entry as
@@ -249,7 +271,7 @@ his/her password</p>
 in vcl/.ht-inc/conf.php</li>
 </ol>
 <p><a name="WebCodeInstallation-*SettingTimeZone*"></a></p>
-<h2 id="setting-time-zone"><em>Setting Time Zone</em></h2>
+<h2 id="setting-time-zone"><em>Setting Time Zone</em><a class="headerlink" href="#setting-time-zone" title="Permanent link">&para;</a></h2>
 <ol>
 <li>Edit /var/www/html/vcl/.ht-inc/php5extras.php to indicate the correct
 time zone:

Modified: websites/staging/vcl/trunk/content/dev/code-documentation.html
==============================================================================
--- websites/staging/vcl/trunk/content/dev/code-documentation.html (original)
+++ websites/staging/vcl/trunk/content/dev/code-documentation.html Wed Oct 18 19:55:31 2017
@@ -36,7 +36,18 @@
   </div>
 
   <div id="navigation"> 
-  <ul>
+  <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
 <li><a href="/index.html">Information</a><ul>
 <li><a href="/info/features.html">Features</a></li>
 <li><a href="/info/architecture.html">Architecture</a></li>
@@ -53,7 +64,7 @@
 <li><a href="/comm/index.html">Community</a><ul>
 <li><a href="/comm/index.html#getInvolved">Getting Involved</a></li>
 <li><a href="/comm/index.html#mail-list">Mailing Lists</a></li>
-<li><a href="/comm/wiki.html">Wiki</a></li>
+<li><a href="https://cwiki.apache.org/confluence/display/VCL/Apache+VCL" target="_blank">Wiki</a></li>
 <li><a href="/dev/index.html">Development</a><ul>
 <li><a href="/dev/jira.html">Issue Tracking</a></li>
 <li><a href="/dev/code-documentation.html">Code Documentation</a></li>
@@ -72,7 +83,18 @@
   
   <div id="content">
     <h1 class="title">Code Documentation</h1>
-    <h2 id="backend-code-documentation">Backend Code Documentation</h2>
+    <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="backend-code-documentation">Backend Code Documentation<a class="headerlink" href="#backend-code-documentation" title="Permanent link">&para;</a></h2>
 <p><a href="image-capture-sequence.html">Image Capture Sequence</a></p>
   </div>
   

Modified: websites/staging/vcl/trunk/content/dev/configsystem.html
==============================================================================
--- websites/staging/vcl/trunk/content/dev/configsystem.html (original)
+++ websites/staging/vcl/trunk/content/dev/configsystem.html Wed Oct 18 19:55:31 2017
@@ -36,7 +36,18 @@
   </div>
 
   <div id="navigation"> 
-  <ul>
+  <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
 <li><a href="/index.html">Information</a><ul>
 <li><a href="/info/features.html">Features</a></li>
 <li><a href="/info/architecture.html">Architecture</a></li>
@@ -53,7 +64,7 @@
 <li><a href="/comm/index.html">Community</a><ul>
 <li><a href="/comm/index.html#getInvolved">Getting Involved</a></li>
 <li><a href="/comm/index.html#mail-list">Mailing Lists</a></li>
-<li><a href="/comm/wiki.html">Wiki</a></li>
+<li><a href="https://cwiki.apache.org/confluence/display/VCL/Apache+VCL" target="_blank">Wiki</a></li>
 <li><a href="/dev/index.html">Development</a><ul>
 <li><a href="/dev/jira.html">Issue Tracking</a></li>
 <li><a href="/dev/code-documentation.html">Code Documentation</a></li>
@@ -72,7 +83,18 @@
   
   <div id="content">
     <h1 class="title">New Configuration System</h1>
-    <div class="toc">
+    <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<div class="toc">
 <ul>
 <li><a href="#database-schema">Database schema</a></li>
 <li><a href="#examples">Examples</a><ul>
@@ -84,7 +106,7 @@
 </ul>
 </div>
 <p>This page describes a new configuration system that will be added to VCL that can be used to dynamically configure deployed systems.</p>
-<h2 id="database-schema">Database schema</h2>
+<h2 id="database-schema">Database schema<a class="headerlink" href="#database-schema" title="Permanent link">&para;</a></h2>
 <p>config:</p>
 <ul>
 <li>id - id of record</li>
@@ -169,8 +191,8 @@
 </ul>
 </li>
 </ul>
-<h2 id="examples">Examples</h2>
-<h3 id="assigning-a-vlan-to-an-image">Assigning a VLAN to an image</h3>
+<h2 id="examples">Examples<a class="headerlink" href="#examples" title="Permanent link">&para;</a></h2>
+<h3 id="assigning-a-vlan-to-an-image">Assigning a VLAN to an image<a class="headerlink" href="#assigning-a-vlan-to-an-image" title="Permanent link">&para;</a></h3>
 <p>This example shows how to assign a VLAN to an image.</p>
 <p>For this example, we'll use the following values from other tables:</p>
 <ul>
@@ -228,7 +250,7 @@ configinstancevariable:
 </tr>
 <tr><td>6854</td><td>486</td><td>30</td></tr>
 </table></p>
-<h3 id="hadoop-cluster-with-variable-amount-of-slave-nodes">Hadoop cluster with variable amount of slave nodes</h3>
+<h3 id="hadoop-cluster-with-variable-amount-of-slave-nodes">Hadoop cluster with variable amount of slave nodes<a class="headerlink" href="#hadoop-cluster-with-variable-amount-of-slave-nodes" title="Permanent link">&para;</a></h3>
 <p>This example shows how a hadoop cluster can be requested with 5-10 slave nodes.
 It can be useful to have the variable amount because 10 nodes may
 be desired, but you may want to cluster anyway if only 5 nodes are
@@ -306,7 +328,7 @@ configinstancevariable:
 <tr><td>5023</td><td>147</td><td>5</td></tr>
 <tr><td>5023</td><td>148</td><td>10</td></tr>
 </table></p>
-<h3 id="sas-cluster">SAS cluster</h3>
+<h3 id="sas-cluster">SAS cluster<a class="headerlink" href="#sas-cluster" title="Permanent link">&para;</a></h3>
 <p>This example shows how to configure a SAS cluster of 3 nodes: meta, midtier, and apps so that they are all deployed and then started in the correct order.</p>
 <p>For this example, we'll use the following values from other tables:</p>
 <ul>

Modified: websites/staging/vcl/trunk/content/dev/database-schema.html
==============================================================================
--- websites/staging/vcl/trunk/content/dev/database-schema.html (original)
+++ websites/staging/vcl/trunk/content/dev/database-schema.html Wed Oct 18 19:55:31 2017
@@ -36,7 +36,18 @@
   </div>
 
   <div id="navigation"> 
-  <ul>
+  <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
 <li><a href="/index.html">Information</a><ul>
 <li><a href="/info/features.html">Features</a></li>
 <li><a href="/info/architecture.html">Architecture</a></li>
@@ -53,7 +64,7 @@
 <li><a href="/comm/index.html">Community</a><ul>
 <li><a href="/comm/index.html#getInvolved">Getting Involved</a></li>
 <li><a href="/comm/index.html#mail-list">Mailing Lists</a></li>
-<li><a href="/comm/wiki.html">Wiki</a></li>
+<li><a href="https://cwiki.apache.org/confluence/display/VCL/Apache+VCL" target="_blank">Wiki</a></li>
 <li><a href="/dev/index.html">Development</a><ul>
 <li><a href="/dev/jira.html">Issue Tracking</a></li>
 <li><a href="/dev/code-documentation.html">Code Documentation</a></li>
@@ -72,7 +83,18 @@
   
   <div id="content">
     <h1 class="title">Database Schema</h1>
-    <div class="toc">
+    <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<div class="toc">
 <ul>
 <li><a href="#affiliation-table">affiliation table</a></li>
 <li><a href="#blockcomputers-table">blockComputers table</a></li>
@@ -153,7 +175,7 @@
 <li><a href="#xmlrpclog-table">xmlrpcLog table</a></li>
 </ul>
 </div>
-<h3 id="affiliation-table">affiliation table</h3>
+<h3 id="affiliation-table">affiliation table<a class="headerlink" href="#affiliation-table" title="Permanent link">&para;</a></h3>
 <p>This table contains a list of affiliations that can access this VCL site.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -165,7 +187,7 @@
 <li><strong>shibonly</strong> - 1 if this affiliation can only be authenticated via shibboleth, 0 if LDAP is also set up</li>
 <li><strong>theme</strong> - theme to be used for the web UI for users with this affiliation; must match something under the themes directory of the web code</li>
 </ul>
-<h3 id="blockcomputers-table">blockComputers table</h3>
+<h3 id="blockcomputers-table">blockComputers table<a class="headerlink" href="#blockcomputers-table" title="Permanent link">&para;</a></h3>
 <p>This table tracks which computers have been allocated to individual block allocation time slots.</p>
 <ul>
 <li><strong>blockTimeid</strong> - reference to blockTimes.id</li>
@@ -173,7 +195,7 @@
 <li><strong>imageid</strong> - reference to image.id</li>
 <li><strong>reloadrequestid</strong> - reference to request.id - reload reservation for preloading this node</li>
 </ul>
-<h3 id="blockrequest-table">blockRequest table</h3>
+<h3 id="blockrequest-table">blockRequest table<a class="headerlink" href="#blockrequest-table" title="Permanent link">&para;</a></h3>
 <p>This table contains all of the block allocations that have been requested and their current state.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -190,7 +212,7 @@
 <li><strong>status</strong> - enum field - requested, accepted, completed, reject - current status of the block allocation</li>
 <li><strong>comments</strong> - any comments entered by the person that requested the block allocation</li>
 </ul>
-<h3 id="blocktimes-table">blockTimes table</h3>
+<h3 id="blocktimes-table">blockTimes table<a class="headerlink" href="#blocktimes-table" title="Permanent link">&para;</a></h3>
 <p>This table contains all of the time slots associated with a block allocation that are active or have not yet been reached. Time slots are deleted after they are completed.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -200,7 +222,7 @@
 <li><strong>processed</strong> - flag for vcld - 1 if block time has been processed by vcld, 0 if not</li>
 <li><strong>skip</strong> - flag for users to skip individual instances of repeating block allocations - 1 to skip, 0 to use</li>
 </ul>
-<h3 id="blockwebdate-table">blockWebDate table</h3>
+<h3 id="blockwebdate-table">blockWebDate table<a class="headerlink" href="#blockwebdate-table" title="Permanent link">&para;</a></h3>
 <p>This table contains date related items associated with a block allocation so that they can more easily be retrieved when editing a block allocation.</p>
 <ul>
 <li><strong>blockRequestid</strong> - reference to blockRequest.id</li>
@@ -209,7 +231,7 @@
 <li><strong>days</strong> - for weekly repeating blocks, this is a bitmask of the selected days; for monthly repeating blocks, this is the day of the week; for lists, this is the order the item is in the set of dates</li>
 <li><strong>weeknum</strong> - only used for monthly repeating blocks - the selected week of the month</li>
 </ul>
-<h3 id="blockwebtime-table">blockWebTime table</h3>
+<h3 id="blockwebtime-table">blockWebTime table<a class="headerlink" href="#blockwebtime-table" title="Permanent link">&para;</a></h3>
 <p>This table contains time related items associated with a block allocation so that they can more easily be retrieved when editing a block allocation.</p>
 <ul>
 <li><strong>blockRequestid</strong> - reference to blockRequest.id</li>
@@ -221,7 +243,7 @@
 <li><strong>endmeridian</strong> - end meridian of block allocation</li>
 <li><strong>order</strong> - for weekly and monthly repeating blocks, this is the sequential order of the time slot; for lists, it is the sequential order of the date/time</li>
 </ul>
-<h3 id="changelog-table">changelog table</h3>
+<h3 id="changelog-table">changelog table<a class="headerlink" href="#changelog-table" title="Permanent link">&para;</a></h3>
 <p>This table logs changes made to reservations.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -236,7 +258,7 @@
 <li><strong>timestamp</strong> - datetime entry was added</li>
 <li><strong>other</strong> - for recording events users cause to happen to reservations such as reinstalling, rebooting, or changing admin/login user groups (recorded by calling addChangeLogEntryOther in the web code)</li>
 </ul>
-<h3 id="clickthroughs-table">clickThroughs table</h3>
+<h3 id="clickthroughs-table">clickThroughs table<a class="headerlink" href="#clickthroughs-table" title="Permanent link">&para;</a></h3>
 <p>This table logs click through agreements users must agree to when they create images.</p>
 <ul>
 <li><strong>userid</strong> - reference to user.id - user that clicked agreement</li>
@@ -245,7 +267,7 @@
 <li><strong>accepted</strong> - datetime agreement clicked</li>
 <li><strong>agreement</strong> - text of agreement at time it was clicked</li>
 </ul>
-<h3 id="computer-table">computer table</h3>
+<h3 id="computer-table">computer table<a class="headerlink" href="#computer-table" title="Permanent link">&para;</a></h3>
 <p>This table contains all information about compute nodes and VMs that VCL controls. All bare metal computers, virtual hosts, and virtual machines must have an entry in this table.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -283,14 +305,14 @@
 <li><strong>vmtypeid</strong> - reference to vmtype.id - only used for virtual machines, this is the type of the VM (vmware, xen, kvm, etc)</li>
 <li><strong>predictivemoduleid</strong> - module.id for the perl module that handles what to do with the node after a reservation</li>
 </ul>
-<h3 id="computerloadflow-table">computerloadflow table</h3>
+<h3 id="computerloadflow-table">computerloadflow table<a class="headerlink" href="#computerloadflow-table" title="Permanent link">&para;</a></h3>
 <p>This table contains entries that establish a flow of states that are followed when a reservation is being deployed so that users can have feedback on the current reservations page about their reservations.</p>
 <ul>
 <li><strong>computerloadstateid</strong> - reference to computerloadstate.id</li>
 <li><strong>nextstateid</strong> - reference to computerloadstate.id - the computer load state that follows this one</li>
 <li><strong>type</strong> - type of load this sequence is for</li>
 </ul>
-<h3 id="computerloadlog-table">computerloadlog table</h3>
+<h3 id="computerloadlog-table">computerloadlog table<a class="headerlink" href="#computerloadlog-table" title="Permanent link">&para;</a></h3>
 <p>This table contains actual log entries for each state processed when a reservation is being deployed so that users can have feedback on the current reservations page about their reservations.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -300,7 +322,7 @@
 <li><strong>timestamp</strong> - date/time entry entered into log</li>
 <li><strong>additionalinfo</strong> - details about this entry</li>
 </ul>
-<h3 id="computerloadstate-table">computerloadstate table</h3>
+<h3 id="computerloadstate-table">computerloadstate table<a class="headerlink" href="#computerloadstate-table" title="Permanent link">&para;</a></h3>
 <p>This table contains the load states that a reservation goes through when being deployed and their estimated time so that an estimate of how much longer the deploy will take can be generated.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -308,7 +330,7 @@
 <li><strong>prettyname</strong> - more descriptive name of state</li>
 <li><strong>est</strong> - estimated time for state in minutes</li>
 </ul>
-<h3 id="connectlog-table">connectlog table</h3>
+<h3 id="connectlog-table">connectlog table<a class="headerlink" href="#connectlog-table" title="Permanent link">&para;</a></h3>
 <p>This table contains information about users connecting to reservations.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -319,7 +341,7 @@
 <li><strong>varified</strong> - </li>
 <li><strong>timestamp</strong> - time stamp when event occurred</li>
 </ul>
-<h3 id="connectmethod-table">connectmethod table</h3>
+<h3 id="connectmethod-table">connectmethod table<a class="headerlink" href="#connectmethod-table" title="Permanent link">&para;</a></h3>
 <p>This table contains all of the connect methods available to be assigned to an image.  Connect methods are things like RDP, ssh, VNC, etc.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -329,7 +351,7 @@
 <li><strong>servicename</strong> - name of service to be started to enable connect method on provisioned node</li>
 <li><strong>startupscript</strong> - name of script to be run to enable connect method on provisioned node</li>
 </ul>
-<h3 id="connectmethodmap-table">connectmethodmap table</h3>
+<h3 id="connectmethodmap-table">connectmethodmap table<a class="headerlink" href="#connectmethodmap-table" title="Permanent link">&para;</a></h3>
 <p>This table contains two types of information and can be somewhat confusing.  It tracks which connect methods are mapped to which OS types, OSes, and image revisions.  It also contains which methods can be assigned to which OS types and OSes.  Entries that have autoprovisioned set to 0 or 1 are entries that tell whether or not the image can be assigned to that OS type or OS.  Entries that have autoprovisioned set to NULL tell whether that method is enabled in addition to default methods for the image, or whether that method is a default one but disable for the image.</p>
 <ul>
 <li><strong>connectmethodid</strong> - reference to connectmethod.id</li>
@@ -339,7 +361,7 @@
 <li><strong>disabled</strong> - flag telling if method is enabled/disabled for combination of OStypeid, OSid, and imagerevisionid</li>
 <li><strong>autoprovisioned</strong> - NULL, 0, or 1 - flag to tell if this connect method can be autoprovisioned by vcld or if the image owner must install the software to enable it</li>
 </ul>
-<h3 id="connectmethodport">connectmethodport</h3>
+<h3 id="connectmethodport">connectmethodport<a class="headerlink" href="#connectmethodport" title="Permanent link">&para;</a></h3>
 <p>This table contains the ports associated with a connectmethod. The ports were initially part of the connectmethod table, but separating them out allowed for multiple ports per connect method.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -347,7 +369,7 @@
 <li><strong>protocol</strong> - TCP or UDP</li>
 <li><strong>port</strong> - tcp or udp port number</li>
 </ul>
-<h3 id="continuations-table">continuations table</h3>
+<h3 id="continuations-table">continuations table<a class="headerlink" href="#continuations-table" title="Permanent link">&para;</a></h3>
 <p>This table contains "continuations" which are basically saved states that can then be submitted by the frontend to perform an action.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -360,14 +382,14 @@
 <li><strong>parentid</strong> - reference to continuations.id - parent of this continuation for continuation chains (can be NULL)</li>
 <li><strong>deletefromid</strong> - reference to continuations.id - id in a continuation chain from which to start deleting the chain</li>
 </ul>
-<h3 id="documentation-table">documentation table</h3>
+<h3 id="documentation-table">documentation table<a class="headerlink" href="#documentation-table" title="Permanent link">&para;</a></h3>
 <p>This table is deprecated.  At one time, there was a built in documentation wiki like part of the site.</p>
 <ul>
 <li><strong>name</strong> - name of entry</li>
 <li><strong>title</strong> - title of documentation item</li>
 <li><strong>data</strong> - text of documentation item</li>
 </ul>
-<h3 id="image-table">image table</h3>
+<h3 id="image-table">image table<a class="headerlink" href="#image-table" title="Permanent link">&para;</a></h3>
 <p>This table contains all information about the images available through VCL.  It comes with a single required special image - "No image" that is used to signify when a computer is not loaded with anything.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -396,7 +418,7 @@
 <li><strong>usage</strong> - notes on how to use image displayed on Connect page</li>
 <li><strong>basedoffrevisionid</strong> - reference to imagerevision.id - image revision this image was based off of</li>
 </ul>
-<h3 id="imagemeta-table">imagemeta table</h3>
+<h3 id="imagemeta-table">imagemeta table<a class="headerlink" href="#imagemeta-table" title="Permanent link">&para;</a></h3>
 <p>This table contains additional information about some images.  It was added so that the extra information would not needed to be recorded for every image when most of them would not need it.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -408,7 +430,7 @@
 <li><strong>rootaccess</strong> - flag to tell if users should have root access on reservations for image - 1 to have it, 0 not to</li>
 <li><strong>sethostname</strong> - flag to determine if vcld should set the hostname of the computer after an image is deployed to the computer.hostname entry for the computer; default value is NULL; default behaviour for windows is not to set it; default behaviour for linux is to set it</li>
 </ul>
-<h3 id="imagerevision-table">imagerevision table</h3>
+<h3 id="imagerevision-table">imagerevision table<a class="headerlink" href="#imagerevision-table" title="Permanent link">&para;</a></h3>
 <p>This table contains an entry for every revision (including the initial one) of each image.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -423,26 +445,26 @@
 <li><strong>imagename</strong> - system name of revision</li>
 <li><strong>autocaptured</strong> - flag to tell if this was an auto-captured revision - 1 if it was, 0 otherwise</li>
 </ul>
-<h3 id="imagerevisioninfo">imagerevisioninfo</h3>
+<h3 id="imagerevisioninfo">imagerevisioninfo<a class="headerlink" href="#imagerevisioninfo" title="Permanent link">&para;</a></h3>
 <ul>
 <li><strong>imagerevisionid</strong> - reference to imagerevision.id</li>
 <li><strong>usernames</strong> - </li>
 <li><strong>firewallenabled</strong> - </li>
 <li><strong>timestamp</strong> - </li>
 </ul>
-<h3 id="imagetype">imagetype</h3>
+<h3 id="imagetype">imagetype<a class="headerlink" href="#imagetype" title="Permanent link">&para;</a></h3>
 <p>This table is a list of all of the types of images VCL can handle.  As of 2.4.2, these values are kickstart, lab, none, partimage, partimage-ng, qcow2, vdi, and vmdk.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
 <li><strong>name</strong> - name of entry</li>
 </ul>
-<h3 id="imtype-table">IMtype table</h3>
+<h3 id="imtype-table">IMtype table<a class="headerlink" href="#imtype-table" title="Permanent link">&para;</a></h3>
 <p>This table never really got used.  The idea was the people could be notified via IM in addition to or instead of via email.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
 <li><strong>name</strong> - name of entry</li>
 </ul>
-<h3 id="localauth-table">localauth table</h3>
+<h3 id="localauth-table">localauth table<a class="headerlink" href="#localauth-table" title="Permanent link">&para;</a></h3>
 <p>This table contains password hashes for local accounts.</p>
 <ul>
 <li><strong>userid</strong> - reference to user.id</li>
@@ -451,7 +473,7 @@
 <li><strong>lastupdated</strong> - date/time entry was last updated</li>
 <li><strong>lockedout</strong> - (unused) flag to tell if this account is locked out - 1 if locked out, 0 otherwise</li>
 </ul>
-<h3 id="log-table">log table</h3>
+<h3 id="log-table">log table<a class="headerlink" href="#log-table" title="Permanent link">&para;</a></h3>
 <p>This table contains an entry for every reservation made in VCL except for those made by the special account 'vclreload'.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -469,7 +491,7 @@
 <li><strong>imageid</strong> - reference to image.id</li>
 <li><strong>size</strong> - ??</li>
 </ul>
-<h3 id="loginlog-table">loginlog table</h3>
+<h3 id="loginlog-table">loginlog table<a class="headerlink" href="#loginlog-table" title="Permanent link">&para;</a></h3>
 <p>This table contains a log of every authentication attempt.</p>
 <ul>
 <li><strong>user</strong> - user id entered on login page</li>
@@ -480,7 +502,7 @@
 <li><strong>remoteIP</strong> - IP address of user's machine</li>
 <li><strong>code</strong> - either "none" or "invalid credentials" - used for recording when an LDAP server responds with "invalid credentials" when attempting to validate a username/password combination</li>
 </ul>
-<h3 id="managementnode-table">managementnode table</h3>
+<h3 id="managementnode-table">managementnode table<a class="headerlink" href="#managementnode-table" title="Permanent link">&para;</a></h3>
 <p>This table contains information about each management node.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -506,7 +528,7 @@
 NOT_STANDALONE - list of affiliations for which federated authentication is used for Linux images, meaning vcld does not need to set a password for users when creating their reservations because the image will handle it via federated authentication</li>
 <li><strong>availablenetworks</strong> - list of networks for which the management node is capable of configuring fixed (static) addresses for server reservations</li>
 </ul>
-<h3 id="module-table">module table</h3>
+<h3 id="module-table">module table<a class="headerlink" href="#module-table" title="Permanent link">&para;</a></h3>
 <p>This table contains information about the various perl modules that are part of vcld.</p>
 <ul>
 <li><strong>id</strong> - id of module</li>
@@ -515,7 +537,7 @@ NOT_STANDALONE - list of affiliations fo
 <li><strong>description</strong> - description of module</li>
 <li><strong>perlpackage</strong> - string to use when including this module in perl scripts</li>
 </ul>
-<h3 id="nathost">nathost</h3>
+<h3 id="nathost">nathost<a class="headerlink" href="#nathost" title="Permanent link">&para;</a></h3>
 <p>This table tracks which nodes are configured to be used as NAT hosts.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -523,13 +545,13 @@ NOT_STANDALONE - list of affiliations fo
 <li><strong>publicIPaddress</strong> - IP address on node that faces the public Internet</li>
 <li><strong>internalIPaddress</strong> - IP address on node that faces the internal network</li>
 </ul>
-<h3 id="nathostcomputermap">nathostcomputermap</h3>
+<h3 id="nathostcomputermap">nathostcomputermap<a class="headerlink" href="#nathostcomputermap" title="Permanent link">&para;</a></h3>
 <p>This table maps compute nodes to nodes being used as a NAT host for them.</p>
 <ul>
 <li><strong>nathostid</strong> - reference to nathost.id</li>
 <li><strong>computerid</strong> - reference to computer.id</li>
 </ul>
-<h3 id="natlog">natlog</h3>
+<h3 id="natlog">natlog<a class="headerlink" href="#natlog" title="Permanent link">&para;</a></h3>
 <p>This table records relevant information about how NAT was configured for a reservation.</p>
 <ul>
 <li><strong>sublogid</strong> - reference to sublog.id - sublog entry for reservation</li>
@@ -541,7 +563,7 @@ NOT_STANDALONE - list of affiliations fo
 <li><strong>protocol</strong> - protocol (TCP or UDP) of port that was forwarded at time of reservation</li>
 <li><strong>timestamp</strong> - timestamp at which the port forward was set up</li>
 </ul>
-<h3 id="natport">natport</h3>
+<h3 id="natport">natport<a class="headerlink" href="#natport" title="Permanent link">&para;</a></h3>
 <p>This table tracks which ports are actively being forwarded on NAT hosts for which reservations.</p>
 <ul>
 <li><strong>reservationid</strong> - reference to reservation.id - reservation for which port is forwarded</li>
@@ -549,18 +571,18 @@ NOT_STANDALONE - list of affiliations fo
 <li><strong>publicport</strong> - public port being forwarded on NAT host</li>
 <li><strong>connectmethodportid</strong> - reference to connectmethodport.id</li>
 </ul>
-<h3 id="openstackcomputermap">openstackcomputermap</h3>
+<h3 id="openstackcomputermap">openstackcomputermap<a class="headerlink" href="#openstackcomputermap" title="Permanent link">&para;</a></h3>
 <ul>
 <li><strong>instanceid</strong> - </li>
 <li><strong>computerid</strong> - </li>
 </ul>
-<h3 id="openstackimagerevision">openstackimagerevision</h3>
+<h3 id="openstackimagerevision">openstackimagerevision<a class="headerlink" href="#openstackimagerevision" title="Permanent link">&para;</a></h3>
 <ul>
 <li><strong>imagerevisionid</strong> - </li>
 <li><strong>imagedetails</strong> - </li>
 <li><strong>flavordetails</strong> - </li>
 </ul>
-<h3 id="os-table">OS table</h3>
+<h3 id="os-table">OS table<a class="headerlink" href="#os-table" title="Permanent link">&para;</a></h3>
 <p>This table contains information about OSes VCL knows about.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -572,32 +594,32 @@ NOT_STANDALONE - list of affiliations fo
 <li><strong>sourcepath</strong> - ??</li>
 <li><strong>moduleid</strong> - reference to module.id - module that handles this OS</li>
 </ul>
-<h3 id="osinstalltype-table">OSinstalltype table</h3>
+<h3 id="osinstalltype-table">OSinstalltype table<a class="headerlink" href="#osinstalltype-table" title="Permanent link">&para;</a></h3>
 <p>This table is a list of the ways an image can be installed.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
 <li><strong>name</strong> - name of entry</li>
 </ul>
-<h3 id="ostype-table">OStype table</h3>
+<h3 id="ostype-table">OStype table<a class="headerlink" href="#ostype-table" title="Permanent link">&para;</a></h3>
 <p>This table contains a list of OS types VCL knows about - linux, unix, windows, etc.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
 <li><strong>name</strong> - name of entry</li>
 </ul>
-<h3 id="platform-table">platform table</h3>
+<h3 id="platform-table">platform table<a class="headerlink" href="#platform-table" title="Permanent link">&para;</a></h3>
 <p>This table contains a list of platforms VCL knows about - i386, i386_lab (special case for lab machines), and ultrasparc.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
 <li><strong>name</strong> - name of entry</li>
 </ul>
-<h3 id="privnode-table">privnode table</h3>
+<h3 id="privnode-table">privnode table<a class="headerlink" href="#privnode-table" title="Permanent link">&para;</a></h3>
 <p>This table contains all of the nodes that make up the Privilege Tree on the Privileges page.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
 <li><strong>parent</strong> - reference to privnode.id - parent of this node</li>
 <li><strong>name</strong> - name of entry</li>
 </ul>
-<h3 id="provisioning-table">provisioning table</h3>
+<h3 id="provisioning-table">provisioning table<a class="headerlink" href="#provisioning-table" title="Permanent link">&para;</a></h3>
 <p>This table contains all of the provisioning modules that are part of vcld.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -605,13 +627,13 @@ NOT_STANDALONE - list of affiliations fo
 <li><strong>prettyname</strong> - more descriptive name of provisioning method</li>
 <li><strong>moduleid</strong> - reference to module.id - id of module that handles this provisioning method</li>
 </ul>
-<h3 id="provisioningosinstalltype-table">provisioningOSinstalltype table</h3>
+<h3 id="provisioningosinstalltype-table">provisioningOSinstalltype table<a class="headerlink" href="#provisioningosinstalltype-table" title="Permanent link">&para;</a></h3>
 <p>This table is a mapping of which provisioning methods can handle which OS install types.</p>
 <ul>
 <li><strong>provisioningid</strong> - reference to provisioning.id</li>
 <li><strong>OSinstalltypeid</strong> - reference to OSinstalltype.id</li>
 </ul>
-<h3 id="querylog-table">querylog table</h3>
+<h3 id="querylog-table">querylog table<a class="headerlink" href="#querylog-table" title="Permanent link">&para;</a></h3>
 <p>This table contains an entry for every query performed by the frontend that modifies the database (i.e. everything but SELECT statements).</p>
 <ul>
 <li><strong>userid</strong> - reference to user.id</li>
@@ -619,7 +641,7 @@ NOT_STANDALONE - list of affiliations fo
 <li><strong>mode</strong> - mode of site when query performed</li>
 <li><strong>query</strong> - string of query</li>
 </ul>
-<h3 id="request-table">request table</h3>
+<h3 id="request-table">request table<a class="headerlink" href="#request-table" title="Permanent link">&para;</a></h3>
 <p>This table contains information about every current or future reservation.  Only a single entry exists in this table for cluster reservations.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -636,7 +658,7 @@ NOT_STANDALONE - list of affiliations fo
 <li><strong>datemodified</strong> - date/time reservation modified</li>
 <li><strong>checkuser</strong> - flag to tell if reservation should be timed out if user is disconnect for &gt; 15 minutes - 0 not to do timeout, 1 to do timeout</li>
 </ul>
-<h3 id="reservation-table">reservation table</h3>
+<h3 id="reservation-table">reservation table<a class="headerlink" href="#reservation-table" title="Permanent link">&para;</a></h3>
 <p>This table contains information about every current or future reservation.  There will be one entry in this table corresponding to each entry in the request table for normal reservations, and multiple entries (one for each node) in this one for each entry in the request table for cluster reservations.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -651,21 +673,21 @@ NOT_STANDALONE - list of affiliations fo
 <li><strong>connectIP</strong> - (unused)</li>
 <li><strong>connectport</strong> - (unused)</li>
 </ul>
-<h3 id="reservationaccounts-table">reservationaccounts table</h3>
+<h3 id="reservationaccounts-table">reservationaccounts table<a class="headerlink" href="#reservationaccounts-table" title="Permanent link">&para;</a></h3>
 <p>This table contains userids and passwords for additional accounts for server reservations.  There is not an entry for the owner of the reservation.  These correspond to the admin and login user groups.</p>
 <ul>
 <li><strong>reservationid</strong> - reference to reservation.id</li>
 <li><strong>userid</strong> - reference to user.id</li>
 <li><strong>password</strong> - user's password for this reservation</li>
 </ul>
-<h3 id="resource-table">resource table</h3>
+<h3 id="resource-table">resource table<a class="headerlink" href="#resource-table" title="Permanent link">&para;</a></h3>
 <p>This table contains an entry for every resource VCL knows about.  Every resource has a unique id from this table, and a sub id from a resource specific table (computer, image, management node, etc).</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
 <li><strong>resourcetypeid</strong> - reference to resourcetype.id - type of this resource</li>
 <li><strong>subid</strong> - reference to id from specific resource table (computer.id, image.id, managementnode.id, etc)</li>
 </ul>
-<h3 id="resourcegroup-table">resourcegroup table</h3>
+<h3 id="resourcegroup-table">resourcegroup table<a class="headerlink" href="#resourcegroup-table" title="Permanent link">&para;</a></h3>
 <p>This table contains all of the resource groups.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -673,19 +695,19 @@ NOT_STANDALONE - list of affiliations fo
 <li><strong>ownerusergroupid</strong> - reference to usergroup.id - user group that owns this resource group</li>
 <li><strong>resourcetypeid</strong> - reference to resourcetype.id - type of this resource group</li>
 </ul>
-<h3 id="resourcegroupmembers-table">resourcegroupmembers table</h3>
+<h3 id="resourcegroupmembers-table">resourcegroupmembers table<a class="headerlink" href="#resourcegroupmembers-table" title="Permanent link">&para;</a></h3>
 <p>This table contains a list of which resources are in which resource groups.</p>
 <ul>
 <li><strong>resourceid</strong> - reference to resource.id</li>
 <li><strong>resourcegroupid</strong> - reference to resourcegroup.id</li>
 </ul>
-<h3 id="resourcemap-table">resourcemap table</h3>
+<h3 id="resourcemap-table">resourcemap table<a class="headerlink" href="#resourcemap-table" title="Permanent link">&para;</a></h3>
 <p>This table contains which resource groups map to other resource groups.</p>
 <p>resourcegroupid1 - reference to resourcegroup.id
 resourcetypeid1 - reference to resourcetype.id
 resourcegroupid2 - reference to resourcegroup.id
 resourcetypeid2 - reference to resourcetype.id</p>
-<h3 id="resourcepriv-table">resourcepriv table</h3>
+<h3 id="resourcepriv-table">resourcepriv table<a class="headerlink" href="#resourcepriv-table" title="Permanent link">&para;</a></h3>
 <p>This table contains the attributes that can be granted to resource groups.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -693,27 +715,27 @@ resourcetypeid2 - reference to resourcet
 <li><strong>privnodeid</strong> - reference to privnode.id - node where attribute being assigned</li>
 <li><strong>type</strong> - block, cascade, available, administer, manageGroup, or manageMapping - attribute being assigned at node</li>
 </ul>
-<h3 id="resourcetype-table">resourcetype table</h3>
+<h3 id="resourcetype-table">resourcetype table<a class="headerlink" href="#resourcetype-table" title="Permanent link">&para;</a></h3>
 <p>This table contains a list of all the resource types.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
 <li><strong>name</strong> - name of entry</li>
 </ul>
-<h3 id="schedule-table">schedule table</h3>
+<h3 id="schedule-table">schedule table<a class="headerlink" href="#schedule-table" title="Permanent link">&para;</a></h3>
 <p>This table contains all of the schedules available.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
 <li><strong>name</strong> - name of entry</li>
 <li><strong>ownerid</strong> - reference to user.id - owner of schedule</li>
 </ul>
-<h3 id="scheduletimes-table">scheduletimes table</h3>
+<h3 id="scheduletimes-table">scheduletimes table<a class="headerlink" href="#scheduletimes-table" title="Permanent link">&para;</a></h3>
 <p>This table contains all of the starts/ends of the time slots for each schedule.  Schedules are what times during a week that computers are available.  They run from midnight Sunday morning (0) to midnight Sunday morning one week later (10080).</p>
 <ul>
 <li><strong>scheduleid</strong> - reference to schedule.id</li>
 <li><strong>start</strong> - start of time slot in minutes since midnight Sunday morning</li>
 <li><strong>end</strong> - end of time slot in minutes since midnight Sunday morning</li>
 </ul>
-<h3 id="semaphone-table">semaphone table</h3>
+<h3 id="semaphone-table">semaphone table<a class="headerlink" href="#semaphone-table" title="Permanent link">&para;</a></h3>
 <p>This table is used by the frontend to manage semaphores for computers being considered for reservations. During normal network and CPU loads, entries in this table should only exist for fractions of a second.</p>
 <ul>
 <li><strong>computerid</strong> - reference to computer.id - computer being locked</li>
@@ -723,7 +745,7 @@ resourcetypeid2 - reference to resourcet
 <li><strong>expires</strong> - timestamp after which the semaphore is considered to be expired; can be configured by setting SEMTIMEOUT in conf.php, defaults to 45 seconds after insertion</li>
 <li><strong>procid</strong> - unique id for process that obtained the lock (combination of hostname and process id)</li>
 </ul>
-<h3 id="serverprofile-table">serverprofile table</h3>
+<h3 id="serverprofile-table">serverprofile table<a class="headerlink" href="#serverprofile-table" title="Permanent link">&para;</a></h3>
 <p>This table contains all of the server profiles.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -738,7 +760,7 @@ resourcetypeid2 - reference to resourcet
 <li><strong>logingroupid</strong> - reference to usergroup.id</li>
 <li><strong>monitored</strong> - (unused)</li>
 </ul>
-<h3 id="serverrequest-table">serverrequest table</h3>
+<h3 id="serverrequest-table">serverrequest table<a class="headerlink" href="#serverrequest-table" title="Permanent link">&para;</a></h3>
 <p>This table contains an entry for each server reservation.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -751,7 +773,7 @@ resourcetypeid2 - reference to resourcet
 <li><strong>logingroupid</strong> - reference to usergroup.id - user group containing users that should be only be able to log in to this machine (will see reservation, but only the Connect button)</li>
 <li><strong>monitored</strong> - 1 to have this reservation monitored, 0 otherwise (unused)</li>
 </ul>
-<h3 id="shibauth-table">shibauth table</h3>
+<h3 id="shibauth-table">shibauth table<a class="headerlink" href="#shibauth-table" title="Permanent link">&para;</a></h3>
 <p>This table contains authentication information related to shibboleth logins.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -760,7 +782,7 @@ resourcetypeid2 - reference to resourcet
 <li><strong>sessid</strong> - shib session id</li>
 <li><strong>data</strong> - various shibboleth related data passed in from httpd</li>
 </ul>
-<h3 id="sitemaintenance-table">sitemaintenance table</h3>
+<h3 id="sitemaintenance-table">sitemaintenance table<a class="headerlink" href="#sitemaintenance-table" title="Permanent link">&para;</a></h3>
 <p>This table contains an entry for any active or upcoming scheduled site maintenance windows.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -773,13 +795,13 @@ resourcetypeid2 - reference to resourcet
 <li><strong>informhoursahead</strong> - hours before the start time that a warning should be displayed on the VCL site about upcoming maintenance</li>
 <li><strong>allowreservations</strong> - 1 to allow reservations to be scheduled ahead of time that overlap with the window, 0 to keep overlapping future reservations from being scheduled</li>
 </ul>
-<h3 id="state-table">state table</h3>
+<h3 id="state-table">state table<a class="headerlink" href="#state-table" title="Permanent link">&para;</a></h3>
 <p>This table contains all of the states used in VCL.  Not all states are used any place where states are used.  For example, there are states used in the request table that are not used in the computer table.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
 <li><strong>name</strong> - name of entry</li>
 </ul>
-<h3 id="statgraphcache-table">statgraphcache table</h3>
+<h3 id="statgraphcache-table">statgraphcache table<a class="headerlink" href="#statgraphcache-table" title="Permanent link">&para;</a></h3>
 <p>This table contains cached values for the stat graphs.  Some of the data points take enough computation time that it is prohibitive to calculate them for really long periods of time.  This table allows historical points to computed once and then saved forever.</p>
 <ul>
 <li><strong>graphtype</strong> - totalres, concurres, concurblade, or concurvm - type of graph for this entry</li>
@@ -788,13 +810,13 @@ resourcetypeid2 - reference to resourcet
 <li><strong>value</strong> - data point value for this entry</li>
 <li><strong>provisioningid</strong> - reference to provisioning.id; provisioning id for this entry or NULL</li>
 </ul>
-<h3 id="subimages-table">subimages table</h3>
+<h3 id="subimages-table">subimages table<a class="headerlink" href="#subimages-table" title="Permanent link">&para;</a></h3>
 <p>This table contains a list of sub images associated with any clusters.</p>
 <ul>
 <li><strong>imagemetaid</strong> - reference to imagemeta.id</li>
 <li><strong>imageid</strong> - reference to image.id - subimage associated with imagemetaid</li>
 </ul>
-<h3 id="sublog-table">sublog table</h3>
+<h3 id="sublog-table">sublog table<a class="headerlink" href="#sublog-table" title="Permanent link">&para;</a></h3>
 <p>This table contains an entry for each computer that was part of a log table entry.  For normal reservations, this is a single entry; for cluster reservations, it is one entry for each subimage.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -810,7 +832,7 @@ resourcetypeid2 - reference to resourcet
 <li><strong>blockStart</strong> - start time of blockTime (if reservation was part of a block allocation)</li>
 <li><strong>blockEnd</strong> - end time of blockTime (if reservation was part of a block allocation)</li>
 </ul>
-<h3 id="user-table">user table</h3>
+<h3 id="user-table">user table<a class="headerlink" href="#user-table" title="Permanent link">&para;</a></h3>
 <p>This table contains an entry for every user that has every logged in to VCL.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -838,7 +860,7 @@ resourcetypeid2 - reference to resourcet
 <li><strong>usepublickeys</strong> - 0 or 1; whether or not user wants to use public key authentication for linux reservations</li>
 <li><strong>sshpublickeys</strong> - data to be put in ~/.ssh/authorized_keys within linux reservations if usepublickeys is set to 1</li>
 </ul>
-<h3 id="usergroup-table">usergroup table</h3>
+<h3 id="usergroup-table">usergroup table<a class="headerlink" href="#usergroup-table" title="Permanent link">&para;</a></h3>
 <p>This table contains all of the user groups.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -853,26 +875,26 @@ resourcetypeid2 - reference to resourcet
 <li><strong>maxextendtime</strong> - max time allowed per extension for users in this group</li>
 <li><strong>overlapResCount</strong> - number of allowed overlapping reservations for users in this group (note that 1 is invalid as it doesn't make sense)</li>
 </ul>
-<h3 id="usergroupmembers-table">usergroupmembers table</h3>
+<h3 id="usergroupmembers-table">usergroupmembers table<a class="headerlink" href="#usergroupmembers-table" title="Permanent link">&para;</a></h3>
 <p>This table tracks which users are members of which user groups.</p>
 <ul>
 <li><strong>userid</strong> - reference to user.id</li>
 <li><strong>usergroupid</strong> - reference to usergroup.id</li>
 </ul>
-<h3 id="usergrouppriv-table">usergrouppriv table</h3>
+<h3 id="usergrouppriv-table">usergrouppriv table<a class="headerlink" href="#usergrouppriv-table" title="Permanent link">&para;</a></h3>
 <p>This table is a list of which additional user group privileges have been assigned to which user groups.</p>
 <ul>
 <li><strong>usergroupid</strong> - reference to usergroup.id</li>
 <li><strong>userprivtypeid</strong> - reference to usergroupprivtype.id - it probably should have been named usergroupprivtypeid</li>
 </ul>
-<h3 id="usergroupprivtype-table">usergroupprivtype table</h3>
+<h3 id="usergroupprivtype-table">usergroupprivtype table<a class="headerlink" href="#usergroupprivtype-table" title="Permanent link">&para;</a></h3>
 <p>This table contains additional privileges that can be associated with user groups that don't make sense to have at any particular privilege node.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
 <li><strong>name</strong> - name of entry</li>
 <li><strong>help</strong> - explaination of privilege type</li>
 </ul>
-<h3 id="userpriv-table">userpriv table</h3>
+<h3 id="userpriv-table">userpriv table<a class="headerlink" href="#userpriv-table" title="Permanent link">&para;</a></h3>
 <p>This table contains the user and user group privileges assigned in the privilege tree.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -881,13 +903,13 @@ resourcetypeid2 - reference to resourcet
 <li><strong>privnodeid</strong> - reference to privnode.id - node where user privilege being granted</li>
 <li><strong>userprivtypeid</strong> - reference to userprivtype.id - user privilege being granted</li>
 </ul>
-<h3 id="userprivtype-table">userprivtype table</h3>
+<h3 id="userprivtype-table">userprivtype table<a class="headerlink" href="#userprivtype-table" title="Permanent link">&para;</a></h3>
 <p>This table contains all of the available user privileges.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
 <li><strong>name</strong> - name of entry</li>
 </ul>
-<h3 id="variable-table">variable table</h3>
+<h3 id="variable-table">variable table<a class="headerlink" href="#variable-table" title="Permanent link">&para;</a></h3>
 <p>This table is a place to store any generic data.  It can be settings that stay around forever, or things that only need to be temporarily stored.  It also provides for a place for the frontend and backend to share less structured information that what is in other tables.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -897,7 +919,7 @@ resourcetypeid2 - reference to resourcet
 <li><strong>setby</strong> - what set the entry - perl module, web code, etc</li>
 <li><strong>timestamp</strong> - date/time entry set</li>
 </ul>
-<h3 id="vmhost-table">vmhost table</h3>
+<h3 id="vmhost-table">vmhost table<a class="headerlink" href="#vmhost-table" title="Permanent link">&para;</a></h3>
 <p>This table contains an entry for each virtual host.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -905,7 +927,7 @@ resourcetypeid2 - reference to resourcet
 <li><strong>vmlimit</strong> - max number of VMs that can be on this host</li>
 <li><strong>vmprofileid</strong> - reference to vmprofile.id - profile being used on this host</li>
 </ul>
-<h3 id="vmprofile-table">vmprofile table</h3>
+<h3 id="vmprofile-table">vmprofile table<a class="headerlink" href="#vmprofile-table" title="Permanent link">&para;</a></h3>
 <p>This table contains an entry for each virtual host profile.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
@@ -931,27 +953,27 @@ resourcetypeid2 - reference to resourcet
 <li><strong>rsakey</strong> - path to private key on management nodes that is used to decrypt password for VM host</li>
 <li><strong>encryptedpasswd</strong> - encrypted password of the administrative or root user residing on the VM host, if encrypted, the "password" field will be NULL</li>
 </ul>
-<h3 id="vmtype-table">vmtype table</h3>
+<h3 id="vmtype-table">vmtype table<a class="headerlink" href="#vmtype-table" title="Permanent link">&para;</a></h3>
 <p>This table contains all of the virtual machine types.</p>
 <ul>
 <li><strong>id</strong> - id of entry</li>
 <li><strong>name</strong> - name of entry</li>
 </ul>
-<h3 id="winkms-table">winKMS table</h3>
+<h3 id="winkms-table">winKMS table<a class="headerlink" href="#winkms-table" title="Permanent link">&para;</a></h3>
 <p>This table contains Windows KMS licensing information.</p>
 <ul>
 <li><strong>affiliationid</strong> - reference to affiliation.id</li>
 <li><strong>address</strong> - IP address of KMS server</li>
 <li><strong>port</strong> - port KMS server is listening on</li>
 </ul>
-<h3 id="winproductkey-table">winProductKey table</h3>
+<h3 id="winproductkey-table">winProductKey table<a class="headerlink" href="#winproductkey-table" title="Permanent link">&para;</a></h3>
 <p>This table contains Windows product key information.</p>
 <ul>
 <li><strong>affiliationid</strong> - reference to affiliation.id</li>
 <li><strong>productname</strong> - ??</li>
 <li><strong>productkey</strong> - ??</li>
 </ul>
-<h3 id="xmlrpclog-table">xmlrpcLog table</h3>
+<h3 id="xmlrpclog-table">xmlrpcLog table<a class="headerlink" href="#xmlrpclog-table" title="Permanent link">&para;</a></h3>
 <p>This table logs each XML RPC API call.</p>
 <ul>
 <li><strong>xmlrpcKeyid</strong> - reference to user.id - user that made API call (originally, every user got their own key, and this was a reference to another table)</li>

Modified: websites/staging/vcl/trunk/content/dev/image-capture-sequence.html
==============================================================================
--- websites/staging/vcl/trunk/content/dev/image-capture-sequence.html (original)
+++ websites/staging/vcl/trunk/content/dev/image-capture-sequence.html Wed Oct 18 19:55:31 2017
@@ -36,7 +36,18 @@
   </div>
 
   <div id="navigation"> 
-  <ul>
+  <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
 <li><a href="/index.html">Information</a><ul>
 <li><a href="/info/features.html">Features</a></li>
 <li><a href="/info/architecture.html">Architecture</a></li>
@@ -53,7 +64,7 @@
 <li><a href="/comm/index.html">Community</a><ul>
 <li><a href="/comm/index.html#getInvolved">Getting Involved</a></li>
 <li><a href="/comm/index.html#mail-list">Mailing Lists</a></li>
-<li><a href="/comm/wiki.html">Wiki</a></li>
+<li><a href="https://cwiki.apache.org/confluence/display/VCL/Apache+VCL" target="_blank">Wiki</a></li>
 <li><a href="/dev/index.html">Development</a><ul>
 <li><a href="/dev/jira.html">Issue Tracking</a></li>
 <li><a href="/dev/code-documentation.html">Code Documentation</a></li>
@@ -72,7 +83,18 @@
   
   <div id="content">
     <h1 class="title">Image Capture Sequence</h1>
-    <h2 id="modularization-example">Modularization Example</h2>
+    <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="modularization-example">Modularization Example<a class="headerlink" href="#modularization-example" title="Permanent link">&para;</a></h2>
 <p>The following diagram shows how the image capture sequence
 differs if different provisioning modules are used -- xCAT and
 VMWare.</p>



Mime
View raw message