vcl-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jftho...@apache.org
Subject svn commit: r1430372 [9/11] - /vcl/site/trunk/content/confluence_export/
Date Tue, 08 Jan 2013 16:37:56 GMT
Added: vcl/site/trunk/content/confluence_export/vcl-2.2.1-web-code-installation.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/vcl-2.2.1-web-code-installation.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/vcl-2.2.1-web-code-installation.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/vcl-2.2.1-web-code-installation.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,244 @@
+Title: VCL 2.2.1 Web Code Installation
+{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}
+
+<a name="VCL2.2.1WebCodeInstallation-Install&ConfiguretheWebComponents"></a>
+# Install & Configure the Web Components
+
+<a name="VCL2.2.1WebCodeInstallation-*Prerequisites*"></a>
+## *Prerequisites*
+
+The following instructions assume these tasks have previously been
+completed:
+* [Apache VCL 2.2.1 has been downloaded](download.html)
+* [VCL database has been installed and configured](vcl:vcl-2.2.1-database-installation.html)
+
+  
+  
+
+<a name="VCL2.2.1WebCodeInstallation-WebServer:"></a>
+#### Web Server:
+
+* Apache HTTP Server v1.3 or v2.x with SSL enabled
+* PHP 5.0 or later
+
+{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}
+
+<a name="VCL2.2.1WebCodeInstallation-RequiredLinuxPackages:"></a>
+#### Required Linux Packages:
+
+* *httpd* \- Apache HTTP Server
+* *mod_ssl* \- SSL/TLS module for the Apache HTTP server
+* *php* \- The PHP HTML-embedded scripting language
+* *libmcrypt* \- Encryption algorithms library (this requirement can be
+removed with a [patch](vcl:patch-to-remove-mcrypt-dependency.html)
+)
+
+<a name="VCL2.2.1WebCodeInstallation-RequiredPHPModules:"></a>
+#### Required PHP Modules:
+
+(Some of these may already be included with your PHP distribution)
+* *php-gd*
+* *php-json* (required if your PHP version is 5.2 or later)
+* *php-mcrypt* (this requirement can be removed with a [patch](vcl:patch-to-remove-mcrypt-dependency.html)
+)
+* *php-mysql*
+* *php-openssl*
+* *php-sysvsem*
+* *php-xml*
+* *php-xmlrpc*
+* *php-ldap* (if you will be using LDAP authentication)
+
+  
+  
+1. # If your web server is running a Red Hat-based OS, the required
+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}
+1. #* If you will be using a self-signed certificate for SSL, [this is a great HOWTO ](http://wiki.centos.org/HowTos/Https)
+explaining how to set it up on CentOS
+1. #* It is useful to configure the server to be able to send debugging
+emails
+1. # Configure the web server daemon (httpd) to start automatically:
+{tip}
+/sbin/chkconfig \--level 345 httpd on
+{tip}
+1. # Start the web server daemon:
+{tip}
+/sbin/service httpd start
+{tip}
+1. # If SELinux is enabled, run the following command to allow the web server
+to connect to the database:
+{tip}
+/usr/sbin/setsebool \-P httpd_can_network_connect=1
+{tip}
+1. # If the iptables firewall is being used, port 80 and 443 should be opened
+up:
+{tip}vi /etc/sysconfig/iptables{tip}
+
+    -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
+
+  
+  
+1. h2. Install the&nbsp;VCL Frontend Web Code
+1. # If you have not already done so, download and extract the source files
+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}
+1. # Copy the *web* directory to a location under the web root of your web
+server and navigate to the&nbsp;destination&nbsp;*.ht-inc* subdirectory:
+{tip}
+cp \-r apache-VCL-2.2.1-incubating/web/ /var/www/html/vcl
+cd /var/www/html/vcl/.ht-inc
+{tip}
+1. # apply patch to fix editing reservations
+{tip}
+wget [https://issues.apache.org/jira/secure/attachment/12477101/utils_virtual_undefined.patch](https://issues.apache.org/jira/secure/attachment/12477101/utils_virtual_undefined.patch)
+patch < utils_virtual_undefined.patch
+{tip}
+1. # apply patch to fix processing of block allocations
+{tip}
+wget [https://issues.apache.org/jira/secure/attachment/12485328/vmhostcheck_fix.patch](https://issues.apache.org/jira/secure/attachment/12485328/vmhostcheck_fix.patch)
+patch < vmhostcheck_fix.patch
+{tip}
+1. # Copy *secrets-default.php* to *secrets.php*:
+{tip}
+cp secrets-default.php secrets.php
+{tip}
+1. # Edit the *secrets.php* file:
+{tip}
+vi secrets.php
+{tip}
+1. #* Set the following variables to match your database configuration:
+1. #** *$vclhost*
+1. #** *$vcldb*
+1. #** *$vclusername*
+1. #** *$vclpassword*
+1. #* Create random passwords for the following variables:
+1. #** *$mcryptkey*
+1. #** *$mcryptiv* (must be 8 hex characters)
+1. #** *$pemkey*
+1. #* Save the secrets.php file
+1. # Run the *genkeys.sh*&nbsp;script.&nbsp; Enter the value you set for
+*$pemkey* in secrets.php as the passphrase (3 times, copy/paste is a good
+idea)
+{tip}
+./genkeys.sh
+{tip}
+1. # Copy *conf-default.php* to *conf.php*:
+{tip}
+cp conf-default.php conf.php
+{tip}
+1. # Modify *conf.php* to match your site
+{tip}vi conf.php{tip}
+{info}Modify every entry under *"Things in this section must be modified"*.
+Descriptions and pointers for each value are included within
+conf.php.{info}
+1. #* *COOKIEDOMAIN* \- set this to the domain name your web server is using
+or leave it blank if you are only accessing the web server by its IP
+address
+1. # Set the owner of the *.ht-inc/maintenance* directory to the web server
+user (normally 'apache'):
+{tip}chown apache maintenance{tip}
+1. # Optionally, you can [install phpseclib and apply a patch](vcl:patch-to-remove-mcrypt-dependency.html)
+ to remove the requirement of having mcrypt installed
+1. # Open the *testsetup.php* page in a web browser:
+1. #* If you set up your site to be [https://my.server.org/vcl/](https://my.server.org/vcl/)
+ open [https://my.server.org/vcl/testsetup.php]
+1. #* Debug any issues reported by testsetup.php
+1. h2. Log In to the VCL Website
+1. # Open the index.php page in your browser ([https://my.server.org/vcl/index.php](https://my.server.org/vcl/index.php)
+)
+1. #* Select *Local Account*
+1. #* Username: *admin*
+1. #* Password: *adminVc1passw0rd*
+1. # Set the admin user password (optional):
+1. ## Click *User Preferences*
+1. ## Enter the current password: *adminVc1passw0rd*
+1. ## Enter a new password
+1. ## Click *Submit Changes*
+1. h2. Add a Management Node to the Database
+1. # Click the *Management Nodes* link
+1. ## Click *Add*
+1. ## Fill in these&nbsp;required fields:
+1. ##* *Hostname -* The name of&nbsp;the management node server. This value
+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;_hostname_ command. For
+example, if you are installing all of the VCL components on the same
+machine you can set this value to _localhost_.
+{info}Take note of the value you enter for Hostname.&nbsp;In a later step performed during the&nbsp;[management node installation](vcl:vcl-2.2.1-management-node-installation.html)
+, 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}
+1. ##* *IP address* \- the public IP address of the management node
+1. ##* *SysAdmin Email Address* \- error emails will be sent to this address
+1. ##* *Install Path* \- this is parent directory under which image files
+will be stored - only required if doing bare metal installs or using VMWare
+with local disks
+1. ##* *End Node SSH Identity Key Files* \- enter /etc/vcl/vcl.key unless you
+know you are using a different SSH identity key file
+1. ## Optionally, fill in these fields:
+1. ##* *Address for Shadow Emails* \- End users are sent various emails about
+the status of their reservations. If this field is configured, copies of
+all of those emails will be sent to this address.
+1. ##* *Public NIC configuration method* \- this defaults to Dynamic DHCP -
+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
+1. # Click *Confirm Management Node*
+1. # Click *Submit*
+1. # Click the *Management Nodes* link
+1. ## Select *Edit Management Node Grouping*
+1. ## Click *Submit*
+1. ## Select the checkbox for your management node
+1. ## Click *Submit Changes*
+
+[Further steps if using only VMWare](vcl-2.2.1---further-steps-if-using-vmware.html)
+
+
+
+
+
+[Further steps if using xCAT](vcl-2.2.1---further-steps-if-using-xcat.html)
+
+
+
+
+
+
+<a name="VCL2.2.1WebCodeInstallation-*Adding&nbsp;LocalVCLAccounts*"></a>
+## *Adding&nbsp;Local VCL Accounts*
+
+Local VCL accounts are&nbsp;contained within the VCL database.&nbsp; The
+*admin* 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 *VCL Base Module*
+1. Select *Add Local VCL User Account*
+1. Enter the requested information
+
+<a name="VCL2.2.1WebCodeInstallation-AddingLDAPAuthentication"></a>
+## Adding LDAP Authentication
+
+Follow the instruction on the&nbsp;[Adding LDAP Authentication](vcl-2.2.1---adding-ldap-authentication.html)
+ page.
+
+  
+  
+----
+Previous Step: [VCL:VCL 2.2.1 Database Installation](vcl:vcl-2.2.1-database-installation.html)
+Next Step: [VCL:VCL 2.2.1 Management Node Installation](vcl:vcl-2.2.1-management-node-installation.html)

Added: vcl/site/trunk/content/confluence_export/vcl-2.2.1.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/vcl-2.2.1.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/vcl-2.2.1.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/vcl-2.2.1.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,264 @@
+Title: VCL 2.2.1
+<a name="VCL2.2.1-TableofContents"></a>
+## Table of Contents
+   * [Download links](#VCL2.2.1-Downloadlinks)
+   * [Release Notes](#VCL2.2.1-ReleaseNotes)
+         * [I. Intro and Description](#VCL2.2.1-I.IntroandDescription)
+         * [II. VCL Roadmap](#VCL2.2.1-II.VCLRoadmap)
+         * [III. Getting Involved in the ASF VCL Community](#VCL2.2.1-III.GettingInvolvedintheASFVCLCommunity)
+         * [IV. How to Submit Bugs and Feature Requests](#VCL2.2.1-IV.HowtoSubmitBugsandFeatureRequests)
+   * [Change Log](#VCL2.2.1-ChangeLog)
+         * [Bug](#VCL2.2.1-Bug)
+         * [Improvement](#VCL2.2.1-Improvement)
+         * [New Feature](#VCL2.2.1-NewFeature)
+
+<a name="VCL2.2.1-Downloadlinks"></a>
+## Download links
+
+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 *make sure* you verify it with MD5 or SHA1 sums *AND* the
+GPG signature (sums and signature files should be downloaded directly from
+Apache, not from mirrors).
+
+[Download ASF VCL 2.2.1](http://www.apache.org/dyn/closer.cgi/incubator/vcl/apache-VCL-2.2.1-incubating.tar.bz2)
+[GPG Signature](http://www.apache.org/dist/incubator/vcl/apache-VCL-2.2.1-incubating.tar.bz2.asc)
+[MD5 Sum](http://www.apache.org/dist/incubator/vcl/apache-VCL-2.2.1-incubating.tar.bz2.md5)
+[SHA1 Sum](http://www.apache.org/dist/incubator/vcl/apache-VCL-2.2.1-incubating.tar.bz2.sha1)
+[VCL KEYS file](http://www.apache.org/dist/incubator/vcl/KEYS)
+
+
+
+
+
+
+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
+
+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
+
+To verify the GPG signature (you'll need to have [GnuPG](http://www.gnupg.org/)
+ 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
+
+For new installs, visit the on-line [installation guide](vcl-2.2.1-installation.html)
+.
+
+For upgrades from version 2.2, visit the on-line [upgrade guide](vcl:upgrade-from-previous-version-(2.2-to-2.2.1).html)
+.
+For upgrades from version 2.1, visit the on-line [upgrade guide for upgrading from 2.1](vcl:upgrade-from-previous-version-(2.1-to-2.2.1).html)
+.
+
+
+<a name="VCL2.2.1-ReleaseNotes"></a>
+## Release Notes
+
+<a name="VCL2.2.1-I.IntroandDescription"></a>
+#### I. Intro and Description
+
+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.
+
+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.
+
+Also using the scheduling API it can be used to automate the provisioning
+of servers in a server farm or HPC cluster.
+
+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.
+
+<a name="VCL2.2.1-II.VCLRoadmap"></a>
+#### II. VCL Roadmap
+
+VCL 2.2.1 (this release)
+* removed frontend dependency on jpgraph
+* remove any access control that is hard coded in frontend
+* added support for VirtualBox hypervisor
+* many bug fixes and improvements to VMWare support
+
+VCL 2.3
+* Service deployments
+* power management
+* improve cluster reservations
+
+VCL 2.4
+* additional and improved hypervisor support
+* KVM and possibly others (virtual box and XEN)
+* Allow for additional access methods for environments (port, other
+protocols, etc)
+
+VCL 2.5
+* develop tools for managing both system and user storage
+
+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.
+
+<a name="VCL2.2.1-III.GettingInvolvedintheASFVCLCommunity"></a>
+#### III. Getting Involved in the ASF VCL Community
+
+There are five ways to become involved in the ASF VCL community.
+
+* 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
+[vcl-user-subscribe@incubator.apache.org](mailto:vcl-user-subscribe@incubator.apache.org|click-to-subscribe.html)
+. To join vcl-dev, send an empty
+message to [vcl-dev-subscribe@incubator.apache.org](mailto:vcl-dev-subscribe@incubator.apache.org|click-to-subscribe.html)
+.
+
+* Submit bug reports and feature requests to our JIRA bug tracking system.
+See section IV below for more information on doing this.
+
+* Create documentation on our Confluence site. Create an account at [http://cwiki.apache.org/confluence/display/VCL/Index](http://cwiki.apache.org/confluence/display/VCL/Index)
+ 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.)
+
+* 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.
+
+* 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.
+
+* 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.
+
+
+<a name="VCL2.2.1-IV.HowtoSubmitBugsandFeatureRequests"></a>
+#### IV. How to Submit Bugs and Feature Requests
+
+If you find a bug, please submit a bug report to our JIRA bug tracking
+system at [http://issues.apache.org/jira/browse/VCL](http://issues.apache.org/jira/browse/VCL)
+ (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.
+
+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.
+
+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.
+
+<a name="VCL2.2.1-ChangeLog"></a>
+## Change Log
+
+
+Release Notes - VCL - Version 2.2.1
+
+<a name="VCL2.2.1-Bug"></a>
+#### Bug
+
+* \[[VCL-113](https://issues.apache.org/jira/browse/VCL-113)
+\] -	     inconsistances with "None" user group
+* \[[VCL-116](https://issues.apache.org/jira/browse/VCL-116)
+\] -	     manage groups interface doesn't correctly handle user groups
+with editusergroupid set to NULL
+* \[[VCL-152](https://issues.apache.org/jira/browse/VCL-152)
+\] -	     problem removing vm from vmhost when vm in reloading state
+without a reservation
+* \[[VCL-361](https://issues.apache.org/jira/browse/VCL-361)
+\] -	     Error is displayed on pages showing image list if last used
+image is deleted
+* \[[VCL-395](https://issues.apache.org/jira/browse/VCL-395)
+\] -	     cannot add new vmprofiles
+* \[[VCL-397](https://issues.apache.org/jira/browse/VCL-397)
+\] -	     Hostname not set on Linux computers if DNS is not configured
+remotely
+* \[[VCL-411](https://issues.apache.org/jira/browse/VCL-411)
+\] -	     Legacy VCL logon and logoff scripts may not be deleted during
+capture causing immediate user logoff
+* \[[VCL-412](https://issues.apache.org/jira/browse/VCL-412)
+\] -	     clicking on tomaintenance reload reservation in timetable
+gives an error
+* \[[VCL-436](https://issues.apache.org/jira/browse/VCL-436)
+\] -	     Predictive Level_1 reload module - can select wrong image for
+computer
+* \[[VCL-437](https://issues.apache.org/jira/browse/VCL-437)
+\] -	     delete image/reservation bug
+* \[[VCL-439](https://issues.apache.org/jira/browse/VCL-439)
+\] -	     trailing commas in statistics.js keeps graphs from showing in
+IE on stats page
+* \[[VCL-440](https://issues.apache.org/jira/browse/VCL-440)
+\] -	     dashboard last 12 hours of reservations graph not positioned
+correctly in IE in compatibility mode
+
+<a name="VCL2.2.1-Improvement"></a>
+#### Improvement
+
+* \[[VCL-140](https://issues.apache.org/jira/browse/VCL-140)
+\] -	     General variable table
+* \[[VCL-310](https://issues.apache.org/jira/browse/VCL-310)
+\] -	     remove jpgraph dependency
+* \[[VCL-312](https://issues.apache.org/jira/browse/VCL-312)
+\] -	     remove View Mode and any uses of user.adminlevelid
+* \[[VCL-373](https://issues.apache.org/jira/browse/VCL-373)
+\] -	     Enable Windows Server 2008 RDP audio - it's disabled by
+default
+* \[[VCL-394](https://issues.apache.org/jira/browse/VCL-394)
+\] -	     Backend VMware improvements for 2.2.1 release
+* \[[VCL-414](https://issues.apache.org/jira/browse/VCL-414)
+\] -	     modify XMLRPCaddUserGroup to accept a paramter specifying
+value for custom field
+* \[[VCL-424](https://issues.apache.org/jira/browse/VCL-424)
+\] -	     Remove unused variables from subroutines in backend modules
+* \[[VCL-425](https://issues.apache.org/jira/browse/VCL-425)
+\] -	     modify scheduler to be aware of RAM allocated to VMs on each
+VM host
+* \[[VCL-426](https://issues.apache.org/jira/browse/VCL-426)
+\] -	     modify scheduler to not give user same computer if user had
+very recent, short reservation and other computers are available
+
+<a name="VCL2.2.1-NewFeature"></a>
+#### New Feature
+
+* \[[VCL-232](https://issues.apache.org/jira/browse/VCL-232)
+\] -	     add way to delete multiple computers
+* \[[VCL-401](https://issues.apache.org/jira/browse/VCL-401)
+\] -	     add manageMapping resource attribute to control resource
+mapping
+* \[[VCL-403](https://issues.apache.org/jira/browse/VCL-403)
+\] -	     make the scheduler aware of image and machine types so that
+virtual and bare images and computers can be mixed
+* \[[VCL-405](https://issues.apache.org/jira/browse/VCL-405)
+\] -	     create provisioningOSinstalltype table to map provisioning
+methods to OSinstalltypes
+* \[[VCL-406](https://issues.apache.org/jira/browse/VCL-406)
+\] -	     add some charts to see how machines are allocated to block
+allocations

Added: vcl/site/trunk/content/confluence_export/vcl-2.2.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/vcl-2.2.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/vcl-2.2.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/vcl-2.2.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,511 @@
+Title: VCL 2.2
+<a name="VCL2.2-TableofContents"></a>
+## Table of Contents
+   * [Download links](#VCL2.2-Downloadlinks)
+   * [Release Notes](#VCL2.2-ReleaseNotes)
+         * [I. Intro and Description](#VCL2.2-I.IntroandDescription)
+         * [II. VCL Roadmap](#VCL2.2-II.VCLRoadmap)
+         * [III. Getting Involved in the ASF VCL Community](#VCL2.2-III.GettingInvolvedintheASFVCLCommunity)
+         * [IV. How to Submit Bugs and Feature Requests](#VCL2.2-IV.HowtoSubmitBugsandFeatureRequests)
+   * [Change Log](#VCL2.2-ChangeLog)
+         * [Bug](#VCL2.2-Bug)
+         * [Improvement](#VCL2.2-Improvement)
+         * [New Feature](#VCL2.2-NewFeature)
+         * [Task](#VCL2.2-Task)
+
+<a name="VCL2.2-Downloadlinks"></a>
+## Download links
+
+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 *make sure* you verify it with MD5 or SHA1 sums *AND* the
+GPG signature (sums and signature files should be downloaded directly from
+Apache, not from mirrors).
+
+[Download ASF VCL 2.2](http://www.apache.org/dyn/closer.cgi/incubator/vcl/apache-VCL-2.2-incubating.tar.bz2)
+[GPG Signature](http://www.apache.org/dist/incubator/vcl/apache-VCL-2.2-incubating.tar.bz2.asc)
+[MD5 Sum](http://www.apache.org/dist/incubator/vcl/apache-VCL-2.2-incubating.tar.bz2.md5)
+[SHA1 Sum](http://www.apache.org/dist/incubator/vcl/apache-VCL-2.2-incubating.tar.bz2.sha1)
+[VCL KEYS file](http://www.apache.org/dist/incubator/vcl/KEYS)
+
+
+
+
+
+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
+
+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
+
+To verify the GPG signature (you'll need to have [GnuPG](http://www.gnupg.org/)
+ 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
+
+For new installs, visit the on-line [installation guide](vcl-2.2-installation.html)
+.
+
+For upgrades from version 2.1, visit the on-line [upgrade guide](vcl:upgrade-from-previous-version.html)
+.
+
+
+
+<a name="VCL2.2-ReleaseNotes"></a>
+## Release Notes
+
+<a name="VCL2.2-I.IntroandDescription"></a>
+#### I. Intro and Description
+
+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.
+
+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.
+
+Also using the scheduling API it can be used to automate the provisioning
+of servers in a server farm or HPC cluster.
+
+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.
+
+<a name="VCL2.2-II.VCLRoadmap"></a>
+#### II. VCL Roadmap
+
+VCL 2.2 (this release)
+* support for xCAT 2.x
+* VMWare Free Server 2.x and ESXi 4
+* improve block reservations (renamed to block allocations)
+
+VCL 2.3
+* Service deployments
+* power management
+* improve cluster reservations
+
+VCL 2.4
+* additional and improved hypervisor support
+* KVM and possibly others (virtual box and XEN)
+* Allow for additional access methods for environments (port, other
+protocols, etc)
+
+VCL 2.5
+* develop tools for managing both system and user storage
+
+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.
+
+<a name="VCL2.2-III.GettingInvolvedintheASFVCLCommunity"></a>
+#### III. Getting Involved in the ASF VCL Community
+
+There are five ways to become involved in the ASF VCL community.
+
+* 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
+[vcl-user-subscribe@incubator.apache.org](mailto:vcl-user-subscribe@incubator.apache.org|click-to-subscribe.html)
+. To join vcl-dev, send an empty
+message to [vcl-dev-subscribe@incubator.apache.org](mailto:vcl-dev-subscribe@incubator.apache.org|click-to-subscribe.html)
+.
+
+* Submit bug reports and feature requests to our JIRA bug tracking system.
+See section IV below for more information on doing this.
+
+* Create documentation on our Confluence site. Create an account at [http://cwiki.apache.org/confluence/display/VCL/Index](http://cwiki.apache.org/confluence/display/VCL/Index)
+ 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.)
+
+* 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.
+
+* 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.
+
+* 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.
+
+
+<a name="VCL2.2-IV.HowtoSubmitBugsandFeatureRequests"></a>
+#### IV. How to Submit Bugs and Feature Requests
+
+If you find a bug, please submit a bug report to our JIRA bug tracking
+system at [http://issues.apache.org/jira/browse/VCL](http://issues.apache.org/jira/browse/VCL)
+ (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.
+
+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.
+
+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.
+
+<a name="VCL2.2-ChangeLog"></a>
+## Change Log
+
+
+      Release Notes - VCL - Version 2.2
+
+<a name="VCL2.2-Bug"></a>
+####    Bug 
+
+* \[[VCL-121](https://issues.apache.org/jira/browse/VCL-121)
+\] -	     special characters in API passwords not handled correctly 
+* \[[VCL-150](https://issues.apache.org/jira/browse/VCL-149)
+\] -	     Pages do not display correctly with IE8 
+* \[[VCL-154](https://issues.apache.org/jira/browse/VCL-154)
+\] -	     run_scp_command() is not catching permission denied errors 
+* \[[VCL-158](https://issues.apache.org/jira/browse/VCL-158)
+\] -	     utils.pm setstaticaddress() does not work correctly for
+Windows 
+* \[[VCL-159](https://issues.apache.org/jira/browse/VCL-159)
+\] -	     xCAT.pm is not always waiting long enough for ssh to respond
+on load 
+* \[[VCL-160](https://issues.apache.org/jira/browse/VCL-160)
+\] -	     Sysprep is overwriting DevicePath key after spdrvscn.exe runs 
+* \[[VCL-165](https://issues.apache.org/jira/browse/VCL-165)
+\] -	     Fix syntax bugs cause reservation processes to die 
+* \[[VCL-181](https://issues.apache.org/jira/browse/VCL-181)
+\] -	     VCL desktop request tool - use API to make reservations 
+* \[[VCL-189](https://issues.apache.org/jira/browse/VCL-189)
+\] -	     cannot add a computer in maintenance state 
+* \[[VCL-193](https://issues.apache.org/jira/browse/VCL-193)
+\] -	     IP address field not large enough for 15-characters 
+* \[[VCL-194](https://issues.apache.org/jira/browse/VCL-194)
+\] -	     Marking new computer to be &quot;maintenance&quot; status
+causes indexing error 
+* \[[VCL-197](https://issues.apache.org/jira/browse/VCL-197)
+\] -	     _is_user_added routine  
+* \[[VCL-210](https://issues.apache.org/jira/browse/VCL-210)
+\] -	     getdynamicaddress returns 127.0.01 for missing public adapter 
+* \[[VCL-214](https://issues.apache.org/jira/browse/VCL-214)
+\] -	     Windows modules don't always disable autoadminlogon 
+* \[[VCL-215](https://issues.apache.org/jira/browse/VCL-215)
+\] -	     reservation_failed sub in State.pm may change state of
+computer currently in maintenance 
+* \[[VCL-220](https://issues.apache.org/jira/browse/VCL-220)
+\] -	     VMs in the available state which aren't assigned to a VM host
+may be reserved 
+* \[[VCL-221](https://issues.apache.org/jira/browse/VCL-221)
+\] -	     Add check to make sure post_load tasks have run before
+reserving a computer 
+* \[[VCL-227](https://issues.apache.org/jira/browse/VCL-227)
+\] -	     deleting user group that owns a resource group 
+* \[[VCL-233](https://issues.apache.org/jira/browse/VCL-233)
+\] -	     all calls to simpleAddRequest need to check for all return
+codes 
+* \[[VCL-241](https://issues.apache.org/jira/browse/VCL-241)
+\] -	     detailed loading summary does not compute times correctly for
+future reservations that are preloaded 
+* \[[VCL-242](https://issues.apache.org/jira/browse/VCL-242)
+\] -	     currentimage.txt permissions incorrect set 
+* \[[VCL-245](https://issues.apache.org/jira/browse/VCL-245)
+\] -	     esx.pm - always reloads  
+* \[[VCL-250](https://issues.apache.org/jira/browse/VCL-250)
+\] -	     authentication for XML RPC X-User doesn't properly check to
+see if no authtype was found 
+* \[[VCL-258](https://issues.apache.org/jira/browse/VCL-258)
+\] -	     cluster loads - cluster_info file 
+* \[[VCL-260](https://issues.apache.org/jira/browse/VCL-260)
+\] -	     Problems occur if root is not the owner of /home/root for
+Windows images 
+* \[[VCL-261](https://issues.apache.org/jira/browse/VCL-261)
+\] -	     Windows.pm filesystem_entry_exists() subroutine may return
+true even if output contains &quot;file not found&quot; 
+* \[[VCL-262](https://issues.apache.org/jira/browse/VCL-262)
+\] -	     Windows capture may remove &quot;Log on as a service&quot;
+right for existing accounts 
+* \[[VCL-265](https://issues.apache.org/jira/browse/VCL-265)
+\] -	     Linux adduser cmd - remove uid parameter if uid not defined in
+user table  
+* \[[VCL-266](https://issues.apache.org/jira/browse/VCL-266)
+\] -	     New process detects another reload process being complete
+before it should 
+* \[[VCL-267](https://issues.apache.org/jira/browse/VCL-267)
+\] -	     cluster loads  listing wrong parent and child addresses
+cluster_info file 
+* \[[VCL-269](https://issues.apache.org/jira/browse/VCL-269)
+\] -	     Windows.pm logoff_users() does not detect disconnected users 
+* \[[VCL-273](https://issues.apache.org/jira/browse/VCL-273)
+\] -	     Single quotes in image pretty name can cause image capture to
+fail 
+* \[[VCL-299](https://issues.apache.org/jira/browse/VCL-299)
+\] -	     shib users may have incorrect full name and email address. 
+* \[[VCL-300](https://issues.apache.org/jira/browse/VCL-300)
+\] -	     shib users always have email notices turned off 
+* \[[VCL-303](https://issues.apache.org/jira/browse/VCL-303)
+\] -	     tomaintenance reservations inserting wrong image revision 
+* \[[VCL-306](https://issues.apache.org/jira/browse/VCL-306)
+\] -	     Web GUI code has hard coded Eastern Time Zone information -
+breaks in other time zones 
+* \[[VCL-307](https://issues.apache.org/jira/browse/VCL-307)
+\] -	     add empty post_reserve routine UnixLab.pm OS module 
+* \[[VCL-317](https://issues.apache.org/jira/browse/VCL-317)
+\] -	     scheduler doesn't take imagerevision into account 
+* \[[VCL-318](https://issues.apache.org/jira/browse/VCL-318)
+\] -	     API error if invalid affiliation is used 
+* \[[VCL-325](https://issues.apache.org/jira/browse/VCL-325)
+\] -	     removing a subimage from a cluster can result in all subimages
+getting removed 
+* \[[VCL-327](https://issues.apache.org/jira/browse/VCL-327)
+\] -	     set_computer_name.vbs causes Sysprep to hang if certain
+applications are installed 
+* \[[VCL-329](https://issues.apache.org/jira/browse/VCL-329)
+\] -	     DataStructure.pm get_computer_private_ip_address() not
+handling all valid formats in /etc/hosts 
+* \[[VCL-331](https://issues.apache.org/jira/browse/VCL-331)
+\] -	     Windows code does not handle special characters in Scheduled
+Task names when changing passwords 
+* \[[VCL-332](https://issues.apache.org/jira/browse/VCL-332)
+\] -	     cannot delete block requests once the start date has passed 
+* \[[VCL-333](https://issues.apache.org/jira/browse/VCL-333)
+\] -	     DataStructure %ENV hash not get detected in _initialize
+routine  
+* \[[VCL-334](https://issues.apache.org/jira/browse/VCL-334)
+\] -	     numeric userids are not handled correctly 
+* \[[VCL-337](https://issues.apache.org/jira/browse/VCL-337)
+\] -	     Windows.pm delete_files_by_pattern may delete unintended files
+if an environment variable isn't defined 
+* \[[VCL-338](https://issues.apache.org/jira/browse/VCL-338)
+\] -	     vmprofiles that are in use can be deleted 
+* \[[VCL-340](https://issues.apache.org/jira/browse/VCL-340)
+\] -	     cannot change name of vmprofile 
+* \[[VCL-346](https://issues.apache.org/jira/browse/VCL-346)
+\] -	     getdynamicaddress routine regex issue 
+* \[[VCL-347](https://issues.apache.org/jira/browse/VCL-347)
+\] -	     cluster connect page rdp file 
+* \[[VCL-349](https://issues.apache.org/jira/browse/VCL-349)
+\] -	     sql insert queries for image and imagerevision tables 
+* \[[VCL-353](https://issues.apache.org/jira/browse/VCL-353)
+\] -	     vmware.pm inserting new images - if original name is not in
+proper format $oldname does not get set correctly. 
+* \[[VCL-356](https://issues.apache.org/jira/browse/VCL-356)
+\] -	     vmware esx pm - vmware image directories 
+* \[[VCL-362](https://issues.apache.org/jira/browse/VCL-362)
+\] -	     vmware.pm power command output not detected under ESX 3.5 
+* \[[VCL-363](https://issues.apache.org/jira/browse/VCL-363)
+\] -	     Passwords for existing Linux accounts are reset when the root
+password is set 
+* \[[VCL-364](https://issues.apache.org/jira/browse/VCL-364)
+\] -	     vmhostid removed when vm put in maintenance state 
+* \[[VCL-368](https://issues.apache.org/jira/browse/VCL-368)
+\] -	     pre-capture and post load linux steps correct sed cmd line
+options 
+* \[[VCL-370](https://issues.apache.org/jira/browse/VCL-370)
+\] -	     Reservation ID not defined errors occur for cluster
+reservations 
+* \[[VCL-371](https://issues.apache.org/jira/browse/VCL-371)
+\] -	     Private IP address is not being found in /etc/hosts under some
+circumstances 
+* \[[VCL-377](https://issues.apache.org/jira/browse/VCL-377)
+\] -	     multiple clicks on Create Reservation button gives multiple
+reservations 
+* \[[VCL-378](https://issues.apache.org/jira/browse/VCL-378)
+\] -	     reservation can be extended into a block allocation for user
+not in block group 
+* \[[VCL-382](https://issues.apache.org/jira/browse/VCL-382)
+\] -	     vmware.pm incorrectly handles free server with network
+datastores 
+
+<a name="VCL2.2-Improvement"></a>
+####    Improvement 
+
+* \[[VCL-2](https://issues.apache.org/jira/browse/VCL-2)
+\] -	     migrate preferredimage to nextimage 
+* \[[VCL-9](https://issues.apache.org/jira/browse/VCL-9)
+\] -	     Update reclaim.pm to use DataStructure methods 
+* \[[VCL-11](https://issues.apache.org/jira/browse/VCL-11)
+\] -	     Update blockrequest.pm to use database subroutines 
+* \[[VCL-31](https://issues.apache.org/jira/browse/VCL-31)
+\] -	     rename conf.php and secrets.php to include -default in the
+name 
+* \[[VCL-32](https://issues.apache.org/jira/browse/VCL-32)
+\] -	     modify XMLRPCaddRequest to allow an end time to be specified 
+* \[[VCL-93](https://issues.apache.org/jira/browse/VCL-93)
+\] -	     LDAP part of a login to fail silently on errors when
+Shibboleth authentication is used 
+* \[[VCL-94](https://issues.apache.org/jira/browse/VCL-94)
+\] -	     Rework image capture flow 
+* \[[VCL-98](https://issues.apache.org/jira/browse/VCL-98)
+\] -	     upgrade all of dojo-0.4.0 code to recent version of dojo 
+* \[[VCL-125](https://issues.apache.org/jira/browse/VCL-125)
+\] -	     Add ability to control whether or not users have
+root/administrator access 
+* \[[VCL-137](https://issues.apache.org/jira/browse/VCL-137)
+\] -	     Update vmware.pm to use provisioning module interface
+subroutine names 
+* \[[VCL-145](https://issues.apache.org/jira/browse/VCL-145)
+\] -	     Store product keys in the database 
+* \[[VCL-148](https://issues.apache.org/jira/browse/VCL-148)
+\] -	     Add management node to current reservations view for
+ADMIN_DEVELOPER 
+* \[[VCL-149](https://issues.apache.org/jira/browse/VCL-149)
+\] -	     Prevent multiple vcld processes 
+* \[[VCL-153](https://issues.apache.org/jira/browse/VCL-153)
+\] -	     Update interface subroutines in xCAT21.pm to match xCAT.pm 
+* \[[VCL-155](https://issues.apache.org/jira/browse/VCL-155)
+\] -	     Decrease initial Current Reservation page refresh interval 
+* \[[VCL-161](https://issues.apache.org/jira/browse/VCL-161)
+\] -	     remove  xmlrpcKey table from vcl.sql  
+* \[[VCL-162](https://issues.apache.org/jira/browse/VCL-162)
+\] -	     create structure to add throttling to provisioning modules 
+* \[[VCL-163](https://issues.apache.org/jira/browse/VCL-163)
+\] -	     move throttle variable from vcld.conf to managment node table 
+* \[[VCL-164](https://issues.apache.org/jira/browse/VCL-164)
+\] -	     Make installation and configuration easier 
+* \[[VCL-200](https://issues.apache.org/jira/browse/VCL-200)
+\] -	     add edit node name option in Privilege tree 
+* \[[VCL-204](https://issues.apache.org/jira/browse/VCL-204)
+\] -	     remove private ssh identity keys from known locations- post
+load / pre-capture routines 
+* \[[VCL-206](https://issues.apache.org/jira/browse/VCL-206)
+\] -	     Alphabetize list of virtual hosts 
+* \[[VCL-211](https://issues.apache.org/jira/browse/VCL-211)
+\] -	     image creation mode - administrator timeout 
+* \[[VCL-223](https://issues.apache.org/jira/browse/VCL-223)
+\] -	     Remove information user should not be able to access on
+post_load 
+* \[[VCL-224](https://issues.apache.org/jira/browse/VCL-224)
+\] -	     Move settings from vcld.conf to database except for database
+connection settings 
+* \[[VCL-244](https://issues.apache.org/jira/browse/VCL-244)
+\] -	     Staticics page - show number of failed loads per image 
+* \[[VCL-248](https://issues.apache.org/jira/browse/VCL-248)
+\] -	     Update provisioning modules' node_status to return READY if
+SSH works but ping doesn't 
+* \[[VCL-251](https://issues.apache.org/jira/browse/VCL-251)
+\] -	     Make &quot;Later&quot; reservation time default to a time in
+the future. 
+* \[[VCL-252](https://issues.apache.org/jira/browse/VCL-252)
+\] -	     XMLHttpTransport Error 
+* \[[VCL-254](https://issues.apache.org/jira/browse/VCL-254)
+\] -	     block request improvements 
+* \[[VCL-255](https://issues.apache.org/jira/browse/VCL-255)
+\] -	     xmlrpc_call routine add better error control 
+* \[[VCL-271](https://issues.apache.org/jira/browse/VCL-271)
+\] -	     clean out unused routines 
+* \[[VCL-272](https://issues.apache.org/jira/browse/VCL-272)
+\] -	     block request form 
+* \[[VCL-275](https://issues.apache.org/jira/browse/VCL-275)
+\] -	     Predictive reloading level_1 module 
+* \[[VCL-284](https://issues.apache.org/jira/browse/VCL-284)
+\] -	     vmware.pm power_reset sub does not catch error if VMware tools
+are not running 
+* \[[VCL-286](https://issues.apache.org/jira/browse/VCL-286)
+\] -	     post_linux load operation - set hostname that matches public
+IP address 
+* \[[VCL-288](https://issues.apache.org/jira/browse/VCL-288)
+\] -	     Add Global affiliation to schema 
+* \[[VCL-293](https://issues.apache.org/jira/browse/VCL-293)
+\] -	     check for remote ldap server being up before connecting to it 
+* \[[VCL-295](https://issues.apache.org/jira/browse/VCL-295)
+\] -	     Combine normal new reservation and imaging new reservation
+code 
+* \[[VCL-302](https://issues.apache.org/jira/browse/VCL-302)
+\] -	     provide feedback to users about block reservation status 
+* \[[VCL-305](https://issues.apache.org/jira/browse/VCL-305)
+\] -	     update code to work with php 5.3 
+* \[[VCL-314](https://issues.apache.org/jira/browse/VCL-314)
+\] -	     change Documentation link to have links to ASF docs 
+* \[[VCL-320](https://issues.apache.org/jira/browse/VCL-320)
+\] -	     random selection of computer for reservations 
+* \[[VCL-326](https://issues.apache.org/jira/browse/VCL-326)
+\] -	     Shutdown Event Tracker causes autologin to fail 
+* \[[VCL-335](https://issues.apache.org/jira/browse/VCL-335)
+\] -	     max allowed ram for computers needs to be increased 
+* \[[VCL-357](https://issues.apache.org/jira/browse/VCL-357)
+\] -	     create update sql script to upgrade to the latest schema 
+* \[[VCL-359](https://issues.apache.org/jira/browse/VCL-359)
+\] -	     Remove DHCP and static IP configuration sections from
+provisioning modules 
+
+<a name="VCL2.2-NewFeature"></a>
+####    New Feature 
+
+* \[[VCL-134](https://issues.apache.org/jira/browse/VCL-134)
+\] -	     Add ability to control whether or not users have
+root/administrator access 
+* \[[VCL-142](https://issues.apache.org/jira/browse/VCL-142)
+\] -	     Add KMS activation server configuration per affiliation 
+* \[[VCL-146](https://issues.apache.org/jira/browse/VCL-146)
+\] -	     add linux support for all VMWare modules 
+* \[[VCL-180](https://issues.apache.org/jira/browse/VCL-180)
+\] -	     add power_X(off,on,reset,status)  routines to provisioning
+modules  
+* \[[VCL-182](https://issues.apache.org/jira/browse/VCL-182)
+\] -	     Linux virtual machine support 
+* \[[VCL-195](https://issues.apache.org/jira/browse/VCL-195)
+\] -	     Add support for Windows Server 2008 
+* \[[VCL-196](https://issues.apache.org/jira/browse/VCL-196)
+\] -	     Add support for 64-bit Windows 
+* \[[VCL-201](https://issues.apache.org/jira/browse/VCL-201)
+\] -	     Add support for Windows Vista VMware images 
+* \[[VCL-208](https://issues.apache.org/jira/browse/VCL-208)
+\] -	     Ability to easily put the VCL site into a maintenance state to
+prevent user access 
+* \[[VCL-239](https://issues.apache.org/jira/browse/VCL-239)
+\] -	     xcat 2.X module 
+* \[[VCL-268](https://issues.apache.org/jira/browse/VCL-268)
+\] -	     OS table - create additional OS ids 
+* \[[VCL-278](https://issues.apache.org/jira/browse/VCL-278)
+\] -	     Add setup mechanism to vcld 
+* \[[VCL-279](https://issues.apache.org/jira/browse/VCL-279)
+\] -	     Add post_load_custom script functionality for Linux images 
+* \[[VCL-292](https://issues.apache.org/jira/browse/VCL-292)
+\] -	     option to save selected authentication method in cookie 
+* \[[VCL-294](https://issues.apache.org/jira/browse/VCL-294)
+\] -	     create a login log 
+* \[[VCL-298](https://issues.apache.org/jira/browse/VCL-298)
+\] -	     Add support for VMware Server 2.x and ESXi 4.x 
+* \[[VCL-301](https://issues.apache.org/jira/browse/VCL-301)
+\] -	     Add support for Windows 7 
+* \[[VCL-351](https://issues.apache.org/jira/browse/VCL-351)
+\] -	     extend vm profile to have more virtualswitches 
+* \[[VCL-352](https://issues.apache.org/jira/browse/VCL-352)
+\] -	     Add additional pre-capture steps for Linux OS 
+* \[[VCL-365](https://issues.apache.org/jira/browse/VCL-365)
+\] -	     change select box for environment on new reservation page to
+dojo filteringselect 
+
+<a name="VCL2.2-Task"></a>
+####    Task 
+
+* \[[VCL-138](https://issues.apache.org/jira/browse/VCL-138)
+\] -	     remove antiquated vcldquery support 
+* \[[VCL-139](https://issues.apache.org/jira/browse/VCL-139)
+\] -	     make users' names optional 
+* \[[VCL-274](https://issues.apache.org/jira/browse/VCL-274)
+\] -	     check for SQL injection / XSS

Added: vcl/site/trunk/content/confluence_export/vcl-2.3---adding-ldap-authentication.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/vcl-2.3---adding-ldap-authentication.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/vcl-2.3---adding-ldap-authentication.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/vcl-2.3---adding-ldap-authentication.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,118 @@
+Title: VCL 2.3 - Adding LDAP Authentication
+<a name="VCL2.3-AddingLDAPAuthentication-*AddingLDAPAuthenciation*"></a>
+## *Adding LDAP Authenciation*
+
+<a name="VCL2.3-AddingLDAPAuthentication-PrerequisitesforyourLDAPserver:"></a>
+### Prerequisites for your LDAP server:
+
+* SSL should be enabled on your LDAP server
+* 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.
+* 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
+
+<a name="VCL2.3-AddingLDAPAuthentication-PrerequisitesforyourVCLwebserver:"></a>
+### Prerequisites for your VCL web server:
+
+* *php-ldap* needs to be installed
+* 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.
+* After adding the certificate, restart httpd:
+{tip}
+service httpd restart
+{tip}
+* 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.
+* You may need to add a line to */etc/openldap/ldap.conf* to point to the
+ca-bundle.crt file. If so, add the following:
+
+    TLS_CACERT /etc/pki/tls/certs/ca-bundle.crt
+
+
+<a name="VCL2.3-AddingLDAPAuthentication-AddingLDAPAuthenticationtotheWebCode"></a>
+### Adding LDAP Authentication to the Web Code
+
+* 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. *Do not* 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}
+* Edit *conf.php* and search for "EXAMPLE1 LDAP"
+* Uncomment the "EXAMPLE1 LDAP" section by removing the '/\*' before it and
+the '\*/' at the end of 'to use this login mechanism'
+* 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.
+* Modify the following fields:
+** *server* \- this is the hostname of your LDAP server - this must match
+the hostname in the certificate.
+** *binddn* \- 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"
+** *userid* \- 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:
+*** %s@example.org
+*** %s@ad.example.org
+*** uid=%s,ou=accounts,dc=example,dc=org'
+** *unityid* \- this is the ldap field that contains a user's login id (for
+Active Directory, this is usually sAMAccountName)
+** *firstname* \- this is the ldap field that contains a user's first name
+** *lastname* \- this is the ldap field that contains a user's last name
+** *email* \- this is the ldap field that contains a user's email address
+** *defaultemail* \- 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.
+** *masterlogin* \- this is the vcllookup account referred to in the
+"Prerequisites for your LDAP server" section - comment out this line if
+using anonymous binds
+** *masterpwd* \- password for the masterlogin account - comment out this
+line if using anonymous binds
+** *affiliationid* \- this is the id from the SELECT statement in the first
+step
+** *lookupuserbeforeauth* \- 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 *lookupuserfield*. 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. 
+** *lookupuserfield* \- If you need to set *lookupuserbeforeauth* to 1, set
+this to the attribute to use to search for the user in ldap. Typical values
+are 'cn', 'uid', and 'samaccountname'.
+** *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
+* Uncomment the *require_once* line for *ldapauth.php* toward the bottom of
+the file

Added: vcl/site/trunk/content/confluence_export/vcl-2.3---further-steps-if-using-vmware.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/vcl-2.3---further-steps-if-using-vmware.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/vcl-2.3---further-steps-if-using-vmware.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/vcl-2.3---further-steps-if-using-vmware.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,263 @@
+Title: VCL 2.3 - Further Steps if Using VMware
+If you are using standalone VMware servers (i.e. ones that VCL did not
+deploy using xCAT), you first need to configure a VM Profile to match your
+setup. Next, add the VMWare servers. Then, you need to add the virtual
+machines. You can either add them individually (Adding Individual VMWare
+Servers/Virtual Machines), or if they have sequential hostnames and IP
+addresses, you can add them all at once (Adding Multiple VMWare
+Servers/Virtual Machines).
+
+Once you have added at least one computer, you can add more computers by
+going to Manage Computers->Edit Computer Information and clicking *Add
+Single Computer* or *Add Multiple Computers*.
+
+1. [Configure VM Profile(s)](vcl-2.3---further-steps-if-using-vmware#vmprofile.html)
+1. [Add VMware Host Servers](vcl-2.3---further-steps-if-using-vmware#addhosts.html)
+1. [Add Virtual Machines](vcl-2.3---further-steps-if-using-vmware#addvms.html)
+1. [Assign Virtual Machine(s) to a Virtual Host](vcl-2.3---further-steps-if-using-vmware#assignvms.html)
+1. [Add entries to dhcpd.conf](vcl-2.3---further-steps-if-using-vmware#adddhcp.html)
+1. [Add entries to /etc/hosts](vcl-2.3---further-steps-if-using-vmware#addetchosts.html)
+
+{anchor:vmprofile}
+
+<a name="VCL2.3-FurtherStepsifUsingVMware-ConfigureVMProfile(s)"></a>
+## Configure VM Profile(s)
+
+1. Click *Virtual Hosts*
+1. Select the *VM Host Profiles* tab
+1. Select a profile whose name matches your setup or click *New Profile...*
+1. # If using an existing profile, click *Configure Profile*
+1. # If creating a new profile:
+1. ## Enter the name of the profile
+1. ## Click *Create Profile*
+1. Configure the profile to match your setup. Hover over any ? icons to get
+further information about that field. More information is available on the [VMware Configuration](vmware-configuration.html)
+ page
+{tip}
+Just click on the text of any field you want to edit to change it. After
+changing it, click somewhere else to save the changed value for that field.
+Changes are immediate; there is no "save" button for this tab.
+{tip}
+
+{anchor:addhosts}
+
+<a name="VCL2.3-FurtherStepsifUsingVMware-AddVMwareHostServers"></a>
+## Add VMware Host Servers
+
+<a name="VCL2.3-FurtherStepsifUsingVMware-AddingIndividualVMwareServers"></a>
+### Adding Individual VMware Servers
+
+1. Click *Manage Computers*
+1. Select the *Add Single Computer* radio button
+1. Click *Submit*
+1. Fill in the following:
+1. * *Hostname*
+1. * *Type* \- blade
+1. * *Public IP Address*
+1. * *Private IP Address* (optional)
+1. * *Public MAC Address* (optional)
+1. * *Private MAC Address* (optional)
+1. * *Provisioning Engine* \- "None"
+1. * *State* \- vmhostinuse
+1. * *VM Host Profile* \- use a default profile or one configured in the
+previous step
+1. * *Owner* \- admin@Local
+1. * *RAM*
+1. * *No. Cores*
+1. * *Processor Speed*
+1. * *Network Speed*
+1. * *Physical Location* (optional)
+1. * Click the checkbox under *allComputers*
+1. Click *Confirm Computer*
+1. Click *Submit*
+{info}The computer you just added isn't listed after clicking Submit. This
+is not a problem.{info}
+
+<a name="VCL2.3-FurtherStepsifUsingVMware-AddingMultipleVMWareServers"></a>
+### Adding Multiple VMWare Servers
+
+1. Click *Manage Computers*
+1. Select the *Add Multiple Computers* radio button
+1. Click *Submit*
+1. Fill in the following:
+1. * *Hostname* \- the hostnames of all the computers must have a numerical
+part that is sequential, use a % as a placeholder where that part would be
+1. * *Start value* \- the first number of the numerical part of the hostname
+1. * *End value* \- the last number of the numerical part of the hostname
+1. * *Type* \- blade
+1. * *Start Public IP Address* \- if using static public addresses, the IP
+addresses must be sequential; enter the first address here; if using DHCP,
+just enter something like 1.1.1.1
+1. * *End Public IP address* \- the last IP address of the sequence; if using
+DHCP, you'll need to enter something that would work out to the last
+address relative to *Start Public IP Address* (i.e. if adding 3 computers,
+use 1.1.1.1 for start and 1.1.1.3 for end)
+1. * *Start Private IP Address* (optional) - the IP addresses must be
+sequential; enter the first private address here
+1. * *End Private IP Address* (optional) - the last IP address of the
+sequence
+1. * *Start MAC Address* (optional) - if MAC addresses are sequential, with
+the first one being the private MAC address for the first computer, the
+second one being the public MAC address for the first computer, the third
+one being the private MAC address of the second computer, etc, you can
+enter the first one here and then have the option of downloading data to
+add to your dhcpd.conf file from the Computer Utilities page
+1. * *Provisioning Engine* \- "None"
+1. * *State* \- vmhostinuse
+1. * *VM Host Profile* \- use a default profile or one configured in the
+previous step
+1. * *Owner* \- admin@Local
+1. * *RAM*
+1. * *No. Cores*
+1. * *Processor Speed*
+1. * *Network Speed*
+1. * *Physical Location* (optional)
+1. * Click the checkbox under *allComputers*
+1. Click *Confirm Computers*
+1. Click *Submit*
+
+{anchor:addvms}
+
+<a name="VCL2.3-FurtherStepsifUsingVMware-AddVirtualMachines"></a>
+## Add Virtual Machines
+
+<a name="VCL2.3-FurtherStepsifUsingVMware-AddingIndividualVirtualMachines"></a>
+### Adding Individual Virtual Machines
+
+1. Click *Manage Computers*
+1. Select *Edit Computer Information*
+1. Click *Submit*
+1. Click *Add Single Computer*
+1. Fill in the following:
+1. * *Hostname*
+1. * *Type* \- virtualmachine
+1. * *Public IP Address*
+1. * *Private IP Address*
+1. * *Public MAC Address*
+1. * *Private MAC Address*
+{note}For VMware virtual machines, the MAC addresses you choose must be in
+the range {color:#008000}{*}00:50:56:00:00:00{*}{color}
+{color:#008000}\-{color}{color:#008000}{*}00:50:56:3F:FF:FF{*}{color}.
+Pay special attention to the upper bound of this range.
+{color:#ff0000}{*}00:50:56:40:00:00{*}{color} {color:#ff0000}\-{color}
+{color:#ff0000}{*}00:50:56:FF:FF:FF{*}{color} are *NOT* valid VMware
+virtual machines.{note}
+1. * *Provisioning Engine* \- VMware
+1. * *State* \- maintenance
+1. * *Owner* \- admin@Local
+1. * *RAM*
+1. * *No. Cores*
+1. * *Processor Speed*
+1. * *Network Speed*
+1. * Check *All VM Computers* and *newvmimages*
+1. Click *Confirm Computer*
+1. Click *Submit*
+
+<a name="VCL2.3-FurtherStepsifUsingVMware-AddingMultipleVirtualMachines"></a>
+### Adding Multiple Virtual Machines
+
+1. Click *Manage Computers*
+1. Select *Edit Computer Information*
+1. Click *Submit*
+1. Click *Add Multiple Computers*
+1. Fill in the following:
+1. * *Hostname* \- the hostnames of all the computers must have a numerical
+part that is sequential, use a % as a placeholder where that part would be
+1. * *Start value* \- the first number of the numerical part of the hostname
+1. * *End value* \- the last number of the numerical part of the hostname
+1. * *Type* \- virtualmachine
+1. * *Start Public IP Address* \- if using static public addresses, the
+Public IP addresses must be sequential; enter the first address here; if
+using DHCP, just enter something like 1.1.1.1
+1. * *End Public IP address* \- the last Public IP address of the sequence;
+if using DHCP, you'll need to enter something that would work out to the
+last address relative to Start IP Address (i.e. if adding 3 computers, use
+1.1.1.1 for start and 1.1.1.3 for end)
+1. * *Start Private IP Address* \- similar to Start Public IP Address, but
+for the private side
+1. * *End Private IP Address* \- similar to the End Public IP Address but for
+the private side
+1. * *Start MAC Address* \- if mac addresses are sequential, with the first
+one being the private MAC address for the first computer, the second one
+being the public MAC address for the first computer, the third one being
+the private MAC address of the second computer, etc, you can enter the
+first one here and then have the option of generating data to add to your
+dhcpd.conf file from the *Computer Utilities* page.
+{note}For VMware virtual machines, the MAC addresses you choose must be in
+the range {color:#008000}{*}00:50:56:00:00:00{*}{color}
+{color:#008000}\-{color}{color:#008000}{*}00:50:56:3F:FF:FF{*}{color}.
+Pay special attention to the upper bound of this range.
+{color:#ff0000}{*}00:50:56:40:00:00{*}{color} {color:#ff0000}\-{color}
+{color:#ff0000}{*}00:50:56:FF:FF:FF{*}{color} are *NOT* valid VMware
+virtual machines.{note}
+1. * *Provisioning Engine* \- VMware
+1. * *State* \- maintenance
+1. * *Owner* \- admin@Local
+1. * *RAM*
+1. * *No. Cores*
+1. * *Processor Speed*
+1. * *Network Speed*
+1. * Check *All VM Computers* and *newvmimages*
+1. Click *Confirm Computers*
+1. Click *Submit*
+
+{anchor:assignvms}
+
+<a name="VCL2.3-FurtherStepsifUsingVMware-AssignVirtualMachine(s)toaVirtualHost"></a>
+## Assign Virtual Machine(s) to a Virtual Host
+
+1. Click *Virtual Hosts*
+1. On the *VM Hosts* tab, select the virtual host server added previously
+1. Click *Configure Host*, You should see VM limit set to a number along
+with the vm profile, two columns of VM's assigned to host and Unassigned
+VMs
+1. Adjust the VM limit to the desired number of vms you would like to run on
+this host.
+{note}
+Please consult your hypervisor documentation for the&nbsp;recommended
+number of virtual machines to run concurrently for your virtual server
+configuration
+{note}
+1. Select the virtual machine nodes from the Unassigned VMs: column
+1. Click Add
+
+{anchor:adddhcp}
+
+<a name="VCL2.3-FurtherStepsifUsingVMware-Addentriestodhcpd.conf"></a>
+## Add entries to dhcpd.conf
+
+You need to add entries for your VMs to your dhcpd.conf file so that they
+will correctly be assigned their private addresses at boot.
+1. Click *Manage Computers*
+1. Select the *All VM Computers* group in the list at the top
+1. Select the *Computer Utilities* radio button
+1. Click *Submit*
+1. Click the *Check All* link at the bottom of the table
+1. Next to *For selected computers, generate computer data for*, select
+*dhcpd*
+1. Click *Generate Data*
+1. Enter the private IP address for your management node
+1. Click *Generate Data*
+1. Copy/Paste the data for dhcpd.conf to the dhcpd.conf file on your
+management node (ignore the part for dhcpd.leases)
+1. Restart dhcpd
+{tip}service dhcpd restart{tip}
+1. Scroll to the bottom and click *Close*
+
+{anchor:addetchosts}
+
+<a name="VCL2.3-FurtherStepsifUsingVMware-Addentriesto/etc/hosts"></a>
+## Add entries to /etc/hosts
+
+You need to add entries for your VM hosts and VMs to /etc/hosts
+1. Click *Manage Computers*
+1. Select the *All VM Computers* and the *allComputers* groups in the list
+at the top
+1. Select the *Computer Utilities* radio button
+1. Click *Submit*
+1. Click the *Check All* link at the bottom of the table
+1. Next to *For selected computers, generate computer data for*, select
+*/etc/hosts*
+1. Click *Generate Data*
+1. Copy/Paste the data to your /etc/hosts file
+1. Click *Close*

Added: vcl/site/trunk/content/confluence_export/vcl-2.3---further-steps-if-using-xcat.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/vcl-2.3---further-steps-if-using-xcat.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/vcl-2.3---further-steps-if-using-xcat.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/vcl-2.3---further-steps-if-using-xcat.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,89 @@
+Title: VCL 2.3 - Further steps if using xCAT
+Once you have added at least one computer, you can add more computers by
+going to Manage Computers->Edit Computer Information and clicking *Add
+Single Computer* or *Add Multiple Computers"*.
+
+<a name="VCL2.3-FurtherstepsifusingxCAT-AddingIndividualComputers"></a>
+### Adding Individual Computers
+
+1. Click *Manage Computers*
+1. Select the *Add Single Computer* radio button
+1. Click *Submit*
+1. Fill in the following:
+1. * *Hostname*
+1. * *Type* - blade
+1. * *Public IP Address*
+1. * *Private IP Address* (optional)
+1. * *Public MAC Address* (optional)
+1. * *Private MAC Address* (optional)
+1. * *Provisioning Engine* - xCAT 2.x
+1. * *State* - available (or maintenance if you do not want it to be
+immediately available)
+1. * *Owner* - admin@Local
+1. * *RAM*
+1. * *No. Cores*
+1. * *Processor Speed*
+1. * *Network Speed*
+1. * *Physical Location* (optional)
+1. * Click the checkboxs under *allComputers* and *newimages*
+1. Click *Confirm Computer*
+1. Click *Submit*
+{info}The computer you just added isn't listed after clicking Submit. This
+is not a problem.{info}
+
+<a name="VCL2.3-FurtherstepsifusingxCAT-AddingMultipleComputers"></a>
+### Adding Multiple Computers
+
+1. Click *Manage Computers*
+1. Select the *Add Multiple Computers* radio button
+1. Click *Submit*
+1. Fill in the following:
+1. * *Hostname* \- the hostnames of all the computers must have a numerical
+part that is sequential, use a % as a placeholder where that part would be
+1. * *Start value* \- the first number of the numerical part of the hostname
+1. * *End value* \- the last number of the numerical part of the hostname
+1. * *Type* \- blade
+1. * *Start Public IP Address* \- if using static public addresses, the IP
+addresses must be sequential; enter the first address here; if using DHCP,
+just enter something like 1.1.1.1
+1. * *End Public IP address* \- the last IP address of the sequence; if using
+DHCP, you'll need to enter something that would work out to the last
+address relative to *Start Public IP Address* (i.e. if adding 3 computers,
+use 1.1.1.1 for start and 1.1.1.3 for end)
+1. * *Start Private IP Address* (optional) - the IP addresses must be
+sequential; enter the first private address here
+1. * *End Private IP Address* (optional) - the last IP address of the
+sequence
+1. * *Start MAC Address* (optional) - if MAC addresses are sequential, with
+the first one being the private MAC address for the first computer, the
+second one being the public MAC address for the first computer, the third
+one being the private MAC address of the second computer, etc, you can
+enter the first one here and then have the option of downloading data to
+add to your dhcpd.conf file from the Computer Utilities page
+1. * *Provisioning Engine* \- xCAT 2.x
+1. * *State* \- available (or maintenance if you do not want them to be
+immediately available)
+1. * *Owner* - owner of the computer
+1. * *RAM*
+1. * *Processor Speed*
+1. * *Network Speed*
+1. * Click the checkboxs under *allComputers* and *newimages*
+1. Click *Confirm Computers*
+1. Click *Submit*
+{info}The computer you just added isn't listed after clicking Submit. This
+is not a problem.{info}
+
+<a name="VCL2.3-FurtherstepsifusingxCAT-Addentriesto/etc/hosts"></a>
+## Add entries to /etc/hosts
+
+You need to add entries for your nodes to /etc/hosts
+1. Click *Manage Computers*
+1. Select the *allComputers* group in the list at the top
+1. Select the *Computer Utilities* radio button
+1. Click *Submit*
+1. Click the *Check All* link at the bottom of the table
+1. Next to *For selected computers, generate computer data for*, select
+*/etc/hosts*
+1. Click *Generate Data*
+1. Copy/Paste the data to your /etc/hosts file
+1. Click *Close*

Added: vcl/site/trunk/content/confluence_export/vcl-2.3-configure-frontend-authentication.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/vcl-2.3-configure-frontend-authentication.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/vcl-2.3-configure-frontend-authentication.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/vcl-2.3-configure-frontend-authentication.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,23 @@
+Title: VCL 2.3 Configure Frontend Authentication
+{excerpt:hidden=true}
+How to configure authentication for the frontend VCL web code using LDAP
+and Local accounts.{excerpt}
+
+<a name="VCL2.3ConfigureFrontendAuthentication-ConfigureFrontendAuthentication"></a>
+# Configure Frontend Authentication
+
+<a name="VCL2.3ConfigureFrontendAuthentication-*AddingLocalVCLAccounts*"></a>
+## *Adding Local VCL Accounts*
+
+Local VCL accounts are contained within the VCL database. The *admin*
+account is a local VCL account. 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 *VCL Base Module*
+1. Select *Add Local VCL User Account*
+1. Enter the requested information
+
+{include:VCL 2.3 - Adding LDAP Authentication}

Added: vcl/site/trunk/content/confluence_export/vcl-2.3-database-installation.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/vcl-2.3-database-installation.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/vcl-2.3-database-installation.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/vcl-2.3-database-installation.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,52 @@
+Title: VCL 2.3 Database Installation
+{excerpt:hidden=true}How to install MySQL Server, create the VCL database,
+and import the VCL database schema{excerpt}
+
+<a name="VCL2.3DatabaseInstallation-Install&ConfiguretheDatabase"></a>
+# Install & Configure the Database
+
+1. h2. Download & Extract the Apache VCL Source
+1. # If you have not already done so, download and the Apache VCL source to
+the database server:
+{tip}wget --trust-server-names
+'{nolink:http://vcl.apache.org/downloads/download.cgi?action=download&filename=%2Fvcl%2Fapache-VCL-2.3.tar.bz2}'{tip}
+1. # Extract the files:
+{tip}tar \-jxvf apache-VCL-2.3.tar.bz2{tip}
+1. h2. Install MySQL Server
+1. # Install MySQL Server 5.x: {tip}yum install mysql-server \-y{tip}
+1. # Configure the MySQL daemon (mysqld) to start automatically:
+{tip}/sbin/chkconfig \--level 345 mysqld on{tip}
+1. # Start the MySQL daemon:
+{tip}/sbin/service mysqld start{tip}
+1. # If the iptables firewall is being used and the web server and management
+nodes will be on different machines, port 3306 should be opend up
+{tip}
+vi /etc/sysconfig/iptables
+{tip}
+
+    -A RH-Firewall-1-INPUT -m state --state NEW -s <web server IP> -p tcp
+--dport 3306 -j ACCEPT
+    -A RH-Firewall-1-INPUT -m state --state NEW -s <management node IP> -p tcp
+--dport 3306 -j ACCEPT
+    service iptables restart
+
+1. h2. Create&nbsp;the VCL Database
+1. # Run the MySQL command-line client: {tip}mysql{tip}
+1. # Create a database:
+{tip}CREATE DATABASE vcl;{tip}
+1. # Create a user with SELECT, INSERT, UPDATE, DELETE, and CREATE TEMPORARY
+TABLES privileges on the database you just created:
+{tip}GRANT SELECT,INSERT,UPDATE,DELETE,CREATE TEMPORARY TABLES ON vcl.\* TO
+'*vcluser*'@'localhost' IDENTIFIED BY '*vcluserpassword*';{tip}
+{note}Replace *vcluser* and *vcluserpassword* with that of the user you
+want to use to connect to the database{note}
+{info}The GRANT command will automatically create the user if it doesn't
+already exist{info}
+1. # Exit the MySQL command-line client: {tip}exit{tip}
+1. # Import the vcl.sql file into the database:
+{tip}mysql vcl < apache-VCL-2.3/mysql/vcl.sql{tip}
+{info}The *vcl.sql* file is included in the *mysql* directory within the
+Apache VCL&nbsp;source code{info}
+
+----
+Next step: [VCL:VCL 2.3 Web Code Installation](vcl:vcl-2.3-web-code-installation.html)

Added: vcl/site/trunk/content/confluence_export/vcl-2.3-installation.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/vcl-2.3-installation.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/vcl-2.3-installation.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/vcl-2.3-installation.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,21 @@
+Title: VCL 2.3 Installation
+<a name="VCL2.3Installation-Install&Configure:"></a>
+### Install & Configure:
+
+1. [Database](vcl:vcl-2.3-installation#database.html)
+1. [Web Components](vcl:vcl-2.3-installation#web.html)
+1. [Management Node Components](vcl:vcl-2.3-installation#managementnode.html)
+1. [Configure Authentication](vcl:vcl-2.3-installation#authentication.html)
+
+----
+{anchor:Database}
+{include:VCL 2.3 Database Installation}
+----
+{anchor:Web}
+{include:VCL 2.3 Web Code Installation}
+----
+{anchor:ManagementNode}
+{include:VCL 2.3 Management Node Installation}
+----
+{anchor:Authentication}
+{include:VCL 2.3 Configure Frontend Authentication}



Mime
View raw message