Page History

...

Check if a Subversion client is already installed on the management node by running the svn command.  If not already installed, you can try to install it using yum with the following command:

yum install subversion

If yum is not available, visit http://subversion.tigris.org and follow the instructions for downloading and installing a Subversion client.

...

Download VCL backend code from the Apache Subversion repository and save it to /usr/local/vcl.

svn export https://svn.apache.org/repos/asf/incubator/vcl/trunk/managementnode/ /usr/local/vcl/

...

A script is provided in the VCL repository called install_perl_libs.pl which will attempt to download and install the required perl libraries.  Run the script:

perl /usr/local/vcl/bin/install_perl_libs.pl

...

Run the script a 2nd time to check if all of the modules the script is configured to install were successfully installed. Output similar to the following should be displayed for each module:

==============================================================================
 URL: http://search.cpan.org/CPAN/authors/id/T/TI/TIMB/DBI-1.609.tar.gz
 Module filename: DBI-1.609.tar.gz
 Module name: DBI-1.609
 Module package: DBI
 Checking if DBI is installed
 Module is already installed: DBI
 ==============================================================================

...

Executing utils.pm does not actually do anything but this will tell you if VCL will be able to run.  If any Perl modules are missing you will see "Can't locate" lines:

Can't locate HTTP/Headers.pm in @INC (@INC contains:...)

Once all of the required modules are installed, you should see output similar to the following:

BIN PATH: /usr/local/vcl/lib/VCL
 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

...

1. Change directories to /tmp:
   cd /tmp 
2. 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
3. Unpack the source package using tar:
   tar xzf libwww-perl-5.827.tar.gz
4. The previous command should have created a libwww-perl-5.827 directory, change to this directory:
   cd libwww-perl-5.827
5. Create a makefile with the following command:
   perl Makefile.PL
6. Compile the module:
   make
7. Test the module:
   make test
8. Install the module:
   make install
   The last line you should see should be:

   No Format
   /usr/bin/make install  -- OK

...

1. Enter the CPAN shell:
   perl -MCPAN -e shell
2. 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.
3. Search for a module using the "m" command:
   m /Zlib/
   You should find the module you were looking for on a line like this:

   No Format
   Module          Compress::Zlib  (P/PM/PMQS/IO-Compress-2.020.tar.gz)

4. Install the module:
   install Compress::Zlib
5. Answer yes if asked to install any prerequisite modules
   The last line you should see should be:

   No Format
   /usr/bin/make install  -- OK

...

Copy the extracted Windows XP Sysprep files to the following directory on the management node after they have been extracted:

...

WSName - Workstation Name Changing Utility

NOTICE: The WSName.exe utility is no longer available.  The set_computer_name.vbs script which calls WSName.exe will be rewritten for the 2.2 release of VCL. In the meantime, this script is being left intact in case you have a previously released version of WSName.exe or are able to obtain it from another source.

The wsnameThe WSName.exe utility is used to change the name of the computer while it is being installed.  Download the WSName.exe utility:

Download: WSName.exe

by VCL to name Windows computers.  It does a reverse DNS lookup so that the computer name is set to the name registered for its public IP address.  The utility is called by set_computer_name.vbs when a Windows image is loaded.  The utility is not vital for the load process to work.  However, the computer will receive a random name if the script is missing or fails to run.

If you do have a previously released version of WSName.exe or are able to locate it from another souce, save WSName.exe Save the WSName.exe utility in the following location on the management node:

...

1. Start the vcld service:
   /sbin/service vcld start
   You should see output similar to the following:

   No Format

   Starting vcld daemon: BIN PATH: /usr/local/vcl/bin 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  ]

   Note: the vcld service can also be started by running the service script directly:
   /etc/init.d/vcld start
2. 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:

   No Format
   2009-06-16 16:57:15|15792|vcld:main(165)|lastcheckin time updated for management node 18: 2009-06-16 16:57:15