...
The following instructions assume the VCL database has been installed and configured and that the managment node information has been added to the database as described on the web code installation page. This also assumes that the perl-DBD-MySQL-3.x and the mysql client (mysql-5.x) packages are installed, for database communications.
Install the Subversion
...
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 commandclient if it is not already installed:
No Format |
---|
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.
-y
|
Download the management node code using the Subversion export command to /usr/local/vcl:
No Format |
---|
svn export httpshttp://svn.apache.org/repos/asf/incubator/vcl/trunk/managementnode/ /usr/local/vcl/ |
...
The VCL Perl code running on a management node requires several additional Perl modules available from CPAN - The Comprehensive Perl Archive Network. A search engine for CPAN modules is available at search.cpan.org.Some of the package prerequisites for the required Perl modules include the following. If they weren't following packages to be installed on the OS before installing the required Perl modules. These packages must be installed if they were not installed as part of your base Linux install, you may need to add them (using yum or rpm or whatever package management tool).. It is easiest to use the package management utility for your OS --- yum, rpm, or other.
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 scriptTo install these packages using yum:
No Format |
---|
perl /usr/local/vcl/bin/install_perl_libs.pl
|
A large amount of output will be displayed on the console the first time the script is run. It will pause if any of the module installations ask for configuration information. Accept all of the defaults by pressing enter when this happens.
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:
yum install expat expat-devel gcc krb5-libs krb5-devel libxml2 libxml2-devel openssl openssl-devel perl-DBD-MySQL xmlsec1-openssl -y
|
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. A search engine for CPAN modules is available at search.cpan.org.
Note: Licensing information for each required Perl module is included below. The content of the "License:" lines was copied from the CPAN page for each module. The content of the other line was copied from the copyright section in the module's source code or from the module's readme file.
The following Perl modules are only required if VCL is configured to send instant messages via Jabber. Jabber support can be enabled or disabled by configuring the "jabber=" line in the vcld.conf file. The following modules do not need to be installed if Jabber support is disabled.
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. Run the script:
No Format |
---|
perl /usr/local/vcl/bin/install_perl_libs.pl
|
A large amount of output will be displayed on the console the first time the script is run. It will pause if any of the module installations ask for configuration information. Accept all of the defaults by pressing enter when this happens.
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:
No Format |
---|
=== |
No Format |
==============================================================================
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
==============================================================================
|
Additional output will be displayed if a module has not been successfully installed. You will need to troubleshoot if any modules were not installed successfully.
Run the following command to execute the utils.pm file:
...
No Format |
---|
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 |
No Format |
---|
/usr/bin/make install -- OK |
No Format |
---|
Module Compress::Zlib (P/PM/PMQS/IO-Compress-2.020.tar.gz) |
No Format |
---|
/usr/bin/make install -- OK |
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. The Sysprep utility is included in the Deployment Tools. You do not need to download Sysprep for Windows Vista or Server 2008 because it is included in the operating system.
...
Panel |
---|
-rw-rw-r-- 1 root root 25600 Aug 18 17:32 setupcl.exe |
Your organizations's Windows XP product key needs to be entered into the Windows XP sysprep.inf file. Find the ProductKey line and replace WIN_XP_PRO_KEY with your organization's Windows Server 2003 XP product key in the following file:
Panel |
---|
/usr/local/vcl/tools/Windows_XP/Utilities/Sysprep/sysprep.inf |
Panel |
---|
/usr/local/vcl/tools/Windows_Server_2003/Utilities/Sysprep/sysprep.inf |
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.
...
This step is complicated. 3rd party mass storage hardware IDs and driver .inf file paths must be added to the SysprepMassStorage section in sysprep.inf for Windows XP and Windows Server 2003 in order for the saved image to boot properly on different hardware.
Example: LSI SAS drivers commonly need to be downloaded and the hardware IDs need to be added to the sysprep.inf files in order for computers with LSI SAS controllers to boot.
...
Panel |
---|
[LSI] |
...
PCI\VEN_1000&DEV_ |
...
0054 |
...
PCI\VEN_1000&DEV_ |
...
0058 |
...
PCI\VEN_1000&DEV_ |
...
0056 |
...
PCI\VEN_1000&DEV_ |
...
0640 |
...
PCI\VEN_1000&DEV_ |
...
0646 |
...
PCI\VEN_1000&DEV_ |
...
0062 |
...
PCI\VEN_1000&DEV |
...
_0054&SUBSYS_1F041028 |
...
PCI\VEN_1000&DEV_0054 |
...
&SUBSYS_1F051028 |
...
PCI\VEN_1000&DEV |
...
_0054&SUBSYS_1F061028 |
...
PCI\VEN_1000&DEV |
...
_0054&SUBSYS_1F071028 |
...
PCI\VEN_1000&DEV_ |
...
0054&SUBSYS_1F081028 |
...
PCI\VEN_1000&DEV_ |
...
0054&SUBSYS_1F091028 |
...
PCI\VEN_1000&DEV |
...
_0058&SUBSYS_1F0E1028 |
...
PCI\VEN_1000&DEV_ |
...
0058&SUBSYS_ |
...
1F0F1028 |
...
PCI\VEN_1000&DEV_ |
...
0058&SUBSYS_ |
...
1F101028 |
Panel |
---|
PCI\VEN_1000&DEV_ |
...
0622 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" |
...
0624 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" |
...
0626 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" |
...
0628 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" |
...
0030 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" |
...
Wiki Markup |
---|
Based on the contents of the .inf file, the following is added to the Windows XP and Windows Server 2003 sysprep.inf files under \[SysprepMassStorage\]: |
Panel |
---|
0032 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" |
If you have hardware using an LSI SAS controller (IBM HS21 blades), the section above can be copied and pasted into your sysprep.inf files:
Panel |
---|
/usr/local/vcl/tools/Windows_XP/Utilities/Sysprep/sysprep.inf |
Panel |
---|
/usr/local/vcl/tools/Windows_Server_2003/Utilities/Sysprep/sysprep.inf |
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 wsname.exe utility is used 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 in the following location on the management node:
Panel |
---|
/usr/local/vcl/tools/Windows |
...
/Utilities/WSName/ |
...
wsname.exe |
NewSID.exe is used to change the SID of a Windows computer if Sysprep is not used. Download the NewSID.exe utility:
Download: NewSID.exe
Save the NewSID.exe utility in the following location on the management node:
Panel |
---|
/usr/local/vcl/tools/Windows |
...
/Utilities/NewSID/newsid.exe |
SPDrvScn.exe is used before an image is captured to enter the paths of drivers to the Windows registry so that they are loaded when Sysprep attempts to install devices. Download the SPDrvScn.exe utility:
Download: SPDrvScn.exe
Save the SPDrvScn.exe utility in the following location on the management node:
Panel |
---|
/usr/local/vcl/tools/Windows/Utilities/SPDrvScn/spdrvscn.exe |
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:
No Format |
---|
vi /root/.ssh/config
|
Add the following lines to the top of the configuration file.
No Format |
---|
Host <vmhost> <vmhost ip>
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
|
Where:
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.
...
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 wsname.exe utility is used 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 in the following location on the management node:
Panel |
---|
/usr/local/vcl/tools/Windows/Utilities/WSName/wsname.exe |
NewSID.exe is used to change the SID of a Windows computer if Sysprep is not used. Download the NewSID.exe utility:
Download: NewSID.exe
Save the NewSID.exe utility in the following location on the management node:
Panel |
---|
/usr/local/vcl/tools/Windows/Utilities/NewSID/newsid.exe |
SPDrvScn.exe is used before an image is captured to enter the paths of drivers to the Windows registry so that they are loaded when Sysprep attempts to install devices. Download the SPDrvScn.exe utility:
Download: SPDrvScn.exe
Save the SPDrvScn.exe utility in the following location on the management node:
...
...