vcl-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r845507 [14/17] - in /websites/staging/vcl/trunk/content: ./ confluence_export/
Date Tue, 08 Jan 2013 16:38:17 GMT
Added: websites/staging/vcl/trunk/content/confluence_export/vcl-2.2.1-web-code-installation.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/vcl-2.2.1-web-code-installation.html (added)
+++ websites/staging/vcl/trunk/content/confluence_export/vcl-2.2.1-web-code-installation.html Tue Jan  8 16:38:15 2013
@@ -0,0 +1,400 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE- 2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+
+  <link href="/css/vcl.css" rel="stylesheet" type="text/css">
+  <link href="/css/code.css" rel="stylesheet" type="text/css">
+  <title>Apache VCL - VCL 2.2.1 Web Code Installation</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+  <div id="sitetitle">
+    <table width="100%" border="0" cellspacing="0" cellpadding="5">
+      <tr>
+         <td><a href="/index.html"><img src="/img/vcl-logo.png" height="100" align="left" alt="Apache VCL logo"></a></td>
+         <td><a href="http://www.apache.org"><img src="/img/asf-logo.png" align="right" alt="Apache Software Foundation logo"></a></td>
+      </tr>
+    </table>
+  </div>
+
+  <div id="navigation"> 
+  <ul>
+<li>Information<ul>
+<li><a href="/info/about.html">What is VCL?</a></li>
+<li><a href="/info/features.html">Features</a></li>
+<li><a href="/info/architecture.html">Architecture</a></li>
+<li><a href="/info/use-cases.html">Use Cases</a></li>
+<li><a href="/downloads/download.cgi">Download</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0.html">License</a></li>
+<li><a href="/info/faq.html">FAQ</a></li>
+</ul>
+</li>
+<li><a href="/docs/index.html">Documentation</a><ul>
+<li><a href="/docs/using-vcl.html">Using VCL</a></li>
+<li><a href="/docs/image-creation.html">Image Creation</a></li>
+<li><a href="/docs/administration.html">Administration</a></li>
+<li><a href="/docs/installation.html">Installation</a></li>
+<li><a href="/docs/deployment-planning.html">Deployment Planning</a></li>
+</ul>
+</li>
+<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/index.html#how-do-i-join-the-project">How can I Join</a></li>
+<li><a href="/comm/wiki.html">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>
+<li><a href="/dev/roadmap.html">Roadmap</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li><a href="http://www.apache.org">Apache Software Foundation</a><ul>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+</ul>
+</li>
+</ul>
+  </div>
+  
+  <div id="content">
+    <h1 class="title">VCL 2.2.1 Web Code Installation</h1>
+    <p>{excerpt:hidden=true}
+How to install and configure the frontend VCL web code. It also describes
+how to add local accounts to the VCL database, configure LDAP
+authentication, and set the timezone correctly.{excerpt}</p>
+<p><a name="VCL2.2.1WebCodeInstallation-Install&ConfiguretheWebComponents"></a></p>
+<h1 id="install-configure-the-web-components">Install &amp; Configure the Web Components</h1>
+<p><a name="VCL2.2.1WebCodeInstallation-*Prerequisites*"></a></p>
+<h2 id="prerequisites"><em>Prerequisites</em></h2>
+<p>The following instructions assume these tasks have previously been
+completed:
+<em> <a href="download.html">Apache VCL 2.2.1 has been downloaded</a>
+</em> <a href="vcl:vcl-2.2.1-database-installation.html">VCL database has been installed and configured</a></p>
+<p><a name="VCL2.2.1WebCodeInstallation-WebServer:"></a></p>
+<h4 id="web-server">Web Server:</h4>
+<ul>
+<li>Apache HTTP Server v1.3 or v2.x with SSL enabled</li>
+<li>PHP 5.0 or later</li>
+</ul>
+<p>{info}The VCL web frontend may run under other web server platforms capable
+of running PHP code, but has only been tested to work with Apache HTTP
+Server.{info}</p>
+<p><a name="VCL2.2.1WebCodeInstallation-RequiredLinuxPackages:"></a></p>
+<h4 id="required-linux-packages">Required Linux Packages:</h4>
+<ul>
+<li><em>httpd</em> - Apache HTTP Server</li>
+<li><em>mod_ssl</em> - SSL/TLS module for the Apache HTTP server</li>
+<li><em>php</em> - The PHP HTML-embedded scripting language</li>
+<li><em>libmcrypt</em> - Encryption algorithms library (this requirement can be
+removed with a <a href="vcl:patch-to-remove-mcrypt-dependency.html">patch</a>
+)</li>
+</ul>
+<p><a name="VCL2.2.1WebCodeInstallation-RequiredPHPModules:"></a></p>
+<h4 id="required-php-modules">Required PHP Modules:</h4>
+<p>(Some of these may already be included with your PHP distribution)
+<em> </em>php-gd<em>
+</em> <em>php-json</em> (required if your PHP version is 5.2 or later)
+<em> </em>php-mcrypt<em> (this requirement can be removed with a <a href="vcl:patch-to-remove-mcrypt-dependency.html">patch</a>
+)
+</em> <em>php-mysql</em>
+<em> </em>php-openssl<em>
+</em> <em>php-sysvsem</em>
+<em> </em>php-xml<em>
+</em> <em>php-xmlrpc</em>
+<em> </em>php-ldap* (if you will be using LDAP authentication)</p>
+<ol>
+<li>
+<h1 id="if-your-web-server-is-running-a-red-hat-based-os-the-required">If your web server is running a Red Hat-based OS, the required</h1>
+components&nbsp;can be installed with:
+{tip}
+yum install httpd mod_ssl php php-gd php-mcrypt php-mysql php-xml
+php-xmlrpc php-ldap -y
+{tip}</li>
+<li>
+<h1 id="if-you-will-be-using-a-self-signed-certificate-for-ssl-this-is-a-great-howto">* If you will be using a self-signed certificate for SSL, <a href="http://wiki.centos.org/HowTos/Https">this is a great HOWTO </a></h1>
+explaining how to set it up on CentOS</li>
+<li>
+<h1 id="it-is-useful-to-configure-the-server-to-be-able-to-send-debugging">* It is useful to configure the server to be able to send debugging</h1>
+emails</li>
+<li>
+<h1 id="configure-the-web-server-daemon-httpd-to-start-automatically">Configure the web server daemon (httpd) to start automatically:</h1>
+{tip}
+/sbin/chkconfig --level 345 httpd on
+{tip}</li>
+<li>
+<h1 id="start-the-web-server-daemon">Start the web server daemon:</h1>
+{tip}
+/sbin/service httpd start
+{tip}</li>
+<li>
+<h1 id="if-selinux-is-enabled-run-the-following-command-to-allow-the-web-server">If SELinux is enabled, run the following command to allow the web server</h1>
+to connect to the database:
+{tip}
+/usr/sbin/setsebool -P httpd_can_network_connect=1
+{tip}</li>
+<li>
+<h1 id="if-the-iptables-firewall-is-being-used-port-80-and-443-should-be-opened">If the iptables firewall is being used, port 80 and 443 should be opened</h1>
+up:
+{tip}vi /etc/sysconfig/iptables{tip}<p>-A RH-Firewall-1-INPUT -m state --state NEW -p tcp --dport 80 -j ACCEPT
+-A RH-Firewall-1-INPUT -m state --state NEW -p tcp --dport 443 -j ACCEPT
+service iptables restart</p>
+</li>
+<li>
+<p>h2. Install the&nbsp;VCL Frontend Web Code</p>
+</li>
+<li>
+<h1 id="if-you-have-not-already-done-so-download-and-extract-the-source-files">If you have not already done so, download and extract the source files</h1>
+on the web server:
+{tip}
+wget
+{nolink:http://www.apache.org/dist/incubator/vcl/apache-VCL-2.2.1-incubating.tar.bz2}
+tar -jxvf apache-VCL-2.2.1-incubating.tar.bz2
+{tip}</li>
+<li>
+<h1 id="copy-the-web-directory-to-a-location-under-the-web-root-of-your-web">Copy the <em>web</em> directory to a location under the web root of your web</h1>
+server and navigate to the&nbsp;destination&nbsp;<em>.ht-inc</em> subdirectory:
+{tip}
+cp -r apache-VCL-2.2.1-incubating/web/ /var/www/html/vcl
+cd /var/www/html/vcl/.ht-inc
+{tip}</li>
+<li>
+<h1 id="apply-patch-to-fix-editing-reservations">apply patch to fix editing reservations</h1>
+{tip}
+wget <a href="https://issues.apache.org/jira/secure/attachment/12477101/utils_virtual_undefined.patch">https://issues.apache.org/jira/secure/attachment/12477101/utils_virtual_undefined.patch</a>
+patch &lt; utils_virtual_undefined.patch
+{tip}</li>
+<li>
+<h1 id="apply-patch-to-fix-processing-of-block-allocations">apply patch to fix processing of block allocations</h1>
+{tip}
+wget <a href="https://issues.apache.org/jira/secure/attachment/12485328/vmhostcheck_fix.patch">https://issues.apache.org/jira/secure/attachment/12485328/vmhostcheck_fix.patch</a>
+patch &lt; vmhostcheck_fix.patch
+{tip}</li>
+<li>
+<h1 id="copy-secrets-defaultphp-to-secretsphp">Copy <em>secrets-default.php</em> to <em>secrets.php</em>:</h1>
+{tip}
+cp secrets-default.php secrets.php
+{tip}</li>
+<li>
+<h1 id="edit-the-secretsphp-file">Edit the <em>secrets.php</em> file:</h1>
+{tip}
+vi secrets.php
+{tip}</li>
+<li>
+<h1 id="set-the-following-variables-to-match-your-database-configuration">* Set the following variables to match your database configuration:</h1>
+</li>
+<li>
+<h1 id="vclhost"><em><em> </em>$vclhost</em></h1>
+</li>
+<li>
+<h1 id="vcldb"><em><em> </em>$vcldb</em></h1>
+</li>
+<li>
+<h1 id="vclusername"><em><em> </em>$vclusername</em></h1>
+</li>
+<li>
+<h1 id="vclpassword"><em><em> </em>$vclpassword</em></h1>
+</li>
+<li>
+<h1 id="create-random-passwords-for-the-following-variables">* Create random passwords for the following variables:</h1>
+</li>
+<li>
+<h1 id="mcryptkey"><em><em> </em>$mcryptkey</em></h1>
+</li>
+<li>
+<h1 id="mcryptiv-must-be-8-hex-characters"><em><em> </em>$mcryptiv</em> (must be 8 hex characters)</h1>
+</li>
+<li>
+<h1 id="pemkey"><em><em> </em>$pemkey</em></h1>
+</li>
+<li>
+<h1 id="save-the-secretsphp-file">* Save the secrets.php file</h1>
+</li>
+<li>
+<h1 id="run-the-genkeysshwzxhzdk27scriptwzxhzdk28-enter-the-value-you-set-for">Run the <em>genkeys.sh</em>&nbsp;script.&nbsp; Enter the value you set for</h1>
+<em>$pemkey</em> in secrets.php as the passphrase (3 times, copy/paste is a good
+idea)
+{tip}
+./genkeys.sh
+{tip}</li>
+<li>
+<h1 id="copy-conf-defaultphp-to-confphp">Copy <em>conf-default.php</em> to <em>conf.php</em>:</h1>
+{tip}
+cp conf-default.php conf.php
+{tip}</li>
+<li>
+<h1 id="modify-confphp-to-match-your-site">Modify <em>conf.php</em> to match your site</h1>
+{tip}vi conf.php{tip}
+{info}Modify every entry under <em>"Things in this section must be modified"</em>.
+Descriptions and pointers for each value are included within
+conf.php.{info}</li>
+<li>
+<h1 id="cookiedomain-45-set-this-to-the-domain-name-your-web-server-is-using">* <em>COOKIEDOMAIN</em> - set this to the domain name your web server is using</h1>
+or leave it blank if you are only accessing the web server by its IP
+address</li>
+<li>
+<h1 id="set-the-owner-of-the-ht-incmaintenance-directory-to-the-web-server">Set the owner of the <em>.ht-inc/maintenance</em> directory to the web server</h1>
+user (normally 'apache'):
+{tip}chown apache maintenance{tip}</li>
+<li>
+<h1 id="optionally-you-can-install-phpseclib-and-apply-a-patch">Optionally, you can <a href="vcl:patch-to-remove-mcrypt-dependency.html">install phpseclib and apply a patch</a></h1>
+ to remove the requirement of having mcrypt installed</li>
+<li>
+<h1 id="open-the-testsetupphp-page-in-a-web-browser">Open the <em>testsetup.php</em> page in a web browser:</h1>
+</li>
+<li>
+<h1 id="if-you-set-up-your-site-to-be-httpsmyserverorgvcl">* If you set up your site to be <a href="https://my.server.org/vcl/">https://my.server.org/vcl/</a></h1>
+ open [https://my.server.org/vcl/testsetup.php]</li>
+<li>
+<h1 id="debug-any-issues-reported-by-testsetupphp">* Debug any issues reported by testsetup.php</h1>
+</li>
+<li>h2. Log In to the VCL Website</li>
+<li>
+<h1 id="open-the-indexphp-page-in-your-browser-httpsmyserverorgvclindexphp">Open the index.php page in your browser (<a href="https://my.server.org/vcl/index.php">https://my.server.org/vcl/index.php</a></h1>
+)</li>
+<li>
+<h1 id="select-local-account">* Select <em>Local Account</em></h1>
+</li>
+<li>
+<h1 id="username-admin">* Username: <em>admin</em></h1>
+</li>
+<li>
+<h1 id="password-adminvc1passw0rd">* Password: <em>adminVc1passw0rd</em></h1>
+</li>
+<li>
+<h1 id="set-the-admin-user-password-optional">Set the admin user password (optional):</h1>
+</li>
+<li>
+<h2 id="click-user-preferences">Click <em>User Preferences</em></h2>
+</li>
+<li>
+<h2 id="enter-the-current-password-adminvc1passw0rd">Enter the current password: <em>adminVc1passw0rd</em></h2>
+</li>
+<li>
+<h2 id="enter-a-new-password">Enter a new password</h2>
+</li>
+<li>
+<h2 id="click-submit-changes">Click <em>Submit Changes</em></h2>
+</li>
+<li>h2. Add a Management Node to the Database</li>
+<li>
+<h1 id="click-the-management-nodes-link">Click the <em>Management Nodes</em> link</h1>
+</li>
+<li>
+<h2 id="click-add">Click <em>Add</em></h2>
+</li>
+<li>
+<h2 id="fill-in-thesewzxhzdk26required-fields">Fill in these&nbsp;required fields:</h2>
+</li>
+<li>
+<h2 id="hostname-the-name-ofwzxhzdk20the-management-node-server-this-value">* <em>Hostname -</em> The name of&nbsp;the management node server. This value</h2>
+doesn't necessarily need to be&nbsp;a name registered in DNS nor does it
+need to be the value displayed by the Linux&nbsp;<em>hostname</em> command. For
+example, if you are installing all of the VCL components on the same
+machine you can set this value to <em>localhost</em>.
+{info}Take note of the value you enter for Hostname.&nbsp;In a later step performed during the&nbsp;<a href="vcl:vcl-2.2.1-management-node-installation.html">management node installation</a>
+, the value enter for Hostname must match the value you enter&nbsp;for FQDN
+in the /etc/vcl/vcld.conf file on the management node.{info}</li>
+<li>
+<h2 id="ip-address-45-the-public-ip-address-of-the-management-node">* <em>IP address</em> - the public IP address of the management node</h2>
+</li>
+<li>
+<h2 id="sysadmin-email-address-45-error-emails-will-be-sent-to-this-address">* <em>SysAdmin Email Address</em> - error emails will be sent to this address</h2>
+</li>
+<li>
+<h2 id="install-path-45-this-is-parent-directory-under-which-image-files">* <em>Install Path</em> - this is parent directory under which image files</h2>
+will be stored - only required if doing bare metal installs or using VMWare
+with local disks</li>
+<li>
+<h2 id="end-node-ssh-identity-key-files-45-enter-etcvclvclkey-unless-you">* <em>End Node SSH Identity Key Files</em> - enter /etc/vcl/vcl.key unless you</h2>
+know you are using a different SSH identity key file</li>
+<li>
+<h2 id="optionally-fill-in-these-fields">Optionally, fill in these fields:</h2>
+</li>
+<li>
+<h2 id="address-for-shadow-emails-45-end-users-are-sent-various-emails-about">* <em>Address for Shadow Emails</em> - End users are sent various emails about</h2>
+the status of their reservations. If this field is configured, copies of
+all of those emails will be sent to this address.</li>
+<li>
+<h2 id="public-nic-configuration-method-45-this-defaults-to-dynamic-dhcp-">* <em>Public NIC configuration method</em> - this defaults to Dynamic DHCP -</h2>
+if DHCP is not available for the public interface of your nodes, you can
+set this to Static. Then, the IP configuration on the nodes will be
+manually set using Public Netmask, Public Gateway, Public DNS Server, and
+the IP address set for the computer under Manage Computers</li>
+<li>
+<h1 id="click-confirm-management-node">Click <em>Confirm Management Node</em></h1>
+</li>
+<li>
+<h1 id="click-submit">Click <em>Submit</em></h1>
+</li>
+<li>
+<h1 id="click-the-management-nodes-link_1">Click the <em>Management Nodes</em> link</h1>
+</li>
+<li>
+<h2 id="select-edit-management-node-grouping">Select <em>Edit Management Node Grouping</em></h2>
+</li>
+<li>
+<h2 id="click-submit_1">Click <em>Submit</em></h2>
+</li>
+<li>
+<h2 id="select-the-checkbox-for-your-management-node">Select the checkbox for your management node</h2>
+</li>
+<li>
+<h2 id="click-submit-changes_1">Click <em>Submit Changes</em></h2>
+</li>
+</ol>
+<p><a href="vcl-2.2.1---further-steps-if-using-vmware.html">Further steps if using only VMWare</a></p>
+<p><a href="vcl-2.2.1---further-steps-if-using-xcat.html">Further steps if using xCAT</a></p>
+<p><a name="VCL2.2.1WebCodeInstallation-*Adding&nbsp;LocalVCLAccounts*"></a></p>
+<h2 id="addingwzxhzdk12local-vcl-accounts"><em>Adding&nbsp;Local VCL Accounts</em></h2>
+<p>Local VCL accounts are&nbsp;contained within the VCL database.&nbsp; The
+<em>admin</em> account&nbsp;is a local VCL account.&nbsp; Additional local
+accounts can be added via the backend management node code. After you have
+finished the backend management node installation, run:
+{tip}
+vcld -setup
+{tip}
+1. Select <em>VCL Base Module</em>
+1. Select <em>Add Local VCL User Account</em>
+1. Enter the requested information</p>
+<p><a name="VCL2.2.1WebCodeInstallation-AddingLDAPAuthentication"></a></p>
+<h2 id="adding-ldap-authentication">Adding LDAP Authentication</h2>
+<p>Follow the instruction on the&nbsp;<a href="vcl-2.2.1---adding-ldap-authentication.html">Adding LDAP Authentication</a>
+ page.</p>
+<hr />
+<p>Previous Step: <a href="vcl:vcl-2.2.1-database-installation.html">VCL:VCL 2.2.1 Database Installation</a>
+Next Step: <a href="vcl:vcl-2.2.1-management-node-installation.html">VCL:VCL 2.2.1 Management Node Installation</a></p>
+  </div>
+  
+  <div id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2012 The Apache Software Foundation, Licensed under 
+        the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+        <br />
+        Apache and the Apache feather logo are trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>
+  
+</body>
+</html>

Added: websites/staging/vcl/trunk/content/confluence_export/vcl-2.2.1.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/vcl-2.2.1.html (added)
+++ websites/staging/vcl/trunk/content/confluence_export/vcl-2.2.1.html Tue Jan  8 16:38:15 2013
@@ -0,0 +1,332 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE- 2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+
+  <link href="/css/vcl.css" rel="stylesheet" type="text/css">
+  <link href="/css/code.css" rel="stylesheet" type="text/css">
+  <title>Apache VCL - VCL 2.2.1</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+  <div id="sitetitle">
+    <table width="100%" border="0" cellspacing="0" cellpadding="5">
+      <tr>
+         <td><a href="/index.html"><img src="/img/vcl-logo.png" height="100" align="left" alt="Apache VCL logo"></a></td>
+         <td><a href="http://www.apache.org"><img src="/img/asf-logo.png" align="right" alt="Apache Software Foundation logo"></a></td>
+      </tr>
+    </table>
+  </div>
+
+  <div id="navigation"> 
+  <ul>
+<li>Information<ul>
+<li><a href="/info/about.html">What is VCL?</a></li>
+<li><a href="/info/features.html">Features</a></li>
+<li><a href="/info/architecture.html">Architecture</a></li>
+<li><a href="/info/use-cases.html">Use Cases</a></li>
+<li><a href="/downloads/download.cgi">Download</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0.html">License</a></li>
+<li><a href="/info/faq.html">FAQ</a></li>
+</ul>
+</li>
+<li><a href="/docs/index.html">Documentation</a><ul>
+<li><a href="/docs/using-vcl.html">Using VCL</a></li>
+<li><a href="/docs/image-creation.html">Image Creation</a></li>
+<li><a href="/docs/administration.html">Administration</a></li>
+<li><a href="/docs/installation.html">Installation</a></li>
+<li><a href="/docs/deployment-planning.html">Deployment Planning</a></li>
+</ul>
+</li>
+<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/index.html#how-do-i-join-the-project">How can I Join</a></li>
+<li><a href="/comm/wiki.html">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>
+<li><a href="/dev/roadmap.html">Roadmap</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li><a href="http://www.apache.org">Apache Software Foundation</a><ul>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+</ul>
+</li>
+</ul>
+  </div>
+  
+  <div id="content">
+    <h1 class="title">VCL 2.2.1</h1>
+    <p><a name="VCL2.2.1-TableofContents"></a></p>
+<h2 id="table-of-contents">Table of Contents</h2>
+<ul>
+<li><a href="#VCL2.2.1-Downloadlinks">Download links</a></li>
+<li><a href="#VCL2.2.1-ReleaseNotes">Release Notes</a>
+         * <a href="#VCL2.2.1-I.IntroandDescription">I. Intro and Description</a>
+         * <a href="#VCL2.2.1-II.VCLRoadmap">II. VCL Roadmap</a>
+         * <a href="#VCL2.2.1-III.GettingInvolvedintheASFVCLCommunity">III. Getting Involved in the ASF VCL Community</a>
+         * <a href="#VCL2.2.1-IV.HowtoSubmitBugsandFeatureRequests">IV. How to Submit Bugs and Feature Requests</a></li>
+<li><a href="#VCL2.2.1-ChangeLog">Change Log</a>
+         * <a href="#VCL2.2.1-Bug">Bug</a>
+         * <a href="#VCL2.2.1-Improvement">Improvement</a>
+         * <a href="#VCL2.2.1-NewFeature">New Feature</a></li>
+</ul>
+<p><a name="VCL2.2.1-Downloadlinks"></a></p>
+<h2 id="download-links">Download links</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
+GPG signature (sums and signature files should be downloaded directly from
+Apache, not from mirrors).</p>
+<p><a href="http://www.apache.org/dyn/closer.cgi/incubator/vcl/apache-VCL-2.2.1-incubating.tar.bz2">Download ASF VCL 2.2.1</a>
+<a href="http://www.apache.org/dist/incubator/vcl/apache-VCL-2.2.1-incubating.tar.bz2.asc">GPG Signature</a>
+<a href="http://www.apache.org/dist/incubator/vcl/apache-VCL-2.2.1-incubating.tar.bz2.md5">MD5 Sum</a>
+<a href="http://www.apache.org/dist/incubator/vcl/apache-VCL-2.2.1-incubating.tar.bz2.sha1">SHA1 Sum</a>
+<a href="http://www.apache.org/dist/incubator/vcl/KEYS">VCL KEYS file</a></p>
+<p>Run the following command to verify the MD5 sum. It should give output
+similar to "apache-VCL-2.2.1-incubating.tar.bz2: OK":
+md5sum -c apache-VCL-2.2.1-incubating.tar.bz2.md5</p>
+<p>Similarly, Run the following command to verify the SHA1 sum. You should get
+output similar to "apache-VCL-2.2.1-incubating.tar.bz2: OK":
+sha1sum -c apache-VCL-2.2.1-incubating.tar.bz2.sha1</p>
+<p>To verify the GPG signature (you'll need to have <a href="http://www.gnupg.org/">GnuPG</a>
+ installed):
+1. download and import the VCL KEYS file (if you've imported the KEYS file
+for previously releases, you do not need to import it again):
+gpg --import KEYS
+1. download the GPG Signature to the same location as the release file
+1. from the directory containing both the release file and the GPG
+signature, run
+gpg --verify apache-VCL-2.2.1-incubating.tar.bz2.asc</p>
+<p>For new installs, visit the on-line <a href="vcl-2.2.1-installation.html">installation guide</a>
+.</p>
+<p>For upgrades from version 2.2, visit the on-line <a href="vcl:upgrade-from-previous-version-(2.2-to-2.2.1).html">upgrade guide</a>
+.
+For upgrades from version 2.1, visit the on-line <a href="vcl:upgrade-from-previous-version-(2.1-to-2.2.1).html">upgrade guide for upgrading from 2.1</a>
+.</p>
+<p><a name="VCL2.2.1-ReleaseNotes"></a></p>
+<h2 id="release-notes">Release Notes</h2>
+<p><a name="VCL2.2.1-I.IntroandDescription"></a></p>
+<h4 id="i-intro-and-description">I. Intro and Description</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
+computers are typically housed in a data center and may be physical blade
+servers, traditional rack mounted servers, or virtual machines. VCL can
+also broker access to standalone machines such as a lab computers on a
+university campus.</p>
+<p>One of the primary goals of VCL is to deliver a dedicated compute
+environment to a user for a limited time through a web interface. This
+compute environment can range from something as simple as a virtual machine
+running productivity software to a machine room blade running high end
+software (i.e. a CAD, GIS, statistical package or an Enterprise level
+application) to a cluster of interconnected physical (bare metal) compute
+nodes.</p>
+<p>Also using the scheduling API it can be used to automate the provisioning
+of servers in a server farm or HPC cluster.</p>
+<p>The release supports provisioning nodes using xCAT 1.3, xCAT 2.x, VMWare
+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.1-II.VCLRoadmap"></a></p>
+<h4 id="ii-vcl-roadmap">II. VCL Roadmap</h4>
+<p>VCL 2.2.1 (this release)
+<em> removed frontend dependency on jpgraph
+</em> remove any access control that is hard coded in frontend
+<em> added support for VirtualBox hypervisor
+</em> many bug fixes and improvements to VMWare support</p>
+<p>VCL 2.3
+<em> Service deployments
+</em> power management
+* improve cluster reservations</p>
+<p>VCL 2.4
+<em> additional and improved hypervisor support
+</em> KVM and possibly others (virtual box and XEN)
+* Allow for additional access methods for environments (port, other
+protocols, etc)</p>
+<p>VCL 2.5
+* develop tools for managing both system and user storage</p>
+<p>With each release, we'll be working toward making VCL easier to install. As
+part of our move to development at the Apache Software Foundation, it is an
+obvious goal to create a community of users and more developers around VCL.
+Bringing in more developers should become easier as VCL becomes easier to
+install.</p>
+<p><a name="VCL2.2.1-III.GettingInvolvedintheASFVCLCommunity"></a></p>
+<h4 id="iii-getting-involved-in-the-asf-vcl-community">III. Getting Involved in the ASF VCL Community</h4>
+<p>There are five ways to become involved in the ASF VCL community.</p>
+<ul>
+<li>
+<p>Join the mailing lists and participate in discussion. There are two
+mailing lists: vcl-user@incubator.apache.org
+vcl-dev@incubator.apache.org
+To join vcl-user, send an empty message to
+<a href="mailto:vcl-user-subscribe@incubator.apache.org|click-to-subscribe.html">vcl-user-subscribe@incubator.apache.org</a>
+. To join vcl-dev, send an empty
+message to <a href="mailto:vcl-dev-subscribe@incubator.apache.org|click-to-subscribe.html">vcl-dev-subscribe@incubator.apache.org</a>
+.</p>
+</li>
+<li>
+<p>Submit bug reports and feature requests to our JIRA bug tracking system.
+See section IV below for more information on doing this.</p>
+</li>
+<li>
+<p>Create documentation on our Confluence site. Create an account at <a href="http://cwiki.apache.org/confluence/display/VCL/Index">http://cwiki.apache.org/confluence/display/VCL/Index</a>
+ and just start adding content. (Note to current community: We should
+create a page explaining the layout so new people will know where to add
+content better.)</p>
+</li>
+<li>
+<p>Submit patches through the vcl-dev mailing list and via the JIRA bug
+tracking system. Once you have become familiar with VCL, you can begin
+assisting with the development of it by picking a JIRA issue to fix or by
+adding a feature needed at your site. Then, contribute a patch of your
+changes through the JIRA tracking system and send a message to the vcl-dev
+list explaining what you have done.</p>
+</li>
+<li>
+<p>Become an official committer to the project. Once you have shown that you
+have a good grasp of the project by submitting patches, you can further
+join the development work by submitting a contributor license agreement
+(CLA) to ASF and having a committer account created to directly contribute
+code to the project.</p>
+</li>
+<li>
+<p>If you are interested in contributing something to the project, please
+discuss it on the vcl-dev list BEFORE starting work on it. This allows the
+community to be involved in decisions and allows current developers to
+provide some guidance.</p>
+</li>
+</ul>
+<p><a name="VCL2.2.1-IV.HowtoSubmitBugsandFeatureRequests"></a></p>
+<h4 id="iv-how-to-submit-bugs-and-feature-requests">IV. How to Submit Bugs and Feature Requests</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 -
+it's free to anyone). Also, we would appreciate it if you mentioned that
+you filed a bug on the vcl-dev list to make sure we don't miss it.</p>
+<p>If you would like to requrest a new feature, you can also submit that in
+the same way through JIRA (just select "New Feature" or "Improvement" as
+the Issue Type). Again, it would be helpful if you mentioned that you filed
+a feature request on the vcl-dev list.</p>
+<p>After you have created a JIRA issue, you have the option to vote on it to
+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.1-ChangeLog"></a></p>
+<h2 id="change-log">Change Log</h2>
+<p>Release Notes - VCL - Version 2.2.1</p>
+<p><a name="VCL2.2.1-Bug"></a></p>
+<h4 id="bug">Bug</h4>
+<ul>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-113">VCL-113</a>
+] -         inconsistances with "None" user group</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-116">VCL-116</a>
+] -         manage groups interface doesn't correctly handle user groups
+with editusergroupid set to NULL</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-152">VCL-152</a>
+] -         problem removing vm from vmhost when vm in reloading state
+without a reservation</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-361">VCL-361</a>
+] -         Error is displayed on pages showing image list if last used
+image is deleted</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-395">VCL-395</a>
+] -         cannot add new vmprofiles</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-397">VCL-397</a>
+] -         Hostname not set on Linux computers if DNS is not configured
+remotely</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-411">VCL-411</a>
+] -         Legacy VCL logon and logoff scripts may not be deleted during
+capture causing immediate user logoff</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-412">VCL-412</a>
+] -         clicking on tomaintenance reload reservation in timetable
+gives an error</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-436">VCL-436</a>
+] -         Predictive Level_1 reload module - can select wrong image for
+computer</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-437">VCL-437</a>
+] -         delete image/reservation bug</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-439">VCL-439</a>
+] -         trailing commas in statistics.js keeps graphs from showing in
+IE on stats page</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-440">VCL-440</a>
+] -         dashboard last 12 hours of reservations graph not positioned
+correctly in IE in compatibility mode</li>
+</ul>
+<p><a name="VCL2.2.1-Improvement"></a></p>
+<h4 id="improvement">Improvement</h4>
+<ul>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-140">VCL-140</a>
+] -         General variable table</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-310">VCL-310</a>
+] -         remove jpgraph dependency</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-312">VCL-312</a>
+] -         remove View Mode and any uses of user.adminlevelid</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-373">VCL-373</a>
+] -         Enable Windows Server 2008 RDP audio - it's disabled by
+default</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-394">VCL-394</a>
+] -         Backend VMware improvements for 2.2.1 release</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-414">VCL-414</a>
+] -         modify XMLRPCaddUserGroup to accept a paramter specifying
+value for custom field</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-424">VCL-424</a>
+] -         Remove unused variables from subroutines in backend modules</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-425">VCL-425</a>
+] -         modify scheduler to be aware of RAM allocated to VMs on each
+VM host</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-426">VCL-426</a>
+] -         modify scheduler to not give user same computer if user had
+very recent, short reservation and other computers are available</li>
+</ul>
+<p><a name="VCL2.2.1-NewFeature"></a></p>
+<h4 id="new-feature">New Feature</h4>
+<ul>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-232">VCL-232</a>
+] -         add way to delete multiple computers</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-401">VCL-401</a>
+] -         add manageMapping resource attribute to control resource
+mapping</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-403">VCL-403</a>
+] -         make the scheduler aware of image and machine types so that
+virtual and bare images and computers can be mixed</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-405">VCL-405</a>
+] -         create provisioningOSinstalltype table to map provisioning
+methods to OSinstalltypes</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-406">VCL-406</a>
+] -         add some charts to see how machines are allocated to block
+allocations</li>
+</ul>
+  </div>
+  
+  <div id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2012 The Apache Software Foundation, Licensed under 
+        the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+        <br />
+        Apache and the Apache feather logo are trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>
+  
+</body>
+</html>

