vcl-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1019714 [11/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/docs/archives/old-releases/adding-ldap-authentication.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/archives/old-releases/adding-ldap-authentication.html (original)
+++ websites/staging/vcl/trunk/content/docs/archives/old-releases/adding-ldap-authentication.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,8 +83,19 @@
   
   <div id="content">
     <h1 class="title">Adding LDAP Authentication</h1>
-    <p><a name="AddingLDAPAuthentication-PrerequisitesforyourLDAPserver:"></a></p>
-<h3 id="prerequisites-for-your-ldap-server">Prerequisites for your LDAP server:</h3>
+    <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="AddingLDAPAuthentication-PrerequisitesforyourLDAPserver:"></a></p>
+<h3 id="prerequisites-for-your-ldap-server">Prerequisites for your LDAP server:<a class="headerlink" href="#prerequisites-for-your-ldap-server" title="Permanent link">&para;</a></h3>
 <ul>
 <li>enable SSL on your LDAP server</li>
 <li>Create an account that can look up a user's first and last names, user
@@ -85,7 +107,7 @@ up userids, names, and email addresses.<
 server to access tcp port 636 on your LDAP server</li>
 </ul>
 <p><a name="AddingLDAPAuthentication-PrerequisitesforyourVCLwebserver:"></a></p>
-<h3 id="prerequisites-for-your-vcl-web-server">Prerequisites for your VCL web server:</h3>
+<h3 id="prerequisites-for-your-vcl-web-server">Prerequisites for your VCL web server:<a class="headerlink" href="#prerequisites-for-your-vcl-web-server" title="Permanent link">&para;</a></h3>
 <ul>
 <li>php-ldap needs to be installed</li>
 <li>If your LDAP server SSL certificate is self-signed, your VCL web server
@@ -118,7 +140,7 @@ not, but if you do, add the following:</
 </li>
 </ul>
 <p><a name="AddingLDAPAuthentication-AddingLDAPAuthenticationtotheWebCode"></a></p>
-<h3 id="adding-ldap-authentication-to-the-web-code">Adding LDAP Authentication to the Web Code</h3>
+<h3 id="adding-ldap-authentication-to-the-web-code">Adding LDAP Authentication to the Web Code<a class="headerlink" href="#adding-ldap-authentication-to-the-web-code" title="Permanent link">&para;</a></h3>
 <ul>
 <li>
 <p>You will need to manually add an entry to the affiliation table in the
@@ -181,9 +203,7 @@ option</li>
 </li>
 <li>Next, there are 6 arrays that would need to be modified, but can be
 replaced with a block of code.</li>
-<li>
-<p>Delete the following lines:</p>
-<div class="codehilite"><pre>$<span class="n">affilValFunc</span> <span class="p">=</span> <span class="n">array</span><span class="p">(</span>1 <span class="p">=</span><span class="o">&gt;</span> <span class="n">create_function</span><span class="p">(</span><span class="s">&#39;&#39;</span><span class="p">,</span> <span class="s">&#39;return 0;&#39;</span><span class="p">),</span>
+<li>Delete the following lines:<div class="codehilite"><pre>$<span class="n">affilValFunc</span> <span class="p">=</span> <span class="n">array</span><span class="p">(</span>1 <span class="p">=</span><span class="o">&gt;</span> <span class="n">create_function</span><span class="p">(</span><span class="s">&#39;&#39;</span><span class="p">,</span> <span class="s">&#39;return 0;&#39;</span><span class="p">),</span>
               <span class="o">/*</span>3 <span class="p">=</span><span class="o">&gt;</span> &quot;<span class="n">validateLDAPUser</span>&quot;<span class="p">,</span><span class="o">*/</span>
 <span class="p">);</span>
 
@@ -238,7 +258,7 @@ $<span class="n">updateUserFuncArgs</spa
 file</li>
 </ul>
 <p><a name="AddingLDAPAuthentication-TweakifyourLDAPserverhasusersinmultiplecontainers"></a></p>
-<h3 id="tweak-if-your-ldap-server-has-users-in-multiple-containers">Tweak if your LDAP server has users in multiple containers</h3>
+<h3 id="tweak-if-your-ldap-server-has-users-in-multiple-containers">Tweak if your LDAP server has users in multiple containers<a class="headerlink" href="#tweak-if-your-ldap-server-has-users-in-multiple-containers" title="Permanent link">&para;</a></h3>
 <p>If your LDAP server has users in multiple containers, then the full DN for
 each user must be looked up before doing a bind to the LDAP server to
 authenticate the user. In this case, you'll need to modify

Modified: websites/staging/vcl/trunk/content/docs/archives/old-releases/adding-support-for-partimage-and-partimage-ng-to-xcat-2.x-unofficial.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/archives/old-releases/adding-support-for-partimage-and-partimage-ng-to-xcat-2.x-unofficial.html (original)
+++ websites/staging/vcl/trunk/content/docs/archives/old-releases/adding-support-for-partimage-and-partimage-ng-to-xcat-2.x-unofficial.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">Adding support for partimage and partimage-ng to xCAT 2.x (unofficial)</h1>
-    <p>This is how I added support for partimage/partimage-ng to xCAT 2.x</p>
+    <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>This is how I added support for partimage/partimage-ng to xCAT 2.x</p>
 
 <h2><a name="Addingsupportforpartimageandpartimage-ngtoxCAT2.x%28unofficial%29-Overview"></a>Overview</h2>
 

Modified: websites/staging/vcl/trunk/content/docs/archives/old-releases/further-steps-if-using-only-vmware.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/archives/old-releases/further-steps-if-using-only-vmware.html (original)
+++ websites/staging/vcl/trunk/content/docs/archives/old-releases/further-steps-if-using-only-vmware.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">Further steps if using only VMWare</h1>
-    <p>If you are using standalone VMWare servers (i.e. ones that VCL did not
+    <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>If you are using standalone VMWare servers (i.e. ones that VCL did not
 deploy using xCAT), you first need to add the VMWare servers; then, you
 need to add the virtual machines. You can either add them individually
 (Adding Individual VMWare Servers/Virtual Machines), or if they have
@@ -83,7 +105,7 @@ Computer" page by going to Manage Comput
 clicking Add. You can get to the "Add Multiple Computers" page by doing the
 same thing but checking the "Add Multiple" checkbox.</p>
 <p><a name="FurtherstepsifusingonlyVMWare-AddingIndividualVMWareServers"></a></p>
-<h3 id="adding-individual-vmware-servers">Adding Individual VMWare Servers</h3>
+<h3 id="adding-individual-vmware-servers">Adding Individual VMWare Servers<a class="headerlink" href="#adding-individual-vmware-servers" title="Permanent link">&para;</a></h3>
 <ol>
 <li>click "Manage Computers"</li>
 <li>select the "Add Single Computer" radio button</li>
@@ -108,13 +130,13 @@ Profile later if needed</li>
 added isn't listed after clicking Submit)</li>
 </ol>
 <p><a name="FurtherstepsifusingonlyVMWare-AddingIndividualVirtualMachines"></a></p>
-<h3 id="adding-individual-virtual-machines">Adding Individual Virtual Machines</h3>
+<h3 id="adding-individual-virtual-machines">Adding Individual Virtual Machines<a class="headerlink" href="#adding-individual-virtual-machines" title="Permanent link">&para;</a></h3>
 <p>VM computers cannot be added individually at the current time because some
 required database properties such as the&nbsp;MAC address&nbsp;do not get
 populated.&nbsp; Instead, use the steps described below to add multiple
 virtual machines.</p>
 <p><a name="FurtherstepsifusingonlyVMWare-AddingMultipleVMWareServers"></a></p>
-<h3 id="adding-multiple-vmware-servers">Adding Multiple VMWare Servers</h3>
+<h3 id="adding-multiple-vmware-servers">Adding Multiple VMWare Servers<a class="headerlink" href="#adding-multiple-vmware-servers" title="Permanent link">&para;</a></h3>
 <ol>
 <li>click "Manage Computers"</li>
 <li>select the "Add Multiple Computers" radio button</li>
@@ -147,7 +169,7 @@ Host Profile later if needed</li>
 <li>click Add Computers</li>
 </ol>
 <p><a name="FurtherstepsifusingonlyVMWare-AddingMultipleVirtualMachines"></a></p>
-<h3 id="adding-multiple-virtual-machines">Adding Multiple Virtual Machines</h3>
+<h3 id="adding-multiple-virtual-machines">Adding Multiple Virtual Machines<a class="headerlink" href="#adding-multiple-virtual-machines" title="Permanent link">&para;</a></h3>
 <ol>
 <li>click "Manage Computers"</li>
 <li>select the "Add Multiple Computers" radio button</li>

Modified: websites/staging/vcl/trunk/content/docs/archives/old-releases/further-steps-if-using-xcat.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/archives/old-releases/further-steps-if-using-xcat.html (original)
+++ websites/staging/vcl/trunk/content/docs/archives/old-releases/further-steps-if-using-xcat.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,11 +83,22 @@
   
   <div id="content">
     <h1 class="title">Further steps if using xCAT</h1>
-    <p>You can initially add individual computers or multiple computers all
+    <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>You can initially add individual computers or multiple computers all
 together. After you have added at least one computer, you will need to go
 to Manage Computers -&gt; Edit Computer Information to additional ones.</p>
 <p><a name="FurtherstepsifusingxCAT-AddingIndividualComputers"></a></p>
-<h3 id="adding-individual-computers">Adding Individual Computers</h3>
+<h3 id="adding-individual-computers">Adding Individual Computers<a class="headerlink" href="#adding-individual-computers" title="Permanent link">&para;</a></h3>
 <ol>
 <li>click "Manage Computers"</li>
 <li>select the "Add Single Computer" radio button</li>
@@ -92,7 +114,7 @@ isn't listed after clicking Submit)</li>
 started checking in, you should be able to make a reservation</li>
 </ol>
 <p><a name="FurtherstepsifusingxCAT-AddingMultipleComputers"></a></p>
-<h3 id="adding-multiple-computers">Adding Multiple Computers</h3>
+<h3 id="adding-multiple-computers">Adding Multiple Computers<a class="headerlink" href="#adding-multiple-computers" title="Permanent link">&para;</a></h3>
 <ol>
 <li>click "Manage Computers"</li>
 <li>select the "Add Multiple Computers" radio button</li>

Modified: websites/staging/vcl/trunk/content/docs/archives/old-releases/upgrade-from-previous-version.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/archives/old-releases/upgrade-from-previous-version.html (original)
+++ websites/staging/vcl/trunk/content/docs/archives/old-releases/upgrade-from-previous-version.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,11 +83,22 @@
   
   <div id="content">
     <h1 class="title">Upgrade From Previous Version</h1>
-    <p>This file provides information on how to upgrade from VCL 2.1 to VCL 2.2.
+    <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>This file provides information on how to upgrade from VCL 2.1 to VCL 2.2.
 Please note it only applies for the upgrade from 2.1 to 2.2, this may or
 may not work for other versions.</p>
 <p><a name="UpgradeFromPreviousVersion-*Thebasicstepsthatwillbeperformed*"></a></p>
-<h2 id="the-basic-steps-that-will-be-performed">The basic steps that will be performed</h2>
+<h2 id="the-basic-steps-that-will-be-performed">The basic steps that will be performed<a class="headerlink" href="#the-basic-steps-that-will-be-performed" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Download and Extract 2.2 code</li>
 <li>Shutdown httpd and vcld services</li>
@@ -89,21 +111,19 @@ changes</li>
 <li>Restart vcld service</li>
 </ul>
 <p><a name="UpgradeFromPreviousVersion-*DownloadandExtract2.2code*"></a></p>
-<h2 id="download-and-extract-22-code">Download and Extract 2.2 code</h2>
+<h2 id="download-and-extract-22-code">Download and Extract 2.2 code<a class="headerlink" href="#download-and-extract-22-code" title="Permanent link">&para;</a></h2>
 <ol>
 <li>follow instructions on <a href="vcl-2.2.html">VCL 2.2</a>
  Release page to download and verify apache-VCL-2.2-incubating.tar.bz2 and
 put in in /root</li>
-<li>
-<p>extract VCL 2.2 code</p>
-<div class="codehilite"><pre><span class="n">tar</span> <span class="n">xjf</span> <span class="n">apache</span><span class="o">-</span><span class="n">VCL</span><span class="o">-</span>2<span class="p">.</span>2<span class="o">-</span><span class="n">incubating</span><span class="p">.</span><span class="n">tar</span><span class="p">.</span><span class="n">bz2</span>
+<li>extract VCL 2.2 code<div class="codehilite"><pre><span class="n">tar</span> <span class="n">xjf</span> <span class="n">apache</span><span class="o">-</span><span class="n">VCL</span><span class="o">-</span>2<span class="p">.</span>2<span class="o">-</span><span class="n">incubating</span><span class="p">.</span><span class="n">tar</span><span class="p">.</span><span class="n">bz2</span>
 </pre></div>
 
 
 </li>
 </ol>
 <p><a name="UpgradeFromPreviousVersion-*Shutdownservices*"></a></p>
-<h2 id="shutdown-services">Shutdown services</h2>
+<h2 id="shutdown-services">Shutdown services<a class="headerlink" href="#shutdown-services" title="Permanent link">&para;</a></h2>
 <p>Shutdown the httpd and vcld services</p>
 <div class="codehilite"><pre>    <span class="n">service</span> <span class="n">httpd</span> <span class="n">stop</span> <span class="n">or</span> <span class="o">/</span><span class="n">etc</span><span class="o">/</span><span class="n">init</span><span class="p">.</span><span class="n">d</span><span class="o">/</span><span class="n">httpd</span> <span class="n">stop</span>
     <span class="n">service</span> <span class="n">vcld</span> <span class="n">stop</span> <span class="n">or</span> <span class="o">/</span><span class="n">etc</span><span class="o">/</span><span class="n">init</span><span class="p">.</span><span class="n">d</span><span class="o">/</span><span class="n">vcld</span> <span class="n">stop</span>
@@ -111,7 +131,7 @@ put in in /root</li>
 
 
 <p><a name="UpgradeFromPreviousVersion-*Createabackupofvcldatabase*"></a></p>
-<h2 id="create-a-backup-of-vcl-database">Create a backup of vcl database</h2>
+<h2 id="create-a-backup-of-vcl-database">Create a backup of vcl database<a class="headerlink" href="#create-a-backup-of-vcl-database" title="Permanent link">&para;</a></h2>
 <p>We will create a backup of the vcl database. This will provide a restore
 point if necessary.</p>
 <div class="codehilite"><pre>    <span class="n">mysqldump</span> <span class="n">vcl</span> <span class="o">&gt;</span> <span class="o">~/</span><span class="n">vcl</span><span class="o">-</span><span class="n">pre2</span><span class="p">.</span>2<span class="o">-</span><span class="n">upgrade</span><span class="p">.</span><span class="n">sql</span>
@@ -119,7 +139,7 @@ point if necessary.</p>
 
 
 <p><a name="UpgradeFromPreviousVersion-*Updatemysqlschema*"></a></p>
-<h2 id="update-mysql-schema">Update mysql schema</h2>
+<h2 id="update-mysql-schema">Update mysql schema<a class="headerlink" href="#update-mysql-schema" title="Permanent link">&para;</a></h2>
 <p>This step updates the mysql schema.</p>
 <div class="codehilite"><pre>    <span class="n">cd</span> <span class="o">/</span><span class="n">root</span><span class="o">/</span><span class="n">apache</span><span class="o">-</span><span class="n">VCL</span><span class="o">-</span>2<span class="p">.</span>2<span class="o">-</span><span class="n">incubating</span>
     <span class="n">mysql</span> <span class="n">vcl</span> <span class="o">&lt;</span> <span class="n">mysql</span><span class="o">/</span><span class="n">update</span><span class="o">-</span>2<span class="p">.</span>2<span class="p">.</span><span class="n">sql</span>
@@ -127,7 +147,7 @@ point if necessary.</p>
 
 
 <p><a name="UpgradeFromPreviousVersion-*Updatewebcode*"></a></p>
-<h2 id="update-web-code">Update web code</h2>
+<h2 id="update-web-code">Update web code<a class="headerlink" href="#update-web-code" title="Permanent link">&para;</a></h2>
 <p>This step we will move the 2.1 web directory out of the way, so we can copy
 in the new web code base. After copying in the new code, we will migrate
 your configuration changes. These instructions assume that you installed
@@ -180,13 +200,13 @@ conf-default.php</p>
 <li>define("DEFAULTTHEME", 'default');</li>
 </ol>
 <p><a name="UpgradeFromPreviousVersion-Restarthttpdservice"></a></p>
-<h2 id="restart-httpd-service">Restart httpd service</h2>
+<h2 id="restart-httpd-service">Restart httpd service<a class="headerlink" href="#restart-httpd-service" title="Permanent link">&para;</a></h2>
 <div class="codehilite"><pre><span class="n">service</span> <span class="n">httpd</span> <span class="n">start</span> <span class="n">or</span> <span class="o">/</span><span class="n">etc</span><span class="o">/</span><span class="n">init</span><span class="p">.</span><span class="n">d</span><span class="o">/</span><span class="n">httpd</span> <span class="n">start</span>
 </pre></div>
 
 
 <p><a name="UpgradeFromPreviousVersion-*Updatemanagementnodecode*"></a></p>
-<h2 id="update-management-node-code">Update management node code</h2>
+<h2 id="update-management-node-code">Update management node code<a class="headerlink" href="#update-management-node-code" title="Permanent link">&para;</a></h2>
 <p>This step will move the 2.1 vcl code base out of the way, so we can cleanly
 copy in the new management node(MN) code.</p>
 <ol>
@@ -224,7 +244,7 @@ is used, options are dynamic DHCP, Manua
 <li>End Node SSH Identity Key Files</li>
 </ol>
 <p><a name="UpgradeFromPreviousVersion-Restartvcldservice"></a></p>
-<h2 id="restart-vcld-service">Restart vcld service</h2>
+<h2 id="restart-vcld-service">Restart vcld service<a class="headerlink" href="#restart-vcld-service" title="Permanent link">&para;</a></h2>
 <div class="codehilite"><pre>    <span class="n">service</span> <span class="n">vcld</span> <span class="n">start</span> <span class="n">or</span> <span class="o">/</span><span class="n">etc</span><span class="o">/</span><span class="n">init</span><span class="p">.</span><span class="n">d</span><span class="o">/</span><span class="n">vcld</span> <span class="n">start</span>
 </pre></div>
   </div>

Modified: websites/staging/vcl/trunk/content/docs/archives/old-releases/vcl-2.2-installation.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/archives/old-releases/vcl-2.2-installation.html (original)
+++ websites/staging/vcl/trunk/content/docs/archives/old-releases/vcl-2.2-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,7 +83,18 @@
   
   <div id="content">
     <h1 class="title">VCL 2.2 Installation</h1>
-    <p>Steps to install VCL:</p>
+    <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>Steps to install VCL:</p>
 <ol>
 <li>Download and verify a release file. Follow instructions on the <a href="vcl-2.2.html">VCL 2.2 release page</a></li>
 <li><a href="2.2-database-configuration.html">Install the database portion of VCL</a></li>

Modified: websites/staging/vcl/trunk/content/docs/archives/old-releases/vcl-2.2.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/archives/old-releases/vcl-2.2.html (original)
+++ websites/staging/vcl/trunk/content/docs/archives/old-releases/vcl-2.2.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">VCL 2.2</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="#download-links">Download links</a></li>
 <li><a href="#release-notes">Release Notes</a><ul>
@@ -92,7 +114,7 @@
 </ul>
 </div>
 <p><a name="VCL2.2-Downloadlinks"></a></p>
-<h2 id="download-links">Download links</h2>
+<h2 id="download-links">Download links<a class="headerlink" href="#download-links" title="Permanent link">&para;</a></h2>
 <p>Please make sure to download VCL from an mirror server. The following link
 will automatically select one for you that should be close to you. After
 downloading it <em>make sure</em> you verify it with MD5 or SHA1 sums <em>AND</em> the
@@ -130,9 +152,9 @@ signature, run</p>
 <p>For new installs, visit the on-line <a href="vcl-2.2-installation.html">installation guide</a>.</p>
 <p>For upgrades from version 2.1, visit the on-line <a href="upgrade-from-previous-version.html">upgrade guide</a>.</p>
 <p><a name="VCL2.2-ReleaseNotes"></a></p>
-<h2 id="release-notes">Release Notes</h2>
+<h2 id="release-notes">Release Notes<a class="headerlink" href="#release-notes" title="Permanent link">&para;</a></h2>
 <p><a name="VCL2.2-I.IntroandDescription"></a></p>
-<h4 id="i-intro-and-description">I. Intro and Description</h4>
+<h4 id="i-intro-and-description">I. Intro and Description<a class="headerlink" href="#i-intro-and-description" title="Permanent link">&para;</a></h4>
 <p>VCL, Virtual Computing Lab. The VCL can be many things, first and foremost
 it is an open-source system used to dynamically provision and broker remote
 access to a dedicated compute environment for an end-user. The provisioned
@@ -153,7 +175,7 @@ of servers in a server farm or HPC clust
 Server 1.x, VMWare Server 2.x, VMWare ESX 3.5, and VMWare ESXi with both
 purchased licenses and free licenses.</p>
 <p><a name="VCL2.2-II.VCLRoadmap"></a></p>
-<h4 id="ii-vcl-roadmap">II. VCL Roadmap</h4>
+<h4 id="ii-vcl-roadmap">II. VCL Roadmap<a class="headerlink" href="#ii-vcl-roadmap" title="Permanent link">&para;</a></h4>
 <p>VCL 2.2 (this release)</p>
 <ul>
 <li>support for xCAT 2.x</li>
@@ -183,7 +205,7 @@ obvious goal to create a community of us
 Bringing in more developers should become easier as VCL becomes easier to
 install.</p>
 <p><a name="VCL2.2-III.GettingInvolvedintheASFVCLCommunity"></a></p>
-<h4 id="iii-getting-involved-in-the-asf-vcl-community">III. Getting Involved in the ASF VCL Community</h4>
+<h4 id="iii-getting-involved-in-the-asf-vcl-community">III. Getting Involved in the ASF VCL Community<a class="headerlink" href="#iii-getting-involved-in-the-asf-vcl-community" title="Permanent link">&para;</a></h4>
 <p>There are five ways to become involved in the ASF VCL community.</p>
 <ul>
 <li>
@@ -226,7 +248,7 @@ provide some guidance.</p>
 </li>
 </ul>
 <p><a name="VCL2.2-IV.HowtoSubmitBugsandFeatureRequests"></a></p>
-<h4 id="iv-how-to-submit-bugs-and-feature-requests">IV. How to Submit Bugs and Feature Requests</h4>
+<h4 id="iv-how-to-submit-bugs-and-feature-requests">IV. How to Submit Bugs and Feature Requests<a class="headerlink" href="#iv-how-to-submit-bugs-and-feature-requests" title="Permanent link">&para;</a></h4>
 <p>If you find a bug, please submit a bug report to our JIRA bug tracking
 system at <a href="http://issues.apache.org/jira/browse/VCL">http://issues.apache.org/jira/browse/VCL</a>
  (you will need to set up an account there if you haven't already done so -
@@ -240,10 +262,10 @@ a feature request on the dev list.</p>
 help us know how to prioritize issues. You can also "watch" the issue to
 see when activity related to it is submitted.</p>
 <p><a name="VCL2.2-ChangeLog"></a></p>
-<h2 id="change-log">Change Log</h2>
+<h2 id="change-log">Change Log<a class="headerlink" href="#change-log" title="Permanent link">&para;</a></h2>
 <p>Release Notes - VCL - Version 2.2</p>
 <p><a name="VCL2.2-Bug"></a></p>
-<h4 id="bug">Bug</h4>
+<h4 id="bug">Bug<a class="headerlink" href="#bug" title="Permanent link">&para;</a></h4>
 <ul>
 <li>[<a href="https://issues.apache.org/jira/browse/VCL-121">VCL-121</a>
 ] -         special characters in API passwords not handled correctly </li>
@@ -404,7 +426,7 @@ not in block group </li>
 datastores </li>
 </ul>
 <p><a name="VCL2.2-Improvement"></a></p>
-<h4 id="improvement">Improvement</h4>
+<h4 id="improvement">Improvement<a class="headerlink" href="#improvement" title="Permanent link">&para;</a></h4>
 <ul>
 <li>[<a href="https://issues.apache.org/jira/browse/VCL-2">VCL-2</a>
 ] -         migrate preferredimage to nextimage </li>
@@ -516,7 +538,7 @@ code </li>
 provisioning modules </li>
 </ul>
 <p><a name="VCL2.2-NewFeature"></a></p>
-<h4 id="new-feature">New Feature</h4>
+<h4 id="new-feature">New Feature<a class="headerlink" href="#new-feature" title="Permanent link">&para;</a></h4>
 <ul>
 <li>[<a href="https://issues.apache.org/jira/browse/VCL-134">VCL-134</a>
 ] -         Add ability to control whether or not users have
@@ -564,7 +586,7 @@ prevent user access </li>
 dojo filteringselect </li>
 </ul>
 <p><a name="VCL2.2-Task"></a></p>
-<h4 id="task">Task</h4>
+<h4 id="task">Task<a class="headerlink" href="#task" title="Permanent link">&para;</a></h4>
 <ul>
 <li>[<a href="https://issues.apache.org/jira/browse/VCL-138">VCL-138</a>
 ] -         remove antiquated vcldquery support </li>

Modified: websites/staging/vcl/trunk/content/docs/assignvmtohost.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/assignvmtohost.html (original)
+++ websites/staging/vcl/trunk/content/docs/assignvmtohost.html Wed Oct 18 19:55:31 2017
@@ -64,7 +64,7 @@ h2:hover > .headerlink, h3:hover > .head
 <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>

Modified: websites/staging/vcl/trunk/content/docs/authorization/administrationconcepts.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/authorization/administrationconcepts.html (original)
+++ websites/staging/vcl/trunk/content/docs/authorization/administrationconcepts.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">Administration Concepts</h1>
-    <p>There are several concepts you need to understand when administering VCL.</p>
+    <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>There are several concepts you need to understand when administering VCL.</p>
 <div class="toc">
 <ul>
 <li><a href="#resources">Resources</a><ul>
@@ -98,10 +120,10 @@
 </li>
 </ul>
 </div>
-<h2 id="resources">Resources</h2>
+<h2 id="resources">Resources<a class="headerlink" href="#resources" title="Permanent link">&para;</a></h2>
 <p>VCL manages sets of resources. There are four types of resources: images, computers, 
 management nodes, and schedules. Each of these resources types are described below.</p>
-<h3 id="imagesenvironments">Images/Environments</h3>
+<h3 id="imagesenvironments">Images/Environments<a class="headerlink" href="#imagesenvironments" title="Permanent link">&para;</a></h3>
 <p>An image is a collection of software that is installed on an operating system. For the 
 most part, these images can be deployed, used, modified, and saved (captured). However, 
 there are some cases where only some of the operations could be proformed on an image. 
@@ -115,7 +137,7 @@ VMWare can be used to provision virtuali
 sturctured in a modularized way such that it is easy to add support for other 
 provisioning technologies. We plan on adding support for other hypervisor technologies 
 in the near future.</p>
-<h3 id="computers">Computers</h3>
+<h3 id="computers">Computers<a class="headerlink" href="#computers" title="Permanent link">&para;</a></h3>
 <p>Images are deployed on to computers. VCL needs to know about all of the computers it 
 will be managing. Entries for both physical computers and Virtual Machines (some people 
 call these "slots") need to be created in VCL for it to be able to manage them.
@@ -123,22 +145,22 @@ Management Nodes</p>
 <p>Management nodes run the VCL backend code (vcld) that is responsible for deploying 
 images to computers when users make reservations for images. Each management node can 
 manage a mix of physical and virtual computers.</p>
-<h3 id="schedules">Schedules</h3>
+<h3 id="schedules">Schedules<a class="headerlink" href="#schedules" title="Permanent link">&para;</a></h3>
 <p>Each computer must have a schedule associated with it. Schedules provide a way to 
 define what times during a week a computer is available through VCL. This allows for 
 computers to be managed by another system during certain parts of a week. For example, 
 computers in a traditional university computing lab may be available through VCL when 
 the lab is physically closed, but you wouldn't want to be assigning remote users to 
 those computers when the lab is open.</p>
-<h2 id="groups">Groups</h2>
+<h2 id="groups">Groups<a class="headerlink" href="#groups" title="Permanent link">&para;</a></h2>
 <p>Users and resources are placed into groups to make management of them easier.</p>
-<h3 id="user-groups">User Groups</h3>
+<h3 id="user-groups">User Groups<a class="headerlink" href="#user-groups" title="Permanent link">&para;</a></h3>
 <p>There are two types of user groups in VCL: those whose membership is manually managed 
 through the web frontend or XML RPC API, and those whose membership is automatically 
 managed by mirroring user groups in an LDAP system. Each user group has certain attributes 
 associated with it. There are various places within VCL that user groups can be used, 
 with the primary place being granting access to resources in the privilege tree.</p>
-<h3 id="resource-groups">Resource Groups</h3>
+<h3 id="resource-groups">Resource Groups<a class="headerlink" href="#resource-groups" title="Permanent link">&para;</a></h3>
 <p>Each resource group has a type associated with it which can be one of image, computer, 
 management node, or schedule. The resource groups are used to grant users access to 
 resources and also to allow VCL to know which resources can be used in relation to other 
@@ -146,10 +168,10 @@ resources. One example of this is to con
 computers. Another example is which management nodes can manage which computers.</p>
 <p>Resource Groups also have an <em>Owning User Group</em> associated with them. The owning 
 user group has administrative access to the group to manage the group within VCL. </p>
-<h2 id="resource-management">Resource Management</h2>
+<h2 id="resource-management">Resource Management<a class="headerlink" href="#resource-management" title="Permanent link">&para;</a></h2>
 <p>VCL needs to know how resources related to one another. This is done by adding the 
 resources to a resource group, and then mapping one type of resource group to another.</p>
-<h3 id="resource-grouping">Resource Grouping</h3>
+<h3 id="resource-grouping">Resource Grouping<a class="headerlink" href="#resource-grouping" title="Permanent link">&para;</a></h3>
 <p>Resource groups can contain any number of resources. Each resource group has a resource 
 type associated with it. Only resources matching that type can be added to the group. 
 Also, it is important to note that when working with computers, physical and virtual 
@@ -157,7 +179,7 @@ computers should not be combined into th
 to assign a physical image to a virtual computer or vice versa. Some upcoming changes 
 to the code will remove this restriction, but for now, keep this restriction in mind 
 while grouping computers.</p>
-<h3 id="resource-mapping">Resource Mapping</h3>
+<h3 id="resource-mapping">Resource Mapping<a class="headerlink" href="#resource-mapping" title="Permanent link">&para;</a></h3>
 <p>After you have grouped your resources, you need to map them together. Image groups are 
 mapped to computer groups, and management node groups are mapped to computer groups. 
 Schedule groups are not mapped to anything (instead, every computer is directly assigned 
@@ -171,13 +193,13 @@ of hardware to an incompatible type of h
 mapping is to partition off parts of your hardware. For example, if you had a set of 
 users purchase their own hardware to be managed by VCL, you could map only their image 
 groups to their computer groups.</p>
-<h2 id="privileges">Privileges</h2>
+<h2 id="privileges">Privileges<a class="headerlink" href="#privileges" title="Permanent link">&para;</a></h2>
 <p>Users are granted access to parts of the VCL web site and to resources through the 
 Privilege tree. User permissions and resource attributes can both be cascaded down 
 from one node to all of its children. Additionally, cascaded user permissions and 
 resource attributes can be blocked at a node so that they do not cascade down to that 
 node or any of its children.</p>
-<h3 id="user-permissions">User Permissions</h3>
+<h3 id="user-permissions">User Permissions<a class="headerlink" href="#user-permissions" title="Permanent link">&para;</a></h3>
 <p>There are nine user permissions that can be granted to users. They can be granted 
 to users directly or to user groups.</p>
 <ul>
@@ -198,7 +220,7 @@ groups with administer or manageGroup gr
 <li><strong>userGrant</strong> - grants users access to control what user permissions are assigned at 
 the same node</li>
 </ul>
-<h3 id="resource-attributes">Resource Attributes</h3>
+<h3 id="resource-attributes">Resource Attributes<a class="headerlink" href="#resource-attributes" title="Permanent link">&para;</a></h3>
 <p>There are three resource attributes that can be assigned to a resource group at any 
 node in the privilege tree.</p>
 <ul>

Modified: websites/staging/vcl/trunk/content/docs/authorization/example2users2images-video.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/authorization/example2users2images-video.html (original)
+++ websites/staging/vcl/trunk/content/docs/authorization/example2users2images-video.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">Video - Granting Two Sets of Users Access to Two Different Sets of Images</h1>
-    <p>This video shows the steps outlined in <a href="example2users2images.html">Example - Granting Two Sets of Users Access to Two Different Sets of Images</a></p>
+    <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>This video shows the steps outlined in <a href="example2users2images.html">Example - Granting Two Sets of Users Access to Two Different Sets of Images</a></p>
 <p>This video was created using <a href="http://www.debugmode.com/wink/">Wink</a></p>
 <p><OBJECT classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" 
    codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,0,0" 

Modified: websites/staging/vcl/trunk/content/docs/authorization/example2users2images.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/authorization/example2users2images.html (original)
+++ websites/staging/vcl/trunk/content/docs/authorization/example2users2images.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">Example - Granting Two Sets of Users Access to Two Different Sets of Images</h1>
-    <p>This page explains how to grant one groups of users access to one set of images, 
+    <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>This page explains how to grant one groups of users access to one set of images, 
 and another set of users access to a separate set of images.</p>
 <p>After looking over these steps, you can watch a <a href="example2users2images-video.html">video</a> of the steps being performed.</p>
 <div class="toc">
@@ -87,7 +109,7 @@ and another set of users access to a sep
 <li><a href="#summary">Summary</a></li>
 </ul>
 </div>
-<h2 id="create-a-user-group-for-each-set-of-users">Create a User Group for Each Set of Users</h2>
+<h2 id="create-a-user-group-for-each-set-of-users">Create a User Group for Each Set of Users<a class="headerlink" href="#create-a-user-group-for-each-set-of-users" title="Permanent link">&para;</a></h2>
 <p>First, you need to create two user groups - one for each set of users.</p>
 <ol>
 <li>Click Manage Groups</li>
@@ -103,7 +125,7 @@ and another set of users access to a sep
 <li>Repeat the steps for the second group</li>
 </ol>
 <p>For the rest of the page, I'll call the groups <strong>faculty</strong> and <strong>student</strong></p>
-<h2 id="add-users-to-each-group">Add Users to Each Group</h2>
+<h2 id="add-users-to-each-group">Add Users to Each Group<a class="headerlink" href="#add-users-to-each-group" title="Permanent link">&para;</a></h2>
 <p>You need to add users to each of the groups.</p>
 <ol>
 <li>Click Manage Groups if you're not still on that page</li>
@@ -114,7 +136,7 @@ LDAP authentication, the users' accounts
 <li>Repeat for all users you wish to add to the <strong>faculty</strong> group</li>
 <li>Repeat these steps for the <strong>student</strong> group</li>
 </ol>
-<h2 id="create-an-image-group-for-each-set-of-images">Create an Image Group for Each Set of Images</h2>
+<h2 id="create-an-image-group-for-each-set-of-images">Create an Image Group for Each Set of Images<a class="headerlink" href="#create-an-image-group-for-each-set-of-images" title="Permanent link">&para;</a></h2>
 <p>Next, you need to create an image group for each set of images.</p>
 <ol>
 <li>Click Manage Groups if you're not still on that page</li>
@@ -129,7 +151,7 @@ will have access to manage some aspects
 <li>Repeat the steps for the second group</li>
 </ol>
 <p>For the rest of the page, I'll call the groups <strong>faculty images</strong> and <strong>student images</strong></p>
-<h2 id="add-images-to-each-group">Add Images to Each Group</h2>
+<h2 id="add-images-to-each-group">Add Images to Each Group<a class="headerlink" href="#add-images-to-each-group" title="Permanent link">&para;</a></h2>
 <p>Now, you need to add the desired images to each group.</p>
 <ol>
 <li>Click Manage Images</li>
@@ -143,7 +165,7 @@ in the list on the right (Ctrl+click to
 <li>Click the &lt;-Add button</li>
 <li>Repeat steps for the <strong>student images</strong> group</li>
 </ol>
-<h2 id="map-the-image-groups-to-computer-groups">Map the Image Groups to Computer Groups</h2>
+<h2 id="map-the-image-groups-to-computer-groups">Map the Image Groups to Computer Groups<a class="headerlink" href="#map-the-image-groups-to-computer-groups" title="Permanent link">&para;</a></h2>
 <p>In order for VCL to know on which computers the images can run, you must map 
 the image groups to computer groups. I'll assume you already have one or more 
 computer groups that contain computers.</p>
@@ -159,7 +181,7 @@ computer groups that contain computers.<
 groups to the same computer group. That will not affect what images the users 
 have access to.)</li>
 </ol>
-<h2 id="create-a-two-privilege-nodes">Create a Two Privilege Nodes</h2>
+<h2 id="create-a-two-privilege-nodes">Create a Two Privilege Nodes<a class="headerlink" href="#create-a-two-privilege-nodes" title="Permanent link">&para;</a></h2>
 <p>Now, you need to create one node for each user group to separate their access.</p>
 <ol>
 <li>Click Privileges</li>
@@ -171,7 +193,7 @@ the two new nodes</li>
 <li>Repeat for the second node for the other user group</li>
 </ol>
 <p>I'll refer to these nodes as <strong>faculty access</strong> and <strong>student access</strong></p>
-<h2 id="assign-rights-at-each-node">Assign Rights at Each Node</h2>
+<h2 id="assign-rights-at-each-node">Assign Rights at Each Node<a class="headerlink" href="#assign-rights-at-each-node" title="Permanent link">&para;</a></h2>
 <p>Finally, you need to give each user group the <strong>imageCheckOut</strong> privilege at 
 their respective nodes, and give each image group the <strong>available</strong> attribute 
 at their respective nodes.</p>
@@ -195,7 +217,7 @@ at their respective nodes.</p>
 <li>Select the checkbox for the <strong>available</strong> attribute</li>
 <li>Click Submit New Resource Group</li>
 </ol>
-<h2 id="summary">Summary</h2>
+<h2 id="summary">Summary<a class="headerlink" href="#summary" title="Permanent link">&para;</a></h2>
 <p>Now, users in the <strong>faculty</strong> user group will have access to check out images 
 in the <strong>faculty images</strong> image group, and users in the <strong>student</strong> user group 
 will have access to check out images in the <strong>student images</strong> image group.</p>

Modified: websites/staging/vcl/trunk/content/docs/authorization/grantaccesstonewimage.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/authorization/grantaccesstonewimage.html (original)
+++ websites/staging/vcl/trunk/content/docs/authorization/grantaccesstonewimage.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">Granting Access to a New Image</h1>
-    <h2 id="overview">Overview</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="overview">Overview<a class="headerlink" href="#overview" title="Permanent link">&para;</a></h2>
 <p>Once you have created a new image, there are a few things you have to do to allow 
 other people to use it.  If you don't have access to do any of the following steps, 
 you will need to get a VCL administrator to do them for you.</p>
@@ -81,7 +103,7 @@ to be run on a few computers that have b
 <p><strong>NOTE</strong>: After you have been through these steps one time, if you are granting the same 
 set of users access to a new image, you may only have to perform step 1.1 for subsequent 
 images.</p>
-<h2 id="step-1-image-mapping">Step 1: Image Mapping</h2>
+<h2 id="step-1-image-mapping">Step 1: Image Mapping<a class="headerlink" href="#step-1-image-mapping" title="Permanent link">&para;</a></h2>
 <p>Images are mapped to be run on a set of computers. See the documentation on 
 <a href="administrationconcepts.html#resource-mapping">Resource Mapping</a> to learn 
 more about why this is done. For your new image to be able to run 
@@ -108,7 +130,7 @@ already have computers that are in those
 </ul>
 </li>
 </ol>
-<h2 id="step-2-privileges">Step 2: Privileges</h2>
+<h2 id="step-2-privileges">Step 2: Privileges<a class="headerlink" href="#step-2-privileges" title="Permanent link">&para;</a></h2>
 <p>Now, you need to grant access to use the image to a user or group of users under the Privileges section of the site.  Here are the steps involved:</p>
 <ol>
 <li>Select <strong>Privileges</strong></li>

Modified: websites/staging/vcl/trunk/content/docs/baseimagecreation.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/baseimagecreation.html (original)
+++ websites/staging/vcl/trunk/content/docs/baseimagecreation.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">Creating Base Images from an ISO - Part 1</h1>
-    <p>This page describes how to create a base image from an install media. </p>
+    <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>This page describes how to create a base image from an install media. </p>
 <p>These instructions are broken up into parts to assist in providing 
 detailed instructions based on the supported provisioning modules and 
 Operating Systems. The supported provisioning methods for VCL are (xCAT, 
@@ -95,7 +117,7 @@ VMware, and KVM).</p>
 <li><a href="#add-the-base-image-to-an-image-group">Add the Base Image to an Image Group</a></li>
 </ul>
 </div>
-<h3 id="requirements">Requirements</h3>
+<h3 id="requirements">Requirements<a class="headerlink" href="#requirements" title="Permanent link">&para;</a></h3>
 <p>Before getting started make sure you have the following requirements 
 completed or on hand:</p>
 <ul>
@@ -122,8 +144,8 @@ for use later in the process</li>
 </ul>
 <p>These instructions assume you have root access on your management 
 node and are using a bash shell.</p>
-<h3 id="preparing-node-under-a-supported-provisioning-system">Preparing node under a supported provisioning system</h3>
-<h4 id="vmware-esxesxi-4x-5x-vcenter">VMware ESX/ESXi 4.x, 5.x, vCenter</h4>
+<h3 id="preparing-node-under-a-supported-provisioning-system">Preparing node under a supported provisioning system<a class="headerlink" href="#preparing-node-under-a-supported-provisioning-system" title="Permanent link">&para;</a></h3>
+<h4 id="vmware-esxesxi-4x-5x-vcenter">VMware ESX/ESXi 4.x, 5.x, vCenter<a class="headerlink" href="#vmware-esxesxi-4x-5x-vcenter" title="Permanent link">&para;</a></h4>
 <p>The instructions assume that VMware has been configured with the 
 following bridged networks:</p>
 <ul>
@@ -176,15 +198,15 @@ following bridged networks:</p>
 <li>Enter the private MAC address you retrieved earlier</li>
 <li>Click <strong>Finish</strong></li>
 </ul>
-<h4 id="kvm">KVM</h4>
+<h4 id="kvm">KVM<a class="headerlink" href="#kvm" title="Permanent link">&para;</a></h4>
 <ul>
 <li>Create guest OS on KVM host...</li>
 </ul>
-<h4 id="bare-metal-via-xcat">Bare Metal via xCAT</h4>
+<h4 id="bare-metal-via-xcat">Bare Metal via xCAT<a class="headerlink" href="#bare-metal-via-xcat" title="Permanent link">&para;</a></h4>
 <p>The requirement in this section is to have a working xCAT system.</p>
-<h3 id="next-steps-installing-os">Next Steps - Installing OS</h3>
-<h4 id="install-windows-os-for-a-base-image">Install Windows OS for a Base Image</h4>
-<h4 id="install-linux-os-for-a-base-image">Install Linux OS for a Base Image</h4>
+<h3 id="next-steps-installing-os">Next Steps - Installing OS<a class="headerlink" href="#next-steps-installing-os" title="Permanent link">&para;</a></h3>
+<h4 id="install-windows-os-for-a-base-image">Install Windows OS for a Base Image<a class="headerlink" href="#install-windows-os-for-a-base-image" title="Permanent link">&para;</a></h4>
+<h4 id="install-linux-os-for-a-base-image">Install Linux OS for a Base Image<a class="headerlink" href="#install-linux-os-for-a-base-image" title="Permanent link">&para;</a></h4>
 <ul>
 <li>Power on the VM and follow the installation instructions for the
 Linux distribution and version you are installing.</li>
@@ -282,7 +304,7 @@ back:</p>
 
 </li>
 </ul>
-<h3 id="capture-the-image">Capture the Image</h3>
+<h3 id="capture-the-image">Capture the Image<a class="headerlink" href="#capture-the-image" title="Permanent link">&para;</a></h3>
 <ul>
 <li>
 <p>Run the following command on the management node:</p>
@@ -310,7 +332,7 @@ of the output saying "image capture succ
 WARNING messages, the last of which says something to the effect "image 
 failed to be captured".  Further troubleshooting is required if the 
 image fails to be captured.</p>
-<h3 id="add-the-base-image-to-an-image-group">Add the Base Image to an Image Group</h3>
+<h3 id="add-the-base-image-to-an-image-group">Add the Base Image to an Image Group<a class="headerlink" href="#add-the-base-image-to-an-image-group" title="Permanent link">&para;</a></h3>
 <p>The vcld --setup utility does not add the new base image to any image 
 groups.  You must add the image to an image group using the VCL website 
 after the image capture process is complete.  Reservations for the 

Modified: websites/staging/vcl/trunk/content/docs/changelog.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/changelog.html (original)
+++ websites/staging/vcl/trunk/content/docs/changelog.html Wed Oct 18 19:55:31 2017
@@ -64,7 +64,7 @@ h2:hover > .headerlink, h3:hover > .head
 <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>

Modified: websites/staging/vcl/trunk/content/docs/configure-the-default-profile.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/configure-the-default-profile.html (original)
+++ websites/staging/vcl/trunk/content/docs/configure-the-default-profile.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,14 +83,25 @@
   
   <div id="content">
     <h1 class="title">Configure the Default Profile</h1>
-    <p>A Windows profile is the desktop environment configured for a
+    <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 Windows profile is the desktop environment configured for a
 particular user. It contains various settings such as desktop colors,
 backgrounds, icon placement, and Windows Explorer settings. The default
 profile is a template profile that is used when a user logs on to a Windows
 computer for the first time. The default profile can be customized by the
 image creator.</p>
-<h1 id="windows-xp-and-windows-server-2003">Windows XP and Windows Server 2003</h1>
-<h3 id="create-a-profile-configuration-account">Create a profile configuration account:</h3>
+<h1 id="windows-xp-and-windows-server-2003">Windows XP and Windows Server 2003<a class="headerlink" href="#windows-xp-and-windows-server-2003" title="Permanent link">&para;</a></h1>
+<h3 id="create-a-profile-configuration-account">Create a profile configuration account:<a class="headerlink" href="#create-a-profile-configuration-account" title="Permanent link">&para;</a></h3>
 <ol>
 <li>While logged on as <strong>Administrator</strong>, create a local Windows user account
 named <strong>VCLProfile</strong> and add it to the <strong>Administrators</strong> group</li>
@@ -92,7 +114,7 @@ named <strong>VCLProfile</strong> and ad
     you will not be able to complete step 7 below.
     </ol></li>
 </ol>
-<h3 id="copy-the-profile-to-default-user">Copy the profile to "Default User":</h3>
+<h3 id="copy-the-profile-to-default-user">Copy the profile to "Default User":<a class="headerlink" href="#copy-the-profile-to-default-user" title="Permanent link">&para;</a></h3>
 <ol>
 <li>Log back on as <strong>Administrator</strong></li>
 <li>Rename the <strong>C:\Documents and Settings\Default User</strong> directory to
@@ -106,7 +128,7 @@ Copy profile to: <strong>C:\Documents an
 Permitted to use: add the <strong>Everyone</strong> group</li>
 <li>Click <strong>OK</strong></li>
 </ol>
-<h3 id="clean-up-the-profile-configuration-account">Clean up the profile configuration account:</h3>
+<h3 id="clean-up-the-profile-configuration-account">Clean up the profile configuration account:<a class="headerlink" href="#clean-up-the-profile-configuration-account" title="Permanent link">&para;</a></h3>
 <ol>
 <li>Delete the <strong>VCLProfile</strong> user</li>
 <li>Delete <strong>C:\Documents and Settings\VCLProfile</strong></li>
@@ -114,13 +136,13 @@ Permitted to use: add the <strong>Everyo
 <p>You can then create another account and log in using it to make sure your
 profile settings take affect for new users. Be sure to delete it once
 you're done testing.</p>
-<h1 id="windows-7-and-windows-server-2008">Windows 7 and Windows Server 2008</h1>
+<h1 id="windows-7-and-windows-server-2008">Windows 7 and Windows Server 2008<a class="headerlink" href="#windows-7-and-windows-server-2008" title="Permanent link">&para;</a></h1>
 <p>Microsoft does not support copying profiles under Windows 7 and Windows
 Server 2008.  The "Copy To" button is grayed out for all profiles except
 the default profile.  The only supported method is built into Sysprep and
 this method is itself very problematic.  The following steps are not
 supported or recommended by Microsoft but seem to work:</p>
-<h3 id="allow-desktop-backgrounds">Allow Desktop Backgrounds</h3>
+<h3 id="allow-desktop-backgrounds">Allow Desktop Backgrounds<a class="headerlink" href="#allow-desktop-backgrounds" title="Permanent link">&para;</a></h3>
 <ol>
 <li>Download and edit the RDP file for your imaging reservation from the VCL
 website to allow desktop backgrounds or else you won’t be able to change
@@ -142,7 +164,7 @@ the desktop background color
     <li>Click <em>OK</em>
     </ol></li>
 </ol>
-<h3 id="create-a-profile-configuration-account_1">Create a profile configuration account:</h3>
+<h3 id="create-a-profile-configuration-account_1">Create a profile configuration account:<a class="headerlink" href="#create-a-profile-configuration-account_1" title="Permanent link">&para;</a></h3>
 <ol>
 <li>Create a new local user account named Profile
     <ol type="a">
@@ -173,7 +195,7 @@ over with a new account, delete the exis
     <li>Logout as VCLProfile
     </ol></li>
 </ol>
-<h3 id="copy-the-profile-to-default">Copy the profile to "Default":</h3>
+<h3 id="copy-the-profile-to-default">Copy the profile to "Default":<a class="headerlink" href="#copy-the-profile-to-default" title="Permanent link">&para;</a></h3>
 <ol>
 <li>Rename the <strong>VCLProfile</strong> user profile folder to <strong>Default</strong>
     <ol type="a">
@@ -234,7 +256,7 @@ applied to it.</em>
 </ol>
 <p>Any new local user accounts created on the computer should receive a user
 profile configured with the customizations you made to the VCLProfile account.</p>
-<h2 id="how-to-force-the-desktop-background-to-appear-on-windows-7-windows-server-2008">How to Force the Desktop Background to Appear on Windows 7 &amp; Windows Server 2008</h2>
+<h2 id="how-to-force-the-desktop-background-to-appear-on-windows-7-windows-server-2008">How to Force the Desktop Background to Appear on Windows 7 &amp; Windows Server 2008<a class="headerlink" href="#how-to-force-the-desktop-background-to-appear-on-windows-7-windows-server-2008" title="Permanent link">&para;</a></h2>
 <ol>
 <li>Run <strong>gpedit.msc</strong></li>
 <li>Navigate to <strong>User Configuration &gt; Scripts</strong></li>

Modified: websites/staging/vcl/trunk/content/docs/connectmethods.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/connectmethods.html (original)
+++ websites/staging/vcl/trunk/content/docs/connectmethods.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">Connect Methods</h1>
-    <h2 id="overview">Overview</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="overview">Overview<a class="headerlink" href="#overview" title="Permanent link">&para;</a></h2>
 <p>A <strong>connect method</strong> is the software used to connect to a reserved node.</p>
 <p>Before 2.3, there were only a few, fixed connect methods used - RDP for Windows
 and ssh for Linux. In 2.3, the first stage of configurable connect methods
@@ -84,7 +106,7 @@ connect methods to be managed through th
 provisioned by vcld (or are considered to be part of an OS by default) 
 and those that must be manually installed in the image by the image
 maintainer. Either type can be added to VCL and mapped to an image.</p>
-<h2 id="connect-method-schema">Connect Method schema</h2>
+<h2 id="connect-method-schema">Connect Method schema<a class="headerlink" href="#connect-method-schema" title="Permanent link">&para;</a></h2>
 <p>Understanding the connect method database schema is key to managing the 
 available connect methods. There are two tables:</p>
 <ul>
@@ -131,7 +153,7 @@ is only done to an OS type <strong>or</s
 Windows OS type, but there was an image where VNC should be used instead, entries would
 be added for any imagerevisionid of that image for RDP with disabled set to 1.</p>
 </blockquote>
-<h2 id="default-entries">Default entries</h2>
+<h2 id="default-entries">Default entries<a class="headerlink" href="#default-entries" title="Permanent link">&para;</a></h2>
 <p>The schema provided with Apache VCL 2.3 has four connect methods by default:</p>
 <ul>
 <li>ssh</li>
@@ -169,8 +191,8 @@ OS. Specifically, the third entry means
 linux images, ssh will be selected as one of the enabled connect methods. The fourth 
 entry means that on the edit image profile page for any windows images, RDP will be
 selected as one of the enabled connect methods.</p>
-<h2 id="examples">Examples</h2>
-<h3 id="adding-vnc-as-an-available-option-for-linux">Adding VNC as an available option for Linux</h3>
+<h2 id="examples">Examples<a class="headerlink" href="#examples" title="Permanent link">&para;</a></h2>
+<h3 id="adding-vnc-as-an-available-option-for-linux">Adding VNC as an available option for Linux<a class="headerlink" href="#adding-vnc-as-an-available-option-for-linux" title="Permanent link">&para;</a></h3>
 <p>In this example, we add VNC as an available connect method that can be selected on 
 edit image profile page for any Linux images. However, we'll set it with autoprovisioned
 set to 0, meaning that the image maintainer is responsible for installing VNC in
@@ -204,7 +226,7 @@ actually assign it to be selected for an
 "VNC on port 5900" will be available as a connect method that can be assigned. If it
 is selected, a warning message will be displayed stating that VCL cannot autoprovision
 VNC and that it must have already been installed in the image by the image maintainer.</p>
-<h3 id="adding-xrdp-for-linux-and-enabling-it-for-os-type-fedora-16">Adding xRDP for Linux and Enabling it for OS type Fedora 16</h3>
+<h3 id="adding-xrdp-for-linux-and-enabling-it-for-os-type-fedora-16">Adding xRDP for Linux and Enabling it for OS type Fedora 16<a class="headerlink" href="#adding-xrdp-for-linux-and-enabling-it-for-os-type-fedora-16" title="Permanent link">&para;</a></h3>
 <p>In this example, we'll add xRDP as an available option for any Linux images and set
 it as enabled for the OS type Fedora 16. We'll use 23 as OS.id for Fedora 16.</p>
 <p>First, we need to add xRDP to the connectmethod table:
@@ -238,7 +260,7 @@ xRDP and that it must have already been
 Additionally, for any Fedora 16 images, it will be listed as an assigned connect
 method by default (note: Fedora 16 does not include xRDP by default, it's just being
 used an example here).</p>
-<h3 id="understanding-entries-created-by-removing-a-default-entry-from-an-image">Understanding entries created by removing a default entry from an image</h3>
+<h3 id="understanding-entries-created-by-removing-a-default-entry-from-an-image">Understanding entries created by removing a default entry from an image<a class="headerlink" href="#understanding-entries-created-by-removing-a-default-entry-from-an-image" title="Permanent link">&para;</a></h3>
 <p>This is not something that a VCL admin would need to do manually in the
 database, but it is useful to understand what happens in the database
 when a connect method that is mapped by OS type or OS is removed from an
@@ -268,7 +290,7 @@ the web server image):</p>
 
 <p>The above entry means, "disable connect method 5 (xRDP) for image revision 582 (web server)
 even if it is enabled for the image's OS or OS type".</p>
-<h2 id="screen-shots">Screen Shots</h2>
+<h2 id="screen-shots">Screen Shots<a class="headerlink" href="#screen-shots" title="Permanent link">&para;</a></h2>
 <p>Here are some screen shots to know what things look like in the web interface.</p>
 <p>This image has the Connect Methods section of the Edit Image Profile page
 highlighted.</p>

Modified: websites/staging/vcl/trunk/content/docs/creating-a-cluster-enviroment.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/creating-a-cluster-enviroment.html (original)
+++ websites/staging/vcl/trunk/content/docs/creating-a-cluster-enviroment.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,14 +83,25 @@
   
   <div id="content">
     <h1 class="title">Creating a Cluster enviroment</h1>
-    <p>Cluster environments are created from existing VCL images.</p>
+    <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>Cluster environments are created from existing VCL images.</p>
 <p>The terms <strong>parent</strong> and <strong>child</strong> are used in this document and with the VCL
 provisioning:</p>
 <p><strong>parent</strong> - the primary image or selectable image through the VCL New
 Reservation menu</p>
 <p><strong>child</strong> - the second image or images that are also loaded and are the sub
 images associated with the parent image</p>
-<h3 id="to-create-a-cluster-image">To Create a cluster image</h3>
+<h3 id="to-create-a-cluster-image">To Create a cluster image<a class="headerlink" href="#to-create-a-cluster-image" title="Permanent link">&para;</a></h3>
 <ol>
 <li>Select <strong>Manage Images -&gt; Edit Image Profiles</strong></li>
 <li>Select <strong>Edit</strong> beside the parent image</li>



Mime
View raw message