vcl-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jftho...@apache.org
Subject svn commit: r1430372 [10/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.3-management-node-installation.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/vcl-2.3-management-node-installation.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/vcl-2.3-management-node-installation.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/vcl-2.3-management-node-installation.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,337 @@
+Title: VCL 2.3 Management Node Installation
+{excerpt:hidden=true}
+How to install and configure the VCL management node components including
+the required Linux packages, Perl modules, VCL daemon (vcld), and Windows
+utility dependencies{excerpt}
+
+<a name="VCL2.3ManagementNodeInstallation-Install&ConfiguretheManagementNodeComponents"></a>
+# Install & Configure the Management Node Components
+
+<a name="VCL2.3ManagementNodeInstallation-Prerequisites"></a>
+### Prerequisites
+
+The following management node installation instructions assume the
+instructions on the following pages have previously been completed:
+* [VCL:VCL 2.3 Database Installation](vcl:vcl-2.3-database-installation.html)
+* [VCL:VCL 2.3 Web Code Installation](vcl:vcl-2.3-web-code-installation.html)
+
+<a name="VCL2.3ManagementNodeInstallation-SupportedOperatingSystems:"></a>
+##### Supported Operating Systems:
+
+The VCL management node daemon (vcld) has been developed to run on an
+operating system based on Red Hat Enterprise Linux (RHEL). It has been
+tested on the following:
+* Red Hat Enterprise Linux 4.x
+* Red Hat Enterprise Linux 5.x
+* Red Hat Enterprise Linux 6.x
+* CentOS 5.x
+* CentOS 6.x
+
+<a name="VCL2.3ManagementNodeInstallation-RequiredLinuxPackages:"></a>
+##### Required Linux Packages:
+
+The VCL management node daemon (vcld) requires the following Linux packages
+and Perl modules in order to run (see step 2 below for installation
+instructions):
+
+
+* *expat* \- A library for parsing XML
+* *expat-devel* \- Libraries and include files to develop XML applications
+with expat
+* *gcc* \- Various compilers (C, C++, Objective-C, Java, ...)
+* *krb5-libs* \- The shared libraries used by Kerberos 5
+* *krb5-devel* \- Development files needed to compile Kerberos 5 programs
+* *libxml2* \- Library providing XML and HTML support
+* *libxml2-devel* \- Libraries, includes, etc. to develop XML and HTML
+applications
+* *mysql* \- MySQL client programs and shared libraries
+* *nmap* \- Network exploration tool and security scanner
+* *openssh* \- The OpenSSH implementation of SSH protocol versions 1 and 2
+* *openssl* \- The OpenSSL toolkit
+* *openssl-devel* \- Files for development of applications which will use
+OpenSSL
+* *perl* \- The Perl programming language
+* *perl-DBD-MySQL* \- A MySQL interface for perl
+* *xmlsec1-openssl* \- OpenSSL crypto plugin for XML Security Library
+
+<a name="VCL2.3ManagementNodeInstallation-RequiredPerlModules:"></a>
+##### Required Perl Modules:
+
+The VCL management node daemon (vcld) is written in Perl and has been
+tested on Perl 5.8.x. The following Perl modules available from [CPAN ](http://www.cpan.org)
+are also required (see step 2 below for installation instructions):
+* *DBI* \- Generic Database Interface
+* *Digest::SHA1* \- NIST SHA message digest algorithm
+* *Mail::Mailer* \- Simple mail agent interface
+* *Object::InsideOut* \- Comprehensive inside-out object support
+* *RPC::XML* \- A set of classes for core data, message and XML handling
+* *YAML* \- YAML Ain't Markup Language
+
+1. h2. Install the VCL Management Node Code - Perl Daemon
+1. # If you have not already done so, download and extract the VCL source
+files to the management node:
+  
+  
+tar \-jxvf apache-VCL-2.3.tar.bz2{tip}
+1. # Copy the *managementnode* directory to the location where you want it to
+reside (typically */usr/local*):
+{tip}cp \-r apache-VCL-2.3/managementnode /usr/local/vcl{tip}
+1. h2. Install the Required Linux Packages & Perl Modules
+*Run the install_perl_libs.pl script:*
+{tip}perl /usr/local/vcl/bin/install_perl_libs.pl{tip}
+The last line of the install_perl_libs.pl script output should be:
+
+    _Note: The script will hang or terminate if it encounters a problem. If
+this occurs, you will need to troubleshoot the problem by looking at the
+output._
+    \\
+    \\
+    The install_perl_libs.pl script included in the VCL distribution will
+attempt to download and install the required Linux packages and Perl
+modules. It uses the yum utility to install the required Linux packages.
+The required Perl modules are available from [CPAN - The Comprehensive Perl Archive Network|http://www.cpan.org]
+. The install_perl_libs.pl script attempts to download and install the
+required Perl modules by using the CPAN.pm module which is included with
+most Perl distributions.
+    \\
+    \\
+    The yum utility should exist on any modern Red Hat-based Linux distribution
+(Red Hat, CentOS, Fedora, etc). If yum isn't available on your management
+node OS, you will need to download and install the required Linux packages
+manually or by using another package management utility. After installing
+the required Linux packages, attempt to run the install_perl_libs.pl script
+again.
+    # h2. Configure vcld.conf
+    ## Create the */etc/vcl* directory:
+    {tip}mkdir /etc/vcl{tip}
+    ## Copy the stock *vcld.conf* file to */etc/vcl*:
+    {tip}cp /usr/local/vcl/etc/vcl/vcld.conf /etc/vcl{tip}
+    ## Edit */etc/vcl/vcld.conf*:
+    {tip}vi /etc/vcl/vcld.conf{tip}
+    The following lines must be configured in order to start the VCL daemon
+(vcld) and allow it to check in to the database:
+    ##* *FQDN* \- the fully qualified name of the management node, this should
+match the name that was configured for the management node in the database
+    ##* *server* \- the IP address or FQDN of the database server
+    ##* *LockerWrtUser* \- database user account with write privileges
+    ##* *wrtPass* \- database user password
+    ##* *xmlrpc_pass* \- password for xmlrpc api from vcld to the web
+interface(can be long). This will be used later to sync the database
+vclsystem user account
+    ##* *xmlrpc_url* \- URL for xmlrpc api
+https://my.server.org/vcl/index.php?mode=xmlrpccall
+    ## Save the vcld.conf file
+    # h2. Configure the SSH Client
+    The SSH client on the management node should be configured to prevent SSH
+processes spawned by the root user to the computers it controls from
+hanging because of missing or different entries in the known_hosts file.
+    \\
+    \\
+    Edit the ssh_config file:
+    {tip}vi /etc/ssh/ssh_config{tip}
+    Set the following parameters:
+
+StrictHostKeyChecking no{noformat}
+_Note: If you do not want these settings applied universally on the
+management node the SSH configuration can also be configured to only apply
+these settings to certain hosts or only for the root user. Consult the SSH
+documentation for more information._
+1. h2. Install and Start the VCL Daemon (vcld) Service
+1. # Copy the vcld service script to /etc/init.d and name it vcld:
+{tip}
+cp /usr/local/vcl/bin/S99vcld.linux /etc/init.d/vcld
+{tip}
+1. # Add the vcld service using chkconfig:
+{tip}
+/sbin/chkconfig \--add vcld
+{tip}
+1. # Configure the vcld service to automatically run at runtime levels 3-5:
+{tip}
+/sbin/chkconfig \--level 345 vcld on
+{tip}
+1. # Start the vcld service:
+{tip}
+/sbin/service vcld start
+{tip}
+You should see output similar to the following:
+
+                                                               [  OK  ]
+{noformat}
+    {info}
+    The vcld service can also be started by running the service script
+directly: */etc/init.d/vcld start{*}{info}
+    ## Check the vcld service by monitoring the vcld.log file: {tip}tail \-f
+/var/log/vcld.log{tip}
+    You should see the following being added to the log file every few seconds
+if the management node is checking in with the database:
+    2012-05-15 13:23:45|25494|vcld:main(167)|lastcheckin time updated for
+management node 1: 2012-05-15 13:23:45
+    {info}The vcld -v (verbose) flag is needed in order to see the check-in
+message.{info} 
+    # h2. Set the vclsystem account password for xmlrpc api
+    Using the vcld -setup tool, set the vclsystem account. This is needed to
+properly use the block allocation features.
+    {tip}
+    /usr/local/vcl/bin/vcld -setup
+    {tip}
+    Select 1. VCL Base Module
+    Select 2. Set Local VCL User Account Password
+    Select 2. vclsystem 
+    From the vcld.conf file, paste or type the password from xmlrpc_pass
+variable and hit enter.
+    \\
+    # h2. Install & Configure the DHCP Service
+    ## Install *dhcp* if it is not already installed:
+    {tip}
+    yum install dhcp \-y
+    {tip}
+    ## Configure the dhcpd service to automatically start at runlevels 3-5:
+    {tip}
+    /sbin/chkconfig \--level 345 dhcpd on
+    {tip}
+    ## Configure the dhcpd.conf file.
+    {tip}
+    vi /etc/dhcpd.conf
+    {tip}
+    {info}Configure your dhcpd.conf file according to your network
+configuration. The contents of the dhcpd.conf file will vary based on how
+your network is configured. Below is an example of a basic dhcpd.conf
+file:{info}
+
+ddns-update-style none;
+shared-network eth0 {
+	subnet 10.100.0.0 netmask 255.255.255.0 {
+		ignore unknown-clients;
+	}
+}
+
+    You will add host definitions to the dhcpd.conf file after you add
+computers to VCL using the website. The website will display the dhcpd.conf
+host definitions after the computers have been added to VCL, which can be
+copied and pasted into the dhcpd.conf file.
+    ## Start the dhcpd service:
+    {tip}/sbin/service dhcpd start{tip}
+    # h2. Configure Windows Product Keys and/or KMS Server Addresses (Optional)
+    If you will be deploying Windows environments your institution's Windows
+product key and/or KMS server addresses must be entered into the VCL
+database. This can be done by running the following command:
+    {tip}/usr/local/vcl/bin/vcld \-setup{tip}
+    Select "*Windows OS Module*" and follow the prompts.
+    # h2. Download Windows Sysprep Utility (Optional)
+    If you will be using VCL to deploy bare-metal Windows XP or Windows Server
+2003 environments via xCAT, the appropriate versions of the Microsoft
+Sysprep utility must be downloaded to the management node. The following
+steps do not need to be completed if you only intend to deploy VMware
+virtual machines.
+    \\
+    \\
+    The Sysprep utility is included in the Deployment Tools available for free
+from Microsoft. You do not need to download Sysprep for Windows 7 or
+Windows Server 2008 because it is included in the operating system.
+    \\
+    \\
+    The Sysprep files need to be downloaded, extracted, and then copied to the
+management node. The format of the file available for download is
+Microsoft's .cab format. It is easiest to extract the files on a Windows
+computer. Windows Explorer is able to open the .cab file and then the files
+contained within can be copied elsewhere.
+    \\
+    \\
+    ## Windows XP
+    ### Download Sysprep for Windows XP: [Windows XP Service Pack 3 Deployment Tools|http://www.microsoft.com/downloads/details.aspx?FamilyID=673a1019-8e3e-4be0-ac31-70dd21b5afa7&displaylang=en]
+    ### Extract the Windows XP Sysprep Files
+    ### Copy the extracted Windows XP Sysprep files to the following directory
+the management node:
+{noformat}/usr/local/vcl/tools/Windows_XP/Utilities/Sysprep{noformat}
+    ## Windows Server 2003
+    ### Download Sysprep for Windows Server 2003: [System Preparation tool for Windows Server 2003 Service Pack 2 Deployment|http://www.microsoft.com/downloads/details.aspx?familyid=93F20BB1-97AA-4356-8B43-9584B7E72556&displaylang=en]
+    ### Extract the Windows Server 2003 Sysprep Files
+    ### Copy the extracted Windows Server 2003 Sysprep files to the following
+directory the management node:
+{noformat}/usr/local/vcl/tools/Windows_Server_2003/Utilities/Sysprep{noformat}
+    # h2. Download Windows Drivers (Optional)
+    Drivers which aren't included with Windows must be downloaded and saved to
+the management node. The drivers required will vary greatly depending on
+the hardware. The only way to know what additional drivers you need is to
+install Windows on a computer and check for missing drivers.
+    \\
+    \\
+    The drivers must be copied to the appropriate directory on the management
+node. The VCL image capture process copies the driver directories to the
+computer before an image is captured. Drivers from multiple directories
+will be copied based on the version of Windows being captured. There are
+driver directories under *tools* for each version of Windows (Windows XP,
+Windows 7) and for each version group of Windows (version 5, 6). This
+allows drivers which are common to multiple versions of Windows to be
+shared in the management node tools directory structure.
+    \\
+    Examples:
+    \\
+    \\
+    If a chipset driver works for all versions of Windows it should be saved
+in:
+    */var/lib/vcl/tools/Windows/Drivers/Chipset*
+    \\
+    \\
+    If Windows XP and Windows Server 2003 both use the same network driver it
+can be saved in:
+    */var/lib/vcl/tools/Windows_Version_5/Drivers/Network*
+    \\
+    \\
+    If a storage driver only works for Windows XP it should be saved in:
+    */var/lib/vcl/tools/Windows_XP/Drivers/Storage*
+    \\
+    \\
+    During the image capture process, each Windows version directory is copied
+to the computer under C:\Cygwin\home\root\VCL. The order in which the
+Windows version directories are copied goes from most general to most
+specific. In the example above, the order would be:
+    */var/lib/vcl/tools/Windows/\**
+    */var/lib/vcl/tools/Windows_Version_5/\**
+    */var/lib/vcl/tools/Windows_XP/\**
+    \\
+    \\
+    The following list shows which driver files should be saved in the driver
+directories:
+    */var/lib/vcl/tools/Windows/Drivers* \- drivers common to all versions of
+Windows
+    */var/lib/vcl/tools/Windows_Version_5/Drivers* \- drivers used by Windows
+XP and Server 2003
+    */var/lib/vcl/tools/Windows_XP/Drivers* \- drivers only used by Windows XP
+    */var/lib/vcl/tools/Windows_Server_2003/Drivers* \- drivers only used by
+Windows Server 2003
+    \\
+    */var/lib/vcl/tools/Windows_Version_6/Drivers* \- drivers used by Windows
+Vista and Server 2008
+    */var/lib/vcl/tools/Windows_7/Drivers* \- drivers only used by Windows 7
+    */var/lib/vcl/tools/Windows_Server_2008/Drivers* \- drivers only used by
+Windows Server 2008
+    \\
+    The directory structure under each Drivers directory does not matter. It is
+helpful to organize each directory by driver class, and each directory
+should be organized using the same theme. For example:
+    */var/lib/vcl/tools/Windows_Version_XP/Drivers{*}*/Chipset*
+    */var/lib/vcl/tools/Windows_Version_XP/Drivers{*}*/Network*
+    */var/lib/vcl/tools/Windows_Version_XP/Drivers{*}*/Storage*
+    */var/lib/vcl/tools/Windows_Version_XP/Drivers{*}*/Video*
+    # h2. Install & Configure Provisioning Engines and Hypervisors
+    VCL supports the following, please see the related websites for
+installation and configuration instructions:
+    ## xCAT - Extreme Cluster Administration Toolkit
+    ##* Versions Supported:
+    ##** 1.3
+    ##** 2.x
+    ##* See the xCAT website for installation & configuration information: [http://xcat.sourceforge.net|http://xcat.sourceforge.net]
+    ## VMware
+    ### See the VMware website for installation & configuration information: [http://www.vmware.com|http://www.vmware.com]
+    ### See the following pages for additional VCL VMware configuration
+information:
+    #### [VCL:VMware Configuration]
+    #### [VCL 2.3 - Further steps if using only VMware|VCL 2.3 - Further Steps if Using VMware]
+ (you probably already did things from this page when installing the web
+code)
+    
+    
+    ----
+    Previous Step: [VCL:VCL 2.3 Web Code Installation]
+    Next Step: [VCL:VCL 2.3 Configure Frontend Authentication]

Added: vcl/site/trunk/content/confluence_export/vcl-2.3-web-code-installation.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/vcl-2.3-web-code-installation.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/vcl-2.3-web-code-installation.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/vcl-2.3-web-code-installation.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,213 @@
+Title: VCL 2.3 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.3WebCodeInstallation-Install&ConfiguretheWebComponents"></a>
+# Install & Configure the Web Components
+
+<a name="VCL2.3WebCodeInstallation-*Prerequisites*"></a>
+## *Prerequisites*
+
+The following instructions assume these tasks have previously been
+completed:
+* [Apache VCL 2.3 has been downloaded](download.html)
+* [VCL database has been installed and configured](vcl:vcl-2.3-database-installation.html)
+
+  
+  
+
+<a name="VCL2.3WebCodeInstallation-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.3WebCodeInstallation-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.3WebCodeInstallation-RequiredPHPModules:"></a>
+#### Required PHP Modules:
+
+* *php-gd*
+* *php-json* (required if your PHP version is 5.2 or later)
+* *php-mysql*
+* *php-openssl*
+* *php-sysvsem*
+* *php-xml*
+* *php-xmlrpc*
+* *php-ldap* (if you will be using LDAP authentication)
+* *php-process* (for RHEL/CentOS 6)
+
+  
+  
+1. # If your web server is running a Red Hat-based OS, the required
+components&nbsp;can be installed with:
+  
+  
+For RHEL / CentOS 5
+{tip}
+yum install httpd mod_ssl php php-gd php-mysql php-xml php-xmlrpc php-ldap
+\-y
+{tip}
+For RHEL / CentOS 6
+{tip}
+yum install httpd mod_ssl php php-gd php-mysql php-xml php-xmlrpc php-ldap
+php-process \-y
+{tip}
+{info}
+You may need the optional server rpm repository for the php-process package
+to add this run the following command:
+rhn-channel \--add \--channel=rhel-x86_64-server-optional-6
+{info}
+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
+
+{tip}
+service iptables restart
+{tip}
+  
+  
+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 --trust-server-names
+'{nolink:http://vcl.apache.org/downloads/download.cgi?action=download&filename=%2Fvcl%2Fapache-VCL-2.3.tar.bz2}'
+tar \-jxvf apache-VCL-2.3.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.3/web/ /var/www/html/vcl
+cd /var/www/html/vcl/.ht-inc
+{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. #** *$cryptkey*
+1. #** *$pemkey*
+1. #* Save the secrets.php file
+1. # Run the *genkeys.sh*
+{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. # 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 required fields:
+1. ##* *Hostname -* The name of the management node server. This value
+doesn't necessarily need to be a name registered in DNS nor does it need to
+be the value displayed by the Linux _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. In a later step
+performed during the [management node installation](vcl:vcl-2.3-management-node-installation.html)
+, the value enter for Hostname must match the value you enter 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*
+1. h2. Install & Configure phpMyAdmin (Optional):
+{excerpt-include:VCL 2.3 phpMyAdmin Installation &
+Configuration|nopanel=true}
+To install phpMyAdmin, follow the instructions on: [VCL:VCL 2.3 phpMyAdmin Installation & Configuration](vcl:vcl-2.3-phpmyadmin-installation-&-configuration.html)
+
+
+[Further steps if using only VMWare](vcl-2.3---further-steps-if-using-vmware.html)
+
+[Further steps if using xCAT](vcl-2.3---further-steps-if-using-xcat.html)
+
+----
+Previous Step: [VCL:VCL 2.3 Database Installation](vcl:vcl-2.3-database-installation.html)
+Next Step: [VCL:VCL 2.3 Management Node Installation](vcl:vcl-2.3-management-node-installation.html)

Added: vcl/site/trunk/content/confluence_export/vcl-2.3.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/vcl-2.3.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/vcl-2.3.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/vcl-2.3.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,624 @@
+Title: VCL 2.3
+VCL 2.3 was release on July 20th, 2012
+
+<a name="VCL2.3-TableofContents"></a>
+## Table of Contents
+   * [Download links](#VCL2.3-Downloadlinks)
+   * [Release Notes](#VCL2.3-ReleaseNotes)
+         * [I. Intro and Description](#VCL2.3-I.IntroandDescription)
+         * [II. VCL Roadmap](#VCL2.3-II.VCLRoadmap)
+         * [III. Getting Involved in the ASF VCL Community](#VCL2.3-III.GettingInvolvedintheASFVCLCommunity)
+         * [IV. How to Submit Bugs and Feature Requests](#VCL2.3-IV.HowtoSubmitBugsandFeatureRequests)
+   * [Change Log](#VCL2.3-ChangeLog)
+         * [Sub-task](#VCL2.3-Sub-task)
+         * [Bug](#VCL2.3-Bug)
+         * [Improvement](#VCL2.3-Improvement)
+         * [New Feature](#VCL2.3-NewFeature)
+         * [Task](#VCL2.3-Task)
+
+<a name="VCL2.3-Downloadlinks"></a>
+## Download links
+
+Please make sure to download VCL from a 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.3](http://vcl.apache.org/downloads/download.cgi)
+[GPG Signature](http://www.apache.org/dist/vcl/apache-VCL-2.3.tar.bz2.asc)
+[MD5 Sum](http://www.apache.org/dist/vcl/apache-VCL-2.3.tar.bz2.md5)
+[SHA1 Sum](http://www.apache.org/dist/vcl/apache-VCL-2.3.tar.bz2.sha1)
+[VCL KEYS file](http://www.apache.org/dist/vcl/KEYS)
+
+
+1. Verify the MD5 sum (output should be "apache-VCL-2.3.tar.bz2: OK"):
+{tip}
+md5sum \-c apache-VCL-2.3.tar.bz2.md5
+{tip}
+1. Verify the SHA1 sum (output should be "apache-VCL-2.3.tar.bz2: OK"):
+{tip}
+sha1sum \-c apache-VCL-2.3.tar.bz2.sha1
+{tip}
+1. 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):
+{tip}
+gpg \--import KEYS
+{tip}
+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
+{tip}
+gpg \--verify apache-VCL-2.3.tar.bz2.asc
+{tip}
+1. For new installs, visit the on-line [installation guide](vcl-2.3-installation.html)
+.
+1. For upgrades, visit the on-line guide for your installed version (you can
+find your version number after the Apache license header in vcl/index.php
+in the web code - i.e. "ASF VCL 2.2.1"):
+1. * [2.2.1 upgrade guide](vcl:upgrade-from-previous-version-(2.2.1-to-2.3).html)
+1. * [2.2 upgrade guide](vcl:upgrade-from-previous-version-(2.2-to-2.3).html)
+1. * [2.1 upgrade guide](vcl:upgrade-from-previous-version-(2.1-to-2.3).html)
+
+<a name="VCL2.3-ReleaseNotes"></a>
+## Release Notes
+
+<a name="VCL2.3-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 compute nodes using
+* xCAT 1.3 and 2.x
+* VMware Server 1.x and 2.x
+* VMware ESX 3.5
+* VMware ESXi 4.x and 5.x
+* VMware vCenter
+* KVM
+* Virtual Box
+
+<a name="VCL2.3-II.VCLRoadmap"></a>
+#### II. VCL Roadmap
+
+VCL 2.3 (this release)
+* Service deployments
+* Allow for additional connect methods for environments (port, other
+protocols, etc)
+* Added framework support for libvirt
+* Added support for KVM
+* Added support for OS X under ESX
+* Added support for VMware VCenter
+* Added multilingualization to frontend
+
+VCL 2.4
+* Improve additional connect methods
+* NAT support
+* Remove requirement for 2 NICs
+* Support for Spice remote display protocol
+* Scripted installation
+* Support for ESX OS for end users
+* Initial support for EC2 API and OpenStack
+
+VCL 2.5
+* Power management
+* Improve cluster reservations
+* Service deployment configuration management
+* Initial support for Libcloud
+
+VCL 2.6
+* 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.3-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: user@vcl.apache.org
+dev@vcl.apache.org
+To join user, send an empty message to
+[user-subscribe@vcl.apache.org](mailto:user-subscribe@vcl.apache.org|click-to-subscribe.html)
+. To join dev, send an empty
+message to [dev-subscribe@vcl.apache.org](mailto:dev-subscribe@vcl.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.3-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.3-ChangeLog"></a>
+## Change Log
+
+
+Release Notes - VCL - Version 2.3
+
+<a name="VCL2.3-Sub-task"></a>
+####    Sub-task 
+
+* \[[VCL-319](https://issues.apache.org/jira/browse/VCL-319)
+\] -	     API LDAP authentication problem with servers where DN must be
+looked up 
+* \[[VCL-339](https://issues.apache.org/jira/browse/VCL-339)
+\] -	     Add the KVM support for VCL 
+* \[[VCL-419](https://issues.apache.org/jira/browse/VCL-419)
+\] -	     allow private IP address to be set and modified for computers 
+
+<a name="VCL2.3-Bug"></a>
+####    Bug 
+
+* \[[VCL-114](https://issues.apache.org/jira/browse/VCL-114)
+\] -	     catch-22 with new installs for creating a vmprofile 
+* \[[VCL-154](https://issues.apache.org/jira/browse/VCL-154)
+\] -	     run_scp_command() is not catching some errors 
+* \[[VCL-192](https://issues.apache.org/jira/browse/VCL-192)
+\] -	     xCAT21.pm - does_image_exist routine  
+* \[[VCL-225](https://issues.apache.org/jira/browse/VCL-225)
+\] -	     no user groups to select from when adding a new user group 
+* \[[VCL-230](https://issues.apache.org/jira/browse/VCL-230)
+\] -	     duplicate entries created in userpriv table 
+* \[[VCL-297](https://issues.apache.org/jira/browse/VCL-297)
+\] -	     Windows code is using the private IP address from the database
+rather than the hosts file 
+* \[[VCL-328](https://issues.apache.org/jira/browse/VCL-328)
+\] -	     shibboleth sp logout URL not using SSL 
+* \[[VCL-342](https://issues.apache.org/jira/browse/VCL-342)
+\] -	     problem selecting image revision id when making a cluster
+reservation with identical subimages 
+* \[[VCL-344](https://issues.apache.org/jira/browse/VCL-344)
+\] -	     local admin account make sure has full access 
+* \[[VCL-345](https://issues.apache.org/jira/browse/VCL-345)
+\] -	     check for whitespace in add computers IP address field 
+* \[[VCL-348](https://issues.apache.org/jira/browse/VCL-348)
+\] -	     Setting privileges in web gui -- Slightly broken 
+* \[[VCL-387](https://issues.apache.org/jira/browse/VCL-387)
+\] -	     xcat 1.3 getmac regex not account for A-F 
+* \[[VCL-396](https://issues.apache.org/jira/browse/VCL-396)
+\] -	     vmprofiles displayed as &#39;Array&#39; when changing a
+computer to vmhostinuse on computer utilities 
+* \[[VCL-400](https://issues.apache.org/jira/browse/VCL-400)
+\] -	     virtual hosts page shows all unassigned vms instead of
+checking which ones the user can access 
+* \[[VCL-420](https://issues.apache.org/jira/browse/VCL-420)
+\] -	     Linux code not setting static IP address correctly 
+* \[[VCL-422](https://issues.apache.org/jira/browse/VCL-422)
+\] -	     Windows image capture may hang when cleanmgr.exe is executed
+or the utility may not be installed 
+* \[[VCL-427](https://issues.apache.org/jira/browse/VCL-427)
+\] -	     for block allocations, setting the managing user group to none
+means no one can edit it if a normal user created it 
+* \[[VCL-429](https://issues.apache.org/jira/browse/VCL-429)
+\] -	     Windows code does not always detect the correct public network
+interface 
+* \[[VCL-433](https://issues.apache.org/jira/browse/VCL-433)
+\] -	     new revisions can be captured of kickstart images 
+* \[[VCL-447](https://issues.apache.org/jira/browse/VCL-447)
+\] -	     Notice: Uninitialized string offset: 0 in
+.../vcl/.ht-inc/utils.php on line 3206 
+* \[[VCL-452](https://issues.apache.org/jira/browse/VCL-452)
+\] -	     Linux.pm get_file_size does not handle thinly-provisioned
+files correctly 
+* \[[VCL-456](https://issues.apache.org/jira/browse/VCL-456)
+\] -	     groupwasnone variable is not properly initialized 
+* \[[VCL-458](https://issues.apache.org/jira/browse/VCL-458)
+\] -	     $virtual undefined in utils.php line 3678 
+* \[[VCL-464](https://issues.apache.org/jira/browse/VCL-464)
+\] -	     SSH password authentication not enabled for Linux images 
+* \[[VCL-466](https://issues.apache.org/jira/browse/VCL-466)
+\] -	     Support for Cygwin 1.7 
+* \[[VCL-467](https://issues.apache.org/jira/browse/VCL-467)
+\] -	     Members of a group from one affiliation have access to groups
+with the same name from other affiliations 
+* \[[VCL-468](https://issues.apache.org/jira/browse/VCL-468)
+\] -	     health_check update 
+* \[[VCL-469](https://issues.apache.org/jira/browse/VCL-469)
+\] -	     Windows.pm may fail to return public IP address if the same
+interface also has a non-public IP address bound 
+* \[[VCL-470](https://issues.apache.org/jira/browse/VCL-470)
+\] -	     The vSphere module does not implement the get_total_space
+subroutine 
+* \[[VCL-471](https://issues.apache.org/jira/browse/VCL-471)
+\] -	     Problem copying vmware files from a datastore to a management
+node using the vSphere API 
+* \[[VCL-472](https://issues.apache.org/jira/browse/VCL-472)
+\] -	     xCAT.pm fails if boot image mounts storage from a host other
+than the management node 
+* \[[VCL-473](https://issues.apache.org/jira/browse/VCL-473)
+\] -	     query in findManagementNode in utils.php doesn&#39;t have
+conditional to join tables 
+* \[[VCL-474](https://issues.apache.org/jira/browse/VCL-474)
+\] -	     recent versions of mysql don&#39;t accept double quotes to
+signify strings in where clauses 
+* \[[VCL-475](https://issues.apache.org/jira/browse/VCL-475)
+\] -	     addShibUser in shibauth.php returns an array when it should be
+returning a user id 
+* \[[VCL-476](https://issues.apache.org/jira/browse/VCL-476)
+\] -	     manage block allocation page may show incorrect next start
+time 
+* \[[VCL-478](https://issues.apache.org/jira/browse/VCL-478)
+\] -	     Windows 6.x Sysprep code results in incorrect root password 
+* \[[VCL-480](https://issues.apache.org/jira/browse/VCL-480)
+\] -	     XMLRPCproccessBlockTime can throw an error about VMhostCheck
+table already existing 
+* \[[VCL-482](https://issues.apache.org/jira/browse/VCL-482)
+\] -	     scheduler does not order VMs properly when no VMs are
+preloaded with the selected image 
+* \[[VCL-483](https://issues.apache.org/jira/browse/VCL-483)
+\] -	     RPC::XML fails with latest version of libwww-perl 
+* \[[VCL-484](https://issues.apache.org/jira/browse/VCL-484)
+\] -	     Requests in the inuse and image states may be changed to
+failed 
+* \[[VCL-486](https://issues.apache.org/jira/browse/VCL-486)
+\] -	     Measures against cross site scripting on the Login form 
+* \[[VCL-487](https://issues.apache.org/jira/browse/VCL-487)
+\] -	     Problem in screen transition after successful login
+authentication 
+* \[[VCL-488](https://issues.apache.org/jira/browse/VCL-488)
+\] -	     Injected user&#39;s UID is hardcoded 
+* \[[VCL-492](https://issues.apache.org/jira/browse/VCL-492)
+\] -	     edit computer info for VM in maintenance state 
+* \[[VCL-494](https://issues.apache.org/jira/browse/VCL-494)
+\] -	     Typo in testsetup.php 
+* \[[VCL-500](https://issues.apache.org/jira/browse/VCL-500)
+\] -	     tomaintenance requests may start too early or fail if
+scheduled in the future 
+* \[[VCL-501](https://issues.apache.org/jira/browse/VCL-501)
+\] -	     Linux.pm does not set the default gateway in the ifcfg file
+for statically assigned addresses 
+* \[[VCL-507](https://issues.apache.org/jira/browse/VCL-507)
+\] -	     Deleted VMs appear in the list of unassigned VMs 
+* \[[VCL-508](https://issues.apache.org/jira/browse/VCL-508)
+\] -	     Modifying reservations to overlap past max causes hang 
+* \[[VCL-509](https://issues.apache.org/jira/browse/VCL-509)
+\] -	     error when adding computer with no groups selected 
+* \[[VCL-510](https://issues.apache.org/jira/browse/VCL-510)
+\] -	     insert correct architecture in image table when adding new
+entry 
+* \[[VCL-511](https://issues.apache.org/jira/browse/VCL-511)
+\] -	     Errors in vcl.sql connectmethodmap 
+* \[[VCL-512](https://issues.apache.org/jira/browse/VCL-512)
+\] -	     Linux.pm does not determine correct block size for some
+versions of Linux 
+* \[[VCL-519](https://issues.apache.org/jira/browse/VCL-519)
+\] -	     New-line control bug in an Edit Image page 
+* \[[VCL-522](https://issues.apache.org/jira/browse/VCL-522)
+\] -	     Error in vcl.sql line 1694 
+* \[[VCL-523](https://issues.apache.org/jira/browse/VCL-523)
+\] -	     Windows code does not set scheduled task credentials when
+changing user passwords 
+* \[[VCL-524](https://issues.apache.org/jira/browse/VCL-524)
+\] -	     Windows get_network_configuration may return an empty hash 
+* \[[VCL-529](https://issues.apache.org/jira/browse/VCL-529)
+\] -	     invalid IP addresses are marked as valid in the
+is_public_ip_address 
+* \[[VCL-530](https://issues.apache.org/jira/browse/VCL-530)
+\] -	     Database field for computer.RAM is limited to 65535 
+* \[[VCL-533](https://issues.apache.org/jira/browse/VCL-533)
+\] -	     error when trying to download dhcp data when private IP
+address was not entered 
+* \[[VCL-534](https://issues.apache.org/jira/browse/VCL-534)
+\] -	     $cluster not reset in for loop in viewRequests 
+* \[[VCL-536](https://issues.apache.org/jira/browse/VCL-536)
+\] -	     xCAT partimage and image_architecture x86_64 
+* \[[VCL-540](https://issues.apache.org/jira/browse/VCL-540)
+\] -	     manageMapping not added to update-vcl.sql and vcl.sql files 
+* \[[VCL-541](https://issues.apache.org/jira/browse/VCL-541)
+\] -	     Remove &quot;return 0&quot; from all subroutines which
+normally return an array or hash 
+* \[[VCL-546](https://issues.apache.org/jira/browse/VCL-546)
+\] -	     OS.pm does not determine the correct public interface name 
+* \[[VCL-547](https://issues.apache.org/jira/browse/VCL-547)
+\] -	     removing site maintenance entry from .ht-inc/maintenance
+directory doesn&#39;t fully remove site from maintenance 
+* \[[VCL-548](https://issues.apache.org/jira/browse/VCL-548)
+\] -	     server reservations not owned by a user count toward that
+user&#39;s overlapping reservation count 
+* \[[VCL-549](https://issues.apache.org/jira/browse/VCL-549)
+\] -	     AJAX error when creating a new schedule 
+* \[[VCL-556](https://issues.apache.org/jira/browse/VCL-556)
+\] -	     edit schedule groups code not doing permissions correctly 
+* \[[VCL-558](https://issues.apache.org/jira/browse/VCL-558)
+\] -	     vcld_cron_check uses incorrect name of VCL Daemon 
+* \[[VCL-563](https://issues.apache.org/jira/browse/VCL-563)
+\] -	     DHCP is not enabled during image capture 
+* \[[VCL-567](https://issues.apache.org/jira/browse/VCL-567)
+\] -	     image profile page does not reflect owner change after
+changing the owner 
+* \[[VCL-569](https://issues.apache.org/jira/browse/VCL-569)
+\] -	     Incorrect public IP address being used if value in database
+does not match computer&#39;s actual IP address 
+* \[[VCL-573](https://issues.apache.org/jira/browse/VCL-573)
+\] -	     Reservations which alter default imagemeta values may affect
+other reservations 
+* \[[VCL-574](https://issues.apache.org/jira/browse/VCL-574)
+\] -	     reinstall option not happening when detecting inuse state 
+* \[[VCL-588](https://issues.apache.org/jira/browse/VCL-588)
+\] -	     Windows may retrieve network configuration before all network
+interfaces are initialized 
+* \[[VCL-589](https://issues.apache.org/jira/browse/VCL-589)
+\] -	     Windows 7 and 2008 Sysprep not working 
+
+<a name="VCL2.3-Improvement"></a>
+####    Improvement 
+
+* \[[VCL-82](https://issues.apache.org/jira/browse/VCL-82)
+\] -	     Add additional information to notify() messages 
+* \[[VCL-92](https://issues.apache.org/jira/browse/VCL-92)
+\] -	     modify predictive loading algorithm level 1 to have 2
+computers loaded with an image 
+* \[[VCL-141](https://issues.apache.org/jira/browse/VCL-141)
+\] -	     allow users to delete images that are set as currentimage 
+* \[[VCL-168](https://issues.apache.org/jira/browse/VCL-168)
+\] -	     Windows Media Player shortcut gets added to desktop for all
+users 
+* \[[VCL-219](https://issues.apache.org/jira/browse/VCL-219)
+\] -	     Improve VMware disk cleanup - add checks for reservations 
+* \[[VCL-234](https://issues.apache.org/jira/browse/VCL-234)
+\] -	     give error when block reservations requests more resources
+than concurrent use of image 
+* \[[VCL-236](https://issues.apache.org/jira/browse/VCL-236)
+\] -	     make Groups first tab on Manage Computers page 
+* \[[VCL-249](https://issues.apache.org/jira/browse/VCL-249)
+\] -	     denote which management node fields are required 
+* \[[VCL-276](https://issues.apache.org/jira/browse/VCL-276)
+\] -	     log Block reservation data 
+* \[[VCL-311](https://issues.apache.org/jira/browse/VCL-311)
+\] -	     add more fields to edit computer page 
+* \[[VCL-313](https://issues.apache.org/jira/browse/VCL-313)
+\] -	     need a way to set computers as vmhosts without a bare metal
+provisioning engine 
+* \[[VCL-321](https://issues.apache.org/jira/browse/VCL-321)
+\] -	     user lookup tool doesn&#39;t show user group affiliation 
+* \[[VCL-354](https://issues.apache.org/jira/browse/VCL-354)
+\] -	     View Computers Table - State Coloring 
+* \[[VCL-358](https://issues.apache.org/jira/browse/VCL-358)
+\] -	     Improve VMware Windows image loading speed 
+* \[[VCL-360](https://issues.apache.org/jira/browse/VCL-360)
+\] -	     Allow users to delete images preloaded on computers which
+aren&#39;t being used 
+* \[[VCL-376](https://issues.apache.org/jira/browse/VCL-376)
+\] -	     mark imagerevisions deleted when user deletes image. 
+* \[[VCL-379](https://issues.apache.org/jira/browse/VCL-379)
+\] -	     alert user if reservation has timed out when they click
+Connect or Get RDP File 
+* \[[VCL-381](https://issues.apache.org/jira/browse/VCL-381)
+\] -	     Move firewall_compare_update to OS modules 
+* \[[VCL-383](https://issues.apache.org/jira/browse/VCL-383)
+\] -	     make future reservations that would be part of a block
+allocation included in the block allocation 
+* \[[VCL-384](https://issues.apache.org/jira/browse/VCL-384)
+\] -	     Remove MAC addresses from ifcfg-eth* files for Linux images
+during capture 
+* \[[VCL-385](https://issues.apache.org/jira/browse/VCL-385)
+\] -	     Hide noimage from showing in the list of images in Edit Image
+Profiles 
+* \[[VCL-390](https://issues.apache.org/jira/browse/VCL-390)
+\] -	     Prevent auto-generated or invalid public IP address from being
+displayed to user 
+* \[[VCL-391](https://issues.apache.org/jira/browse/VCL-391)
+\] -	     Windows Server 2003 shutdown and reboot fails 
+* \[[VCL-393](https://issues.apache.org/jira/browse/VCL-393)
+\] -	     Handle Windows computers going to sleep 
+* \[[VCL-398](https://issues.apache.org/jira/browse/VCL-398)
+\] -	     make block allocations tie up concurrent usage of image 
+* \[[VCL-402](https://issues.apache.org/jira/browse/VCL-402)
+\] -	     Login screensaver not needed for VMs 
+* \[[VCL-404](https://issues.apache.org/jira/browse/VCL-404)
+\] -	     Prevent and/or remove color code escape characters from SSH
+output 
+* \[[VCL-407](https://issues.apache.org/jira/browse/VCL-407)
+\] -	     Add makesshgkh check in gen_node_key.sh 
+* \[[VCL-408](https://issues.apache.org/jira/browse/VCL-408)
+\] -	     Imaging reservations that fail very early on may not be put
+into the maintenance state 
+* \[[VCL-410](https://issues.apache.org/jira/browse/VCL-410)
+\] -	     Update and improve install_perl_libs.pl script for VCL 2.3 
+* \[[VCL-413](https://issues.apache.org/jira/browse/VCL-413)
+\] -	     Management node OS object 
+* \[[VCL-418](https://issues.apache.org/jira/browse/VCL-418)
+\] -	     simplify adding LDAP authentication 
+* \[[VCL-421](https://issues.apache.org/jira/browse/VCL-421)
+\] -	     Update Windows code to work with Cygwin 1.7 
+* \[[VCL-423](https://issues.apache.org/jira/browse/VCL-423)
+\] -	     Suppress unnecessary warning messages from vcld.log 
+* \[[VCL-432](https://issues.apache.org/jira/browse/VCL-432)
+\] -	     auto capture for imaging and long-term reservations 
+* \[[VCL-435](https://issues.apache.org/jira/browse/VCL-435)
+\] -	     Add support for ESXi 4.1 scripted installs 
+* \[[VCL-438](https://issues.apache.org/jira/browse/VCL-438)
+\] -	     allow new users to be added to VCL when shibboleth
+authentication is used without LDAP 
+* \[[VCL-441](https://issues.apache.org/jira/browse/VCL-441)
+\] -	     getPossibleRecentFailures in isAvailable can end up removing
+only available machine 
+* \[[VCL-444](https://issues.apache.org/jira/browse/VCL-444)
+\] -	     time delay the display of the Get RDP File button to allow
+vcld to grant access 
+* \[[VCL-446](https://issues.apache.org/jira/browse/VCL-446)
+\] -	     End of reservation notices  
+* \[[VCL-450](https://issues.apache.org/jira/browse/VCL-450)
+\] -	     Backend VMware improvements for 2.3 release 
+* \[[VCL-453](https://issues.apache.org/jira/browse/VCL-453)
+\] -	     iptables  
+* \[[VCL-455](https://issues.apache.org/jira/browse/VCL-455)
+\] -	     put alt text with a image generated by textimage.php 
+* \[[VCL-460](https://issues.apache.org/jira/browse/VCL-460)
+\] -	     Send critical notification if KMS or MAK activation fails 
+* \[[VCL-461](https://issues.apache.org/jira/browse/VCL-461)
+\] -	     Color depth is limited when connecting to Windows images via
+RDP 
+* \[[VCL-462](https://issues.apache.org/jira/browse/VCL-462)
+\] -	     Remove Windows service pack installation files during image
+capture 
+* \[[VCL-479](https://issues.apache.org/jira/browse/VCL-479)
+\] -	     remove dependency on mcrypt 
+* \[[VCL-489](https://issues.apache.org/jira/browse/VCL-489)
+\] -	     allow dhcp and hosts info to be downloaded about computers any
+time instead of just when adding 
+* \[[VCL-490](https://issues.apache.org/jira/browse/VCL-490)
+\] -	     restrict fields when adding computers 
+* \[[VCL-491](https://issues.apache.org/jira/browse/VCL-491)
+\] -	     adding multiple computers - confusing error messages when
+incorrect count entered 
+* \[[VCL-495](https://issues.apache.org/jira/browse/VCL-495)
+\] -	     Allow change of vmprofile for an active vmhost 
+* \[[VCL-496](https://issues.apache.org/jira/browse/VCL-496)
+\] -	     DataStructure.pm does not implement a
+set_computer_private_ip_address subroutine 
+* \[[VCL-497](https://issues.apache.org/jira/browse/VCL-497)
+\] -	     dedup eppn 
+* \[[VCL-498](https://issues.apache.org/jira/browse/VCL-498)
+\] -	     simplify group time inputs 
+* \[[VCL-499](https://issues.apache.org/jira/browse/VCL-499)
+\] -	     support for controlling VMware vCenter infrastructure through
+the vSphere SDK 
+* \[[VCL-502](https://issues.apache.org/jira/browse/VCL-502)
+\] -	     allow aspects of automatic user groups to be managed through
+UI 
+* \[[VCL-504](https://issues.apache.org/jira/browse/VCL-504)
+\] -	     Multiple critical messages are generated if inuse process
+fails to initialize 
+* \[[VCL-505](https://issues.apache.org/jira/browse/VCL-505)
+\] -	     Dojo is slow to load, especially on pages with many ancillary
+class files 
+* \[[VCL-506](https://issues.apache.org/jira/browse/VCL-506)
+\] -	     Retrieve accurate computer hardware specs and update the
+computer table 
+* \[[VCL-513](https://issues.apache.org/jira/browse/VCL-513)
+\] -	     allow block allocation control per affiliation 
+* \[[VCL-514](https://issues.apache.org/jira/browse/VCL-514)
+\] -	     decrease the number of queries done by the frontend 
+* \[[VCL-515](https://issues.apache.org/jira/browse/VCL-515)
+\] -	     suggest available time when selection not available instead of
+showing time table 
+* \[[VCL-517](https://issues.apache.org/jira/browse/VCL-517)
+\] -	     Linux udev net-persistent rule 
+* \[[VCL-520](https://issues.apache.org/jira/browse/VCL-520)
+\] -	     Improving display control, on an detailed information of an
+image 
+* \[[VCL-521](https://issues.apache.org/jira/browse/VCL-521)
+\] -	     An OS image named in japanese 2byte characters doesn&#39;t run 
+* \[[VCL-528](https://issues.apache.org/jira/browse/VCL-528)
+\] -	     customizing image capture flow using vcl_exclude_list 
+* \[[VCL-543](https://issues.apache.org/jira/browse/VCL-543)
+\] -	     OSX under ESXi 4.1 
+* \[[VCL-544](https://issues.apache.org/jira/browse/VCL-544)
+\] -	     Linux systemd services 
+* \[[VCL-553](https://issues.apache.org/jira/browse/VCL-553)
+\] -	     Make OS.pm wait_for_reboot arguments consistent with other
+wait_* subroutines 
+* \[[VCL-554](https://issues.apache.org/jira/browse/VCL-554)
+\] -	     Add check to image capture to determine if user shutdown
+computer 
+* \[[VCL-557](https://issues.apache.org/jira/browse/VCL-557)
+\] -	     xCAT2 reset node to boot state on DESTROY	
+* \[[VCL-565](https://issues.apache.org/jira/browse/VCL-565)
+\] -	     Convert code which directly accesses
+$ENV\{management_node_info\} 
+* \[[VCL-575](https://issues.apache.org/jira/browse/VCL-575)
+\] -	     Improvements to gen-node-key.sh 
+* \[[VCL-578](https://issues.apache.org/jira/browse/VCL-578)
+\] -	     Improve how inuse reservations which aren&#39;t responding to
+SSH are handled 
+
+<a name="VCL2.3-NewFeature"></a>
+####    New Feature 
+
+* \[[VCL-30](https://issues.apache.org/jira/browse/VCL-30)
+\] -	     additional user access methods for connecting to reserved
+compute node  
+* \[[VCL-323](https://issues.apache.org/jira/browse/VCL-323)
+\] -	     ESX provisioning modules - based on snapshots 
+* \[[VCL-367](https://issues.apache.org/jira/browse/VCL-367)
+\] -	     make Connect and Get RDP File buttons check for reservation
+being timed out 
+* \[[VCL-399](https://issues.apache.org/jira/browse/VCL-399)
+\] -	     add a dashboard where admins can see current state of VCL
+system 
+* \[[VCL-417](https://issues.apache.org/jira/browse/VCL-417)
+\] -	     Provisioning module for VirtualBox 
+* \[[VCL-463](https://issues.apache.org/jira/browse/VCL-463)
+\] -	     add ability to deploy images as servers 
+* \[[VCL-477](https://issues.apache.org/jira/browse/VCL-477)
+\] -	     add caching of statistics data 
+* \[[VCL-485](https://issues.apache.org/jira/browse/VCL-485)
+\] -	     Multilingualization of Web UI 
+* \[[VCL-527](https://issues.apache.org/jira/browse/VCL-527)
+\] -	     Allow users to reinstall newer revisions 
+* \[[VCL-545](https://issues.apache.org/jira/browse/VCL-545)
+\] -	     Libvirt Provisioning Module 
+* \[[VCL-550](https://issues.apache.org/jira/browse/VCL-550)
+\] -	     Add post_reserve functionality to Windows code 
+
+<a name="VCL2.3-Task"></a>
+####    Task 
+
+* \[[VCL-443](https://issues.apache.org/jira/browse/VCL-443)
+\] -	     update XMLRPC example to use API v2 
+* \[[VCL-576](https://issues.apache.org/jira/browse/VCL-576)
+\] -	     Finalizing for 2.3 release

Added: vcl/site/trunk/content/confluence_export/vcl-architecture.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/vcl-architecture.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/vcl-architecture.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/vcl-architecture.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,7 @@
+Title: VCL Architecture
+{gliffy:name=VCL Architecture diagram|space=VCL|page=VCL
+Architecture|align=left|size=L}
+The VCL Architecture consists or 3 main components:
+* Web
+* Database
+* Management node

Added: vcl/site/trunk/content/confluence_export/vcl-conf-call-2-5-2009.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/vcl-conf-call-2-5-2009.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/vcl-conf-call-2-5-2009.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/vcl-conf-call-2-5-2009.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,91 @@
+Title: VCL conf call 2-5-2009
+VCL-dev 2/05/2009 call
+
+Roll Call:
+
+Josh Thompson
+Andy Kurth
+John Bass
+Andrew Brown
+Brian Bouterse
+Aaron Peeler
+
+Agenda
+1 - ESX module VCL-29
+2 - OS module progress VCL-23
+3 - Access methods NX protocol VCL-80
+
+1 - ESX module VCL-29
+Brian - ESX module readme file
+[https://svn.apache.org/repos/asf/incubator/vcl/trunk/managementnode/lib/VCL/Module/Provisioning/esx.README](https://svn.apache.org/repos/asf/incubator/vcl/trunk/managementnode/lib/VCL/Module/Provisioning/esx.README)
+Brian/Andrew - ESX host flow for esx.pm module using ARP as to not
+pre-define fixed
+addresses in dhcpd.conf. esx module registers vmx configured to
+autogenerate MAC address. by using vmware tools query the vm server what
+the MAC address is. Then poll ARP table to find assigned IP address then
+edit /etc/hosts file so vcld can use shortname to talk to guest OS.
+
+John/Aaron - May cause issues with multiple management node in the same
+subnet or subnet ranges or need to pre-define which MAC addresses.
+John - suggestion, may need to explore cisco based tool dhcpd helper or
+something to
+help coordinate the dhcp tasks.
+
+Andrew - suggestion - to add support to esx.pm to handle both cases
+if MAC address defined in computer table proceed as normal
+elsif MAC address if not defined in computer table use the vmware
+autogenerated method.
+
+2 - OS module progress VCL-23
+Review what is involved with the capture routine/s
+Andy - provides overview of the capture process
+this process differs between xCAT and vmware module. Future target goal is
+to have single primary process for any provisioning module.
+Andy - flow for xcat capture process:
+a)OS capture_prep
+set root password to common
+log users off - if connected
+remove user account
+sshd-> auto
+clean temp...
+defrag
+remove pagefile/reboot
+wait until back up
+sshd \-> manual
+config firewall
+copy sysprep/scripts/drivers
+
+b)Prov capture_prep xCAT specific
+create .tmpl
+edit nodetype.tab
+nodeset <node> image
+
+c) Prov capture_begin
+sysprep.cmd
+
+d) Prov capture_monitor
+monitors the capture process for xcat type of resources
+checks boot state
+
+Again the plan is to expand these routines for all modules currently
+vmware.pm is using
+internal capture routine and not using any of these.
+
+Andy - will document that flow/logic on confluence
+Brian - will create JIRA issues on dev plans on esx.pm
+
+Aaron - suggestion - extend vmhostprofile table to store any hard coded
+settings that are being used within the esx module. Would allow greater
+flexibility for small changes in infrastructure environments.
+
+3 - Access methods VCL-23
+Brian - NX protocol - talking with NX members.
+would like to make NX (Nomachine) an access method
+
+Group discussion - General goal is to extend the image profile for the
+support of multiple
+remote access connection methods/profiles on a per image basis. Then either
+present to the user each available access method available or in user
+preferences order which access method is desired(if available).
+
+End of meeting

Added: vcl/site/trunk/content/confluence_export/vcl-installation.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/vcl-installation.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/vcl-installation.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/vcl-installation.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1 @@
+Title: VCL Installation

Added: vcl/site/trunk/content/confluence_export/vcl-release-procedures.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/vcl-release-procedures.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/vcl-release-procedures.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/vcl-release-procedures.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,154 @@
+Title: VCL Release Procedures
+<a name="VCLReleaseProcedures-Prerequisites:Thingsthatmustbedonebeforearelease"></a>
+## Prerequisites: Things that must be done before a release
+
+* all items from the JIRA roadmap for the release must be completed or
+moved to a future release
+* ALL human readable files must contain the Apache license header
+** this includes style sheets, test code, and documentation - when in
+doubt, add a header
+** files that are part of other software packages that are bundled with a
+release must not contain the header (unless that software is also ASF
+software) and should be clearly documented as being bundled software
+* LICENSE and NOTICE files should be reviewed
+** LICENSE: This file should have the Apache License at the top of it; any
+third party artifacts or documents included in the release should have
+their licenses included in this file along with a clear explanation of
+which files each license applies to.
+** NOTICE: This file is for additional copyright and attribution statements
+any third party licenses may require. A typical NOTICE document at a
+minimum includes a copyright and attribution statement for The Apache
+Software Foundation. Nothing else belongs in the NOTICE document.
+** Make sure copyright date is correct in NOTICE file
+* Files containing the VCL version should be updated to the version being
+released
+** The backend Perl files contain a line defining a $VERSION variable, this
+should be updated in every file
+* documentation on how to upgrade from a previous release must be created
+** if appropriate, scripts to help users upgrade should be created (don't
+forget steps/scripts to upgrade the database schema)
+* RELEASE_NOTES file needs to be updated and should contain:
+** release version
+** an intro to VCL
+** a brief description of the aims of VCL
+** a brief roadmap of VCL and how this release fits in to it
+** a list of ways for users to get involved
+** a description of how users can submit issues
+* the README file must also contain all dependencies (this includes PHP,
+Perl, MySQL versions in addition to perl and php modules, dojo, etc.) for
+running VCL, any changes in dependencies since the last release must be
+listed in the CHANGLOG file
+* generate a CHANGELOG file
+** go to the [JIRA site](http://issues.apache.org/jira/browse/VCL)
+** click *Release Notes*
+** select the release version
+** select *text* as the style
+** scroll down to *Edit/Copy Release Notes*
+** copy/paste the contents to a new section in the CHANGELOG file
+** make sure to add any changes in the dependencies since the last release
+* make sure INSTALLATION file is up to date with content from Confluence on
+how to install each part
+* ensure LICENSE, NOTICE, RELEASE_NOTES, CHANGELOG, INSTALLATION, UPGRADE,
+and README files are in top level directory of trunk (or the branch that
+will be used for the release)
+* an export from HEAD should result in a directory tree with all files and
+directories having appropriate permissions
+* release manager's GPG signing key must be in KEYS file in toplevel
+directory of SVN (one above trunk)
+* a release/download page needs to be created for the specific release
+containing:
+** link to release artifact (link to a mirror)
+** link to signatures and checksums (link directly to apache.org)
+** steps explaining how to verify artifact using signatures and checksums
+** either a link to release notes or contain them inline
+** either a link to a change log or contain it inline
+* a decision needs to be made determining which, if any, previously
+released artifacts should be removed from the main distribution site after
+this release is completed
+* make sure the index.php file from the web code has the correct VCL
+version at the top of it
+
+<a name="VCLReleaseProcedures-Stepstocreateareleasecandidateartifact"></a>
+## Steps to create a release candidate artifact
+
+* A tag for the release candidate needs to be created in subversion. It
+should be created under the *tags* directory of the repository and should
+be named *release-W.X.Y-RCZ* (with Z being the release candidate number,
+starting with 1 and with .Y only being included if Y > 0)
+* export from this tag to get the code for the release candidate
+* add Dojo Toolkit
+** download and extract most recent (and tested to work with web code)
+version of Dojo Toolkit under 'web'
+** rename extracted dojo directory to just 'dojo'
+** change to themes directory and run './copydojocss.sh default'
+** update the version listed for Dojo in the README file
+* remove any VCL perl modules that should not be part of the release
+* create a tarball of the directory
+** compress it with bzip2
+** name it apache-VCL-W.X.Y-RCZ-incubating.tar.bz2 (the .Y should only be
+included if Y > 0)
+* create MD5 and SHA-1 sums of the tarball
+* sign the tarball with GPG
+** [This document](http://www.apache.org/dev/release-signing.html#sign-release)
+ contains information on how to sign the tarball
+* distribute the RC through the release manager's personal web space on
+people.apache.org (RC are not to be release from the main distribution area
+to cut down on archive storage and mirroring bandwidth)
+
+<a name="VCLReleaseProcedures-CommunityandPMCvotingprocess"></a>
+## Community and PMC voting process
+
+*NOTICE: these steps may not be completely correct*
+* release manager should start a [VOTE](http://incubator.apache.org/guides/releasemanagement.html#note-votes)
+ thread on the dev list; [this is a good example|http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200601.mbox/%3C43C1C0A0.7040401%40roguewave.com%3E]
+; however, the example is missing an explicit vote block that needs to be
+included:
+\[ \](-\.html)
+ \+1 yes, release VCL W.X.Y
+\[ \](-\.html)
+ 0 dunno
+\[ \](-\.html)
+ \-1 no, don't release VCL W.X.Y (provide reasons if this is your vote)
+* the release manage's vote should be posted in a separate message from the
+one calling for the vote
+* the VOTE thread should be ended with a reply post including \[RESULT\](result\.html)
+ in the subject; [this is a good example|http://mail-archives.apache.org/mod_mbox/incubator-general/200605.mbox/<5BDE9EBE-2645-4940-9CB9-C038E531B8A2%40gmail.com>]
+
+<a name="VCLReleaseProcedures-StepstomaketheRCavailableasareleaseartifact"></a>
+## Steps to make the RC available as a release artifact
+
+* create a tag for the release from the approved RC tag (svn copy from RC
+tag to new release tag)
+* create a copy of the approved RC artifact and name it
+apache-VCL-X.Y.Z-incubating.tar.bz2 (the .Z should only be included if Z >
+0) - untar old one, rename director to not have RC part, create new tarball
+* sign the file with GPG
+* create md5 and sha1 sum files
+
+<a name="VCLReleaseProcedures-Stepstomakereleaseartifactavailabletousers"></a>
+## Steps to make release artifact available to users
+
+* place the release artifact, sums, and signature in
+/www/www.apache.org/dist/vcl on people.apache.org
+* ensure the artifact has permissions 664 and is owned by the vcl group
+* wait 24 hours for the artifact to propagate to the mirrors before
+announcing the release
+** ideally, a test download should be done from the mirror and a check of
+the sums and signatures should be done
+* After successfully performing a test download from the mirror,
+announcements should be made
+** on the dev@ list
+** on the user@ list
+** update currently listed version and download link on confluence Index
+page
+** (update this list as the community grows)
+* Set the newly released version to the Release status in JIRA so that
+people will be able to see it as released when reporting bugs
+** Go to the [JIRA site](https://issues.apache.org/jira/secure/project/ViewProject.jspa?pid=12310840)
+** click "Manage versions" under the Versions section
+** In the Operations column, click the Release link for the specified
+version
+
+*IMPORTANT*: Once a release is copied to the dist location, it *must not be
+modified*. This can signal that an attack is being performed. If an error
+is found, a new .Z release should be made.

Added: vcl/site/trunk/content/confluence_export/video---granting-two-sets-of-users-access-to-two-different-sets-of-images.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/video---granting-two-sets-of-users-access-to-two-different-sets-of-images.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/video---granting-two-sets-of-users-access-to-two-different-sets-of-images.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/video---granting-two-sets-of-users-access-to-two-different-sets-of-images.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,6 @@
+Title: Video - Granting Two Sets of Users Access to Two Different Sets of Images
+This video shows the steps outlined in [Example - Granting Two Sets of Users Access to Two Different Sets of Images](example---granting-two-sets-of-users-access-to-two-different-sets-of-images.html)
+
+This video was created using [Wink](http://www.debugmode.com/wink/)
+
+!example_two_sets_of_groups.swf|width=895,height=581!



Mime
View raw message