{excerpt:hidden=true} How to install and configure the VCL management node components including the required Linux packages, Perl modules, VCL daemon (vcld), and Windows utility dependencies{excerpt}
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):
files to the management node:
tar -jxvf apache-VCL-2.2.1-incubating.tar.bz2{tip}
reside (typically /usr/local): {tip}cp -r apache-VCL-2.2.1-incubating/managementnode /usr/local/vcl{tip}
h2. Install the Required Linux Packages & Perl Modules Run the install_perl_libs.pl script: {tip}perl /usr/local/vcl/bin/install_perl_libs.pl{tip} The last line of the install_perl_libs.pl script output should be:
Note: The script will hang or terminate if it encounters a problem. If this occurs, you will need to troubleshoot the problem by looking at the output. \ \ Note: RPC::XML may not install correctly on CentOS 5.6. The CPAN install of RPC::XML fails because RPC::XML needs ‘XML::LibXML’ for it‘s ‘self tests’ - even though - it’s NOT configured as a dependency, and the ‘self tests’ are suppose to skip tests involving ‘XML::LibXML’ if it‘s not installed. You may need to install the module manually before running the ‘install_perl_libs.pl’ script. (i.e. cpan -i XML::LibXML ) \ \ The install_perl_libs.pl script included in the VCL distribution will attempt to download and install the required Linux packages and Perl modules. It uses the yum utility to install the required Linux packages. The required Perl modules are available from [CPAN - The Comprehensive Perl Archive Network|http://www.cpan.org] . The install_perl_libs.pl script attempts to download and install the required Perl modules by using the CPAN.pm module which is included with most Perl distributions. \ \ The yum utility should exist on any modern Red Hat-based Linux distribution (Red Hat, CentOS, Fedora, etc). If yum isn’t available on your management node OS, you will need to download and install the required Linux packages manually or by using another package management utility. After installing the required Linux packages, attempt to run the install_perl_libs.pl script again.
/usr/local/vcl/etc/vcl/vcld.conf /etc/vcl{tip} ## Edit */etc/vcl/vcld.conf*: {tip}vi /etc/vcl/vcld.conf{tip} The following lines must be configured in order to start the VCL daemon (vcld) and allow it to check in to the database: ##* FQDN - the fully qualified name of the management node, this should match the name that was configured for the management node in the database ##* server - the IP address or FQDN of the database server ##* LockerWrtUser - database user account with write privileges ##* wrtPass - database user password ## Save the vcld.conf file # h2. Configure the SSH Client The SSH client on the management node should be configured to prevent SSH processes spawned by the root user to the computers it controls from hanging because of missing or different entries in the known_hosts file. \ \ Edit the ssh_config file: {tip}vi /etc/ssh/ssh_config{tip} Locate the UserKnownHostsFile and StrictHostKeyChecking lines and change them to the following:
StrictHostKeyChecking no{noformat} Note: If you do not want these settings applied universally on the management node the SSH configuration can also be configured to only apply these settings to certain hosts or only for the root user. Consult the SSH documentation for more information.
{tip} cp /usr/local/vcl/bin/S99vcld.linux /etc/init.d/vcld {tip}
{tip} /sbin/chkconfig --add vcld {tip}
{tip} /sbin/chkconfig --level 345 vcld on {tip}
{tip} /sbin/service vcld start {tip} You should see output similar to the following:
============================================================================ VCL Management Node Daemon (vcld) | 2011-03-15 10:23:04 ============================================================================ bin path:����� /usr/local/vcl/bin config file:�� /etc/vcl/vcld.conf log file:����� /var/log/vcld.log pid file:����� /var/run/vcld.pid daemon mode:�� 1 setup mode:��� 0 verbose mode:� 1 ============================================================================ Created VCL daemon process: 8465 ���������������������������������������������������������� [� OK� ]
{noformat} {info} The vcld service can also be started by running the service script directly: /etc/init.d/vcld start{}{info} ## Check the vcld service by monitoring the vcld.log file: {tip}tail -f /var/log/vcld.log{tip} You should see the following being added to the log file every few seconds if the management node is checking in with the database:
{tip} yum install dhcp -y {tip}
to avoid conflicts with other networks. Configure the dhcpd service startup script to only listen on the private interface: {tip} vi /etc/sysconfig/dhcpd {tip} Add eth0 the to the DHCPDARGS line:
# Command line options here DHCPDARGS=eth0
{tip} /sbin/chkconfig --level 345 dhcpd on {tip}
{tip} vi /etc/dhcpd.conf {tip} {info}Configure your dhcpd.conf file according to your network configuration. The contents of the dhcpd.conf file will vary based on how your network is configured. Below is an example of a basic dhcpd.conf file:{info}
ddns-update-style none;
shared-network eth0 {
subnet 10.100.0.0 netmask 255.255.255.0 {
ignore unknown-clients;
}
}
You will add host definitions to the dhcpd.conf file after you add computers to VCL using the website. The website will display the dhcpd.conf host definitions after the computers have been added to VCL, which can be copied and pasted into the dhcpd.conf file.
{tip}/sbin/service dhcpd start{tip}
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.
the management node: {noformat}/usr/local/vcl/tools/Windows_XP/Utilities/Sysprep{noformat}
directory the management node: {noformat}/usr/local/vcl/tools/Windows_Server_2003/Utilities/Sysprep{noformat}
The drivers must be copied to the appropriate directory on the management node. The VCL image capture process copies the driver directories to the computer before an image is captured. Drivers from multiple directories will be copied based on the version of Windows being captured. There are driver directories under tools for each version of Windows (Windows XP, Windows 7) and for each version group of Windows (version 5, 6). This allows drivers which are common to multiple versions of Windows to be shared in the management node tools directory structure.
Examples:
If a chipset driver works for all versions of Windows it should be saved in: /var/lib/vcl/tools/Windows/Drivers/Chipset
If Windows XP and Windows Server 2003 both use the same network driver it can be saved in: /var/lib/vcl/tools/Windows_Version_5/Drivers/Network
If a storage driver only works for Windows XP it should be saved in: /var/lib/vcl/tools/Windows_XP/Drivers/Storage
During the image capture process, each Windows version directory is copied to the computer under C:\Cygwin\home\root\VCL. The order in which the Windows version directories are copied goes from most general to most specific. In the example above, the order would be: /var/lib/vcl/tools/Windows/* /var/lib/vcl/tools/Windows_Version_5/* /var/lib/vcl/tools/Windows_XP/*
The following list shows which driver files should be saved in the driver directories: /var/lib/vcl/tools/Windows/Drivers - drivers common to all versions of Windows /var/lib/vcl/tools/Windows_Version_5/Drivers - drivers used by Windows XP and Server 2003 /var/lib/vcl/tools/Windows_XP/Drivers - drivers only used by Windows XP /var/lib/vcl/tools/Windows_Server_2003/Drivers - drivers only used by Windows Server 2003
/var/lib/vcl/tools/Windows_Version_6/Drivers - drivers used by Windows Vista and Server 2008 /var/lib/vcl/tools/Windows_7/Drivers - drivers only used by Windows 7 /var/lib/vcl/tools/Windows_Server_2008/Drivers - drivers only used by Windows Server 2008
The directory structure under each Drivers directory does not matter. It is helpful to organize each directory by driver class, and each directory should be organized using the same theme. For example: /var/lib/vcl/tools/Windows_Version_XP/Drivers{}/Chipset /var/lib/vcl/tools/Windows_Version_XP/Drivers{}/Network /var/lib/vcl/tools/Windows_Version_XP/Drivers{}/Storage /var/lib/vcl/tools/Windows_Version_XP/Drivers{}/Video
information: