vcl-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1019714 [5/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/managegroups.py---remotely-managing-user-groups.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/managegroups.py---remotely-managing-user-groups.html (original)
+++ websites/staging/vcl/trunk/content/confluence_export/managegroups.py---remotely-managing-user-groups.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,19 +83,30 @@
   
   <div id="content">
     <h1 class="title">managegroups.py - Remotely managing user groups</h1>
-    <p>managegroups.py is a script for remotely managing VCL user groups. It uses
+    <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>managegroups.py is a script for remotely managing VCL user groups. It uses
 VCL's XML RPC API to provide an easy command line driven way of doing group
 management.</p>
-<p>{color:#ff0000}{<em>}NOTE: This script does not work with python 2.7. It
+<p>{color:#ff0000}{<em color="color">}NOTE: This script does not work with python 2.7. It
 relies on the xmlrpclib module which changed from 2.6 to 2.7 in a way that
-broke the script. You need to use python 2.6 for it to work.</em>{color}</p>
+broke the script. You need to use python 2.6 for it to work.</em></p>
 <p><a name="managegroups.py-Remotelymanagingusergroups-Downloadinformation"></a></p>
-<h2 id="download-information">Download information</h2>
+<h2 id="download-information">Download information<a class="headerlink" href="#download-information" title="Permanent link">&para;</a></h2>
 <p>managegroups.py is not included in any official releases. You can download
 it from our subversion repository.</p>
 <p><a href="https://svn.apache.org/repos/asf/vcl/sandbox/useful_scripts/managegroups.py">Download managegroups.py</a></p>
 <p><a name="managegroups.py-Remotelymanagingusergroups-AvailableCommands"></a></p>
-<h2 id="available-commands">Available Commands</h2>
+<h2 id="available-commands">Available Commands<a class="headerlink" href="#available-commands" title="Permanent link">&para;</a></h2>
 <p>Running managegroups.py with no arguments provides help on how to use it.
 It is used by specifying one of the following commands along with
 parameters specific to each command.</p>
@@ -107,7 +129,7 @@ parameters specific to each command.</p>
  - removes all users currently in a group</li>
 </ul>
 <p><a name="managegroups.py-Remotelymanagingusergroups-ReturnStatus"></a></p>
-<h2 id="return-status">Return Status</h2>
+<h2 id="return-status">Return Status<a class="headerlink" href="#return-status" title="Permanent link">&para;</a></h2>
 <p>These are the possible values of the return status:
 <em> 0 - successful execution
 </em> 1 - missing authentication information
@@ -117,7 +139,7 @@ the file
 <em> 4 - no users specified to add to or remove from a group
 </em> 5 - error encountered while performing XML RPC API call</p>
 <p><a name="managegroups.py-Remotelymanagingusergroups-ReturnOutput"></a></p>
-<h2 id="return-output">Return Output</h2>
+<h2 id="return-output">Return Output<a class="headerlink" href="#return-output" title="Permanent link">&para;</a></h2>
 <p>The output of managegroups.py will always start with one of:
 <em> SUCCESS: - indicates successful run of the command
 </em> ERROR: - indicates a problem running the command
@@ -127,7 +149,7 @@ There is one exception. If you specify a
 for it, the option parser used in the script will generate an error.
 However, in those cases, the return status of the command will always be 2.</p>
 <p><a name="managegroups.py-Remotelymanagingusergroups-Authentication"></a></p>
-<h2 id="authentication">Authentication</h2>
+<h2 id="authentication">Authentication<a class="headerlink" href="#authentication" title="Permanent link">&para;</a></h2>
 <p>The script needs to know what userid/password to use and what URL to
 access. These can either be defined as variables within the script (look at
 the very top of the file) or specified as parameters on the command line,
@@ -147,7 +169,7 @@ it contains spaces
 index.php?mode=xmlrpccall - i.e. <a href="https://vcl.ncsu.edu/scheduling/index.php?mode=xmlrpccall">https://vcl.ncsu.edu/scheduling/index.php?mode=xmlrpccall</a>
 )</p>
 <p><a name="managegroups.py-Remotelymanagingusergroups-{anchor:addUserGroup}addUserGroup"></a></p>
-<h2 id="anchoraddusergroupaddusergroup">{anchor:addUserGroup}addUserGroup</h2>
+<h2 id="anchoraddusergroupaddusergroup">{anchor:addUserGroup}addUserGroup<a class="headerlink" href="#anchoraddusergroupaddusergroup" title="Permanent link">&para;</a></h2>
 <p>Use this command to create a new user group.</p>
 <p>parameters:
 <em> -n name - name of new user group
@@ -165,7 +187,7 @@ extension to a reservation at a time</p>
 <p>on success, returns:
 SUCCESS: User group sucessfully created</p>
 <p><a name="managegroups.py-Remotelymanagingusergroups-{anchor:getUserGroupAttributes}getUserGroupAttributes"></a></p>
-<h2 id="anchorgetusergroupattributesgetusergroupattributes">{anchor:getUserGroupAttributes}getUserGroupAttributes</h2>
+<h2 id="anchorgetusergroupattributesgetusergroupattributes">{anchor:getUserGroupAttributes}getUserGroupAttributes<a class="headerlink" href="#anchorgetusergroupattributesgetusergroupattributes" title="Permanent link">&para;</a></h2>
 <p>Use this command to get existing information about a user group's
 attributes (it does not include the current membership of the group).
 parameters:
@@ -180,7 +202,7 @@ initialMaxTime: <max allowed initial res
 totalMaxTime: <total allowed reservation time>
 maxExtendTime: <make time allowed per extension></p>
 <p><a name="managegroups.py-Remotelymanagingusergroups-{anchor:deleteUserGroup}deleteUserGroup"></a></p>
-<h2 id="anchordeleteusergroupdeleteusergroup">{anchor:deleteUserGroup}deleteUserGroup</h2>
+<h2 id="anchordeleteusergroupdeleteusergroup">{anchor:deleteUserGroup}deleteUserGroup<a class="headerlink" href="#anchordeleteusergroupdeleteusergroup" title="Permanent link">&para;</a></h2>
 <p>Use this command to delete an existing user group.
 parameters:
 <em> -n name - name of an existing user group
@@ -188,7 +210,7 @@ parameters:
 <p>on success, returns:
 SUCCESS: User group sucessfully deleted</p>
 <p><a name="managegroups.py-Remotelymanagingusergroups-{anchor:editUserGroup}editUserGroup"></a></p>
-<h2 id="anchoreditusergroupeditusergroup">{anchor:editUserGroup}editUserGroup</h2>
+<h2 id="anchoreditusergroupeditusergroup">{anchor:editUserGroup}editUserGroup<a class="headerlink" href="#anchoreditusergroupeditusergroup" title="Permanent link">&para;</a></h2>
 <p>Use this command to modify attributes of an existing user group (it is not
 used for editing the membership of the group). You can specify any
 combination of the parameters labeled as optional.
@@ -210,7 +232,7 @@ request as an extension to a reservation
 <p>on success, returns:
 SUCCESS: User group sucessfully updated</p>
 <p><a name="managegroups.py-Remotelymanagingusergroups-{anchor:getUserGroupMembers}getUserGroupMembers"></a></p>
-<h2 id="anchorgetusergroupmembersgetusergroupmembers">{anchor:getUserGroupMembers}getUserGroupMembers</h2>
+<h2 id="anchorgetusergroupmembersgetusergroupmembers">{anchor:getUserGroupMembers}getUserGroupMembers<a class="headerlink" href="#anchorgetusergroupmembersgetusergroupmembers" title="Permanent link">&para;</a></h2>
 <p>Use this command to get the current members of a group. Note that it is
 possible for a group to have no members.
 parameters:
@@ -220,7 +242,7 @@ parameters:
 SUCCESS: Membership retrieved
 followed by one user per line in username@affiliation form</p>
 <p><a name="managegroups.py-Remotelymanagingusergroups-{anchor:addUsersToGroup}addUsersToGroup"></a></p>
-<h2 id="anchoradduserstogroupadduserstogroup">{anchor:addUsersToGroup}addUsersToGroup</h2>
+<h2 id="anchoradduserstogroupadduserstogroup">{anchor:addUsersToGroup}addUsersToGroup<a class="headerlink" href="#anchoradduserstogroupadduserstogroup" title="Permanent link">&para;</a></h2>
 <p>Use this command to add users to an existing user group. <em>Note</em>: The users
 will either need to already exist in VCL or be part of an affiliation that
 is backed by LDAP so that the users can be verified.
@@ -235,7 +257,7 @@ in username@affiliation form</p>
 <p>on success, returns:
 SUCCESS: Users sucessfully added to group</p>
 <p><a name="managegroups.py-Remotelymanagingusergroups-{anchor:removeUsersFromGroup}removeUsersFromGroup"></a></p>
-<h2 id="anchorremoveusersfromgroupremoveusersfromgroup">{anchor:removeUsersFromGroup}removeUsersFromGroup</h2>
+<h2 id="anchorremoveusersfromgroupremoveusersfromgroup">{anchor:removeUsersFromGroup}removeUsersFromGroup<a class="headerlink" href="#anchorremoveusersfromgroupremoveusersfromgroup" title="Permanent link">&para;</a></h2>
 <p>Use this command to remove users from an existing user group.
 parameters:
 <em> -n name - name of an existing user group
@@ -248,7 +270,7 @@ in username@affiliation form</p>
 <p>on success, returns:
 SUCCESS: Users sucessfully removed from group</p>
 <p><a name="managegroups.py-Remotelymanagingusergroups-{anchor:emptyGroupMembership}emptyGroupMembership"></a></p>
-<h2 id="anchoremptygroupmembershipemptygroupmembership">{anchor:emptyGroupMembership}emptyGroupMembership</h2>
+<h2 id="anchoremptygroupmembershipemptygroupmembership">{anchor:emptyGroupMembership}emptyGroupMembership<a class="headerlink" href="#anchoremptygroupmembershipemptygroupmembership" title="Permanent link">&para;</a></h2>
 <p>Use this command to empty the membership of an existing user group.
 parameters:
 <em> -n name - name of an existing user group
@@ -256,7 +278,7 @@ parameters:
 <p>on success, returns:
 SUCCESS: Users sucessfully removed from group</p>
 <p><a name="managegroups.py-Remotelymanagingusergroups-Examples"></a></p>
-<h2 id="examples">Examples</h2>
+<h2 id="examples">Examples<a class="headerlink" href="#examples" title="Permanent link">&para;</a></h2>
 <p>The last example includes the authentication information on the command
 line. For the other examples, the authentication would have been specified
 inline in the script. Authentication information was only included in one

Modified: websites/staging/vcl/trunk/content/confluence_export/management-node-installation.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/management-node-installation.html (original)
+++ websites/staging/vcl/trunk/content/confluence_export/management-node-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>

Modified: websites/staging/vcl/trunk/content/confluence_export/missing_from_export.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/missing_from_export.html (original)
+++ websites/staging/vcl/trunk/content/confluence_export/missing_from_export.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"></h1>
-    <p>The following pages were not properly exported and need to be manually copied from Confluence:</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>The following pages were not properly exported and need to be manually copied from Confluence:</p>
 <p>administrator\'s-faq.mdtext</p>
 <p>current-&amp;-future-development-topics.mdtext</p>
 <p>how-to\'s.mdtext</p>

Modified: websites/staging/vcl/trunk/content/confluence_export/modularized-architecture.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/modularized-architecture.html (original)
+++ websites/staging/vcl/trunk/content/confluence_export/modularized-architecture.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">Modularized Architecture</h1>
-    <p><a name="ModularizedArchitecture-Background"></a></p>
-<h1 id="background">Background</h1>
+    <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="ModularizedArchitecture-Background"></a></p>
+<h1 id="background">Background<a class="headerlink" href="#background" title="Permanent link">&para;</a></h1>
 <p>The VCL backend code was significantly reworked in version 2.0
 to&nbsp;utilize a&nbsp;"modularized" framework.&nbsp; This framework allows
 certain parts of the code to be separated from the core code through the
@@ -94,7 +116,7 @@ a reservation is complete.&nbsp; A modul
 and configuring a management node to use a certain algorithm is as simple
 as changing one value in the database.</p>
 <p><a name="ModularizedArchitecture-ObjectOrientationandInheritance"></a></p>
-<h2 id="object-orientation-and-inheritance">Object Orientation and Inheritance</h2>
+<h2 id="object-orientation-and-inheritance">Object Orientation and Inheritance<a class="headerlink" href="#object-orientation-and-inheritance" title="Permanent link">&para;</a></h2>
 <p>Object orientation and inheritance are used in the VCL modular framework,
 allowing modules to access functionality from&nbsp;the classes which they
 inherit from.&nbsp; This relieves module developers from having
@@ -114,13 +136,13 @@ including:
 </strong> data access
 <strong> module initialization
 </strong> access to&nbsp;other auxiliary modules where appropriate</p>
-<p>{color:#6600ff}{<em>}Explain:</em>{color}
+<p>{color:#6600ff}{<em color="color">}Explain:</em>
 <em> {color:#6600ff}{<em>}abstract and concrete classes - abstract are not
 instantiated{</em>}{color}</em> {color:#6600ff}{<em>}classes can be empty, contain no subs, but act as a
 placeholder in case it's decided later on that a sub would be
 useful{</em>}{color}{color:#6600ff}&nbsp;{color}</p>
 <p><a name="ModularizedArchitecture-Advantages"></a></p>
-<h2 id="advantages">Advantages</h2>
+<h2 id="advantages">Advantages<a class="headerlink" href="#advantages" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Modules make it easier for developers to implement new technologies to be
 used with VCL&nbsp;easily</li>
@@ -132,62 +154,62 @@ technologies or functionality</li>
 distinct task and the core code does not need to check for numerous
 different conditions based on the technology being used</li>
 </ul>
-<p>{color:#6600ff}{<em>}Explain:&nbsp;</em>{color}
+<p>{color:#6600ff}{<em color="color">}Explain:&nbsp;</em>
 <em> {color:#6600ff}{<em>}more about benefits of inheritance{</em>}{color}</em> {color:#6600ff}{<em>}give OS example and include diagram{</em>}{color}
 <strong> {color:#6600ff}{<em>}Windows - Desktop - XP - Vista{</em>}{color}</strong> {color:#6600ff}{<em>}implement subs as high up as possible so child classes
 inherit them{</em>}{color}
 <strong> {color:#6600ff}{<em>}child classes can override an inherited sub if it
-doesn't fit its needs{</em>}{color}</strong> {color:#6600ff}{<em>}use example of firewalls in Windows.&nbsp; Windows.pm
+doesn't fit its needs{</em>}{color}</strong> {color:#6600ff}{<em color="color">}use example of firewalls in Windows.&nbsp; Windows.pm
 implements a firewall sub which works for everything but Vista.&nbsp;
 Vista.pm can implement a sub with the same name and it will override the
 one in Windows.pm, yet Vista.pm still enjoys everthing else Windows.pm
-offers.</em>{color}</p>
+offers.</em></p>
 <p><a name="ModularizedArchitecture-CoreModules"></a></p>
-<h1 id="core-modules">Core Modules</h1>
-<p>&nbsp;&nbsp;{color:#6600ff}{<em>}Explain:</em>{color}
+<h1 id="core-modules">Core Modules<a class="headerlink" href="#core-modules" title="Permanent link">&para;</a></h1>
+<p>&nbsp;&nbsp;{color:#6600ff}{<em color="color">}Explain:</em>
 <em> {color:#6600ff}{<em>}only core modules should ever change the request
 state/laststate/computer state{</em>}{color}</em> {color:#6600ff}{<em>}only core modules should change anything in the request
 and rsvp tables{</em>}{color}
 <em> {color:#6600ff}{<em>}provide state flow{</em>}{color}</em> {color:#6600ff}{<em>}provide data access{</em>}{color}
-<em> {color:#6600ff}{<em>}provide utility functions&nbsp;</em>{color}</em> {color:#6600ff}{<em>}database and data structure are abstracted from
+<em> {color:#6600ff}{<em color="color">}provide utility functions&nbsp;</em></em> {color:#6600ff}{<em>}database and data structure are abstracted from
 auxiliary modules{</em>}{color}
-* {color:#6600ff}{<em>}ongoing - should not contain code specific to something
-that can be modularized such as "if windows... else linux..."</em>{color}</p>
+* {color:#6600ff}{<em color="color">}ongoing - should not contain code specific to something
+that can be modularized such as "if windows... else linux..."</em></p>
 <p><a name="ModularizedArchitecture-vcld(VCL::vcld)"></a></p>
-<h3 id="vcld-vclvcld">vcld (VCL::vcld)</h3>
-<p>{color:#6600ff}{<em>}Explain:</em>{color}
+<h3 id="vcld-vclvcld">vcld (VCL::vcld)<a class="headerlink" href="#vcld-vclvcld" title="Permanent link">&para;</a></h3>
+<p>{color:#6600ff}{<em color="color">}Explain:</em>
 <em> {color:#6600ff}{<em>}main exe{</em>}{color}</em> {color:#6600ff}{<em>}loops every 12 seconds by default{</em>}{color}
 <em> {color:#6600ff}{<em>}doesn't inherit{</em>}{color}</em> {color:#6600ff}{<em>}creates DataStructure object{</em>}{color}
 <em> {color:#6600ff}{<em>}forks{</em>}{color}</em> {color:#6600ff}{<em>}sets some $ENV variables{</em>}{color}
 * {color:#6600ff}{<em>}reaps dead processes{</em>}{color}</p>
 <p><a name="ModularizedArchitecture-DataStructure.pm(VCL::DataStructure)"></a></p>
-<h3 id="datastructurepm-vcldatastructure">DataStructure.pm (VCL::DataStructure)</h3>
-<p>{color:#6600ff}{<em>}Explain:</em>{color}
+<h3 id="datastructurepm-vcldatastructure">DataStructure.pm (VCL::DataStructure)<a class="headerlink" href="#datastructurepm-vcldatastructure" title="Permanent link">&para;</a></h3>
+<p>{color:#6600ff}{<em color="color">}Explain:</em>
 <em> {color:#6600ff}{<em>}abstracts database and data structure{</em>}{color}</em> {color:#6600ff}{<em>}aux modules shouldn't know about the DB or data
 structure{</em>}{color}
 <em> {color:#6600ff}{<em>}should be able to change db or data structure and still
 have aux modules work{</em>}{color}</em> {color:#6600ff}{<em>}uses "Inside Out" technique to accessing modules can't
 get to the underlying data{</em>}{color}
 <em> {color:#6600ff}{<em>}data is encapsulated, can only be accessed using
-accessor functions{</em>}{color}</em><em> {color:#6600ff}{<em>}encapsulation is good, explain what it is{</em>}{color}</em> {color:#6600ff}{<em>}usage: $self-&gt;data-&gt;get_image_name()</em>{color}
+accessor functions{</em>}{color}</em><em> {color:#6600ff}{<em>}encapsulation is good, explain what it is{</em>}{color}</em> {color:#6600ff}{<em color="color">}usage: $self-&gt;data-&gt;get_image_name()</em>
 <em> {color:#6600ff}{<em>}need to list methods somewhere (not here), there are
 tons of them{</em>}{color}</em> {color:#6600ff}{<em>}gets created by vcld when it finds a
 reservation{</em>}{color}
-<em> {color:#6600ff}{<em>}passed to&nbsp;module constructor{</em>}{color}</em> {color:#6600ff}{<em>}Module.pm sets up access via data()</em>{color}
+<em> {color:#6600ff}{<em>}passed to&nbsp;module constructor{</em>}{color}</em> {color:#6600ff}{<em color="color">}Module.pm sets up access via data()</em>
 * {color:#6600ff}{<em>}Result: any class that inherits from VCL::Module gets
 access{</em>}{color}</p>
 <p><a name="ModularizedArchitecture-utils.pm(VCL::utils)"></a></p>
-<h3 id="utilspm-vclutils">utils.pm (VCL::utils)</h3>
-<p>{color:#6600ff}{<em>}Explain:</em>{color}
-<em> {color:#6600ff}{<em>}contains several utility subs{</em>}{color}</em> {color:#6600ff}{<em>}doesn't inherit from Module.pm (might be a good idea to
-look into this)</em>{color}
+<h3 id="utilspm-vclutils">utils.pm (VCL::utils)<a class="headerlink" href="#utilspm-vclutils" title="Permanent link">&para;</a></h3>
+<p>{color:#6600ff}{<em color="color">}Explain:</em>
+<em> {color:#6600ff}{<em>}contains several utility subs{</em>}{color}</em> {color:#6600ff}{<em color="color">}doesn't inherit from Module.pm (might be a good idea to
+look into this)</em>
 <em> {color:#6600ff}{<em>}contains some legacy stuff - some subs will be removed
-and moved to OS or provisioing modules{</em>}{color}</em> {color:#6600ff}{<em>}should probably make a page describing utility subs
-such as notify, run_ssh_command...</em>{color}
+and moved to OS or provisioing modules{</em>}{color}</em> {color:#6600ff}{<em color="color">}should probably make a page describing utility subs
+such as notify, run_ssh_command...</em>
 *<em> {color:#6600ff}{<em>}This should really get sucked out of POD comments in
 the actual code{</em>}{color}</em> {color:#6600ff}{<em>}have to 'use VCL::utils' in order to use it{</em>}{color}</p>
 <p><a name="ModularizedArchitecture-Module.pm(VCL::Module)"></a></p>
-<h3 id="modulepm-vclmodule">Module.pm (VCL::Module)</h3>
+<h3 id="modulepm-vclmodule">Module.pm (VCL::Module)<a class="headerlink" href="#modulepm-vclmodule" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Provides a constructor for all derived objects to use
 <strong> Objects which inherit from VCL::Module do not need to implement their
@@ -200,7 +222,7 @@ subroutine implemented by Module.pm
  or $self-&gt;data-&gt;[set_something]</li>
 </ul>
 <p><a name="ModularizedArchitecture-State.pm(VCL::Module::State)"></a></p>
-<h3 id="statepm-vclmodulestate">State.pm (VCL::Module::State)</h3>
+<h3 id="statepm-vclmodulestate">State.pm (VCL::Module::State)<a class="headerlink" href="#statepm-vclmodulestate" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Supports the core VCL state modules such as new.pm, image.pm, reclaim.pm,
 and others</li>
@@ -213,7 +235,7 @@ a state object is created
 performs&nbsp;a consistent set of&nbsp;tasks when a reservation fails</li>
 </ul>
 <p><a name="ModularizedArchitecture-Provisioning.pm(VCL::Module::Provisioning)"></a></p>
-<h3 id="provisioningpm-vclmoduleprovisioning">Provisioning.pm (VCL::Module::Provisioning)</h3>
+<h3 id="provisioningpm-vclmoduleprovisioning">Provisioning.pm (VCL::Module::Provisioning)<a class="headerlink" href="#provisioningpm-vclmoduleprovisioning" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Provisioning engine modules should inherit from VCL::Module::Provisioning</li>
 <li>Modules which are a subclass of VCL::Module::Provisioning
@@ -223,7 +245,7 @@ inheritance</li>
 the OS object created for the reservation</li>
 </ul>
 <p><a name="ModularizedArchitecture-OS.pm(VCL::Module::OS)"></a></p>
-<h3 id="ospm-vclmoduleos">OS.pm (VCL::Module::OS)</h3>
+<h3 id="ospm-vclmoduleos">OS.pm (VCL::Module::OS)<a class="headerlink" href="#ospm-vclmoduleos" title="Permanent link">&para;</a></h3>
 <ul>
 <li>OS&nbsp;modules should inherit from VCL::Module::OS</li>
 <li>Modules which are a subclass of VCL::Module::OS also&nbsp;receive
@@ -234,51 +256,51 @@ object created for the reservation
 the computer if a reboot fails</li>
 </ul>
 <p><a name="ModularizedArchitecture-ImplementationDetails"></a></p>
-<h1 id="implementation-details">Implementation Details</h1>
+<h1 id="implementation-details">Implementation Details<a class="headerlink" href="#implementation-details" title="Permanent link">&para;</a></h1>
 <p><a name="ModularizedArchitecture-WorkingwithInheritance"></a></p>
-<h3 id="working-with-inheritance">Working with Inheritance</h3>
-<p>{color:#6600ff}{<em>}Explain:</em>{color}
-<em> {color:#6600ff}{<em>}code to set up inheritance{</em>}{color}</em> {color:#6600ff}{<em>}using $self-&gt;</em>{color}
-<em> {color:#6600ff}{<em>}when to use $self-&gt; (object method) and when to call a
-sub directly (class method)</em>{color}</em> {color:#6600ff}how to check if sub was called as an object method or
+<h3 id="working-with-inheritance">Working with Inheritance<a class="headerlink" href="#working-with-inheritance" title="Permanent link">&para;</a></h3>
+<p>{color:#6600ff}{<em color="color">}Explain:</em>
+<em> {color:#6600ff}{<em>}code to set up inheritance{</em>}{color}</em> {color:#6600ff}{<em color="color">}using $self-&gt;</em>
+<em> {color:#6600ff}{<em color="color">}when to use $self-&gt; (object method) and when to call a
+sub directly (class method)</em></em> {color:#6600ff}how to check if sub was called as an object method or
 not{color}</p>
 <p><a name="ModularizedArchitecture-IncludingNon-InheritedModules"></a></p>
-<h3 id="including-non-inherited-modules">Including Non-Inherited Modules</h3>
-<p>&nbsp;{color:#6600ff}{<em>}Explain:</em>{color}
-<em> {color:#6600ff}{<em>}use{</em>}{color} {color:#6600ff}<em><a href="file::bin.html">file::bin</a>
-</em>{color} {color:#6600ff}{<em>}to include the lib directory{</em>}{color}</em> {color:#6600ff}{<em>}use warnings, strict, diagnostics are a good
+<h3 id="including-non-inherited-modules">Including Non-Inherited Modules<a class="headerlink" href="#including-non-inherited-modules" title="Permanent link">&para;</a></h3>
+<p>&nbsp;{color:#6600ff}{<em color="color">}Explain:</em>
+<em> {color:#6600ff}{<em>}use{</em>}{color} {color:#6600ff}<em color="color"><a href="file::bin.html">file::bin</a>
+</em> {color:#6600ff}{<em>}to include the lib directory{</em>}{color}</em> {color:#6600ff}{<em>}use warnings, strict, diagnostics are a good
 practice{</em>}{color}
 * {color:#6600ff}{<em>}use 'VCL::utils' is the only VCL module you should need
 to include, all else should be handled by inheritance/objects{</em>}{color}</p>
 <p><a name="ModularizedArchitecture-ModuleInitialization"></a></p>
-<h3 id="module-initialization">Module Initialization</h3>
+<h3 id="module-initialization">Module Initialization<a class="headerlink" href="#module-initialization" title="Permanent link">&para;</a></h3>
 <p>{color:#6600ff}{<em>}Explain how modules can implement initialize() subs which
 are automatically called{</em>}{color}</p>
 <p><a name="ModularizedArchitecture-DatabaseConfigurationforModules"></a></p>
-<h3 id="database-configuration-for-modules">Database Configuration for Modules</h3>
+<h3 id="database-configuration-for-modules">Database Configuration for Modules<a class="headerlink" href="#database-configuration-for-modules" title="Permanent link">&para;</a></h3>
 <p>{color:#6600ff}{<em>}Explain module table, computer.moduleid,
 managementnode.predictivemoduleid{</em>}{color}</p>
 <p><a name="ModularizedArchitecture-Cross-ModuleAccess"></a></p>
-<h3 id="cross-module-access">Cross-Module Access</h3>
+<h3 id="cross-module-access">Cross-Module Access<a class="headerlink" href="#cross-module-access" title="Permanent link">&para;</a></h3>
 <p>{color:#6600ff}{<em>}Explain why some modules shouldn't have access to others,
 which is why Module.pm doesn't make os() and provisioner()
 available{</em>}{color}</p>
 <p><a name="ModularizedArchitecture-Required&OptionalModuleSubroutines"></a></p>
-<h3 id="required-optional-module-subroutines">Required &amp; Optional Module Subroutines</h3>
-<p>{color:#6600ff}{<em>}Explain:</em>{color}
+<h3 id="required-optional-module-subroutines">Required &amp; Optional Module Subroutines<a class="headerlink" href="#required-optional-module-subroutines" title="Permanent link">&para;</a></h3>
+<p>{color:#6600ff}{<em color="color">}Explain:</em>
 <em> {color:#6600ff}{<em>}Perl's can() function{</em>}{color}</em> {color:#6600ff}{<em>}core modules use can() to check if module
 implements&nbsp;a subroutine{</em>}{color}
 <em> {color:#6600ff}{<em>}some subs should be required such as OS::load(), most
 should not{</em>}{color}</em> {color:#6600ff}{<em>}if you can think of an exception why a sub wouldn't be
 needed it shouldn't be required{</em>}{color}</p>
 <p><a name="ModularizedArchitecture-PackageOrganization"></a></p>
-<h3 id="package-organization">Package Organization</h3>
-<p>{color:#6600ff}{<em>}Explain:</em>{color}
+<h3 id="package-organization">Package Organization<a class="headerlink" href="#package-organization" title="Permanent link">&para;</a></h3>
+<p>{color:#6600ff}{<em color="color">}Explain:</em>
 <em> {color:#6600ff}{<em>}how directories under lib/VCL should be
 organized{</em>}{color}</em> {color:#6600ff}{<em>}the 'package' line in the modules should match the
 location of the file{</em>}{color}
-*<em> {color:#6600ff}{<em>}Example: "package VCL::Module::OS::Windows" resides in
-"lib/VCL/Module/OS/Windows.pm"</em>{color}</em> {color:#6600ff}{<em>}some core modules don't follow this - the state modules
+*<em> {color:#6600ff}{<em color="color">}Example: "package VCL::Module::OS::Windows" resides in
+"lib/VCL/Module/OS/Windows.pm"</em></em> {color:#6600ff}{<em>}some core modules don't follow this - the state modules
 reside directly under lib/VCL, should eventually reside under
 lib/VCL/Module/State{</em>}{color}</p>
   </div>

Modified: websites/staging/vcl/trunk/content/confluence_export/network-layout.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/network-layout.html (original)
+++ websites/staging/vcl/trunk/content/confluence_export/network-layout.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,75 +83,7 @@
   
   <div id="content">
     <h1 class="title">Network Layout</h1>
-    <p>{excerpt}This page describes the basic network layout required in order for
-VCL to function. It also describes the recommended network layout if a
-blade chassis management module is used.{excerpt}</p>
-<p><a name="NetworkLayout-AtthesimplestformVCLusestwonetworks"></a></p>
-<h1 id="at-the-simplest-form-vcl-uses-two-networks">At the simplest form VCL uses two networks</h1>
-<ol>
-<li>Private - applies to provisioning modules where node is reloaded, esx,
-vmware, etc.</li>
-<li>
-<ul>
-<li>loading and boot strapping images</li>
-</ul>
-</li>
-<li>
-<ul>
-<li>managing reservations, adding/deleting accounts, controlling the OS on
-the node</li>
-</ul>
-</li>
-<li>
-<ul>
-<li>opens access ports on node for user requests on public network interface</li>
-</ul>
-</li>
-<li>
-<ul>
-<li>image creation</li>
-</ul>
-</li>
-<li>
-<ul>
-<li>DHCP serves fixed-addresses over this network to the eth0 adapter of the
-node</li>
-</ul>
-</li>
-<li>
-<ul>
-<li>DHCP is run on the management node - prerequisite</li>
-</ul>
-</li>
-<li>Public</li>
-<li>
-<ul>
-<li>user accessible</li>
-</ul>
-</li>
-<li>
-<ul>
-<li>VCL can either use dhcp(preferred) or statically assign addresses to the
-node on the public network</li>
-</ul>
-</li>
-</ol>
-<p>The diagram below shows the simple layout:
-{gliffy:name=Simple network layout|space=VCL|page=Network
-Layout|align=left|size=M}</p>
-<p><a name="NetworkLayout-BladeCenternetworklayout"></a></p>
-<h1 id="blade-center-network-layout">Blade Center network layout</h1>
-<p>The network using blade center is more involved by adding a 2nd private
-network.
-1. Private 1 - applies to provisioning modules, xCAT, vmware, etc.
-1. Private 2
-1. * allows management node to interact with blade center management module
-1. * provides scaling method for adding multiple blade center's
-1. Public - user access</p>
-<p>The diagram below shows the suggested network layout when using blade
-center.</p>
-<p>{gliffy:name=Blade Center network layout|space=VCL|page=Network
-Layout|align=left|size=M}</p>
+    
   </div>
   
   <div id="footer">

Modified: websites/staging/vcl/trunk/content/confluence_export/network-requirements.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/network-requirements.html (original)
+++ websites/staging/vcl/trunk/content/confluence_export/network-requirements.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">Network requirements</h1>
-    <p>For the current Apache VCL release (version 2.2.1), the system requires 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>For the current Apache VCL release (version 2.2.1), the system requires a
 minimum of two parallel networks, i.e.:
 (1) A private network, providing interconnectivity between the VCL
 management node and the deployed target server(s) (the latter with the

Modified: websites/staging/vcl/trunk/content/confluence_export/operating-system-module-inheritance.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/operating-system-module-inheritance.html (original)
+++ websites/staging/vcl/trunk/content/confluence_export/operating-system-module-inheritance.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,37 +83,7 @@
   
   <div id="content">
     <h1 class="title">Operating System Module Inheritance</h1>
-    <p>{gliffy:name=OS Modularization Transition|space=VCL|page=Operating System
-Module Inheritance|align=center|size=L}
-{gliffy:name=OS Module Inheritance|space=VCL|page=Operating System Module
-Inheritance|align=center|size=L}
-<em> Each row in the image table is configured with an OSid
-(image.OSid),&nbsp;this points to the id column in the OS table (OS.id)
-</em> Each&nbsp;row in the OS table is configured with a moduleid
-(OS.moduleid), this points to the id column in the module table (module.id)
-<em> The module table contains a column named perlpackage
-(module.perlpackage), this tells the backend VCL code which Perl module to
-load and use
-</em> The module.perlpackage value, the package statement in the Perl module
-file, and the directory structure of the Perl modules must all align
-<strong> module.perlpackage = VCL::Module::OS::Windows_mod::Version_5::XP_mod
-</strong> lib/VCL/Module/OS/Windows_mod/Version_5/XP_mod.pm:</p>
-<div class="codehilite"><pre><span class="n">package</span> <span class="n">VCL</span><span class="p">::</span><span class="n">Module</span><span class="p">::</span><span class="n">OS</span><span class="p">::</span><span class="n">Windows_mod</span><span class="p">::</span><span class="n">Version_5</span><span class="p">::</span><span class="n">XP_mod</span><span class="p">;</span>
-</pre></div>
-
-
-<ul>
-<li>Inheritance reduces redundant code</li>
-<li>Subroutines should reside as high up in the hierarchy as possible
-** This allows all objects which&nbsp;are instantiated as a&nbsp;child
-class to use the subroutine</li>
-<li>Child classes can implement subroutines with the same name as one
-implemented by a parent class
-** The child subroutine in the child class overrides the subroutine in the
-parent class
-{gliffy:name=Inheritance Example|space=VCL|page=Operating System Module
-Inheritance|align=center|size=L}</li>
-</ul>
+    
   </div>
   
   <div id="footer">

Modified: websites/staging/vcl/trunk/content/confluence_export/operating-system-module-interface-specification.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/operating-system-module-interface-specification.html (original)
+++ websites/staging/vcl/trunk/content/confluence_export/operating-system-module-interface-specification.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">Operating System Module Interface Specification</h1>
-    <p><a name="OperatingSystemModuleInterfaceSpecification-Background"></a></p>
-<h1 id="background">Background</h1>
+    <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="OperatingSystemModuleInterfaceSpecification-Background"></a></p>
+<h1 id="background">Background<a class="headerlink" href="#background" title="Permanent link">&para;</a></h1>
 <ul>
 <li>OS module objects are created by State.pm::initialize() when a new state
 object is created.</li>
@@ -84,7 +106,7 @@ safety.&nbsp;&nbsp; For example,&nbsp;a
 should not be able&nbsp;to call the OS module's shutdown subroutine.</li>
 </ul>
 <p><a name="OperatingSystemModuleInterfaceSpecification-OSModuleSubroutines"></a></p>
-<h1 id="os-module-subroutines">OS Module Subroutines</h1>
+<h1 id="os-module-subroutines">OS Module Subroutines<a class="headerlink" href="#os-module-subroutines" title="Permanent link">&para;</a></h1>
 <p>It is highly recommended that all OS modules implement the following
 subroutines.&nbsp; There may be many additional subroutines implemented
 within an OS module.&nbsp; These will not be called by any of the core VCL
@@ -100,7 +122,7 @@ modules nor any of the provisioning engi
 <p>&nbsp;&nbsp;</p>
 <hr />
 <p><a name="OperatingSystemModuleInterfaceSpecification-pre_capture{anchor:pre_capture}"></a></p>
-<h2 id="pre_capture-anchorpre_capture">pre_capture {anchor:pre_capture}</h2>
+<h2 anchor:pre_capture="anchor:pre_capture" id="pre_capture">pre_capture<a class="headerlink" href="#pre_capture" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Description
 <strong> Configures the&nbsp;OS so that it can be captured by a provisioning
@@ -150,12 +172,10 @@ resource.
 </em></strong> Resource was either shut down or left in the state specified by the
 end_state argument.
 <strong><em> Provisioning module can proceed to capture the image.
-** 0
-</em></strong> Resource OS could not be completely prepared to be captured.
-</strong>* Provisioning module should not proceed to capture the image.</li>
+</em>* 0</strong>* Resource OS could not be completely prepared to be captured.</strong>* Provisioning module should not proceed to capture the image.</li>
 </ul>
 <p><a name="OperatingSystemModuleInterfaceSpecification-post_load{anchor:post_load}"></a></p>
-<h2 id="post_load-anchorpost_load">post_load {anchor:post_load}</h2>
+<h2 anchor:post_load="anchor:post_load" id="post_load">post_load<a class="headerlink" href="#post_load" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Description
 <strong> Performs tasks to configure the OS&nbsp;after an image was loaded.
@@ -184,14 +204,12 @@ it is ready to be reserved.</li>
 <li>Return Values
 <strong> 1
 <strong><em> All OS post-load tasks were completed successfully
-** 0
-</em></strong> All OS post-load tasks could not be completed but the resource became
-accessible
-</strong> Undefined
+</em>* 0</strong>* All OS post-load tasks could not be completed but the resource became
+accessible</strong> Undefined
 *** Resource never became accessible</li>
 </ul>
 <p><a name="OperatingSystemModuleInterfaceSpecification-sanitize{anchor:sanitize}"></a></p>
-<h2 id="sanitize-anchorsanitize">sanitize {anchor:sanitize}</h2>
+<h2 anchor:sanitize="anchor:sanitize" id="sanitize">sanitize<a class="headerlink" href="#sanitize" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Description
 <strong> Reverts the changes made when preparing a resource for a particular
@@ -224,12 +242,10 @@ sanitize the resource after it was reser
 </em></strong> Resource is ready to be provisioned and reserved for another
 reservation
 <strong><em> Resource does not need&nbsp;to be reloaded
-** 0
-</em></strong> Sanitization could not be completed
-</strong>* Resource needs to be reloaded</li>
+</em>* 0</strong>* Sanitization could not be completed</strong>* Resource needs to be reloaded</li>
 </ul>
 <p><a name="OperatingSystemModuleInterfaceSpecification-reboot{anchor:reboot}"></a></p>
-<h2 id="reboot-anchorreboot">reboot {anchor:reboot}</h2>
+<h2 anchor:reboot="anchor:reboot" id="reboot">reboot<a class="headerlink" href="#reboot" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Description
 <strong> Performs a complete graceful reboot of the OS.
@@ -269,7 +285,7 @@ should be returned
 </strong>* Reboot could not be initiated</li>
 </ul>
 <p><a name="OperatingSystemModuleInterfaceSpecification-shutdown{anchor:shutdown}"></a></p>
-<h2 id="shutdown-anchorshutdown">shutdown {anchor:shutdown}</h2>
+<h2 anchor:shutdown="anchor:shutdown" id="shutdown">shutdown<a class="headerlink" href="#shutdown" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Description
 <strong> Performs a graceful shutdown of the OS.
@@ -298,16 +314,14 @@ down, 0 should be returned
 </em></strong> Possible Values:
 </em>*** Any positive integer</li>
 <li>Return Values
-** 1
+<em><em> 1
 <strong><em> Shudown completed successfully
-** 0
-</em></strong> Shutdown was initiated but computer never shut down
+</em>* 0</strong></em> Shutdown was initiated but computer never shut down
 <strong><em> Timeout was reached
-** Undefined
-</em></strong> Shutdown could not be initiated</li>
+</em>* Undefined</strong></em> Shutdown could not be initiated</li>
 </ul>
 <p><a name="OperatingSystemModuleInterfaceSpecification-get_current_image_name{anchor:get_current_image_name}"></a></p>
-<h2 id="get_current_image_name-anchorget_current_image_name">get_current_image_name {anchor:get_current_image_name}</h2>
+<h2 anchor:get_current_image_name="anchor:get_current_image_name" id="get_current_image_name">get_current_image_name<a class="headerlink" href="#get_current_image_name" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Description
 <strong> Returns the name of the current image that is loaded on the
@@ -333,14 +347,12 @@ string will be returned if the resource
 <li>Return Values
 <strong> String
 <strong><em> String contains a VCL image name
-** 0
-</em></strong> Computer is accessible but failed&nbsp;to determine the current loaded
-image
-</strong> Undefined
+</em>* 0</strong>* Computer is accessible but failed&nbsp;to determine the current loaded
+image</strong> Undefined
 *** Computer is not accessible</li>
 </ul>
 <p><a name="OperatingSystemModuleInterfaceSpecification-reserve&nbsp;{anchor:reserve}"></a></p>
-<h2 id="reservewzxhzdk22anchorreserve">reserve&nbsp;{anchor:reserve}</h2>
+<h2 id="reserveanchorreserve">reserve&nbsp;{anchor:reserve}<a class="headerlink" href="#reserveanchorreserve" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Description
 <strong> reserve() gets called by new.pm after a machine has been reloaded if the
@@ -377,13 +389,12 @@ presented to the user</li>
 ($os-&gt;reserve())
 </strong> No arguments</li>
 <li>Return Values
-** True (1)&nbsp;
+*<em> True (1)&nbsp;
 <strong><em> Computer has successfully been configured for a particular reservation
-** False (0 or undefined)&nbsp;
-</em></strong> Computer could not be configured for a particular reservation</li>
+</em>* False (0 or undefined)&nbsp;</strong></em> Computer could not be configured for a particular reservation</li>
 </ul>
 <p><a name="OperatingSystemModuleInterfaceSpecification-grant_access&nbsp;{anchor:grant_access}"></a></p>
-<h2 id="grant_accesswzxhzdk25anchorgrant_access">grant_access&nbsp;{anchor:grant_access}</h2>
+<h2 id="grant_accessanchorgrant_access">grant_access&nbsp;{anchor:grant_access}<a class="headerlink" href="#grant_accessanchorgrant_access" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Description
 <strong> grant_access()&nbsp;gets called by reserved.pm after the user has
@@ -405,11 +416,10 @@ the OS</li>
 ($os-&gt;get_current_image_name())
 </strong> No arguments</li>
 <li>Return Values
-** True (1)&nbsp;
+*<em> True (1)&nbsp;
 <strong><em> Computer was successfully configured to allow access for the
 reservation users
-** False (0 or undefined)
-</em></strong> Computer could not be configured to allow access for the reservation
+</em>* False (0 or undefined)</strong></em> Computer could not be configured to allow access for the reservation
 users</li>
 </ul>
   </div>

Modified: websites/staging/vcl/trunk/content/confluence_export/patch-to-remove-mcrypt-dependency.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/patch-to-remove-mcrypt-dependency.html (original)
+++ websites/staging/vcl/trunk/content/confluence_export/patch-to-remove-mcrypt-dependency.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">Patch to remove mcrypt dependency</h1>
-    <p>This page explains how to use a php package called <a href="http://phpseclib.sourceforge.net/">phpseclib</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>This page explains how to use a php package called <a href="http://phpseclib.sourceforge.net/">phpseclib</a>
  to remove the requirement of mcrypt. phpseclib will use mcrypt functions
 if it is installed but will use native php to implement the encryption if
 it is not installed.</p>
-<p>Here are the steps to remove the dependency:
+<p tip="tip">Here are the steps to remove the dependency:
 <em> Download <a href="http://sourceforge.net/projects/phpseclib/files/phpseclib0.2.2.zip/download">phpseclib</a>
  to /tmp (version 0.2.2 was used for testing)
 {tip}
@@ -101,8 +123,7 @@ wget {nolink:http://people.apache.org/~j
 {tip}
 * Apply the patch
 {tip}
-patch &lt; no_mcrypt.patch
-{tip}</p>
+patch &lt; no_mcrypt.patch</p>
   </div>
   
   <div id="footer">

Modified: websites/staging/vcl/trunk/content/confluence_export/pre-release-test-procedures.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/pre-release-test-procedures.html (original)
+++ websites/staging/vcl/trunk/content/confluence_export/pre-release-test-procedures.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,9 +83,20 @@
   
   <div id="content">
     <h1 class="title">Pre-release test procedures</h1>
-    <p>Recommended test cases for release candidates.</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>Recommended test cases for release candidates.</p>
 <p><a name="Pre-releasetestprocedures-Webfrontend"></a></p>
-<h3 id="web-frontend">Web frontend</h3>
+<h3 id="web-frontend">Web frontend<a class="headerlink" href="#web-frontend" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Block Allocations
 <strong> For each of these, test for weekly, monthly, and list
@@ -92,10 +114,10 @@ without an email address in the user tab
 the current time to check viewing the block status</li>
 </ul>
 <p><a name="Pre-releasetestprocedures-WebfrontendXMLRPCAPI"></a></p>
-<h3 id="web-frontend-xml-rpc-api">Web frontend XML RPC API</h3>
+<h3 id="web-frontend-xml-rpc-api">Web frontend XML RPC API<a class="headerlink" href="#web-frontend-xml-rpc-api" title="Permanent link">&para;</a></h3>
 <p>(placeholder)</p>
 <p><a name="Pre-releasetestprocedures-Backend-Managementnode"></a></p>
-<h3 id="backend-management-node">Backend - Management node</h3>
+<h3 id="backend-management-node">Backend - Management node<a class="headerlink" href="#backend-management-node" title="Permanent link">&para;</a></h3>
 <p>General range of tests for the back-end processing. The tests would more
 detailed depending on the provisioning module and OS module.</p>
 <ul>

Modified: websites/staging/vcl/trunk/content/confluence_export/provisioning-engine-module-interface-specification.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/provisioning-engine-module-interface-specification.html (original)
+++ websites/staging/vcl/trunk/content/confluence_export/provisioning-engine-module-interface-specification.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">Provisioning Engine Module Interface Specification</h1>
-    <p><a name="ProvisioningEngineModuleInterfaceSpecification-Background"></a></p>
-<h1 id="background">Background</h1>
+    <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="ProvisioningEngineModuleInterfaceSpecification-Background"></a></p>
+<h1 id="background">Background<a class="headerlink" href="#background" title="Permanent link">&para;</a></h1>
 <ul>
 <li>Provisioning module objects are created by State.pm::initialize() when a
 new state object is created.</li>
@@ -82,12 +104,12 @@ OS modules</li>
 <li>Provisioning module objects are not available within other types of
 modules for safety.</li>
 </ul>
-<p>{color:#6600ff}{<em>}Explain:</em>{color}
-<em> {color:#6600ff}{<em>}define what we mean by "provisioning system"</em>{color}</em> {color:#6600ff}{<em>}give examples of provisioning systems{</em>}{color}
+<p>{color:#6600ff}{<em color="color">}Explain:</em>
+<em> {color:#6600ff}{<em color="color">}define what we mean by "provisioning system"</em></em> {color:#6600ff}{<em>}give examples of provisioning systems{</em>}{color}
 <em> {color:#6600ff}{<em>}could be bare metal, virtual, differentiated,
 undifferentiated, a service, a special piece of hardware, eventually VCL
-could provision various types of resources{</em>}{color}</em> {color:#6600ff}{<em>}relationships among mgt nodes, computers, provisioning
-systems (such as computer is assigned 1 prov system at a time)</em>{color}
+could provision various types of resources{</em>}{color}</em> {color:#6600ff}{<em color="color">}relationships among mgt nodes, computers, provisioning
+systems (such as computer is assigned 1 prov system at a time)</em>
 <em> {color:#6600ff}{<em>}computer.provisioningid{</em>}{color}</em> {color:#6600ff}{<em>}provisioning table{</em>}{color}
 <em> {color:#6600ff}{<em>}future: management node to provisioning
 mapping{</em>}{color}</em> {color:#6600ff}{<em>}provisioning module implementation is responsible for
@@ -95,7 +117,7 @@ knowing which OS interactions are necess
 ** {color:#6600ff}{<em>}image.pm calls provisioner-&gt;capture, new.pm calls
 provisioner-&gt;load, it calls OS subs as necessary{</em>}{color}</p>
 <p><a name="ProvisioningEngineModuleInterfaceSpecification-ProvisioningModuleSubroutines"></a></p>
-<h1 id="provisioning-module-subroutines">Provisioning Module Subroutines</h1>
+<h1 id="provisioning-module-subroutines">Provisioning Module Subroutines<a class="headerlink" href="#provisioning-module-subroutines" title="Permanent link">&para;</a></h1>
 <p>It is highly recommended that all&nbsp;provisioning modules implement the
 following subroutines.&nbsp; There may be many additional subroutines
 implemented within a provisioning module.&nbsp; These will not be called by
@@ -110,7 +132,7 @@ any of the core VCL modules.
 </em> <a href="#get_image_size.html">#get_image_size</a></p>
 <hr />
 <p><a name="ProvisioningEngineModuleInterfaceSpecification-node_status{anchor:node_status}"></a></p>
-<h2 id="node_status-anchornode_status">node_status {anchor:node_status}</h2>
+<h2 anchor:node_status="anchor:node_status" id="node_status">node_status<a class="headerlink" href="#node_status" title="Permanent link">&para;</a></h2>
 <ul>
 <li>
 <p>Description
@@ -134,7 +156,7 @@ hashref: reference to hash with keys/val
 <p>** The status key/value tells the vcl system the node is ready or needs to
 be reloaded.</p>
 <p><a name="ProvisioningEngineModuleInterfaceSpecification-capture{anchor:capture}"></a></p>
-<h2 id="capture-anchorcapture">capture {anchor:capture}</h2>
+<h2 anchor:capture="anchor:capture" id="capture">capture<a class="headerlink" href="#capture" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Description
 <strong> A provisioning module's capture() subroutine saves the current state of
@@ -175,7 +197,7 @@ available to be provisioned.
 </em></strong> An administrator needs to investigate the problem.</li>
 </ul>
 <p><a name="ProvisioningEngineModuleInterfaceSpecification-load{anchor:load}"></a></p>
-<h2 id="load-anchorload">load {anchor:load}</h2>
+<h2 anchor:load="anchor:load" id="load">load<a class="headerlink" href="#load" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Description
 <strong> A provisioning module's load() subroutine is responsible for
@@ -195,13 +217,11 @@ provisioning&nbsp;object ($provisioner-&
 <li>Return Values
 <strong> 1
 <strong><em> ...
-** 0
-</em></strong> ...
-</strong> Undefined
+</em>* 0</strong>* ...</strong> Undefined
 *** ...</li>
 </ul>
 <p><a name="ProvisioningEngineModuleInterfaceSpecification-power_off{anchor:power_off}"></a></p>
-<h2 id="power_off-anchorpower_off">power_off {anchor:power_off}</h2>
+<h2 anchor:power_off="anchor:power_off" id="power_off">power_off<a class="headerlink" href="#power_off" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Description
 ** A provisioning module's power_off() subroutine is responsible for
@@ -219,13 +239,11 @@ provisioning&nbsp;object ($provisioner-&
 <li>Return Values
 <strong> 1
 <strong><em> ...
-** 0
-</em></strong> ...
-</strong> Undefined
+</em>* 0</strong>* ...</strong> Undefined
 *** ...</li>
 </ul>
 <p><a name="ProvisioningEngineModuleInterfaceSpecification-power_on{anchor:power_on}"></a></p>
-<h2 id="power_on-anchorpower_on">power_on {anchor:power_on}</h2>
+<h2 anchor:power_on="anchor:power_on" id="power_on">power_on<a class="headerlink" href="#power_on" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Description
 ** A provisioning module's power_on() subroutine is responsible for
@@ -243,13 +261,11 @@ provisioning&nbsp;object ($provisioner-&
 <li>Return Values
 <strong> 1
 <strong><em> ...
-** 0
-</em></strong> ...
-</strong> Undefined
+</em>* 0</strong>* ...</strong> Undefined
 *** ...</li>
 </ul>
 <p><a name="ProvisioningEngineModuleInterfaceSpecification-get_current_image{anchor:get_current_image}"></a></p>
-<h2 id="get_current_image-anchorget_current_image">get_current_image {anchor:get_current_image}</h2>
+<h2 anchor:get_current_image="anchor:get_current_image" id="get_current_image">get_current_image<a class="headerlink" href="#get_current_image" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Description
 ** A provisioning module's get_current_image() subroutine is responsible
@@ -267,13 +283,11 @@ provisioning&nbsp;object ($provisioner-&
 <li>Return Values
 <strong> 1
 <strong><em> ...
-** 0
-</em></strong> ...
-</strong> Undefined
+</em>* 0</strong>* ...</strong> Undefined
 *** ...</li>
 </ul>
 <p><a name="ProvisioningEngineModuleInterfaceSpecification-get_image_size&nbsp;{anchor:get_image_size}"></a></p>
-<h2 id="get_image_sizewzxhzdk21anchorget_image_size">get_image_size&nbsp;{anchor:get_image_size}</h2>
+<h2 id="get_image_sizeanchorget_image_size">get_image_size&nbsp;{anchor:get_image_size}<a class="headerlink" href="#get_image_sizeanchorget_image_size" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Description
 ** A provisioning module's get_image_size() subroutine is responsible for
@@ -291,9 +305,7 @@ provisioning&nbsp;object ($provisioner-&
 <li>Return Values
 <strong> 1
 <strong><em> ...
-** 0
-</em></strong> ...
-</strong> Undefined
+</em>* 0</strong>* ...</strong> Undefined
 *** ...</li>
 </ul>
   </div>

Modified: websites/staging/vcl/trunk/content/confluence_export/security-features.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/security-features.html (original)
+++ websites/staging/vcl/trunk/content/confluence_export/security-features.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">Security Features</h1>
-    <p>Baseline VCL security for the end-user environments:
+    <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>Baseline VCL security for the end-user environments:
 <em> The VCL environments are not generally shared. One user to one machine.
 </em> After an environment is used - the machine is reloaded(sanitized) with
 the same or another golden environment. All residual data is destroyed or

Modified: websites/staging/vcl/trunk/content/confluence_export/states.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/states.html (original)
+++ websites/staging/vcl/trunk/content/confluence_export/states.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">States</h1>
-    <p><a name="States-RequestStates"></a></p>
-<h2 id="request-states">Request States</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="States-RequestStates"></a></p>
+<h2 id="request-states">Request States<a class="headerlink" href="#request-states" title="Permanent link">&para;</a></h2>
 <table>
 <tr><th> Request State </th><th> Processed by Module </th><th> Description </th></tr>
 <tr><td> new </td><td> new.pm </td><td> * Normal reservation initiated by user

Modified: websites/staging/vcl/trunk/content/confluence_export/storage-management.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/storage-management.html (original)
+++ websites/staging/vcl/trunk/content/confluence_export/storage-management.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">Storage Management</h1>
-    <p>Something VCL has been lacking is automated management of storage, both on
+    <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>Something VCL has been lacking is automated management of storage, both on
 the system side and on the user side. This is a list of areas that should
 be addressed when designing storage management and automation:</p>
 <ul>

Modified: websites/staging/vcl/trunk/content/confluence_export/sysprep-fails-because-of-unsigned-storage-drivers.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/sysprep-fails-because-of-unsigned-storage-drivers.html (original)
+++ websites/staging/vcl/trunk/content/confluence_export/sysprep-fails-because-of-unsigned-storage-drivers.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">Sysprep Fails Because of Unsigned Storage Drivers</h1>
-    <p>Sysprep may fail if mass storage drivers are not signed.&nbsp; This problem
+    <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>Sysprep may fail if mass storage drivers are not signed.&nbsp; This problem
 occurs even if the sysprep.inf file is configured with
 DriverSigningPolicy=Ignore.&nbsp; This is a known problem with some
 versions of LSI SAS drivers (1.30.02.00) used on IBM blades.&nbsp; The
@@ -81,7 +103,7 @@ driver available from&nbsp;LSI's website
 correctly signed. &nbsp;It can be downloaded from:
 <a href="http://www-947.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-5073138&amp;brandind=5000020">(Critical update) IBM and LSI Basic or Integrated RAID SAS driver v1.30.02.00 for Microsoft Windows Server 2008 and Windows Server 2003 - IBM BladeCenter and System x</a></p>
 <p><a name="SysprepFailsBecauseofUnsignedStorageDrivers-HowtoTellifthisProblemOccurred&nbsp;"></a></p>
-<h4 id="how-to-tell-if-this-problem-occurredwzxhzdk10">How to Tell if this Problem Occurred&nbsp;</h4>
+<h4 id="how-to-tell-if-this-problem-occurred">How to Tell if this Problem Occurred&nbsp;<a class="headerlink" href="#how-to-tell-if-this-problem-occurred" title="Permanent link">&para;</a></h4>
 <p>Open C:\Windows\setupapi.log.&nbsp; Look for lines containing
 "{color:#ff0000}{<em>}An unsigned or incorrectly signed file{</em>}{color}":&nbsp;
 {panel}
@@ -105,14 +127,14 @@ Corporation"; Section name: "SYMMPI_Inst
 #I060 Set selected driver.
 #I058 Selected best compatible driver.
 #-124 Doing copy-only install of "ROOT\SYSPREP_TEMPORARY\0000".
-{color:#ff0000}<em>#E358 An unsigned or incorrectly signed file
+{color:#ff0000}<em color="color">#E358 An unsigned or incorrectly signed file
 "c:\cygwin\home\root\vcl\drivers\storage\lsi-sas\mpixp32.cat" for driver
 "LSI Adapter, 2Gb FC, models 44929, G2 with 929" blocked (server install).
 Error 0x800b0003: The form specified for the subject is not one supported
-or known by the specified trust provider.</em>{color}
+or known by the specified trust provider.</em>
 #W187 Install failed, attempting to restore original files.</p>
 <p><a name="SysprepFailsBecauseofUnsignedStorageDrivers-HowtoResolvethisProblem"></a></p>
-<h4 id="how-to-resolve-this-problem">How to Resolve this Problem</h4>
+<h4 id="how-to-resolve-this-problem">How to Resolve this Problem<a class="headerlink" href="#how-to-resolve-this-problem" title="Permanent link">&para;</a></h4>
 <p>The preferred method is to obtain a signed driver.&nbsp; If a signed driver
 cannot be located, try configuring the local computer policy to allow
 unsigned drivers:

Modified: websites/staging/vcl/trunk/content/confluence_export/terms.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/terms.html (original)
+++ websites/staging/vcl/trunk/content/confluence_export/terms.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">Terms</h1>
-    <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>backend</li>
 <li>block request</li>
 <li>cluster reservation</li>



Mime
View raw message