Note: This version of the VDT (1.1.11) is no longer supported. Feel free to look through the documentation and install it, but we cannot guarantee support for it. The current stable release is 2.0.0.

VDT Installation

Installation

What is in the VDT?

The VDT consists of three pieces, the server, the client, and the SDK. The server contains software you would want on a server: the Globus gatekeeper, Condor, etc. The client contains software you would use to run jobs at a remote Grid site. The SDK contains libraries to develop new software.

If you don't know what to install, we recommend installing all three pieces. It doesn't take very long, and you do not have to use the pieces you don't want to. If you install the server, we strongly recommend also installing the client so you can test your installation.

The exact software in the VDT is described elsewhere.

Why should you install the VDT?

You could install all of the pieces of the VDT individually, and you wouldn't need the VDT. So why should you install the VDT?

Installation Instructions

  1. Install Pacman:
    • Download Pacman This is version 2.116, which is the most recent version tested with VDT 1.1.11. More recent versions of Pacman and additional information about Pacman may be available from the main Pacman web site.
    • Unpack Pacman:
      tar xzf pacman-2.116.tar.gz
    • Setup your environment to use pacman:
      cd pacman-2.116
      source setup.csh
      This will set your PATH environment variable to find Pacman.
  2. Prepare to install the VDT:
    • It is common to set up a Condor cluster with a condor user, where Condor files are placed. The VDT installation will not do this, because of concerns some VDT users have had about the VDT installation messing with an existing Condor installation. Therefore, condor files are always installed in the condor_home subdirectory of the vdt directory. Should you wish to change this, you can do so after the installation. If you like, you can read about it in the Condor manual.
    • Decide where you want to install it. It doesn't matter what you choose. Common choices are /vdt and /opt/vdt. For the examples that follow, we'll assume that you wish to install into /vdt.
    • Change into that directory:

      cd /vdt
    • Decide what user you wish to install as. You can install as any user, but we recommend installing as root if you want to do a server installation; for client installations, you can certainly install as non-root. If you install as root, the VDT can automatically set up system configuration for you to make sure that daemons will be running.

      If you wish to install the server as non-root and do the system configuration later, the installation process will create a a post-install directory within the /vdt directory. Within this directory will be instructions for setting up your system that you can give to your system adminstrator, who has root privileges.

  3. Advanced pre-installation tips:
    These will help people already comfortable with installing the VDT. If this is your first time installing the VDT, please just skip to the next step.
  4. Install the VDT:
    • If your system is running behind a Web proxy, tell Pacman about it:

      pacman -http_proxy:http://someproxy.com:port


      Of course, subsitute the name and port number of your proxy.
    • Tell Pacman where to find the VDT 1.1.11 software cache:
      pacman -cache:http://vdt.cs.wisc.edu/vdt_1111_cache
    • Install the VDT Server:

      pacman -get VDT-Server

      You will be asked two questions:

      • Do you want to start a new installation here? This is your chance to back out if you are installing in the wrong directory.
      • Do you want to trust the registered cache [VDT]? Feel free to say no, but if you do say no, you won't be able to install the VDT.

      After you answer the preliminary questions, you will see some output as Pacman fetches the necessary files. Then, before the rest installation of these files begins, Pacman will ask you to agree to some licenses:

            VDT 1.1.11 installs a variety of software, each with its own license.
            In order to continue, you must agree to the licenses.
            You can view the licenses online at:
            
                 http://vdt.cs.wisc.edu/licenses/1.1.11
            
            After the installation has completed, you will also be able to 
            view the licenses in the 'licenses' directory.
            
            Do you agree to the licenses? (y/n)

      If you are root, you will be asked if you want to set up the Globus daemons. You are also asked if you want the EDG CRL Update program to run automatically. If you don't wish to do these steps or you aren't root, instructions for setting them up will be placed in /vdt/post-install/README, along with some extra files to help you out.

    • Install the VDT Client:

      pacman -get VDT-Client

      This step is like installing the server

    • Install the VDT Software Development Kits:

      pacman -get VDT-SDK

      Again, this step is like installing the server, but there is less to install and there are no questions to answer.

    • Install a Globus subset of the VDT:

      You can install just the Globus subset of the VDT by doing one or both of:

      pacman -get VDT-Globus-Server
      pacman -get VDT-Globus-Client

  5. See what happened:
    • Do an 'ls' command, you should see a number of directories with Globus, Condor, and the rest of the software installed.
    • Read through /vdt/post-install/README. It will tell you about anything that the VDT installation process was unable to do. Also, the Condor set up is tricky, and VDT installer may have had to make some guesses about how to configure Condor--these will be noted in this same README. You should be able to use a personal Condor or Condor-G with no changes, but if you want to set up a Condor pool, you may need to edit the Condor Configuration. The post-install README will get you started with that process.
    • If you let the VDT installer set up the daemons, it edited /etc/services, either /etc/inetd.conf (RedHat 6.2) or /etc/xinetd.d/ (RedHat 7.2), and /etc/rc.d/init.d. Look at the changes, if you wish.
  6. Change the VDT's configuration:
    • The VDT did the best it could to configure Globus for you, but you may wish to change it. You can use the configure_globus script.
    • The VDT did the best it could to configure Condor and Condor-G for you, but you may wish to change it. You can use the condor_configure script.
    • Using other batch systems:
      You can setup Globus to allow access to PBS, LSF, and FBSng easily. It is a two-step process. First, make sure that that PBS or LSF command-line utilities are in your path. (You should be able to execute them if you wish, without using a complete pathname.) Next, install the appropriate package:
      pacman -get Globus-PBS-Setup
          or
      pacman -get Globus-LSF-Setup
         or
      pacman -get FBSNG
  7. Get certificates:
  8. Get more information:
  9. Install other software
    • RLS: The RLS client is installed by default in the VDT-Client. The RLS server is installed in the VDT-Server, but none of the additional support software is installed. If you want to install MySQL, IODBC and MyODBC and configure them for use with RLS, you can do so with:
      pacman -get Globus-RLS-Server-Setup-MySQL

      You can find more documentation on RLS at the Globus web site.

    • Pippy:

      pacman -get UTA:pippy

      Pippy will publish information about software installed via Pacman to your GRIS. At some point this may be part of the standard VDT installation, but first it needs to undergo some testing by the VDT team. Currently it requires you to be root in order to install.