Added: websites/staging/vcl/trunk/content/confluence_export/vcl-2.2.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/vcl-2.2.html (added)
+++ websites/staging/vcl/trunk/content/confluence_export/vcl-2.2.html Tue Jan  8 16:38:15 2013
@@ -0,0 +1,588 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE- 2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+
+  <link href="/css/vcl.css" rel="stylesheet" type="text/css">
+  <link href="/css/code.css" rel="stylesheet" type="text/css">
+  <title>Apache VCL - VCL 2.2</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+  <div id="sitetitle">
+    <table width="100%" border="0" cellspacing="0" cellpadding="5">
+      <tr>
+         <td><a href="/index.html"><img src="/img/vcl-logo.png" height="100" align="left" alt="Apache VCL logo"></a></td>
+         <td><a href="http://www.apache.org"><img src="/img/asf-logo.png" align="right" alt="Apache Software Foundation logo"></a></td>
+      </tr>
+    </table>
+  </div>
+
+  <div id="navigation"> 
+  <ul>
+<li>Information<ul>
+<li><a href="/info/about.html">What is VCL?</a></li>
+<li><a href="/info/features.html">Features</a></li>
+<li><a href="/info/architecture.html">Architecture</a></li>
+<li><a href="/info/use-cases.html">Use Cases</a></li>
+<li><a href="/downloads/download.cgi">Download</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0.html">License</a></li>
+<li><a href="/info/faq.html">FAQ</a></li>
+</ul>
+</li>
+<li><a href="/docs/index.html">Documentation</a><ul>
+<li><a href="/docs/using-vcl.html">Using VCL</a></li>
+<li><a href="/docs/image-creation.html">Image Creation</a></li>
+<li><a href="/docs/administration.html">Administration</a></li>
+<li><a href="/docs/installation.html">Installation</a></li>
+<li><a href="/docs/deployment-planning.html">Deployment Planning</a></li>
+</ul>
+</li>
+<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/index.html#how-do-i-join-the-project">How can I Join</a></li>
+<li><a href="/comm/wiki.html">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>
+<li><a href="/dev/roadmap.html">Roadmap</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li><a href="http://www.apache.org">Apache Software Foundation</a><ul>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+</ul>
+</li>
+</ul>
+  </div>
+  
+  <div id="content">
+    <h1 class="title">VCL 2.2</h1>
+    <p><a name="VCL2.2-TableofContents"></a></p>
+<h2 id="table-of-contents">Table of Contents</h2>
+<ul>
+<li><a href="#VCL2.2-Downloadlinks">Download links</a></li>
+<li><a href="#VCL2.2-ReleaseNotes">Release Notes</a>
+         * <a href="#VCL2.2-I.IntroandDescription">I. Intro and Description</a>
+         * <a href="#VCL2.2-II.VCLRoadmap">II. VCL Roadmap</a>
+         * <a href="#VCL2.2-III.GettingInvolvedintheASFVCLCommunity">III. Getting Involved in the ASF VCL Community</a>
+         * <a href="#VCL2.2-IV.HowtoSubmitBugsandFeatureRequests">IV. How to Submit Bugs and Feature Requests</a></li>
+<li><a href="#VCL2.2-ChangeLog">Change Log</a>
+         * <a href="#VCL2.2-Bug">Bug</a>
+         * <a href="#VCL2.2-Improvement">Improvement</a>
+         * <a href="#VCL2.2-NewFeature">New Feature</a>
+         * <a href="#VCL2.2-Task">Task</a></li>
+</ul>
+<p><a name="VCL2.2-Downloadlinks"></a></p>
+<h2 id="download-links">Download links</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
+GPG signature (sums and signature files should be downloaded directly from
+Apache, not from mirrors).</p>
+<p><a href="http://www.apache.org/dyn/closer.cgi/incubator/vcl/apache-VCL-2.2-incubating.tar.bz2">Download ASF VCL 2.2</a>
+<a href="http://www.apache.org/dist/incubator/vcl/apache-VCL-2.2-incubating.tar.bz2.asc">GPG Signature</a>
+<a href="http://www.apache.org/dist/incubator/vcl/apache-VCL-2.2-incubating.tar.bz2.md5">MD5 Sum</a>
+<a href="http://www.apache.org/dist/incubator/vcl/apache-VCL-2.2-incubating.tar.bz2.sha1">SHA1 Sum</a>
+<a href="http://www.apache.org/dist/incubator/vcl/KEYS">VCL KEYS file</a></p>
+<p>Run the following command to verify the MD5 sum. You should get the same
+number that is in apache-VCL-2.2-incubating.tar.bz2.md5:
+md5sum apache-VCL-2.2-incubating.tar.bz2</p>
+<p>Similarly, Run the following command to verify the SHA1 sum. You should get
+the same number that is in apache-VCL-2.2-incubating.tar.bz2.sha1:
+sha1sum apache-VCL-2.2-incubating.tar.bz2</p>
+<p>To verify the GPG signature (you'll need to have <a href="http://www.gnupg.org/">GnuPG</a>
+ installed):
+1. download and import the VCL KEYS file:
+gpg --import KEYS
+1. download the GPG Signature to the same location as the release file
+1. from the directory containing both the release file and the GPG
+signature, run
+gpg --verify apache-VCL-2.2-incubating.tar.bz2.asc</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="vcl:upgrade-from-previous-version.html">upgrade guide</a>
+.</p>
+<p><a name="VCL2.2-ReleaseNotes"></a></p>
+<h2 id="release-notes">Release Notes</h2>
+<p><a name="VCL2.2-I.IntroandDescription"></a></p>
+<h4 id="i-intro-and-description">I. Intro and Description</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
+computers are typically housed in a data center and may be physical blade
+servers, traditional rack mounted servers, or virtual machines. VCL can
+also broker access to standalone machines such as a lab computers on a
+university campus.</p>
+<p>One of the primary goals of VCL is to deliver a dedicated compute
+environment to a user for a limited time through a web interface. This
+compute environment can range from something as simple as a virtual machine
+running productivity software to a machine room blade running high end
+software (i.e. a CAD, GIS, statistical package or an Enterprise level
+application) to a cluster of interconnected physical (bare metal) compute
+nodes.</p>
+<p>Also using the scheduling API it can be used to automate the provisioning
+of servers in a server farm or HPC cluster.</p>
+<p>The release supports provisioning nodes using xCAT 1.3, xCAT 2.x, VMWare
+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>
+<p>VCL 2.2 (this release)
+<em> support for xCAT 2.x
+</em> VMWare Free Server 2.x and ESXi 4
+* improve block reservations (renamed to block allocations)</p>
+<p>VCL 2.3
+<em> Service deployments
+</em> power management
+* improve cluster reservations</p>
+<p>VCL 2.4
+<em> additional and improved hypervisor support
+</em> KVM and possibly others (virtual box and XEN)
+* Allow for additional access methods for environments (port, other
+protocols, etc)</p>
+<p>VCL 2.5
+* develop tools for managing both system and user storage</p>
+<p>With each release, we'll be working toward making VCL easier to install. As
+part of our move to development at the Apache Software Foundation, it is an
+obvious goal to create a community of users and more developers around VCL.
+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>
+<p>There are five ways to become involved in the ASF VCL community.</p>
+<ul>
+<li>
+<p>Join the mailing lists and participate in discussion. There are two
+mailing lists: vcl-user@incubator.apache.org
+vcl-dev@incubator.apache.org
+To join vcl-user, send an empty message to
+<a href="mailto:vcl-user-subscribe@incubator.apache.org|click-to-subscribe.html">vcl-user-subscribe@incubator.apache.org</a>
+. To join vcl-dev, send an empty
+message to <a href="mailto:vcl-dev-subscribe@incubator.apache.org|click-to-subscribe.html">vcl-dev-subscribe@incubator.apache.org</a>
+.</p>
+</li>
+<li>
+<p>Submit bug reports and feature requests to our JIRA bug tracking system.
+See section IV below for more information on doing this.</p>
+</li>
+<li>
+<p>Create documentation on our Confluence site. Create an account at <a href="http://cwiki.apache.org/confluence/display/VCL/Index">http://cwiki.apache.org/confluence/display/VCL/Index</a>
+ and just start adding content. (Note to current community: We should
+create a page explaining the layout so new people will know where to add
+content better.)</p>
+</li>
+<li>
+<p>Submit patches through the vcl-dev mailing list and via the JIRA bug
+tracking system. Once you have become familiar with VCL, you can begin
+assisting with the development of it by picking a JIRA issue to fix or by
+adding a feature needed at your site. Then, contribute a patch of your
+changes through the JIRA tracking system and send a message to the vcl-dev
+list explaining what you have done.</p>
+</li>
+<li>
+<p>Become an official committer to the project. Once you have shown that you
+have a good grasp of the project by submitting patches, you can further
+join the development work by submitting a contributor license agreement
+(CLA) to ASF and having a committer account created to directly contribute
+code to the project.</p>
+</li>
+<li>
+<p>If you are interested in contributing something to the project, please
+discuss it on the vcl-dev list BEFORE starting work on it. This allows the
+community to be involved in decisions and allows current developers to
+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>
+<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 -
+it's free to anyone). Also, we would appreciate it if you mentioned that
+you filed a bug on the vcl-dev list to make sure we don't miss it.</p>
+<p>If you would like to requrest a new feature, you can also submit that in
+the same way through JIRA (just select "New Feature" or "Improvement" as
+the Issue Type). Again, it would be helpful if you mentioned that you filed
+a feature request on the vcl-dev list.</p>
+<p>After you have created a JIRA issue, you have the option to vote on it to
+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>
+<div class="codehilite"><pre>  <span class="n">Release</span> <span class="n">Notes</span> <span class="o">-</span> <span class="n">VCL</span> <span class="o">-</span> <span class="n">Version</span> <span class="mf">2.2</span>
+</pre></div>
+
+
+<p><a name="VCL2.2-Bug"></a></p>
+<h4 id="bug">Bug</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>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-149">VCL-150</a>
+] -         Pages do not display correctly with IE8 </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-154">VCL-154</a>
+] -         run_scp_command() is not catching permission denied errors </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-158">VCL-158</a>
+] -         utils.pm setstaticaddress() does not work correctly for
+Windows </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-159">VCL-159</a>
+] -         xCAT.pm is not always waiting long enough for ssh to respond
+on load </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-160">VCL-160</a>
+] -         Sysprep is overwriting DevicePath key after spdrvscn.exe runs </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-165">VCL-165</a>
+] -         Fix syntax bugs cause reservation processes to die </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-181">VCL-181</a>
+] -         VCL desktop request tool - use API to make reservations </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-189">VCL-189</a>
+] -         cannot add a computer in maintenance state </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-193">VCL-193</a>
+] -         IP address field not large enough for 15-characters </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-194">VCL-194</a>
+] -         Marking new computer to be &quot;maintenance&quot; status
+causes indexing error </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-197">VCL-197</a>
+] -         _is_user_added routine<br />
+</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-210">VCL-210</a>
+] -         getdynamicaddress returns 127.0.01 for missing public adapter </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-214">VCL-214</a>
+] -         Windows modules don't always disable autoadminlogon </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-215">VCL-215</a>
+] -         reservation_failed sub in State.pm may change state of
+computer currently in maintenance </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-220">VCL-220</a>
+] -         VMs in the available state which aren't assigned to a VM host
+may be reserved </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-221">VCL-221</a>
+] -         Add check to make sure post_load tasks have run before
+reserving a computer </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-227">VCL-227</a>
+] -         deleting user group that owns a resource group </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-233">VCL-233</a>
+] -         all calls to simpleAddRequest need to check for all return
+codes </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-241">VCL-241</a>
+] -         detailed loading summary does not compute times correctly for
+future reservations that are preloaded </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-242">VCL-242</a>
+] -         currentimage.txt permissions incorrect set </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-245">VCL-245</a>
+] -         esx.pm - always reloads<br />
+</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-250">VCL-250</a>
+] -         authentication for XML RPC X-User doesn't properly check to
+see if no authtype was found </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-258">VCL-258</a>
+] -         cluster loads - cluster_info file </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-260">VCL-260</a>
+] -         Problems occur if root is not the owner of /home/root for
+Windows images </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-261">VCL-261</a>
+] -         Windows.pm filesystem_entry_exists() subroutine may return
+true even if output contains &quot;file not found&quot; </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-262">VCL-262</a>
+] -         Windows capture may remove &quot;Log on as a service&quot;
+right for existing accounts </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-265">VCL-265</a>
+] -         Linux adduser cmd - remove uid parameter if uid not defined in
+user table<br />
+</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-266">VCL-266</a>
+] -         New process detects another reload process being complete
+before it should </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-267">VCL-267</a>
+] -         cluster loads  listing wrong parent and child addresses
+cluster_info file </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-269">VCL-269</a>
+] -         Windows.pm logoff_users() does not detect disconnected users </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-273">VCL-273</a>
+] -         Single quotes in image pretty name can cause image capture to
+fail </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-299">VCL-299</a>
+] -         shib users may have incorrect full name and email address. </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-300">VCL-300</a>
+] -         shib users always have email notices turned off </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-303">VCL-303</a>
+] -         tomaintenance reservations inserting wrong image revision </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-306">VCL-306</a>
+] -         Web GUI code has hard coded Eastern Time Zone information -
+breaks in other time zones </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-307">VCL-307</a>
+] -         add empty post_reserve routine UnixLab.pm OS module </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-317">VCL-317</a>
+] -         scheduler doesn't take imagerevision into account </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-318">VCL-318</a>
+] -         API error if invalid affiliation is used </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-325">VCL-325</a>
+] -         removing a subimage from a cluster can result in all subimages
+getting removed </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-327">VCL-327</a>
+] -         set_computer_name.vbs causes Sysprep to hang if certain
+applications are installed </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-329">VCL-329</a>
+] -         DataStructure.pm get_computer_private_ip_address() not
+handling all valid formats in /etc/hosts </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-331">VCL-331</a>
+] -         Windows code does not handle special characters in Scheduled
+Task names when changing passwords </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-332">VCL-332</a>
+] -         cannot delete block requests once the start date has passed </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-333">VCL-333</a>
+] -         DataStructure %ENV hash not get detected in _initialize
+routine<br />
+</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-334">VCL-334</a>
+] -         numeric userids are not handled correctly </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-337">VCL-337</a>
+] -         Windows.pm delete_files_by_pattern may delete unintended files
+if an environment variable isn't defined </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-338">VCL-338</a>
+] -         vmprofiles that are in use can be deleted </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-340">VCL-340</a>
+] -         cannot change name of vmprofile </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-346">VCL-346</a>
+] -         getdynamicaddress routine regex issue </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-347">VCL-347</a>
+] -         cluster connect page rdp file </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-349">VCL-349</a>
+] -         sql insert queries for image and imagerevision tables </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-353">VCL-353</a>
+] -         vmware.pm inserting new images - if original name is not in
+proper format $oldname does not get set correctly. </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-356">VCL-356</a>
+] -         vmware esx pm - vmware image directories </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-362">VCL-362</a>
+] -         vmware.pm power command output not detected under ESX 3.5 </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-363">VCL-363</a>
+] -         Passwords for existing Linux accounts are reset when the root
+password is set </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-364">VCL-364</a>
+] -         vmhostid removed when vm put in maintenance state </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-368">VCL-368</a>
+] -         pre-capture and post load linux steps correct sed cmd line
+options </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-370">VCL-370</a>
+] -         Reservation ID not defined errors occur for cluster
+reservations </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-371">VCL-371</a>
+] -         Private IP address is not being found in /etc/hosts under some
+circumstances </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-377">VCL-377</a>
+] -         multiple clicks on Create Reservation button gives multiple
+reservations </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-378">VCL-378</a>
+] -         reservation can be extended into a block allocation for user
+not in block group </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-382">VCL-382</a>
+] -         vmware.pm incorrectly handles free server with network
+datastores </li>
+</ul>
+<p><a name="VCL2.2-Improvement"></a></p>
+<h4 id="improvement">Improvement</h4>
+<ul>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-2">VCL-2</a>
+] -         migrate preferredimage to nextimage </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-9">VCL-9</a>
+] -         Update reclaim.pm to use DataStructure methods </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-11">VCL-11</a>
+] -         Update blockrequest.pm to use database subroutines </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-31">VCL-31</a>
+] -         rename conf.php and secrets.php to include -default in the
+name </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-32">VCL-32</a>
+] -         modify XMLRPCaddRequest to allow an end time to be specified </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-93">VCL-93</a>
+] -         LDAP part of a login to fail silently on errors when
+Shibboleth authentication is used </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-94">VCL-94</a>
+] -         Rework image capture flow </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-98">VCL-98</a>
+] -         upgrade all of dojo-0.4.0 code to recent version of dojo </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-125">VCL-125</a>
+] -         Add ability to control whether or not users have
+root/administrator access </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-137">VCL-137</a>
+] -         Update vmware.pm to use provisioning module interface
+subroutine names </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-145">VCL-145</a>
+] -         Store product keys in the database </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-148">VCL-148</a>
+] -         Add management node to current reservations view for
+ADMIN_DEVELOPER </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-149">VCL-149</a>
+] -         Prevent multiple vcld processes </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-153">VCL-153</a>
+] -         Update interface subroutines in xCAT21.pm to match xCAT.pm </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-155">VCL-155</a>
+] -         Decrease initial Current Reservation page refresh interval </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-161">VCL-161</a>
+] -         remove  xmlrpcKey table from vcl.sql<br />
+</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-162">VCL-162</a>
+] -         create structure to add throttling to provisioning modules </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-163">VCL-163</a>
+] -         move throttle variable from vcld.conf to managment node table </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-164">VCL-164</a>
+] -         Make installation and configuration easier </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-200">VCL-200</a>
+] -         add edit node name option in Privilege tree </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-204">VCL-204</a>
+] -         remove private ssh identity keys from known locations- post
+load / pre-capture routines </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-206">VCL-206</a>
+] -         Alphabetize list of virtual hosts </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-211">VCL-211</a>
+] -         image creation mode - administrator timeout </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-223">VCL-223</a>
+] -         Remove information user should not be able to access on
+post_load </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-224">VCL-224</a>
+] -         Move settings from vcld.conf to database except for database
+connection settings </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-244">VCL-244</a>
+] -         Staticics page - show number of failed loads per image </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-248">VCL-248</a>
+] -         Update provisioning modules' node_status to return READY if
+SSH works but ping doesn't </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-251">VCL-251</a>
+] -         Make &quot;Later&quot; reservation time default to a time in
+the future. </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-252">VCL-252</a>
+] -         XMLHttpTransport Error </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-254">VCL-254</a>
+] -         block request improvements </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-255">VCL-255</a>
+] -         xmlrpc_call routine add better error control </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-271">VCL-271</a>
+] -         clean out unused routines </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-272">VCL-272</a>
+] -         block request form </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-275">VCL-275</a>
+] -         Predictive reloading level_1 module </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-284">VCL-284</a>
+] -         vmware.pm power_reset sub does not catch error if VMware tools
+are not running </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-286">VCL-286</a>
+] -         post_linux load operation - set hostname that matches public
+IP address </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-288">VCL-288</a>
+] -         Add Global affiliation to schema </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-293">VCL-293</a>
+] -         check for remote ldap server being up before connecting to it </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-295">VCL-295</a>
+] -         Combine normal new reservation and imaging new reservation
+code </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-302">VCL-302</a>
+] -         provide feedback to users about block reservation status </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-305">VCL-305</a>
+] -         update code to work with php 5.3 </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-314">VCL-314</a>
+] -         change Documentation link to have links to ASF docs </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-320">VCL-320</a>
+] -         random selection of computer for reservations </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-326">VCL-326</a>
+] -         Shutdown Event Tracker causes autologin to fail </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-335">VCL-335</a>
+] -         max allowed ram for computers needs to be increased </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-357">VCL-357</a>
+] -         create update sql script to upgrade to the latest schema </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-359">VCL-359</a>
+] -         Remove DHCP and static IP configuration sections from
+provisioning modules </li>
+</ul>
+<p><a name="VCL2.2-NewFeature"></a></p>
+<h4 id="new-feature">New Feature</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
+root/administrator access </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-142">VCL-142</a>
+] -         Add KMS activation server configuration per affiliation </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-146">VCL-146</a>
+] -         add linux support for all VMWare modules </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-180">VCL-180</a>
+] -         add power_X(off,on,reset,status)  routines to provisioning
+modules<br />
+</li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-182">VCL-182</a>
+] -         Linux virtual machine support </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-195">VCL-195</a>
+] -         Add support for Windows Server 2008 </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-196">VCL-196</a>
+] -         Add support for 64-bit Windows </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-201">VCL-201</a>
+] -         Add support for Windows Vista VMware images </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-208">VCL-208</a>
+] -         Ability to easily put the VCL site into a maintenance state to
+prevent user access </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-239">VCL-239</a>
+] -         xcat 2.X module </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-268">VCL-268</a>
+] -         OS table - create additional OS ids </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-278">VCL-278</a>
+] -         Add setup mechanism to vcld </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-279">VCL-279</a>
+] -         Add post_load_custom script functionality for Linux images </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-292">VCL-292</a>
+] -         option to save selected authentication method in cookie </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-294">VCL-294</a>
+] -         create a login log </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-298">VCL-298</a>
+] -         Add support for VMware Server 2.x and ESXi 4.x </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-301">VCL-301</a>
+] -         Add support for Windows 7 </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-351">VCL-351</a>
+] -         extend vm profile to have more virtualswitches </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-352">VCL-352</a>
+] -         Add additional pre-capture steps for Linux OS </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-365">VCL-365</a>
+] -         change select box for environment on new reservation page to
+dojo filteringselect </li>
+</ul>
+<p><a name="VCL2.2-Task"></a></p>
+<h4 id="task">Task</h4>
+<ul>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-138">VCL-138</a>
+] -         remove antiquated vcldquery support </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-139">VCL-139</a>
+] -         make users' names optional </li>
+<li>[<a href="https://issues.apache.org/jira/browse/VCL-274">VCL-274</a>
+] -         check for SQL injection / XSS</li>
+</ul>
+  </div>
+  
+  <div id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2012 The Apache Software Foundation, Licensed under 
+        the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+        <br />
+        Apache and the Apache feather logo are trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>
+  
+</body>
+</html>

