vcl-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r845587 - in /websites/staging/vcl/trunk/content: ./ confluence_export/vcl-2.2.html docs/archives/ docs/archives/old-releases/ docs/archives/old-releases/vcl-2.2.html
Date Tue, 08 Jan 2013 20:54:55 GMT
Author: buildbot
Date: Tue Jan  8 20:54:54 2013
New Revision: 845587

Staging update by buildbot for vcl

    websites/staging/vcl/trunk/content/   (props changed)

Propchange: websites/staging/vcl/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Tue Jan  8 20:54:54 2013
@@ -1 +1 @@

Added: websites/staging/vcl/trunk/content/docs/archives/old-releases/vcl-2.2.html
--- websites/staging/vcl/trunk/content/docs/archives/old-releases/vcl-2.2.html (added)
+++ websites/staging/vcl/trunk/content/docs/archives/old-releases/vcl-2.2.html Tue Jan  8
20:54:54 2013
@@ -0,0 +1,609 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "">
+    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
+ 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">
+  <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=""><img src="/img/asf-logo.png"
align="right" alt="Apache Software Foundation logo"></a></td>
+      </tr>
+    </table>
+  </div>
+  <div id="navigation"> 
+  <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="">License</a></li>
+<li><a href="/info/faq.html">FAQ</a></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>
+<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>
+<li><a href="">Apache Software Foundation</a><ul>
+<li><a href="">Thanks</a></li>
+<li><a href="">Become a Sponsor</a></li>
+  </div>
+  <div id="content">
+    <h1 class="title">VCL 2.2</h1>
+    <div class="toc">
+<li><a href="#download-links">Download links</a></li>
+<li><a href="#release-notes">Release Notes</a><ul>
+<li><a href="#i-intro-and-description">I. Intro and Description</a><ul>
+<li><a href="#ii-vcl-roadmap">II. VCL Roadmap</a></li>
+<li><a href="#iii-getting-involved-in-the-asf-vcl-community">III. Getting Involved
in the ASF VCL Community</a></li>
+<li><a href="#iv-how-to-submit-bugs-and-feature-requests">IV. How to Submit Bugs
and Feature Requests</a></li>
+<li><a href="#change-log">Change Log</a><ul>
+<li><a href="#bug">Bug</a><ul>
+<li><a href="#improvement">Improvement</a></li>
+<li><a href="#new-feature">New Feature</a></li>
+<li><a href="#task">Task</a></li>
+<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>
+GPG signature (sums and signature files should be downloaded directly from
+Apache, not from mirrors).</p>
+<p><a href=";action=download&amp;filename=%2Fincubator%2Fvcl%2Fapache-VCL-2.2-incubating.tar.bz2">Download
ASF VCL 2.2</a><br>
+<a href="">GPG
+<a href="">MD5
+<a href="">SHA1
+<a href="">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:</p>
+<div class="codehilite"><pre><span class="n">md5sum</span> <span
class="n">apache</span><span class="o">-</span><span class="n">VCL</span><span
class="o">-</span><span class="mf">2.2</span><span class="o">-</span><span
class="n">incubating</span><span class="o">.</span><span class="n">tar</span><span
class="o">.</span><span class="n">bz2</span>
+<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:</p>
+<div class="codehilite"><pre><span class="n">sha1sum</span> <span
class="n">apache</span><span class="o">-</span><span class="n">VCL</span><span
class="o">-</span><span class="mf">2.2</span><span class="o">-</span><span
class="n">incubating</span><span class="o">.</span><span class="n">tar</span><span
class="o">.</span><span class="n">bz2</span>
+<p>To verify the GPG signature (you'll need to have <a href="">GnuPG</a>
+ installed):</p>
+<p>download and import the VCL KEYS file:</p>
+<p>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</p>
+<p>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
+<p>For upgrades from version 2.1, visit the on-line <a href="upgrade-from-previous-version.html">upgrade
+<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
+<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)</p>
+<li>support for xCAT 2.x</li>
+<li>VMWare Free Server 2.x and ESXi 4</li>
+<li>improve block reservations (renamed to block allocations)</li>
+<p>VCL 2.3</p>
+<li>Service deployments</li>
+<li>power management</li>
+<li>improve cluster reservations</li>
+<p>VCL 2.4</p>
+<li>additional and improved hypervisor support</li>
+<li>KVM and possibly others (virtual box and XEN)</li>
+<li>Allow for additional access methods for environments (port, other
+protocols, etc)</li>
+<p>VCL 2.5</p>
+<li>develop tools for managing both system and user storage</li>
+<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
+<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>
+<p>Join the mailing lists and participate in discussion. There are two
+mailing lists:<br><br><br>
+To join user, send an empty message to
+<a href=""></a>.

