|Apache VCL > Apache VCL > Documentation > For VCL Administrators > VCL Installation > Upcoming Release > VCL 2.2.1 Installation > VCL 2.2.1 Management Node Installation|
The following management node installation instructions assume the instructions on the following pages have previously been completed:
The VCL management node daemon (vcld) has been developed to run on an operating system based on Red Hat Enterprise Linux (RHEL). It has been tested on the following:
The VCL management node daemon (vcld) requires the following Linux packages and Perl modules in order to run (see step 2 below for installation instructions):
The VCL management node daemon (vcld) is written in Perl and has been tested on Perl 5.8.x. The following Perl modules available from CPAN are also required (see step 2 below for installation instructions):
tar -jxvf apache-VCL-2.2.1-incubating.tar.bz2
|cp -r apache-VCL-2.2.1-incubating/managementnode /usr/local/vcl|
Run the install_perl_libs.pl script:
The last line of the install_perl_libs.pl script output should be:
Note: The script will hang or terminate if it encounters a problem. If this occurs, you will need to troubleshoot the problem by looking at the output.
The install_perl_libs.pl script included in the VCL distribution will attempt to download and install the required Linux packages and Perl modules. It uses the yum utility to install the required Linux packages. The required Perl modules are available from CPAN - The Comprehensive Perl Archive Network. The install_perl_libs.pl script attempts to download and install the required Perl modules by using the CPAN.pm module which is included with most Perl distributions.
The yum utility should exist on any modern Red Hat-based Linux distribution (Red Hat, CentOS, Fedora, etc). If yum isn't available on your management node OS, you will need to download and install the required Linux packages manually or by using another package management utility. After installing the required Linux packages, attempt to run the install_perl_libs.pl script again.
|cp /usr/local/vcl/etc/vcl/vcld.conf /etc/vcl|
The following lines must be configured in order to start the VCL daemon (vcld) and allow it to check in to the database:
The SSH client on the management node should be configured to prevent SSH processes spawned by the root user to the computers it controls from hanging because of missing or different entries in the known_hosts file.
Edit the ssh_config file:
Locate the UserKnownHostsFile and StrictHostKeyChecking lines and change them to the following:
Note: If you do not want these settings applied universally on the management node the SSH configuration can also be configured to only apply these settings to certain hosts or only for the root user. Consult the SSH documentation for more information.
|cp /usr/local/vcl/bin/S99vcld.linux /etc/init.d/vcld|
|/sbin/chkconfig --add vcld|
|/sbin/chkconfig --level 345 vcld on|
|/sbin/service vcld start|
You should see output similar to the following:
|The vcld service can also be started by running the service script directly: /etc/init.d/vcld start|
|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:
If you will be deploying Windows environments your institution's Windows product key and/or KMS server addresses must be entered into the VCL database. This can be done by running the following command:
Select "Windows OS Module" and follow the prompts.
If you will be using VCL to deploy bare-metal Windows XP or Windows Server 2003 environments via xCAT, the appropriate versions of the Microsoft Sysprep utility must be downloaded to the management node. The following steps do not need to be completed if you only intend to deploy VMware virtual machines.
The Sysprep utility is included in the Deployment Tools available for free from Microsoft. You do not need to download Sysprep for Windows 7 or Windows Server 2008 because it is included in the operating system.
The Sysprep files need to be downloaded, extracted, and then copied to the management node. The format of the file available for download is Microsoft's .cab format. It is easiest to extract the files on a Windows computer. Windows Explorer is able to open the .cab file and then the files contained within can be copied elsewhere.
Drivers which aren't included with Windows must be downloaded and saved to the management node. The drivers required will vary greatly depending on the hardware. The only way to know what additional drivers you need is to install Windows on a computer and check for missing drivers.
The drivers must be copied to the appropriate directory on the management node. The VCL image capture process copies the driver directories to the computer before an image is captured. Drivers from multiple directories will be copied based on the version of Windows being captured. There are driver directories under tools for each version of Windows (Windows XP, Windows 7) and for each version group of Windows (version 5, 6). This allows drivers which are common to multiple versions of Windows to be shared in the management node tools directory structure.
If a chipset driver works for all versions of Windows it should be saved in:
If Windows XP and Windows Server 2003 both use the same network driver it can be saved in:
If a storage driver only works for Windows XP it should be saved in:
During the image capture process, each Windows version directory is copied to the computer under C:\Cygwin\home\root\VCL. The order in which the Windows version directories are copied goes from most general to most specific. In the example above, the order would be:
The following list shows which driver files should be saved in the driver directories:
/var/lib/vcl/tools/Windows/Drivers - drivers common to all versions of Windows
/var/lib/vcl/tools/Windows_Version_5/Drivers - drivers used by Windows XP and Server 2003
/var/lib/vcl/tools/Windows_XP/Drivers - drivers only used by Windows XP
/var/lib/vcl/tools/Windows_Server_2003/Drivers - drivers only used by Windows Server 2003
/var/lib/vcl/tools/Windows_Version_6/Drivers - drivers used by Windows Vista and Server 2008
/var/lib/vcl/tools/Windows_7/Drivers - drivers only used by Windows 7
/var/lib/vcl/tools/Windows_Server_2008/Drivers - drivers only used by Windows Server 2008
The directory structure under each Drivers directory does not matter. It is helpful to organize each directory by driver class, and each directory should be organized using the same theme. For example:
VCL supports the following, please see the related websites for installation and configuration instructions: