vcl-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jftho...@apache.org
Subject svn commit: r1430372 [1/11] - /vcl/site/trunk/content/confluence_export/
Date Tue, 08 Jan 2013 16:37:56 GMT
Author: jfthomps
Date: Tue Jan  8 16:37:53 2013
New Revision: 1430372

URL: http://svn.apache.org/viewvc?rev=1430372&view=rev
Log:
commit of pages exported from confluence and converted to markdown format

Added:
    vcl/site/trunk/content/confluence_export/
    vcl/site/trunk/content/confluence_export/2.2-database-configuration.mdtext
    vcl/site/trunk/content/confluence_export/2.2-management-node-installation.mdtext
    vcl/site/trunk/content/confluence_export/2.2-web-code-installation.mdtext
    vcl/site/trunk/content/confluence_export/2009-01-incubator-vcl-report.mdtext
    vcl/site/trunk/content/confluence_export/2009-02-incubator-vcl-report.mdtext
    vcl/site/trunk/content/confluence_export/2009-05-incubator-vcl-report.mdtext
    vcl/site/trunk/content/confluence_export/2009-11-incubator-vcl-report.mdtext
    vcl/site/trunk/content/confluence_export/2010-02-incubator-vcl-report.mdtext
    vcl/site/trunk/content/confluence_export/2010-05-incubator-vcl-report.mdtext
    vcl/site/trunk/content/confluence_export/2010-08-incubator-vcl-report.mdtext
    vcl/site/trunk/content/confluence_export/2010-11-incubator-vcl-report.mdtext
    vcl/site/trunk/content/confluence_export/2011-02-incubator-vcl-report.mdtext
    vcl/site/trunk/content/confluence_export/2011-05-incubator-vcl-report.mdtext
    vcl/site/trunk/content/confluence_export/2011-08-incubator-vcl-report.mdtext
    vcl/site/trunk/content/confluence_export/2011-11-incubator-vcl-report.mdtext
    vcl/site/trunk/content/confluence_export/2012-02-incubator-vcl-report.mdtext
    vcl/site/trunk/content/confluence_export/2012-05-incubator-vcl-report.mdtext
    vcl/site/trunk/content/confluence_export/2012-07-25-apache-vcl-board-report.mdtext
    vcl/site/trunk/content/confluence_export/2012-08-15-apache-vcl-board-report.mdtext
    vcl/site/trunk/content/confluence_export/2012-09-19-apache-vcl-board-report.mdtext
    vcl/site/trunk/content/confluence_export/2012-12-19-apache-vcl-board-report.mdtext
    vcl/site/trunk/content/confluence_export/adding-a-new-locale-to-the-vcl-web-frontend.mdtext
    vcl/site/trunk/content/confluence_export/adding-ldap-authentication.mdtext
    vcl/site/trunk/content/confluence_export/adding-local-vcl-accounts.mdtext
    vcl/site/trunk/content/confluence_export/adding-new-os-module.mdtext
    vcl/site/trunk/content/confluence_export/adding-xcat-kickstart-based-image.mdtext
    vcl/site/trunk/content/confluence_export/additional-steps-for-linux-images.mdtext
    vcl/site/trunk/content/confluence_export/additional-steps-for-windows-images.mdtext
    vcl/site/trunk/content/confluence_export/advanced-image-options.mdtext
    vcl/site/trunk/content/confluence_export/apache-derby-database.mdtext
    vcl/site/trunk/content/confluence_export/apache-vcl.mdtext
    vcl/site/trunk/content/confluence_export/automated-installation-of-vcl-and-xcat.mdtext
    vcl/site/trunk/content/confluence_export/automated-installation-of-vcl.mdtext
    vcl/site/trunk/content/confluence_export/backend.mdtext
    vcl/site/trunk/content/confluence_export/base-image-creation.mdtext
    vcl/site/trunk/content/confluence_export/becoming-a-committer.mdtext
    vcl/site/trunk/content/confluence_export/board-reports.mdtext
    vcl/site/trunk/content/confluence_export/capture-a-base-image.mdtext
    vcl/site/trunk/content/confluence_export/configuration-management.mdtext
    vcl/site/trunk/content/confluence_export/configure-the-default-profile.mdtext
    vcl/site/trunk/content/confluence_export/configuring-a-standalone-vcl-environment-using-vmware-server-1.x.mdtext
    vcl/site/trunk/content/confluence_export/configuring-a-standalone-vcl-environment-using-vmware-server-2.0.mdtext
    vcl/site/trunk/content/confluence_export/copy-administator-profile-with-bat-scripts.mdtext
    vcl/site/trunk/content/confluence_export/create-a-linux-base-image.mdtext
    vcl/site/trunk/content/confluence_export/create-a-windows-base-image.mdtext
    vcl/site/trunk/content/confluence_export/creating-a-cluster-enviroment.mdtext
    vcl/site/trunk/content/confluence_export/creating-a-new-image-from-a-base-image.mdtext
    vcl/site/trunk/content/confluence_export/creating-a-virtual-machine-for-the-vcl-server.mdtext
    vcl/site/trunk/content/confluence_export/database-configuration.mdtext
    vcl/site/trunk/content/confluence_export/database-schema.mdtext
    vcl/site/trunk/content/confluence_export/dependencies.mdtext
    vcl/site/trunk/content/confluence_export/developer-guidelines.mdtext
    vcl/site/trunk/content/confluence_export/example---granting-two-sets-of-users-access-to-two-different-sets-of-images.mdtext
    vcl/site/trunk/content/confluence_export/for-vcl-users.mdtext
    vcl/site/trunk/content/confluence_export/frontend.mdtext
    vcl/site/trunk/content/confluence_export/further-steps-if-using-only-vmware.mdtext
    vcl/site/trunk/content/confluence_export/further-steps-if-using-xcat.mdtext
    vcl/site/trunk/content/confluence_export/graduation-board-resolution.mdtext
    vcl/site/trunk/content/confluence_export/graduation-migration-todo.mdtext
    vcl/site/trunk/content/confluence_export/granting-access-to-a-new-image.mdtext
    vcl/site/trunk/content/confluence_export/guidelines-for-large-contributions.mdtext
    vcl/site/trunk/content/confluence_export/how-do-i-grant-a-user-access-to-an-image?.mdtext
    vcl/site/trunk/content/confluence_export/how-to-increase-the-size-of-a-virtual-machine-hard-drive-under-vmware-esxi.mdtext
    vcl/site/trunk/content/confluence_export/image-capture-sequence.mdtext
    vcl/site/trunk/content/confluence_export/image-creation-problems.mdtext
    vcl/site/trunk/content/confluence_export/image-load-flow.mdtext
    vcl/site/trunk/content/confluence_export/index.mdtext
    vcl/site/trunk/content/confluence_export/install-windows-for-a-base-image.mdtext
    vcl/site/trunk/content/confluence_export/issue-tracking.mdtext
    vcl/site/trunk/content/confluence_export/kvm-configuration.mdtext
    vcl/site/trunk/content/confluence_export/lab.pm-provisioning-module.mdtext
    vcl/site/trunk/content/confluence_export/libvirt-provisioning-module.mdtext
    vcl/site/trunk/content/confluence_export/making-a-reservation.mdtext
    vcl/site/trunk/content/confluence_export/managegroups.py---remotely-managing-user-groups.mdtext
    vcl/site/trunk/content/confluence_export/management-node-installation.mdtext
    vcl/site/trunk/content/confluence_export/missing_from_export.mdtext
    vcl/site/trunk/content/confluence_export/modularized-architecture.mdtext
    vcl/site/trunk/content/confluence_export/network-layout.mdtext
    vcl/site/trunk/content/confluence_export/network-requirements.mdtext
    vcl/site/trunk/content/confluence_export/operating-system-module-inheritance.mdtext
    vcl/site/trunk/content/confluence_export/operating-system-module-interface-specification.mdtext
    vcl/site/trunk/content/confluence_export/patch-to-remove-mcrypt-dependency.mdtext
    vcl/site/trunk/content/confluence_export/pre-release-test-procedures.mdtext
    vcl/site/trunk/content/confluence_export/provisioning-engine-module-interface-specification.mdtext
    vcl/site/trunk/content/confluence_export/save-the-image.mdtext
    vcl/site/trunk/content/confluence_export/security-features.mdtext
    vcl/site/trunk/content/confluence_export/states.mdtext
    vcl/site/trunk/content/confluence_export/storage-management.mdtext
    vcl/site/trunk/content/confluence_export/sysprep-fails-because-of-unsigned-storage-drivers.mdtext
    vcl/site/trunk/content/confluence_export/terms.mdtext
    vcl/site/trunk/content/confluence_export/troubleshooting.mdtext
    vcl/site/trunk/content/confluence_export/updating-an-existing-image.mdtext
    vcl/site/trunk/content/confluence_export/upgrade-from-previous-version.mdtext
    vcl/site/trunk/content/confluence_export/variable-table.mdtext
    vcl/site/trunk/content/confluence_export/vcl-2.1-goals.mdtext
    vcl/site/trunk/content/confluence_export/vcl-2.1-installation.mdtext
    vcl/site/trunk/content/confluence_export/vcl-2.1.mdtext
    vcl/site/trunk/content/confluence_export/vcl-2.2-installation.mdtext
    vcl/site/trunk/content/confluence_export/vcl-2.2.1---adding-ldap-authentication.mdtext
    vcl/site/trunk/content/confluence_export/vcl-2.2.1---further-steps-if-using-vmware.mdtext
    vcl/site/trunk/content/confluence_export/vcl-2.2.1---further-steps-if-using-xcat.mdtext
    vcl/site/trunk/content/confluence_export/vcl-2.2.1-database-installation.mdtext
    vcl/site/trunk/content/confluence_export/vcl-2.2.1-installation.mdtext
    vcl/site/trunk/content/confluence_export/vcl-2.2.1-management-node-installation.mdtext
    vcl/site/trunk/content/confluence_export/vcl-2.2.1-web-code-installation.mdtext
    vcl/site/trunk/content/confluence_export/vcl-2.2.1.mdtext
    vcl/site/trunk/content/confluence_export/vcl-2.2.mdtext
    vcl/site/trunk/content/confluence_export/vcl-2.3---adding-ldap-authentication.mdtext
    vcl/site/trunk/content/confluence_export/vcl-2.3---further-steps-if-using-vmware.mdtext
    vcl/site/trunk/content/confluence_export/vcl-2.3---further-steps-if-using-xcat.mdtext
    vcl/site/trunk/content/confluence_export/vcl-2.3-configure-frontend-authentication.mdtext
    vcl/site/trunk/content/confluence_export/vcl-2.3-database-installation.mdtext
    vcl/site/trunk/content/confluence_export/vcl-2.3-installation.mdtext
    vcl/site/trunk/content/confluence_export/vcl-2.3-management-node-installation.mdtext
    vcl/site/trunk/content/confluence_export/vcl-2.3-web-code-installation.mdtext
    vcl/site/trunk/content/confluence_export/vcl-2.3.mdtext
    vcl/site/trunk/content/confluence_export/vcl-architecture.mdtext
    vcl/site/trunk/content/confluence_export/vcl-conf-call-2-5-2009.mdtext
    vcl/site/trunk/content/confluence_export/vcl-installation.mdtext
    vcl/site/trunk/content/confluence_export/vcl-release-procedures.mdtext
    vcl/site/trunk/content/confluence_export/video---granting-two-sets-of-users-access-to-two-different-sets-of-images.mdtext
    vcl/site/trunk/content/confluence_export/vmware-configuration.mdtext
    vcl/site/trunk/content/confluence_export/vmware-provisioning-module-information.mdtext
    vcl/site/trunk/content/confluence_export/web-code-installation.mdtext
    vcl/site/trunk/content/confluence_export/web-code-overview.mdtext

Added: vcl/site/trunk/content/confluence_export/2.2-database-configuration.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/2.2-database-configuration.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/2.2-database-configuration.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/2.2-database-configuration.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,51 @@
+Title: 2.2 Database Configuration
+{excerpt}This page describes how to create the VCL MySQL database and
+import the VCL database schema.{excerpt}
+
+
+<a name="2.2DatabaseConfiguration-*Prerequisites*"></a>
+## *Prerequisites*
+
+1. You should have mysql server 5.x installed.&nbsp;If mysql server is not
+installed:
+
+    yum install mysql-server -y
+    /sbin/chkconfig --level 345 mysqld on
+    /sbin/service mysqld start
+
+1. Your host based firewall (IPTables) should be configured to allow traffic
+from the web server and management server to connect to TCP port 3306
+(mysqld).
+
+
+<a name="2.2DatabaseConfiguration-*SettingUptheDatabaseforVCL*"></a>
+## *Setting Up the Database for VCL*
+
+1. start the mysql command line client by running 
+
+    mysql
+
+1. create a database in mysql named for use with VCL
+
+    CREATE DATABASE vcl;
+
+1. create a user with SELECT, INSERT, UPDATE, and DELETE privileges on the
+database you just created
+*NOTE*: Replace vcluserpassword with your own password\!
+
+    GRANT SELECT,INSERT,UPDATE,DELETE ON vcl.* TO 'vcluser'@'localhost'
+IDENTIFIED BY 'vcluserpassword';
+
+1. exit from the mysql command line client:
+
+    exit
+
+1. locate vcl.sql file
+The vcl.sql file should be contained in the release artifact you should
+have downloaded already. After extracting it, look in the mysql directory.
+1. import vcl.sql file into database
+
+    mysql vcl < vcl.sql
+
+
+Next step: [Web Code Installation](2.2-web-code-installation.html)