Added: websites/staging/vcl/trunk/content/confluence_export/vcl-2.3---adding-ldap-authentication.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/vcl-2.3---adding-ldap-authentication.html (added)
+++ websites/staging/vcl/trunk/content/confluence_export/vcl-2.3---adding-ldap-authentication.html Tue Jan  8 16:38:15 2013
@@ -0,0 +1,205 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE- 2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+
+  <link href="/css/vcl.css" rel="stylesheet" type="text/css">
+  <link href="/css/code.css" rel="stylesheet" type="text/css">
+  <title>Apache VCL - VCL 2.3 - Adding LDAP Authentication</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+  <div id="sitetitle">
+    <table width="100%" border="0" cellspacing="0" cellpadding="5">
+      <tr>
+         <td><a href="/index.html"><img src="/img/vcl-logo.png" height="100" align="left" alt="Apache VCL logo"></a></td>
+         <td><a href="http://www.apache.org"><img src="/img/asf-logo.png" align="right" alt="Apache Software Foundation logo"></a></td>
+      </tr>
+    </table>
+  </div>
+
+  <div id="navigation"> 
+  <ul>
+<li>Information<ul>
+<li><a href="/info/about.html">What is VCL?</a></li>
+<li><a href="/info/features.html">Features</a></li>
+<li><a href="/info/architecture.html">Architecture</a></li>
+<li><a href="/info/use-cases.html">Use Cases</a></li>
+<li><a href="/downloads/download.cgi">Download</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0.html">License</a></li>
+<li><a href="/info/faq.html">FAQ</a></li>
+</ul>
+</li>
+<li><a href="/docs/index.html">Documentation</a><ul>
+<li><a href="/docs/using-vcl.html">Using VCL</a></li>
+<li><a href="/docs/image-creation.html">Image Creation</a></li>
+<li><a href="/docs/administration.html">Administration</a></li>
+<li><a href="/docs/installation.html">Installation</a></li>
+<li><a href="/docs/deployment-planning.html">Deployment Planning</a></li>
+</ul>
+</li>
+<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/index.html#how-do-i-join-the-project">How can I Join</a></li>
+<li><a href="/comm/wiki.html">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>
+<li><a href="/dev/roadmap.html">Roadmap</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li><a href="http://www.apache.org">Apache Software Foundation</a><ul>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+</ul>
+</li>
+</ul>
+  </div>
+  
+  <div id="content">
+    <h1 class="title">VCL 2.3 - Adding LDAP Authentication</h1>
+    <p><a name="VCL2.3-AddingLDAPAuthentication-*AddingLDAPAuthenciation*"></a></p>
+<h2 id="adding-ldap-authenciation"><em>Adding LDAP Authenciation</em></h2>
+<p><a name="VCL2.3-AddingLDAPAuthentication-PrerequisitesforyourLDAPserver:"></a></p>
+<h3 id="prerequisites-for-your-ldap-server">Prerequisites for your LDAP server:</h3>
+<ul>
+<li>SSL should be enabled on your LDAP server</li>
+<li>An LDAP account that can look up a user's first and last names, user id,
+and email address (email address is optional) - this will be referred to as
+'vcllookup' on this page. You can skip this step if anonymous binds are
+enabled on your LDAP server and an anonymous bind will be able to look up
+userids, names, and email addresses.</li>
+<li>If your LDAP server is behind a firewall, you will need to allow your VCL
+web server to access tcp port 636 on your LDAP server</li>
+</ul>
+<p><a name="VCL2.3-AddingLDAPAuthentication-PrerequisitesforyourVCLwebserver:"></a></p>
+<h3 id="prerequisites-for-your-vcl-web-server">Prerequisites for your VCL web server:</h3>
+<ul>
+<li><em>php-ldap</em> needs to be installed</li>
+<li>If your LDAP server's SSL certificate is self-signed, your VCL web server
+needs to have the root CA certificate that was used to sign the LDAP server
+certificate installed. The PEM formatted certificate needs to be added to
+the ca-bundle.crt file. On CentOS, the file is located at
+/etc/pki/tls/certs/ca-bundle.crt. The hostname in the certificate must
+match the hostname entered in the conf.php file further down. If your
+certificate does not have the correct hostname in it, you can put an entry
+in /etc/hosts for the hostname in the certificate.</li>
+<li>After adding the certificate, restart httpd:
+{tip}
+service httpd restart
+{tip}</li>
+<li>You can verify that the certificate is properly installed using this
+command:
+{tip}
+openssl s_client -showcerts -CAfile /etc/pki/tls/certs/ca-bundle.crt
+-connect your.ldap.server.here:636
+{tip}
+If you see "Verify return code: 0 (ok)" at the end of the output then it is
+installed correctly. If you see a different return code, then you'll need
+to troubleshoot the problem.</li>
+<li>
+<p>You may need to add a line to <em>/etc/openldap/ldap.conf</em> to point to the
+ca-bundle.crt file. If so, add the following:</p>
+<p>TLS_CACERT /etc/pki/tls/certs/ca-bundle.crt</p>
+</li>
+</ul>
+<p><a name="VCL2.3-AddingLDAPAuthentication-AddingLDAPAuthenticationtotheWebCode"></a></p>
+<h3 id="adding-ldap-authentication-to-the-web-code">Adding LDAP Authentication to the Web Code</h3>
+<ul>
+<li>You will need to manually add an entry to the affiliation table in the
+VCL database. Choose a name for the affiliation. This will be appended to
+all userids for the affiliation to distinguish them from other affiliations
+you may configure later. <em>Do not</em> use the Global affiliation for this.
+Initials or a short name of your organization are a good idea. The
+affiliation name cannot contain spaces. Use the following to add the
+affiliation, replacing 'EXAMPLE' with the name you chose. Take note of the
+id from the 2nd SQL statement as you will need it later. It is the
+numerical id for this affiliation.
+{tip}
+mysql vcl
+{tip}
+{tip}
+INSERT INTO affiliation (name) VALUES ('EXAMPLE');
+{tip}
+{tip}
+SELECT id FROM affiliation WHERE name = 'EXAMPLE';
+{tip}
+{tip}
+exit
+{tip}</li>
+<li>Edit <em>conf.php</em> and search for "EXAMPLE1 LDAP"</li>
+<li>Uncomment the "EXAMPLE1 LDAP" section by removing the '/*' before it and
+the '*/' at the end of 'to use this login mechanism'</li>
+<li>Change 'EXAMPLE1 LDAP' to something to match your location, for example
+at NCSU, it is 'NCSU LDAP'. This string is what users will see where they
+select the authentication mechanism to use when logging in.</li>
+<li>Modify the following fields:
+<strong> <em>server</em> - this is the hostname of your LDAP server - this must match
+the hostname in the certificate.</strong> <em>binddn</em> - typically, you'll want to use the base DN of your LDAP
+server; for Active Directory, this is usually dc= for each of your domain
+name components. For example, your your domain name was ad.example.org, it
+would be "dc=ad,dc=example,dc=org"
+<strong> <em>userid</em> - this is a string that is added to the userid a user enters
+on the login page. Place a '%s' where the entered userid should go. Some
+examples are:
+<strong><em> %s@example.org
+</em></strong> %s@ad.example.org</strong><em> uid=%s,ou=accounts,dc=example,dc=org'
+<strong> <em>unityid</em> - this is the ldap field that contains a user's login id (for
+Active Directory, this is usually sAMAccountName)</strong> </em>firstname<em> - this is the ldap field that contains a user's first name
+<strong> <em>lastname</em> - this is the ldap field that contains a user's last name</strong> </em>email<em> - this is the ldap field that contains a user's email address
+<strong> <em>defaultemail</em> - if an email address is not provided by the ldap
+server, this will be appended to the end of the userid to create an email
+address. In this case, email notifications will be disabled by default.</strong> </em>masterlogin<em> - this is the vcllookup account referred to in the
+"Prerequisites for your LDAP server" section - comment out this line if
+using anonymous binds
+<strong> <em>masterpwd</em> - password for the masterlogin account - comment out this
+line if using anonymous binds</strong> </em>affiliationid<em> - this is the id from the SELECT statement in the first
+step
+<strong> <em>lookupuserbeforeauth</em> - Some LDAP servers will only allow the full DN
+of a user to be used when authenticating. If this is the case, you will
+need to set this to 1 and set a value for <em>lookupuserfield</em>. You can
+probably start out with this set to 0. If your LDAP server has users in
+multiple containers, you will probably need to set this to 1. </strong> </em>lookupuserfield<em> - If you need to set </em>lookupuserbeforeauth<em> to 1, set
+this to the attribute to use to search for the user in ldap. Typical values
+are 'cn', 'uid', and 'samaccountname'.
+</em><em> </em>help* - this is some text that will show up on the page where users
+select the authentication method explaining why they would select this
+option</li>
+<li>Uncomment the <em>require_once</em> line for <em>ldapauth.php</em> toward the bottom of
+the file</li>
+</ul>
+  </div>
+  
+  <div id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2012 The Apache Software Foundation, Licensed under 
+        the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+        <br />
+        Apache and the Apache feather logo are trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>
+  
+</body>
+</html>



Mime
View raw message