Versions Compared

Old Version 16

changes.mady.by.user Andy Kurth

Saved on

compared with

New Version 17

changes.mady.by.user Andy Kurth

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Install the VCL Management Node Code - Perl Daemon

    1. If you have not already done so, download and extract the VCL source files to the management node:
      Tip

      wget http://www.devlib.org/apache/incubator/vcl/apache-VCL-2.2-incubating.tar.bz2
      tar -jxvf apache-VCL-2.2-incubating.tar.bz2

    2. Copy the managementnode directory to the location where you want it to reside (typically /usr/local):
      Tip

      cp -r apache-VCL-2.2-incubating/managementnode /usr/local/vcl

  2. Install the Required Linux Packages & Perl Modules

    Run the install_perl_libs.pl script:
    Tip

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

    The last line of the install_perl_libs.pl script output should be:
    No Format
    successfully installed required Perl modules
    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.

  3. Configure vcld.conf

    1. Create the */etc/vcl* directory:
      Tip

      mkdir /etc/vcl

    2. Copy the stock *vcld.conf* file to */etc/vcl*:
      Tip

      cp /usr/local/vcl/etc/vcl/vcld.conf /etc/vcl

    3. Edit */etc/vcl/vcld.conf*:
      Tip

      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:
      • 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
    4. Save the vcld.conf file

  4. 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

    Locate the UserKnownHostsFile and StrictHostKeyChecking lines and change them to the following:
    No Format
    UserKnownHostsFile /dev/null
StrictHostKeyChecking no
    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.

  5. Install and Start the VCL Daemon (vcld) Service

    1. Copy the vcld service script to /etc/init.d and name it vcld:
      Tip

      cp /usr/local/vcl/bin/S99vcld.linux /etc/init.d/vcld

    2. Add the vcld service using chkconfig:
      Tip

      /sbin/chkconfig --add vcld

    3. Configure the vcld service to automatically run at runtime levels 3-5:
      Tip

      /sbin/chkconfig --level 345 vcld on

    4. Start the vcld service:
      Tip

      /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
      Info

      The vcld service can also be started by running the service script directly:

      Tip

      /etc/init.d/vcld start

    5. Check the vcld service by monitoring the vcld.log file:
      Tip

      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

  6. Configure Windows Product Keys and/or KMS Server Addresses (Optional)

    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:
    Tip

    /usr/local/vcl/bin/vcld -setup

    Select "Windows OS Module" and follow the prompts.

  7. Download Windows Sysprep Utility (Optional)

    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.

    1. Windows XP
      1. Download Sysprep for Windows XP: Windows XP Service Pack 3 Deployment Tools
      2. Extract the Windows XP Sysprep Files
      3. Copy the extracted Windows XP Sysprep files to the following directory the management node:
        No Format
        /usr/local/vcl/tools/Windows_XP/Utilities/Sysprep
    2. Windows Server 2003
      1. Download Sysprep for Windows Server 2003: System Preparation tool for Windows Server 2003 Service Pack 2 Deployment
      2. Extract the Windows Server 2003 Sysprep Files
      3. Copy the extracted Windows Server 2003 Sysprep files to the following directory the management node:
        No Format
        /usr/local/vcl/tools/Windows_Server_2003/Utilities/Sysprep

  8. Download Windows Drivers (Optional)

    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.

...