Added: vcl/site/trunk/content/confluence_export/2.2-management-node-installation.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/2.2-management-node-installation.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/2.2-management-node-installation.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/2.2-management-node-installation.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,379 @@
+Title: 2.2 Management Node Installation
+{excerpt}This page describes how to install and configure the backend VCL
+management node components including the required Perl modules, VCL daemon
+(vcld), and Windows utility dependencies.{excerpt}
+
+<a name="2.2ManagementNodeInstallation-Assumptions"></a>
+## Assumptions
+
+The following instructions assume the VCL [database has been installed and configured](database-configuration.html)
+ and that the managment node information has been added to the database as
+described on the [web code installation page|Web Code Installation]
+. This also assumes that the perl-DBD-MySQL-3.x and the mysql client
+(mysql-5.x) packages are installed, for database communications.
+
+<a name="2.2ManagementNodeInstallation-InstallingVCLManagementNodeCode-PerlDaemon"></a>
+## Installing VCL Management Node Code - Perl Daemon
+
+1. If you haven't already done so, download and extract a copy of the latest
+release. There is a link to it under the Project Resources section on our
+wiki [home page](apache-vcl.html)
+. Look for "Current version".
+1. copy the "managementnode" directory to a location, typically /usr/local
+
+    cp -r managementnode /usr/local/vcl
+
+
+<a name="2.2ManagementNodeInstallation-InstallRequiredPackages"></a>
+## Install Required Packages
+
+The following packages to be installed on the OS before installing the
+required Perl modules.&nbsp; These packages must be installed if they were
+not installed as part of your base Linux install.&nbsp; It is easiest to
+use the package management utility for your OS \--\- yum, rpm, or other.
+
+* expat
+* expat-devel
+* gcc
+* krb5-libs
+* krb5-devel
+* libxml2
+* libxml2-devel
+* nmap
+* openssl
+* openssl-devel
+* perl-DBD-MySQL
+* xmlsec1-openssl
+
+To install these packages using yum:
+
+
+
+<a name="2.2ManagementNodeInstallation-InstallRequiredPerlModules"></a>
+## Install Required Perl Modules
+
+The VCL Perl code running on the management node requires additional Perl
+modules in order to run. These Perl modules are available from [CPAN - The Comprehensive Perl Archive Network](http://cpan.org/)
+. A search engine for CPAN modules is available at [search.cpan.org|http://search.cpan.org/]
+.  The Perl modules are licensed under the [Artistic|http://dev.perl.org/licenses/artistic.html]
+ and [GPL|http://www.opensource.org/licenses/gpl-license.php]
+ licenses.
+
+* [Class-Data-Inheritable](http://search.cpan.org/dist/Class-Data-Inheritable/)
+* [Compress-Raw-Zlib](http://search.cpan.org/dist/Compress-Raw-Zlib/)
+* [Crypt-SSLeay](http://search.cpan.org/dist/Crypt-SSLeay/)
+* [DBI](http://search.cpan.org/dist/DBI/)
+* [Devel-StackTrace](http://search.cpan.org/dist/Devel-StackTrace/)
+* [Digest-SHA1](http://search.cpan.org/dist/Digest-SHA1/)
+* [Exception-Class](http://search.cpan.org/dist/Exception-Class/)
+* [HTML-Parser](http://search.cpan.org/dist/HTML-Parser/)
+* [IO-Compress](http://search.cpan.org/dist/IO-Compress/)
+* [libwww-perl](http://search.cpan.org/dist/libwww-perl/)
+* [MailTools](http://search.cpan.org/dist/MailTools/)
+* [Object-InsideOut](http://search.cpan.org/dist/Object-InsideOut/)
+* [RPC-XML](http://search.cpan.org/dist/RPC-XML/)
+* [XML-Parser](http://search.cpan.org/dist/XML-Parser/)
+* [YAML](http://search.cpan.org/dist/YAML/)
+
+
+<a name="2.2ManagementNodeInstallation-Runinstall_perl_libs.plScript"></a>
+#### Run install_perl_libs.pl Script
+
+A script is provided in the managementnode/bin directory called
+*install_perl_libs.pl* which will attempt to download and install the
+required perl libraries.&nbsp; Run the script:
+
+
+
+
+<a name="2.2ManagementNodeInstallation-HowtoTestifRequiredPerlModulesareInstalled"></a>
+#### How to Test if Required Perl Modules are Installed
+
+Run the following command to execute the utils.pm file:
+
+    perl /usr/local/vcl/lib/VCL/utils.pm
+
+Executing utils.pm does not actually do anything but this will tell you if
+VCL will be able to run.&nbsp; If any Perl modules are missing you will see
+"Can't locate" lines:
+
+
+
+    pre-execution: config file being used: /etc/vcl/vcld.conf
+    Uncaught exception from user code:
+            VCLD : /etc/vcl/vcld.conf does not exist, exiting --  No such file
+or directory
+    BEGIN failed--compilation aborted at /usr/local/vcl/lib/VCL/utils.pm line
+616.
+     at /usr/local/vcl/lib/VCL/utils.pm line 616
+
+
+<a name="2.2ManagementNodeInstallation-WhattodoifaModuleisMissing"></a>
+#### What to do if a Module is Missing
+
+1. Determine the name of the missing module by looking at the "Can't locate"
+line
+1. Search for the missing module on search.cpan.org and install it manually
+
+
+<a name="2.2ManagementNodeInstallation-HowtoInstallaPerl&nbsp;ModuleManually"></a>
+#### How to Install a Perl&nbsp;Module Manually
+
+1. Change directories to /tmp:
+*cd /tmp*&nbsp;
+1. Download the module's source package using wget:
+*wget* *[http://search.cpan.org/CPAN/authors/id/G/GA/GAAS/libwww-perl-5.827.tar.gz](http://search.cpan.org/CPAN/authors/id/G/GA/GAAS/libwww-perl-5.827.tar.gz)
+*
+1. Unpack the source package using tar:
+*tar xzf libwww-perl-5.827.tar.gz*
+1. The previous command should have created a libwww-perl-5.827 directory,
+change to this directory:
+*cd libwww-perl-5.827*
+1. Create a makefile with the following command:
+*perl Makefile.PL*
+1. Compile the module:
+*make*
+1. Test the module:
+*make test*
+1. Install the module:
+*make install*
+The last line you should see should be:
+
+
+
+<a name="2.2ManagementNodeInstallation-HowtoInstallaPerlModuleUsingCPAN"></a>
+#### How to Install a Perl Module Using CPAN
+
+1. Enter the CPAN shell:
+*perl \-MCPAN \-e shell*
+1. You will need to configure CPAN if it's the first time it is being run.
+Enter *No* at the first prompt to auto-configure the CPAN module.
+1. Search for a module using the "m" command:
+*m /Zlib/*
+You should find the module you were looking for on a line like this:
+
+
+1. Install the module:
+*install Compress::Zlib*
+1. Answer *yes* if asked to install any prerequisite modules
+The last line you should see should be:
+
+
+
+<a name="2.2ManagementNodeInstallation-Configurevcld.conf"></a>
+## Configure vcld.conf
+
+1. Create the /etc/vcl directory:
+*mkdir /etc/vcl*&nbsp;
+1. Copy the generic vcld.conf file to /etc/vcl:
+*cp /usr/local/vcl/etc/vcl/vcld.conf /etc/vcl*
+1. Edit the /etc/vcl/vcld.conf file:
+*vi /etc/vcl/vcld.conf*
+The following lines must be configured in order to start the VCL daemon
+(vcld) and allow it to check in to the database:
+1. * FQDN - the fully qualified name of the management node, this should
+match the name that was configured for the management node in the database
+1. * server - the IP address or FQDN of the database server
+1. * LockerWrtUser - database user account with write privileges
+1. * wrtPass - database user password
+1. Save the vcld.conf file
+
+<a name="2.2ManagementNodeInstallation-InstalltheVCLDaemon(vcld)&nbsp;Service"></a>
+## Install the VCL Daemon (vcld)&nbsp;Service
+
+1. Copy the vcld service script to /etc/init.d and name it vcld:
+*cp /usr/local/vcl/bin/S99vcld.linux /etc/init.d/vcld*
+1. Add the vcld service using chkconfig:
+*/sbin/chkconfig \--add vcld*
+1. Configure the vcld service to automatically run at runtime levels 3-5:
+*/sbin/chkconfig \--level 345 vcld on*
+
+<a name="2.2ManagementNodeInstallation-StartandCheck&nbsp;thevcldService"></a>
+## Start and Check&nbsp;the vcld Service
+
+1. Start the vcld service:
+*/sbin/service vcld start*
+You should see output similar to the following:
+
+    pre-execution: config file being used: /etc/vcl/vcld.conf
+    FQDN is not listed
+    pre-execution: process name is set to: vcld
+    pre-execution: verbose mode is set to: 1
+    pre-execution: testing mode is set to: 0
+    pre-execution: log file being used: /var/log/vcld.log
+    pre-execution: PID file being used: /var/run/vcld.pid
+    Created process 23696 renamed to vcld ...
+                                                               [  OK  ]
+
+*/etc/init.d/vcld start*
+1. Check the vcld service by monitoring the vcld.log file:
+*tail \-f /var/log/vcld.log*
+You should see the following being added to the log file every few seconds
+if the management node is checking in with the database:
+
+
+
+<a name="2.2ManagementNodeInstallation-ConfiguretheSSHClient"></a>
+### Configure the SSH Client
+
+To insure that the management node can SSH into your virtual machines
+without problems, you will need to edit the SSH client config for the root
+user:
+
+
+
+
+Add the following lines to the top of the configuration file.
+
+
+    Host <vmhost> <vmhost ip>
+       UserKnownHostsFile /dev/null
+       StrictHostKeyChecking no
+
+
+Where:
+
+* <vmhost> - Is a wildcard reference to the hostnames for your virtual
+machines.
+** For example, if your VM hostnames look like: vmhost1, vmhost2,
+vmhost3.... then replace <vmhost> with "vmhost*"
+
+* <vmhost ip> - Is a wildcard IP reference to the IPs used by your virtual
+machines.
+** For example, if your VMs all have IP addresses starting with 10.0.0,
+then replace <vmhost ip> with "10.0.0.*"
+
+This will insure that new VM hosts will not hang on the known hosts prompts
+when the management node attempts to connect to them for the first time.
+
+
+<a name="2.2ManagementNodeInstallation-DownloadRequiredUtilities&Drivers"></a>
+## Download Required Utilities & Drivers
+
+
+
+<a name="2.2ManagementNodeInstallation-WindowsXPandServer2003DeploymentTools(Sysprep)"></a>
+#### Windows XP and Server 2003 Deployment Tools (Sysprep)
+
+
+The Windows XP and Server 2003 Deployment Tools are available for free from
+Microsoft and are required in order for the capture of Windows XP and
+Server 2003 VCL images to work.&nbsp; The Sysprep utility is included in
+the Deployment Tools.&nbsp; You do not need to download Sysprep for Windows
+7 or Windows Server 2008 because it is included in the operating system.
+
+
+
+Download: [Windows XP Service Pack 3 Deployment Tools](http://www.microsoft.com/downloads/details.aspx?FamilyID=673a1019-8e3e-4be0-ac31-70dd21b5afa7&displaylang=en)
+Download: [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)
+
+
+
+
+
+
+The Sysprep files need to be extracted from the file you download which is
+in Microsoft's .cab format.&nbsp; It is easiest to extract the files on a
+Windows computer.&nbsp; Windows Explorer is able to open the .cab file and
+then the files contained within can be copied elsewhere.&nbsp; There are
+also some Linux utilities which claim to be able to extract .cab files.
+
+Copy the extracted Windows XP Sysprep files to the following directory on
+the management node after they have been extracted:
+{panel}
+/usr/local/vcl/tools/Windows_XP/Utilities/Sysprep
+{panel}Copy the extracted Windows Server 2003 Sysprep files to the
+following directory on the management node after they have been extracted:
+{panel}
+/usr/local/vcl/tools/Windows_Server_2003/Utilities/Sysprep
+{panel}
+The Sysprep directories should already exist on the management node because
+they exist the Subversion repository.&nbsp; The Sysprep directories should
+contain the following files at a minimum:
+{panel}
+\-rw-rw-r-\- 1 root root 25600 Aug 18 17:32 setupcl.exe
+\-rw-rw-r-\- 1 root root 88576 Aug 18 17:32 sysprep.exe
+{panel}
+
+Your Windows product keys and/or KMS server addresses need to be entered
+into the VCL database in order to capture a Windows image using
+Sysprep.&nbsp; Enter the information into the database by running the the
+following command:
+
+{panel}
+/usr/local/vcl/bin/vcld \-setup
+{panel}
+
+Select "Windows OS Module" and follow the prompts.
+
+
+<a name="2.2ManagementNodeInstallation-DownloadDrivers"></a>
+#### Download Drivers
+
+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 Vista) 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.
+
+For example, if a chipset driver works for all versions of Windows, it can
+be saved in:
+*tools/Windows/Drivers/Chipset*
+
+If Windows XP and Windows Server 2003 both use the same network driver, it
+can be saved in:
+*tools/Windows_Version_5/Drivers/Network*
+
+If a storage driver only works for Windows XP, it should be saved in:
+*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.&nbsp; In the example above, the order would be:
+1. *tools/Windows/Drivers/Chipset*
+1. *tools/Windows_Version_5/Drivers/Network*
+1. *tools/Windows_XP/Drivers/Storage*
+
+The resulting directory structure on the Windows computer will be:
+* *C:\Cygwin\home\root\VCL\Drivers*
+** *\Chipset* \- driver works for all versions of windows
+** *\Network* \- driver works for Windows XP and Server 2003
+** *\Storage* \- driver only works for Windows XP
+
+The following list shows which driver files should be saved in the driver
+directories:
+
+* *tools/Windows/Drivers* \- drivers common to all versions of Windows
+** *tools/Windows_Version_5/Drivers* \- drivers used by Windows XP and
+Server 2003
+*** *tools/Windows_Version_XP/Drivers* \- drivers only used by Windows XP
+*** *tools/Windows_Version_Server_2003/Drivers* \- drivers only used by
+Windows Server 2003
+** *tools/Windows_Version_6/Drivers* \- drivers used by Windows Vista and
+Server 2008
+*** *tools/Windows_Vista/Drivers* \- drivers only used by Windows Vista
+*** *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.&nbsp; For example:
+* *tools/Windows_Version_XP/Drivers*
+** *Chipset*
+** *Network*
+** *Storage*
+** *Video*
+
+
+<a name="2.2ManagementNodeInstallation-"></a>
+### 

Added: vcl/site/trunk/content/confluence_export/2.2-web-code-installation.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/2.2-web-code-installation.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/2.2-web-code-installation.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/2.2-web-code-installation.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,136 @@
+Title: 2.2 Web Code Installation
+{excerpt}This page describes how to install and configure the frontend VCL
+web code components including the web server prerequisites and frontend VCL
+web code. It also describes how to add local web accounts, configure LDAP
+authentication, and set the timezone correctly.{excerpt}
+
+
+<a name="2.2WebCodeInstallation-*Prerequisites*"></a>
+## *Prerequisites*
+
+Your web server should meet the following criteria before installing the
+frontend VCL code:
+* Apache HTTP Server v1.3 or v2.x with SSL enabled - while VCL may run
+under another webserver capable of running PHP code, it has only been
+tested to work with Apache HTTP Server
+* PHP 5
+* php modules that should be installed (depending on your Linux distro,
+some of these may be compiled in to php instead of being a separate
+module):
+** php-gd
+** php-json (if your PHP version is < 5.2, this is not required)
+** php-mcrypt
+** php-mysql
+** php-openssl
+** php-sysvsem
+** php-xml
+** php-xmlrpc
+** php-ldap (if you will be using ldap authentication)
+* If you are running RedHat or CentOS, these can be installed with
+
+    yum install httpd mod_ssl php-gd php-mcrypt php-mysql php-xml php-xmlrpc
+php-ldap
+
+* 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 that up on CentOS.
+* useful to have the server set up to be able to send debugging emails
+* php-mcrypt requires libmcrypt and mcrypt libraries as dependencies. 
+These may need to be installed first.
+
+<a name="2.2WebCodeInstallation-*InstallingVCLFrontendWebCode*"></a>
+## *Installing VCL Frontend Web Code*
+
+1. If you haven't already done so, download and extract a copy of the latest
+release. There is a link to it under the Project Resources section on our
+wiki [home page](apache-vcl.html)
+. Look for "Current version".
+1. copy the "web" directory to a location somewhere under the web root of
+your web server:
+
+    cp -r web/ /var/www/html/vcl
+
+1. copy/rename secrets-default.php to secrets.php
+1. modify vcl/.ht-inc/secrets.php
+1. * set $vclhost, $vcldb, $vclusername, and $vclpassword to match your
+database setup
+1. * create random passwords for $mcryptkey, $mcryptiv, and $pemkey -
+$mcryptiv must be 8 hex characters
+1. run the genkeys.sh script from within vcl/.ht-inc and give it $pemkey
+from secrets.php as the passphrase (3 times, copy/paste is a good idea
+here)
+1. copy/rename conf-default.php to conf.php
+1. modify vcl/.ht-inc/conf.php to match your site - COOKIEDOMAIN needs to be
+the domain name your web server is using, or left blank if you are
+accessing it by IP only.
+\**You really need to modify every entry in the "Things in this section
+must be modified" part of the file.*\*
+1. \**NOTICE*\* JpGraph 2.x is no longer available.  JpGraph 3.x is released
+under a dual license. QPL 1.0 (Qt Free Licensee).  Free for non-commercial,
+open-source or educational use (JpGraph Professional License for commercial
+use).  If you are planning to use this for commercial use and don't want to
+pay for JpGraph, you can safely skip this step with the only side effect of
+not being able to display a few graphs on the statistics page.
+Download JpGraph from [http://www.aditus.nu/jpgraph/jpdownload.php](http://www.aditus.nu/jpgraph/jpdownload.php)
+1. * download the 3.x series, extract it, and copy the src directory from it
+to vcl/.ht-inc/jpgraph
+1. make the .ht-inc/maintenance directory writable by the web server user -
+i.e. if the httpd process is running as user 'apache' run 'chown apache
+.ht-inc/maintenance'
+1. open the testsetup.php page in a web browser
+1. * i.e. 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. now, open the index.php page in your browser
+1. select Local Account and use 'admin' as the user and 'adminVc1passw0rd'
+as the password
+\**Now would be a good time to change the password from the default by
+going to User Preferences
+1. click the "Management Nodes" link
+1. enter the hostname and IP of your management node
+1. click Add
+1. fill in these additional required fields:
+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 - probably just enter "/etc/vcl/vcl.key"
+1. optionally, fill in these unrequired 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
+
+[Further steps if using only VMWare](further-steps-if-using-only-vmware.html)
+
+
+[Further steps if using xCAT](further-steps-if-using-xcat.html)
+
+
+Next Step: [Management Node Installation](2.2-management-node-installation.html)
+
+
+<a name="2.2WebCodeInstallation-*Addingextralocalaccounts*"></a>
+## *Adding extra local accounts*
+
+Additional local accounts can now be added using the backend code. After
+you have finished the backend install, run
+
+    vcld -setup
+
+select vcl base module option and follow the prompts.
+
+<a name="2.2WebCodeInstallation-AddingLDAPAuthentication"></a>
+## Adding LDAP Authentication
+instructions on [Adding LDAP Authentication](adding-ldap-authentication.html)
+ have been moved to a separate page

Added: vcl/site/trunk/content/confluence_export/2009-01-incubator-vcl-report.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/2009-01-incubator-vcl-report.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/2009-01-incubator-vcl-report.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/2009-01-incubator-vcl-report.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,23 @@
+Title: 2009-01 Incubator VCL Report
+Included is the monthly status report for VCL to the Incubator PMC for
+January 2009
+
+* Community
+The community has been active on the vcl-dev mailing list.  Some new
+interested parties have subscribed and open discussion about goals,
+development processes, etc. have been happening.
+
+There has been some discussion about the use of the project name VCL as NC
+State is still using this name for their student computing lab.  The issue
+was raised about whether this is acceptable or not.  This issue should be
+resolved before the next board report.
+
+
+* Source Code
+Code has been committed and folks are getting accustomed to the structure
+and layout of the VCL architecture.
+
+
+
+* Miscellaneous
+No issues at this time.

Added: vcl/site/trunk/content/confluence_export/2009-02-incubator-vcl-report.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/2009-02-incubator-vcl-report.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/2009-02-incubator-vcl-report.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/2009-02-incubator-vcl-report.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,25 @@
+Title: 2009-02 Incubator VCL Report
+February 2009 VCL Incubator status report
+
+VCL has been incubating since December 2008
+
+VCL is a framework for doing cloud management of physical and virtual
+machines
+
+* Community
+There has been discussion on the vcl-dev list about how to handle JIRA
+issues, discussion on development and design of various aspects of VCL, the
+role of parts of the database component of VCL and how to use it, and
+whether or not having design meetings via phone conference are a good idea.
+
+Discussion about using the name VCL has not resumed; so, that issue has not
+yet been resolved.
+
+* Source Code is being actively contributed
+* Plans have started to use Confluence to manage the main website
+documentation
+* As current users of VCL report bugs and request features, we are pointing
+them to JIRA to create an account and file bugs/feature requests there
+* Creation of these reports has migrated from one of the project mentors to
+the contributing community - we're developing a process to ensure these are
+submitted on time in the future.

Added: vcl/site/trunk/content/confluence_export/2009-05-incubator-vcl-report.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/2009-05-incubator-vcl-report.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/2009-05-incubator-vcl-report.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/2009-05-incubator-vcl-report.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,44 @@
+Title: 2009-05 Incubator VCL Report
+<a name="2009-05IncubatorVCLReport-May&nbsp;2009VCLIncubatorstatusreport"></a>
+# May&nbsp;2009 VCL Incubator status report
+
+VCL has been incubating since December 2008.&nbsp;VCL is a framework for
+doing cloud management of physical and virtual machines.
+
+*Project Name*
+* Discussion about using the name VCL has continued but the issue has not
+been resolved.
+* A question was posed on the legal discussion list regarding the use of
+the VCL name.&nbsp;&nbsp;A response was givin indicating that NCSU should
+make it obvious that both the VCL name and code are donated to the ASF.
+* NCSU is working to make it obvious on its website that VCL is developed
+at the ASF.
+* The development community is working to remove references to NCSU from
+the VCL code.
+* More guidance is required from the project mentors or others from ASF in
+order to resolve this issue.
+
+*Development*
+* Code development has continued and many commits have been made to the ASF
+VCL repository.
+* The vcl-dev list is actively being used to discuss development issues.
+* The Jira issue system is being used for tracking and to plan the first
+release.
+
+*Release Preparation*
+* The development community is researching the ASF release process.
+* Work is being done to complete a&nbsp;few&nbsp;Jira issues before
+creating release.
+
+*Documentation*
+* The community decided to use a Confluence wiki&nbsp;for the
+project&nbsp;documentation.
+* Work has been done to organize project documentation.
+* Documentation is actively being contributed to wiki.
+* Questions were asked of the mentors regarding the rules governing wiki
+contributions from individuals who have not signed the CLA. It is the
+community's understanding that a separate wiki will be needed \-\- one for
+official documentation included with releases and one containing
+contributions from individual who have not signed the CLA.
+* A&nbsp;request&nbsp;has been&nbsp;made to one of the mentors who had
+offered&nbsp;to create a 2nd wiki instance.

Added: vcl/site/trunk/content/confluence_export/2009-11-incubator-vcl-report.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/2009-11-incubator-vcl-report.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/2009-11-incubator-vcl-report.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/2009-11-incubator-vcl-report.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,83 @@
+Title: 2009-11 Incubator VCL Report
+VCL has been incubating since December 2008.&nbsp; VCL is a&nbsp;cloud
+computing platform for the management of physical and virtual machines.
+
+*Community Involvement*
+* The Apache VCL community is growing and people from several organizations
+are contributing
+* Questions about&nbsp;administration and end user use of Apache VCL are
+being asked and answered on the project's vcl-dev and vcl-user lists
+* A growing number of community members from multiple organizations are
+answering questions
+* Collaboration is occurring for architectural design and release planning
+via the vcl-dev list
+* Code patches have been discussed on the vcl-dev list and submitted to
+the&nbsp;Jira issue tracking system
+
+*Release Preparation - Apache VCL 2.1*
+* The community is working to complete the final administrative&nbsp;tasks
+required to issue the first release (Apache VCL 2.1)
+* Josh Thompson has volunteered to act as the&nbsp;release manager for 2.1
+per the advice of Matt Hogstrom, one of the project mentors
+* PGP keys have been created and added to the distribution area
+* A release candidate artifact&nbsp;has been created and is currently being
+discussed
+* Code and documentation updates are being made to the release candidate
+per community consensus
+* The tasks required to complete the release are being discussed on the
+vcl-dev list
+* Jira is being used to track the release tasks and to assemble the release
+changelog
+* Release procedures are being documented as the community develops its
+release process
+
+*3rd Party Dependencies*
+* Procedures for handling 3rd party dependencies are being worked out by
+the VCL community with help from the ASF legal-discuss list
+* Major components of VCL are written in Perl and the Apache VCL release
+will only contain Perl code developed by the ASF
+* A Perl interpreter and supplemental Perl modules are required.&nbsp;
+These are licensed under the Artistic License, GPL, and LGPL.
+* Concerns were brought up by the project mentors and a question was posed
+to the legal-discuss list.&nbsp; The question was answered and we are
+working on implementing the recommendation.
+
+*Project Name*
+* The Apache VCL project name issue has been resolved
+* NCSU has taken steps to clearly indicate on its Apache VCL instance
+website that Apache VCL is&nbsp;developed by the&nbsp;ASF
+* References to NCSU have been removed from the code
+* NCSU employees&nbsp;affiliated with the Apache VCL
+project&nbsp;routinely&nbsp;communicate that&nbsp;VCL is an ASF
+project&nbsp;and encourage colleagues of other organizations to do the same
+
+*Documentation*
+* A large amount of documentation has been added to the project's
+Confluence site
+* People from multiple organizations have contributed to improving the
+documentation, both by editing the pages themselves and by pointing out
+areas for improvement on the lists
+
+*Unresolved&nbsp;Issues*
+* As noted in the May 2009 report \-\- questions were asked of the mentors
+regarding the rules governing wiki contributions from individuals who have
+not signed the CLA. It is the community's understanding that a separate
+wiki will be needed \-\- one for official documentation included with
+releases and one containing contributions from individual who have not
+signed the CLA. &nbsp;A&nbsp;request&nbsp;has been&nbsp;made to one of the
+mentors who had offered&nbsp;to create a 2nd wiki instance.&nbsp; This has
+not been completed yet.
+* A request has been made to the mentors to create a Confluence committers
+group that contains the Apache VCL community members with a CLA on file
+* A request has been made to the mentors to create a Jira Committers role
+that contains the Apache VCL community members with a CLA on file
+* Some committers have lost administrative access to Jira.&nbsp; The
+project mentors have been asked to restore the permissions.
+
+*Top Issues Before Graduation*
+* Complete the release of Apache VCL 2.1
+* Continue to increase contributors from multiple institutions
+
+Signed off by mentor:
+
+* Alan Cabrera, Kevan Miller

Added: vcl/site/trunk/content/confluence_export/2010-02-incubator-vcl-report.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/2010-02-incubator-vcl-report.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/2010-02-incubator-vcl-report.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/2010-02-incubator-vcl-report.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,42 @@
+Title: 2010-02 Incubator VCL Report
+VCL has been incubating since December 2008. VCL is a cloud computing
+platform for the management of physical and virtual machines.
+
+*Community Involvement*
+* The Apache VCL community continues to grow. We're seeing more and more
+people start to contribute to our online documentation and file JIRA issues
+- some with patches attached.
+* We're seeing more feature requests come in which means more people are
+using VCL.
+* More people have joined the vcl-dev list and are asking questions as they
+install VCL at new locations.
+* Aaron Peeler, Andy Kurth, and Josh Thompson have become part of the PPMC.
+
+*First Official Release*
+* Our first official release (Apache VCL 2.1) was made available on Dec.
+4th, 2009.
+* We set a small number of features to work on for the next few releases in
+hopes of getting releases out more quickly.
+
+*3rd Party Dependencies*
+Procedures for handling 3rd party dependencies have been worked out. All
+dependencies that have incompatible licenses are now specified as "System
+Requirements" as stated under "System Requirements" at [http://www.apache.org/legal/3party.html](http://www.apache.org/legal/3party.html)
+
+*Documentation*
+* A large amount of documentation has been added to the project's
+Confluence site
+* People from multiple organizations have contributed to improving the
+documentation, both by editing the pages themselves and by pointing out
+areas for improvement on the lists
+* A new confluence space has been created to be used for managing the
+official documentation for the project. Documentation that should be
+included with releases will be migrated from the existing confluence space
+to the new one, and the autoexport of the space will be cron copied to our
+official documentation location. Work on this migration has not started.
+
+*Unresolved&nbsp;Issues*
+All unresolved issues reported in our 2009-11 report have been resolved.
+
+*Top Issues Before Graduation*
+* Continue to increase contributors from multiple institutions

Added: vcl/site/trunk/content/confluence_export/2010-05-incubator-vcl-report.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/2010-05-incubator-vcl-report.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/2010-05-incubator-vcl-report.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/2010-05-incubator-vcl-report.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,32 @@
+Title: 2010-05 Incubator VCL Report
+VCL has been incubating since December 2008. VCL is a cloud computing
+platform for the management of physical and virtual machines.
+
+*Community Involvement*
+* As stated in the previous report, the Apache VCL community continues to
+grow. We're seeing more and more people start to contribute to our online
+documentation and file JIRA issues.
+* A few people from the community have been contacted by PPMC members
+encouraging them to become more involved in the project.
+* We continue to see people from new locations asking questions on the
+vcl-dev list which shows that interest in VCL is continuing to grow.
+* Interest from the community to have support for a more recent version of
+VMWare Free Server drove the decision to swap that feature (originally
+slated for VCL 2.3) with cluster reservation improvements (originally
+slated for VCL 2.2).
+
+*Plans for next Release*
+* We hope to have our next release out by the end of June. This would be
+1/2 the time it took to get our previous release out. We hope to continue
+to shorten the time between releases as we move forward.
+
+*Documentation*
+* Migration of official documentation to our second Confluence space has
+started. The next step is to pick an autoexport template, and then set up a
+cronjob to copy the autoexported content to our official documentation
+location.
+
+*Top Issues Before Graduation*
+* Continue to increase contributors from multiple institutions
+
+Signed off by mentor:

Added: vcl/site/trunk/content/confluence_export/2010-08-incubator-vcl-report.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/2010-08-incubator-vcl-report.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/2010-08-incubator-vcl-report.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/2010-08-incubator-vcl-report.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,25 @@
+Title: 2010-08 Incubator VCL Report
+VCL has been incubating since December 2008. VCL is a cloud computing
+platform for the management of physical and virtual machines.
+
+*Community Involvement*
+* As stated in the previous report, the Apache VCL community continues to
+grow. We're seeing more people start to contribute to our online
+documentation and file JIRA issues.
+* As reported in the last board report a few people from the community have
+been contacted by PPMC members encouraging them to become more involved in
+the project. There was positive interest from a few, they submitted iCLA's
+but have yet to contribute anything for the PPMC's to review for
+acceptance. 
+* We see people from new locations asking questions on the vcl-dev list
+which shows that interest in VCL is growing.
+
+*Plans for next Release*
+* The next release has been delayed slightly to make sure all jira issues
+were satisfied correctly. The new target date is to have the next release
+candidate out available by the end of August 2010.
+
+*Top Issues Before Graduation*
+* Continue to increase contributors from multiple institutions
+
+Signed off by mentor:

Added: vcl/site/trunk/content/confluence_export/2010-11-incubator-vcl-report.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/2010-11-incubator-vcl-report.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/2010-11-incubator-vcl-report.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/2010-11-incubator-vcl-report.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,19 @@
+Title: 2010-11 Incubator VCL Report
+VCL has been incubating since December 2008. VCL is a cloud computing
+platform for the management of physical and virtual machines.
+
+*Community Involvement*
+* The Apache VCL user community continues to grow. We really need to get
+more committers. We have asked on our development list for more people to
+get involved and also individually contacted people encouraging them to get
+involved, but are still having trouble getting people on board.
+
+*Plans for next Release*
+* We announced our second release through ASF on Oct. 5th
+* We plan to reduce the number of items to go in to the next release in
+hopes of decreasing time between releases.
+
+*Top Issues Before Graduation*
+* Continue to increase contributors from multiple institutions
+
+Signed off by mentor:

Added: vcl/site/trunk/content/confluence_export/2011-02-incubator-vcl-report.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/2011-02-incubator-vcl-report.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/2011-02-incubator-vcl-report.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/2011-02-incubator-vcl-report.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,21 @@
+Title: 2011-02 Incubator VCL Report
+VCL has been incubating since December 2008. VCL is a cloud computing platform for the management of physical and virtual machines.[https://cwiki.apache.org/VCL/](https://cwiki.apache.org/VCL/)
+
+*Community Involvement*
+* We are very excited to introduce a new committer, David Hutchins.
+* As stated in the previous report, the Apache VCL community continues to
+grow. We're seeing more people start to contribute to our online
+documentation and file JIRA issues.
+* We continue to see growing interest in the VCL project from a variety of
+locations. Several others have submitted patches.&nbsp;
+
+*Plans for next Release*
+* The next release is scheduled toward the end of&nbsp;February. This will
+be a dot release (VCL 2.2.1) to fix a few bugs and add improved code for
+handling virtual machines. The 2.3 release is planned for late spring.
+
+*Top Issues Before Graduation*
+* Continue to increase contributors from multiple institutions.
+* Discuss next steps for Graduation with mentors. 
+
+Signed off by mentor:

Added: vcl/site/trunk/content/confluence_export/2011-05-incubator-vcl-report.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/2011-05-incubator-vcl-report.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/2011-05-incubator-vcl-report.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/2011-05-incubator-vcl-report.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,24 @@
+Title: 2011-05 Incubator VCL Report
+VCL has been incubating since December 2008. VCL is a cloud computing platform for the management of physical and virtual machines.[https://cwiki.apache.org/VCL/](https://cwiki.apache.org/VCL/)
+
+*Community Involvement*
+* As stated in the previous report, the Apache VCL community continues to
+grow. We're seeing more people start to contribute to our online
+documentation and file JIRA issues. We're also starting to see more patches
+attached to JIRA issues.
+* We continue to see growing interest in the VCL project from a variety of
+locations.
+
+*Releases*
+* We cut a new release that was primarily for bugfixes.  Apache VCL 2.2.1
+was released on April 8th, 2011. In our last report, we stated that we had
+hoped to get it out by the end of February. Other duties of the developers
+caused some of the delay. Additional delay was due to a bug found after the
+release voting took place, requiring a new round of voting.
+
+*Top Issues Before Graduation*
+* Continue to increase contributors to establish a more diverse development
+community
+
+
+Signed off by mentor:

Added: vcl/site/trunk/content/confluence_export/2011-08-incubator-vcl-report.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/2011-08-incubator-vcl-report.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/2011-08-incubator-vcl-report.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/2011-08-incubator-vcl-report.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,30 @@
+Title: 2011-08 Incubator VCL Report
+VCL has been incubating since December 2008. VCL is a cloud computing platform for the management of physical and virtual machines.[[https://cwiki.apache.org/VCL](http://cwiki.apache.org/VCL)
+|]
+
+*Community Involvement*
+* As stated in the previous report, the Apache VCL community continues to
+grow. We're seeing more people start to contribute to our online
+documentation and file JIRA issues. We're also starting to see more patches
+attached to JIRA issues.
+* We continue to see growing interest in the VCL project from a variety of
+locations.
+* We are currently working on growing the committers for Apache VCL
+project.
+
+*Releases*
+* The Apache VCL 2.2.1 version was release on April 8th 2011 and addressed
+bugfixes and minor improvements.
+* Our next release Apache VCL 2.3 is on track and we are targeting late
+fall timeframe. New features planned include support for the KVM hypervisor
+which is to be contributed by the community. In addition to KVM, the
+committers will address server loads, and the improvement of cluster
+reservations.
+
+*Top Issues Before Graduation*
+* Continue to increase contributors to establish a more diverse development
+community
+
+Signed off by mentor:
+
+Alan Cabrera

Added: vcl/site/trunk/content/confluence_export/2011-11-incubator-vcl-report.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/2011-11-incubator-vcl-report.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/2011-11-incubator-vcl-report.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/2011-11-incubator-vcl-report.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,46 @@
+Title: 2011-11 Incubator VCL Report
+VCL has been incubating since December 2008. VCL is a cloud computing  platform for the management of physical and virtual machines.\[[https://cwiki.apache.org/VCL](http://cwiki.apache.org/VCL)
+\|\]
+
+<a name="2011-11IncubatorVCLReport-CommunityInvolvement"></a>
+#### Community Involvement
+
+* Numerous Apache VCL community members have gained enough knowledge and
+are actively answering questions on the mailing lists.
+* Questions have been posted to the lists related to several new
+installations from around the world.
+* Development issues are being discussed with participants from many
+different organizations.
+
+<a name="2011-11IncubatorVCLReport-CodeContributions"></a>
+#### Code Contributions
+
+* Support for IBM Power7 hardware was discussed on the development
+list.&nbsp; Code and documentation was contributed by Sunil Venkatesh of
+the University of Maryland Baltimore County.
+* Received a contribution from Satoshi Kobayashi of Hitachi Ltd. Japan to
+add Multilingualization/internationalization of the web UI and several
+other improvements.
+* Received a provisioning module for VMware vCenter clusters from Aaron
+Coburn at Amherst college.
+* Mark Gardner from Virginia Tech is working on adding support for IPv6.
+
+<a name="2011-11IncubatorVCLReport-NewCommitters"></a>
+#### New Committers
+
+* Several individuals from different institutions have expressed interest
+in becoming committers.
+* The main barrier encountered is obtaining university legal department
+approval of individual and corporate contributor license agreements.&nbsp;
+Current committers are working with interested individuals to share
+experience and work through these issues.
+
+<a name="2011-11IncubatorVCLReport-TopIssuesBeforeGraduation"></a>
+#### Top Issues Before Graduation
+
+* Work with the individuals who have already contributed code to Apache VCL
+and have expressed interest in becoming a committer.&nbsp; Assist them with
+the process of submitting the license agreement.&nbsp; Complete the process
+by conducting a vote on the vcl-private list.
+
+Signed off by mentor:

Added: vcl/site/trunk/content/confluence_export/2012-02-incubator-vcl-report.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/2012-02-incubator-vcl-report.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/2012-02-incubator-vcl-report.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/2012-02-incubator-vcl-report.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,28 @@
+Title: 2012-02 Incubator VCL Report
+VCL has been incubating since December 2008. VCL is a cloud computing
+platform for the management of physical and virtual machines.
+
+New Committers
+
+* The Apache VCL community recently added Aaron Coburn of Amherst College
+as a committer. We welcome Aaron and look forward to his expertise and
+knowledge to help advance VCL software.
+* There are a couple of other potential committers that might be able to
+join the community as committers. We look forward to hopefully bring them
+aboard.
+
+Community Involvement
+
+* The Apache VCL community is seeing continued growth and interest around
+the world.&nbsp;
+* The community&nbsp;activity&nbsp;on the mailing list is an open
+discussion and members respectfully exchange ideas and provide support.
+
+Releases
+* Our next release is behind our intended schedule, we are working through
+the remaining issues and features. We are targeting a March Release for
+Apache VCL 2.3. This will included support for Vcenter, kvm hypervisors,
+server based profiles and lots of bug fixes.
+Top Issues Before Graduation
+* Continue to increase contributors to establish a more diverse development
+community.&nbsp;

Added: vcl/site/trunk/content/confluence_export/2012-05-incubator-vcl-report.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/2012-05-incubator-vcl-report.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/2012-05-incubator-vcl-report.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/2012-05-incubator-vcl-report.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,42 @@
+Title: 2012-05 Incubator VCL Report
+VCL has been incubating since December 2008. VCL is a cloud computing
+platform for the management of physical and virtual machines. It
+provides&nbsp;comparatively&nbsp;easy and simple base line install with a
+end-user self service interface.
+
+New Committers
+
+* The Apache VCL community recently added James O'Dell from California
+State University at Fullerton as a committer. We welcome James and look
+forward to his expertise and knowledge to help advance VCL project and
+community.
+
+New PPMC member
+
+* The Apache VCL PPMC recently added Aaron Coburn as a new PPMC member. The
+current PPMC welcomes Aaron.
+
+Community Involvement
+* The Apache VCL community is a growing community with global interest from
+Education and&nbsp;commercial&nbsp;entities.&nbsp;
+* The community is fast to respond to user questions and discuss design
+ideas in a respectful manner.
+* We have seen cross project interest as through a contribution of a VCL
+driver to the&nbsp;Apache LIBCLOUD project.
+* There are other potential&nbsp;candidates&nbsp;that have expressed
+interest in becoming committers. They are working through their initial
+contributions. We look forward to hopefully bring them aboard.
+
+Releases
+
+* Our next release has been delayed from our previous board report.
+* This 2.3 release is a very large release, including bug-fixes, support
+from kvm, VMWare vcenter,&nbsp;multi-lingualization,&nbsp;and approved
+contributions from the community.
+* We are in testing now and hope to generate a 2.3 release
+candidate&nbsp;in the next few days.
+
+Top Issues Before Graduation
+
+* Graduation work itself - As a community discuss graduation to determine
+if we are ready. If so proceed with starting the process.

Added: vcl/site/trunk/content/confluence_export/2012-07-25-apache-vcl-board-report.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/2012-07-25-apache-vcl-board-report.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/2012-07-25-apache-vcl-board-report.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/2012-07-25-apache-vcl-board-report.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,39 @@
+Title: 2012-07-25 Apache VCL Board Report
+DESCRIPTION
+
+VCL is a modular cloud computing platform which dynamically provisions and
+brokers remote access to compute resources including virtual machines,
+bare-metal computers, and resources in other cloud platforms. A
+self-service web portal is used to request resources and for
+administration. VCL became a TLP on June 20, 2012.
+
+CURRENT ACTIVITY
+* The community is working to complete the post-graduation tasks with the
+help of Infrastructure. [1](1.html)
+* Mailing lists have been moved to vcl.apache.org.
+* PMC and private list have been established.
+* Repository has been moved.
+* Project website will be migrated from Confluence to the CMS.
+* Attempted to release VCL 2.3 in June but bugs were found which required
+new release candidates. Decided to hold off until after graduation. A vote
+to release VCL 2.3 is currently underway. It will likely be released before
+the board meeting.
+
+RELEASES
+* None at the time this report was written. A vote to release VCL 2.3 is
+currently underway.
+
+COMMUNITY
+* Subscribers to the user list: 152
+* Subscribers to the dev list: 140
+* Committers: 9
+* PMC members: 6
+
+COMMITTER/PMC CHANGES
+* New committer: Dmitri Chebotarov (2012-5-30)
+
+ISSUES
+* There are no issues requiring board attention at this time.
+
+[1](1.html)
+ [https://issues.apache.org/jira/browse/INFRA-4761]

Added: vcl/site/trunk/content/confluence_export/2012-08-15-apache-vcl-board-report.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/2012-08-15-apache-vcl-board-report.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/2012-08-15-apache-vcl-board-report.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/2012-08-15-apache-vcl-board-report.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,34 @@
+Title: 2012-08-15 Apache VCL Board Report
+DESCRIPTION
+
+VCL is a modular cloud computing platform which dynamically provisions and
+brokers remote access to compute resources including virtual machines,
+bare-metal computers, and resources in other cloud platforms. A
+self-service web portal is used to request resources and for
+administration. VCL became a TLP on June 20, 2012.
+
+CURRENT ACTIVITY
+* The community has completed most of the post-graduation tasks with the
+help of Infrastructure. [1](1.html)
+* A CMS website has been created. [2](2.html)
+ We are working to migrate content from Confluence to the CMS.
+* A VCL 2.3.1 bugfix branch has been created. This will be released in a
+few months.
+* Development is beginning for VCL 2.4 features.
+
+RELEASES
+* VCL 2.3 was released on 2012-07-20
+
+COMMUNITY
+* Subscribers to the user list: 150
+* Subscribers to the dev list: 143
+* Committers: 9
+* PMC members: 6
+
+ISSUES
+* There are no issues requiring board attention at this time.
+
+[1](1.html)
+ [https://issues.apache.org/jira/browse/INFRA-4761]
+[2](2.html)
+ [http://vcl.apache.org]

Added: vcl/site/trunk/content/confluence_export/2012-09-19-apache-vcl-board-report.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/2012-09-19-apache-vcl-board-report.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/2012-09-19-apache-vcl-board-report.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/2012-09-19-apache-vcl-board-report.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,42 @@
+Title: 2012-09-19 Apache VCL Board Report
+DESCRIPTION
+
+VCL is a modular cloud computing platform which dynamically provisions and
+brokers remote access to compute resources including virtual machines,
+bare-metal computers, and resources in other cloud platforms. A
+self-service web portal is used to request resources and for
+administration. VCL became a TLP on June 20, 2012.
+
+CURRENT ACTIVITY
+* The community has completed the post-graduation tasks.
+* Work continues to migrate content from Confluence to the new CMS website
+and to improve the design.
+* Several commits have been made to the VCL 2.3.1 bugfix branch to address
+minor problems with VCL 2.3, which was released in July. VCL 2.3.1 will be
+released this fall.
+* Traffic on the lists has been fairly high, mostly due to questions
+related to recently released VCL 2.3.
+* Development is still in the beginning stage for the VCL 2.4 features. 
+Most development has been devoted to bug fixes.
+* One of the committers is working to develop code to provide a VCL block
+in Moodle. Some licensing concerns arose from this due to Moodle's GPL
+license. [1](1.html)
+ Guidance was provided by legal-discuss. It was decided for this to be a
+separate non-ASF project independent of the Apache VCL.
+
+RELEASES
+* None
+
+COMMUNITY
+* Subscribers to the user list: 154
+* Posts to user list, 8/2012: 130
+* Subscribers to the dev list: 144
+* Posts to dev list, 8/2012: 159
+* Committers: 9
+* PMC members: 6
+
+ISSUES
+* There are no issues requiring board attention at this time.
+
+[1](1.html)
+ http://markmail.org/thread/leb6jw5e3d45lswy

Added: vcl/site/trunk/content/confluence_export/2012-12-19-apache-vcl-board-report.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/2012-12-19-apache-vcl-board-report.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/2012-12-19-apache-vcl-board-report.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/2012-12-19-apache-vcl-board-report.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,35 @@
+Title: 2012-12-19 Apache VCL Board Report
+DESCRIPTION
+
+VCL is a modular cloud computing platform which dynamically provisions and
+brokers remote access to compute resources including virtual machines,
+bare-metal computers, and resources in other cloud platforms. A
+self-service web portal is used to request resources and for
+administration. VCL became a TLP on June 20, 2012.
+
+CURRENT ACTIVITY
+* Work continues to migrate content from Confluence to the new CMS website
+and to improve the design.
+* VCL 2.3.1 will likely be released before the December 2012 board meeting.
+This is a bug fix release. All of the issues targeted for VCL 2.3.1 have
+been resolved and the release process is beginning.
+* Most development has been devoted to addressing bugs in VCL 2.3 and
+preparing VCL 2.3.1. Work on new features slated for VCL 2.4 will increase
+now that VCL 2.3.1 is complete.
+* Alan Cabrera and Kevan Miller have resigned from the VCL PMC. They were
+mentors of the VCL project throughout incubation. The VCL community is
+grateful for all of their help.
+
+RELEASES
+* None
+
+COMMUNITY
+* Subscribers to the user list: 153
+* Posts to user list, 9/12-11/12: 211
+* Subscribers to the dev list: 137
+* Posts to dev list, 9/12-11/12: 167
+* Committers: 7
+* PMC members: 4
+
+ISSUES
+* There are no issues requiring board attention at this time.

Added: vcl/site/trunk/content/confluence_export/adding-a-new-locale-to-the-vcl-web-frontend.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/adding-a-new-locale-to-the-vcl-web-frontend.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/adding-a-new-locale-to-the-vcl-web-frontend.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/adding-a-new-locale-to-the-vcl-web-frontend.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,138 @@
+Title: Adding a New Locale to the VCL Web Frontend
+<a name="AddingaNewLocaletotheVCLWebFrontend-Introduction"></a>
+## Introduction
+
+VCL 2.3 has the first step in multilingualization by allowing the parts of
+the site that the basic user sees to be presented in different languages.
+The initial work was done and contributed by Toru Yokoyama in JIRA-485. 
+
+More work will be done in future releases to add multilingualization to all
+parts of the site. Also, there are currently several sections where a
+paragraph may be translated in portions instead of as a whole. This does
+not provide for optimal translations. This should be addressed if future
+releases.
+
+There are three places where translation work needs to happen to add a new
+language: a gettext translation file (.po or portable object file), a
+javascript translation file, and a few database entries.
+
+<a name="AddingaNewLocaletotheVCLWebFrontend-Obtainingnecessaryfiles"></a>
+## Obtaining necessary files
+Until the 2.3 release is out, the files referenced below will need to be
+obtained from subversion. You can either check out the whole directory
+structure for the web code or just get the needed files.
+
+You can check out the whole structure like this:
+{tip}svn co https://svn.apache.org/repos/asf/vcl/trunk/web/ vclweb{tip}
+
+You can get the individual files containing strings to be translated like
+this:
+{tip}
+svn export
+https://svn.apache.org/repos/asf/vcl/trunk/web/locale/po_files/vcl.po.template
+svn export
+https://svn.apache.org/repos/asf/vcl/trunk/web/js/nls/messages.js.template
+svn export https://svn.apache.org/repos/asf/vcl/trunk/mysql/update-vcl.sql
+{tip}
+
+For the update-vcl.sql file, you'll need to search for the string "Inserts
+for table `connectmethod`" (without the double quotes, with the back tick
+quotes). Then, the 2nd and 4th fields (corresponding to discription and
+connecttext) will need to be translated.
+
+<a name="AddingaNewLocaletotheVCLWebFrontend-Creatingagettexttranslationfile"></a>
+## Creating a gettext translation file
+There is a base translation file at vcl/locale/po_files/vcl.po.template.
+You need to create two new directories under vcl/locale for your new locale
+(using es_PR as an example):
+
+{tip}
+vcl/locale/es_PR/LC_MESSAGES
+vcl/locale/po_files/es_PR
+{tip}
+
+Next, create a file named *language* in the new locale directory
+(vcl/locale/es_PR) with the name you would like displayed in the drop-down
+box for selecting the locale:
+
+{tip}
+echo 'Spanish (PR)' &gt; vcl/locale/es_PR/language
+{tip}
+
+Next, copy vcl/locale/po_files/vcl.po.template under the new po path:
+
+{tip}
+cp vcl/locale/po_files/vcl.po.template vcl/locale/po_files/es_PR/vcl.po
+{tip}
+
+You need to translate each string in your new vcl.po file in to the new
+language. The file has pairs of lines like
+
+{tip}
+msgid "<H2>Welcome to the Virtual Computing Lab</H2>\n"
+msgstr ""
+{tip}
+
+You must translate the string listed after msgid and place the translation
+on the msgstr line. There is a program under Linux named poedit from the
+gettext suite that makes this easier. Make sure you incorporate any HTML in
+the string into your translated string.
+
+After you have translated everything, you need to compile the .po file into
+a .mo file using msgfmt, also from the gettext suite, placing the .mo file
+under the vcl/locale/es_PR/LC_MESSAGES/ path:
+
+{tip}
+msgfmt --output=vcl/locale/es_PR/LC_MESSAGES/vcl.mo
+vcl/locale/po/es_PR/vcl.po
+{tip}
+
+<a name="AddingaNewLocaletotheVCLWebFrontend-Creatingajavascripttranslationfile"></a>
+## Creating a javascript translation file
+There is a base translation file at vcl/js/nls/messages.js.template. You
+need to create a new directory under vcl/js/nls (using es_PR as an
+example):
+
+{tip}
+vcl/js/nls/es_PR
+{tip}
+
+Next, copy vcl/js/nls/messages.js.template under the new nls path:
+
+{tip}
+cp vcl/js/nls/messages.js.template vcl/js/nls/messages.js
+{tip}
+
+You need to translate each string in your new messages.js file in to the
+new language. The file has an English string and a translation string on
+each line line:
+
+{tip}
+'Times cannot be suggested for cluster reservations': '',
+{tip}
+
+You must translate the string in the first set of quotes and place the
+translation in the second set of quotes for each string in the file.
+
+<a name="AddingaNewLocaletotheVCLWebFrontend-Addingentriestoconnectmethodtableindatabase"></a>
+## Adding entries to connectmethod table in database
+VCL 2.3 also introduced Connection Methods. This actually introduced a
+problem with multilingualization because most of the text for the Connect
+page is now in the database. Each connect method has a description and the
+text to be displayed on the Connect page. These are in the
+connectmethod.description and connectmethod.connecttext fields. If will
+only need a single language for your site, you can just change the text in
+those fields to be in your desired language. If you will need multiple
+languages, you can add additional fields to the table for each locale. You
+need to add two fields for each locale (using es_PR as an example):
+
+{tip}
+connectmethod.description_es_PR
+connectmethod.connecttext_es_PR
+{tip}
+
+You can add as many of the pairs of fields to the database as needed. The
+VCL code will check for the existance of fields with names like the above,
+and automatically display the text from the correct one if it exists. If it
+does not, the content of connectmethod.description and
+connectmethod.connecttext will be used.

Added: vcl/site/trunk/content/confluence_export/adding-ldap-authentication.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/adding-ldap-authentication.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/adding-ldap-authentication.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/adding-ldap-authentication.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,172 @@
+Title: Adding LDAP Authentication
+<a name="AddingLDAPAuthentication-PrerequisitesforyourLDAPserver:"></a>
+### Prerequisites for your LDAP server:
+* enable SSL on your LDAP server
+* Create an 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 firewalled, you will need to allow your VCL web
+server to access tcp port 636 on your LDAP server
+
+<a name="AddingLDAPAuthentication-PrerequisitesforyourVCLwebserver:"></a>
+### Prerequisites for your VCL web server:
+* php-ldap needs to be installed
+* If your LDAP server 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. On CentOS, information about the certificate needs
+to be added to /etc/pki/tls/certs/ca-bundle.crt - this [script](adding-ldap-authentication^convert_crt_for_ldapssl.html)
+ will take as input a file containing the base64 encoded certificate and
+generate the lines that need to be added to the ca-bundle.crt file.
+* After adding the certificate, restart httpd:
+
+    service httpd restart
+
+* You can verify that the certificate is properly installed using this
+command:
+
+    openssl s_client -showcerts -CAfile /etc/pki/tls/certs/ca-bundle.crt
+-connect your.ldap.server.here:636
+
+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 work through the problem.
+* You may need to add a line to /etc/openldap/ldap.conf to point to the
+ca-bundle.crt file. I'm not sure of a good way to tell if you need it or
+not, but if you do, add the following:
+
+    TLS_CACERT /etc/pki/tls/certs/ca-bundle.crt
+
+
+<a name="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. You need to come up with 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. Initials or a short name
+of your organization are a good idea. This 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 affiliationid for this affiliation.
+
+    mysql vcl
+    INSERT INTO affiliation (name) VALUES ('EXAMPLE');
+    SELECT id FROM affiliation WHERE name = 'EXAMPLE';
+    exit
+
+* 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
+** 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
+** 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
+* Next, there are 6 arrays that would need to be modified, but can be
+replaced with a block of code.
+* Delete the following lines:
+
+    $affilValFunc = array(1 => create_function('', 'return 0;'),
+    		      /*3 => "validateLDAPUser",*/
+    );
+    
+    $affilValFuncArgs = array(/*3 => 'EXAMPLE1 LDAP',*/
+    );
+    
+    $addUserFunc = array(1 => create_function('', 'return 0;'),
+    		     /*3 => 'addLDAPUser',*/
+    );
+    
+    $addUserFuncArgs = array(/*3 => 'EXAMPLE1 LDAP',*/
+    );
+    
+    $updateUserFunc = array(1 => create_function('', 'return 0;'),
+    			/*3 => 'updateLDAPUser',*/
+    );
+    
+    $updateUserFuncArgs = array(/*3 => 'EXAMPLE1 LDAP',*/
+    );
+
+and replace them with
+
+    $affilValFunc = array();
+    $affilValFuncArgs = array();
+    $addUserFunc = array();
+    $addUserFuncArgs = array();
+    $updateUserFunc = array();
+    $updateUserFuncArgs = array();
+    foreach($authMechs as $key => $item) {
+       if($item['type']
+ == 'ldap') {
+          $affilValFunc[$item['affiliationid']
+] = 'validateLDAPUser';
+          $affilValFuncArgs[$item['affiliationid']
+] = $key;
+          $addUserFunc[$item['affiliationid']
+] = 'addLDAPUser';
+          $addUserFuncArgs[$item['affiliationid']
+] = $key;
+          $updateUserFunc[$item['affiliationid']
+] = 'updateLDAPUser';
+          $updateUserFuncArgs[$item['affiliationid']
+] = $key;
+       }
+       elseif($item['type']
+ == 'local') {
+          $affilValFunc[$item['affiliationid']
+] = create_function('', 'return 0;');
+          $addUserFunc[$item['affiliationid']
+] = create_function('', 'return 0;');
+          $updateUserFunc[$item['affiliationid']
+] = create_function('', 'return 0;');
+       }
+    }
+
+* uncomment the require_once line for ldapauth.php toward the bottom of the
+file
+
+<a name="AddingLDAPAuthentication-TweakifyourLDAPserverhasusersinmultiplecontainers"></a>
+### Tweak if your LDAP server has users in multiple containers
+If your LDAP server has users in multiple containers, then the full DN for
+each user must be looked up before doing a bind to the LDAP server to
+authenticate the user. In this case, you'll need to modify
+authentication.php.
+* edit authenciation.php
+* search for ldapLogin
+* search for EXAMPLE1 LDAP in the function
+* uncomment the block of code it is contained in by removing the '/\*' at the beginning of the line containing 'EXAMPLE1 LDAP', and removing the '\*/' at the end of the else that is before '$ldapuser = sprintf($authMechs[$authtype]($authtype.html)
+['userid'], $userid);'
+* Look for the line containing 'cn=$userid'. If you use 'cn' to look up
+userids in your LDAP server, the line is fine as is. If you use something
+else, such as 'uid', change 'cn' to 'uid' or whatever is used on your LDAP
+server.
+* save the file

Added: vcl/site/trunk/content/confluence_export/adding-local-vcl-accounts.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/adding-local-vcl-accounts.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/adding-local-vcl-accounts.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/adding-local-vcl-accounts.mdtext Tue Jan  8 16:37:53 2013
@@ -0,0 +1,52 @@
+Title: 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 after the backend&nbsp;[management node](vcl:vcl-2.2.1-management-node-installation.html)
+&nbsp;component has been installed by executing the *vcld* file with the
+*\-setup* argument:
+{tip}
+/usr/local/vcl/bin/vcld \-setup
+{tip}
+{info}
+It is safe to run *vcld \-setup* while the normal vcld daemon process is
+running on a management node. Running *vcld \-setup* will not affect it.
+{info}
+You will see a menu. Enter the number next to the *VCL Base Module* entry:
+
+    [root@mgt-node]
+# /usr/local/vcl/bin/vcld -setup
+    VCL Management Node Setup
+    ----------------------------------------------------------------------------
+    Select a module to configure:
+    1. VCL Base Module
+    2. VCL Image State Module
+    3. Windows OS Module
+    
+    [vcld]
+    Make a selection (1-3, 'c' to cancel): 1
+
+
+Enter the number next to the *Add Local VCL User Account* entry:
+
+    ----------------------------------------------------------------------------
+    Choose an operation:
+    1. Add Local VCL User Account
+    
+    [vcld/User Accounts]
+    Make a selection (1, 'c' to cancel): 1
+
+
+Enter the requested information:
+
+    Enter the user login name ('c' to cancel): localuser
+    
+    Enter the first name ('c' to cancel): Local
+    
+    Enter the last name ('c' to cancel): User
+    
+    Enter the email address [not set]
+: localuser@example.com
+    
+    Enter the password ('c' to cancel): ******
+
+
+After adding the local user account, you can continue to navigate the menus
+or press Ctrl-C to exit.



Mime
View raw message