+To join dev, send an empty message to 
+<a href=""></a>.</p>
+<p>Submit bug reports and feature requests to our JIRA bug tracking system.
+See section IV below for more information on doing this.</p>
+<p><a href="/comm/contribute-documentation.html">Create documentation</a>
on our CMS site. </p>
+<p>Submit patches through the 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 dev
+list explaining what you have done.</p>
+<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>
+<p>If you are interested in contributing something to the project, please
+discuss it on the 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>
+<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
+<p>If you find a bug, please submit a bug report to our JIRA bug tracking
+system at <a href=""></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 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 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>
+<p><a name="VCL2.2-Bug"></a></p>
+<h4 id="bug">Bug</h4>
+<li>[<a href="">VCL-121</a>
+] -         special characters in API passwords not handled correctly </li>
+<li>[<a href="">VCL-150</a>
+] -         Pages do not display correctly with IE8 </li>
+<li>[<a href="">VCL-154</a>
+] -         run_scp_command() is not catching permission denied errors </li>
+<li>[<a href="">VCL-158</a>
+] - setstaticaddress() does not work correctly for
+Windows </li>
+<li>[<a href="">VCL-159</a>
+] - is not always waiting long enough for ssh to respond
+on load </li>
+<li>[<a href="">VCL-160</a>
+] -         Sysprep is overwriting DevicePath key after spdrvscn.exe runs </li>
+<li>[<a href="">VCL-165</a>
+] -         Fix syntax bugs cause reservation processes to die </li>
+<li>[<a href="">VCL-181</a>
+] -         VCL desktop request tool - use API to make reservations </li>
+<li>[<a href="">VCL-189</a>
+] -         cannot add a computer in maintenance state </li>
+<li>[<a href="">VCL-193</a>
+] -         IP address field not large enough for 15-characters </li>
+<li>[<a href="">VCL-194</a>
+] -         Marking new computer to be &quot;maintenance&quot; status
+causes indexing error </li>
+<li>[<a href="">VCL-197</a>
+] -         _is_user_added routine<br />
+<li>[<a href="">VCL-210</a>
+] -         getdynamicaddress returns 127.0.01 for missing public adapter </li>
+<li>[<a href="">VCL-214</a>
+] -         Windows modules don't always disable autoadminlogon </li>
+<li>[<a href="">VCL-215</a>
+] -         reservation_failed sub in may change state of
+computer currently in maintenance </li>
+<li>[<a href="">VCL-220</a>
+] -         VMs in the available state which aren't assigned to a VM host
+may be reserved </li>
+<li>[<a href="">VCL-221</a>
+] -         Add check to make sure post_load tasks have run before
+reserving a computer </li>
+<li>[<a href="">VCL-227</a>
+] -         deleting user group that owns a resource group </li>
+<li>[<a href="">VCL-233</a>
+] -         all calls to simpleAddRequest need to check for all return
+codes </li>
+<li>[<a href="">VCL-241</a>
+] -         detailed loading summary does not compute times correctly for
+future reservations that are preloaded </li>
+<li>[<a href="">VCL-242</a>
+] -         currentimage.txt permissions incorrect set </li>
+<li>[<a href="">VCL-245</a>
+] - - always reloads<br />
+<li>[<a href="">VCL-250</a>
+] -         authentication for XML RPC X-User doesn't properly check to
+see if no authtype was found </li>
+<li>[<a href="">VCL-258</a>
+] -         cluster loads - cluster_info file </li>
+<li>[<a href="">VCL-260</a>
+] -         Problems occur if root is not the owner of /home/root for
+Windows images </li>
+<li>[<a href="">VCL-261</a>
+] - filesystem_entry_exists() subroutine may return
+true even if output contains &quot;file not found&quot; </li>
+<li>[<a href="">VCL-262</a>
+] -         Windows capture may remove &quot;Log on as a service&quot;
+right for existing accounts </li>
+<li>[<a href="">VCL-265</a>
+] -         Linux adduser cmd - remove uid parameter if uid not defined in
+user table<br />
+<li>[<a href="">VCL-266</a>
+] -         New process detects another reload process being complete
+before it should </li>
+<li>[<a href="">VCL-267</a>
+] -         cluster loads  listing wrong parent and child addresses
+cluster_info file </li>
+<li>[<a href="">VCL-269</a>
+] - logoff_users() does not detect disconnected users </li>
+<li>[<a href="">VCL-273</a>
+] -         Single quotes in image pretty name can cause image capture to
+fail </li>
+<li>[<a href="">VCL-299</a>
+] -         shib users may have incorrect full name and email address. </li>
+<li>[<a href="">VCL-300</a>
+] -         shib users always have email notices turned off </li>
+<li>[<a href="">VCL-303</a>
+] -         tomaintenance reservations inserting wrong image revision </li>
+<li>[<a href="">VCL-306</a>
+] -         Web GUI code has hard coded Eastern Time Zone information -
+breaks in other time zones </li>
+<li>[<a href="">VCL-307</a>
+] -         add empty post_reserve routine OS module </li>
+<li>[<a href="">VCL-317</a>
+] -         scheduler doesn't take imagerevision into account </li>
+<li>[<a href="">VCL-318</a>
+] -         API error if invalid affiliation is used </li>
+<li>[<a href="">VCL-325</a>
+] -         removing a subimage from a cluster can result in all subimages
+getting removed </li>
+<li>[<a href="">VCL-327</a>
+] -         set_computer_name.vbs causes Sysprep to hang if certain
+applications are installed </li>
+<li>[<a href="">VCL-329</a>
+] - get_computer_private_ip_address() not
+handling all valid formats in /etc/hosts </li>
+<li>[<a href="">VCL-331</a>
+] -         Windows code does not handle special characters in Scheduled
+Task names when changing passwords </li>
+<li>[<a href="">VCL-332</a>
+] -         cannot delete block requests once the start date has passed </li>
+<li>[<a href="">VCL-333</a>
+] -         DataStructure %ENV hash not get detected in _initialize
+routine<br />
+<li>[<a href="">VCL-334</a>
+] -         numeric userids are not handled correctly </li>
+<li>[<a href="">VCL-337</a>
+] - delete_files_by_pattern may delete unintended files
+if an environment variable isn't defined </li>
+<li>[<a href="">VCL-338</a>
+] -         vmprofiles that are in use can be deleted </li>
+<li>[<a href="">VCL-340</a>
+] -         cannot change name of vmprofile </li>
+<li>[<a href="">VCL-346</a>
+] -         getdynamicaddress routine regex issue </li>
+<li>[<a href="">VCL-347</a>
+] -         cluster connect page rdp file </li>
+<li>[<a href="">VCL-349</a>
+] -         sql insert queries for image and imagerevision tables </li>
+<li>[<a href="">VCL-353</a>
+] - inserting new images - if original name is not in
+proper format $oldname does not get set correctly. </li>
+<li>[<a href="">VCL-356</a>
+] -         vmware esx pm - vmware image directories </li>
+<li>[<a href="">VCL-362</a>
+] - power command output not detected under ESX 3.5 </li>
+<li>[<a href="">VCL-363</a>
+] -         Passwords for existing Linux accounts are reset when the root
+password is set </li>
+<li>[<a href="">VCL-364</a>
+] -         vmhostid removed when vm put in maintenance state </li>
+<li>[<a href="">VCL-368</a>
+] -         pre-capture and post load linux steps correct sed cmd line
+options </li>
+<li>[<a href="">VCL-370</a>
+] -         Reservation ID not defined errors occur for cluster
+reservations </li>
+<li>[<a href="">VCL-371</a>
+] -         Private IP address is not being found in /etc/hosts under some
+circumstances </li>
+<li>[<a href="">VCL-377</a>
+] -         multiple clicks on Create Reservation button gives multiple
+reservations </li>
+<li>[<a href="">VCL-378</a>
+] -         reservation can be extended into a block allocation for user
+not in block group </li>
+<li>[<a href="">VCL-382</a>
+] - incorrectly handles free server with network
+datastores </li>
+<p><a name="VCL2.2-Improvement"></a></p>
+<h4 id="improvement">Improvement</h4>
+<li>[<a href="">VCL-2</a>
+] -         migrate preferredimage to nextimage </li>
+<li>[<a href="">VCL-9</a>
+] -         Update to use DataStructure methods </li>
+<li>[<a href="">VCL-11</a>
+] -         Update to use database subroutines </li>
+<li>[<a href="">VCL-31</a>
+] -         rename conf.php and secrets.php to include -default in the
+name </li>
+<li>[<a href="">VCL-32</a>
+] -         modify XMLRPCaddRequest to allow an end time to be specified </li>
+<li>[<a href="">VCL-93</a>
+] -         LDAP part of a login to fail silently on errors when
+Shibboleth authentication is used </li>
+<li>[<a href="">VCL-94</a>
+] -         Rework image capture flow </li>
+<li>[<a href="">VCL-98</a>
+] -         upgrade all of dojo-0.4.0 code to recent version of dojo </li>
+<li>[<a href="">VCL-125</a>
+] -         Add ability to control whether or not users have
+root/administrator access </li>
+<li>[<a href="">VCL-137</a>
+] -         Update to use provisioning module interface
+subroutine names </li>
+<li>[<a href="">VCL-145</a>
+] -         Store product keys in the database </li>
+<li>[<a href="">VCL-148</a>
+] -         Add management node to current reservations view for
+<li>[<a href="">VCL-149</a>
+] -         Prevent multiple vcld processes </li>
+<li>[<a href="">VCL-153</a>
+] -         Update interface subroutines in to match </li>
+<li>[<a href="">VCL-155</a>
+] -         Decrease initial Current Reservation page refresh interval </li>
+<li>[<a href="">VCL-161</a>
+] -         remove  xmlrpcKey table from vcl.sql<br />
+<li>[<a href="">VCL-162</a>
+] -         create structure to add throttling to provisioning modules </li>
+<li>[<a href="">VCL-163</a>
+] -         move throttle variable from vcld.conf to managment node table </li>
+<li>[<a href="">VCL-164</a>
+] -         Make installation and configuration easier </li>
+<li>[<a href="">VCL-200</a>
+] -         add edit node name option in Privilege tree </li>
+<li>[<a href="">VCL-204</a>
+] -         remove private ssh identity keys from known locations- post
+load / pre-capture routines </li>
+<li>[<a href="">VCL-206</a>
+] -         Alphabetize list of virtual hosts </li>
+<li>[<a href="">VCL-211</a>
+] -         image creation mode - administrator timeout </li>
+<li>[<a href="">VCL-223</a>
+] -         Remove information user should not be able to access on
+post_load </li>
+<li>[<a href="">VCL-224</a>
+] -         Move settings from vcld.conf to database except for database
+connection settings </li>
+<li>[<a href="">VCL-244</a>
+] -         Staticics page - show number of failed loads per image </li>
+<li>[<a href="">VCL-248</a>
+] -         Update provisioning modules' node_status to return READY if
+SSH works but ping doesn't </li>
+<li>[<a href="">VCL-251</a>
+] -         Make &quot;Later&quot; reservation time default to a time in
+the future. </li>
+<li>[<a href="">VCL-252</a>
+] -         XMLHttpTransport Error </li>
+<li>[<a href="">VCL-254</a>
+] -         block request improvements </li>
+<li>[<a href="">VCL-255</a>
+] -         xmlrpc_call routine add better error control </li>
+<li>[<a href="">VCL-271</a>
+] -         clean out unused routines </li>
+<li>[<a href="">VCL-272</a>
+] -         block request form </li>
+<li>[<a href="">VCL-275</a>
+] -         Predictive reloading level_1 module </li>
+<li>[<a href="">VCL-284</a>
+] - power_reset sub does not catch error if VMware tools
+are not running </li>
+<li>[<a href="">VCL-286</a>
+] -         post_linux load operation - set hostname that matches public
+IP address </li>
+<li>[<a href="">VCL-288</a>
+] -         Add Global affiliation to schema </li>
+<li>[<a href="">VCL-293</a>
+] -         check for remote ldap server being up before connecting to it </li>
+<li>[<a href="">VCL-295</a>
+] -         Combine normal new reservation and imaging new reservation
+code </li>
+<li>[<a href="">VCL-302</a>
+] -         provide feedback to users about block reservation status </li>
+<li>[<a href="">VCL-305</a>
+] -         update code to work with php 5.3 </li>
+<li>[<a href="">VCL-314</a>
+] -         change Documentation link to have links to ASF docs </li>
+<li>[<a href="">VCL-320</a>
+] -         random selection of computer for reservations </li>
+<li>[<a href="">VCL-326</a>
+] -         Shutdown Event Tracker causes autologin to fail </li>
+<li>[<a href="">VCL-335</a>
+] -         max allowed ram for computers needs to be increased </li>
+<li>[<a href="">VCL-357</a>
+] -         create update sql script to upgrade to the latest schema </li>
+<li>[<a href="">VCL-359</a>
+] -         Remove DHCP and static IP configuration sections from
+provisioning modules </li>
+<p><a name="VCL2.2-NewFeature"></a></p>
+<h4 id="new-feature">New Feature</h4>
+<li>[<a href="">VCL-134</a>
+] -         Add ability to control whether or not users have
+root/administrator access </li>
+<li>[<a href="">VCL-142</a>
+] -         Add KMS activation server configuration per affiliation </li>
+<li>[<a href="">VCL-146</a>
+] -         add linux support for all VMWare modules </li>
+<li>[<a href="">VCL-180</a>
+] -         add power_X(off,on,reset,status)  routines to provisioning
+modules<br />
+<li>[<a href="">VCL-182</a>
+] -         Linux virtual machine support </li>
+<li>[<a href="">VCL-195</a>
+] -         Add support for Windows Server 2008 </li>
+<li>[<a href="">VCL-196</a>
+] -         Add support for 64-bit Windows </li>
+<li>[<a href="">VCL-201</a>
+] -         Add support for Windows Vista VMware images </li>
+<li>[<a href="">VCL-208</a>
+] -         Ability to easily put the VCL site into a maintenance state to
+prevent user access </li>
+<li>[<a href="">VCL-239</a>
+] -         xcat 2.X module </li>
+<li>[<a href="">VCL-268</a>
+] -         OS table - create additional OS ids </li>
+<li>[<a href="">VCL-278</a>
+] -         Add setup mechanism to vcld </li>
+<li>[<a href="">VCL-279</a>
+] -         Add post_load_custom script functionality for Linux images </li>
+<li>[<a href="">VCL-292</a>
+] -         option to save selected authentication method in cookie </li>
+<li>[<a href="">VCL-294</a>
+] -         create a login log </li>
+<li>[<a href="">VCL-298</a>
+] -         Add support for VMware Server 2.x and ESXi 4.x </li>
+<li>[<a href="">VCL-301</a>
+] -         Add support for Windows 7 </li>
+<li>[<a href="">VCL-351</a>
+] -         extend vm profile to have more virtualswitches </li>
+<li>[<a href="">VCL-352</a>
+] -         Add additional pre-capture steps for Linux OS </li>
+<li>[<a href="">VCL-365</a>
+] -         change select box for environment on new reservation page to
+dojo filteringselect </li>
+<p><a name="VCL2.2-Task"></a></p>
+<h4 id="task">Task</h4>
+<li>[<a href="">VCL-138</a>
+] -         remove antiquated vcldquery support </li>
+<li>[<a href="">VCL-139</a>
+] -         make users' names optional </li>
+<li>[<a href="">VCL-274</a>
+] -         check for SQL injection / XSS</li>
+  </div>
+  <div id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2012 The Apache Software Foundation, Licensed under 
+        the <a href="">Apache License, Version
+        <br />
+        Apache and the Apache feather logo are trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>

View raw message