Note: This version of the VDT (1.1.14) 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.

Installing VDT 1.1.14

Installing VDT 1.1.14

Things you should consider before installing the VDT

If you want to do a quick trial installation of the VDT to see how things work, you do not need to worry about these yet. The defaults in the VDT will work fine for small VDT installations.

Installation Instructions

  1. Install Pacman:
    • Download Pacman This is version 2.116, which is the most recent version tested with VDT 1.1.14. For installing Redhat 9 specific packages you need to install version 2.116 or above. 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:
    • 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 (this will also be referred to as $VDT_LOCATION)
    • Create the directory and change into it:
      mkdir /vdt
      cd /vdt
  3. Install the VDT:
    • If your system is running behind a Web proxy, tell Pacman about it:
      pacman -http_proxy:
      Of course, subsitute the name and port number of your proxy.
    • Install VDT:
      pacman -get VDT:VDT

      Pacman will be asked two questions before anything can begin:

      • 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]? Choose "yes"; otherwise 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.14 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:
      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)
      You must answer y (presumably after reading the licences) in order to continue with the installation.

      You will then be asked a series of other questions on how to configure your VDT installation. If you're not sure how to answer a question or if it is not relevant to you, choose skip. You can always configure the relevant item(s) later. The instructions for configuring them will be placed in $VDT_LOCATION/post-install/README. If you are doing hands-free installations and you want to avoid answering these questions during the installation, you can answer them in advance.

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

Things you might want to do after a VDT installation