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

Installing VDT RPMs

A subset of the VDT is now available in RPMs. We will be working to make RPMs for the other packages provided by the VDT in the future releases of the VDT.

Caveats: Using the VDT RPMs is not as nice as using the Pacman installation. The RPMs do no configuration so it is up to you to figure out how to do it. Currently none of the nifty VDT utilities are part of the RPMs. This is a subset of the software.

With these caveats you might ask why we provide the RPMs at all. There are two reasons. First, they are used by LCG as a basis for their Grid installations. Second, other VDT users may find them useful if they use an cluster management tool like Rocks.

Steps for installing RPMS

• Identify the RedHat linux version running on your system. Please note that the rpms for RedHat 7.2 will not work for RedHat 9.0.
• Download the rpms.
• Install the rpms.
• Perform post-installation.

Downloading the rpms

Globus services are broken into several RPMs as shown in the Diagram. If you want you can install only a subset of these services.

If you are using RedHat 7.2, you probably want the default compiler unless you are from LCG. If you are using RedHat Enterprise Linux 3, you can use the RedHat 9.0 binaries.

• Redhat 7.2 with default compiler
• Redhat 7.2 with gcc3.2.2 compiler (LCG)
• Redhat 9.0 with default compiler

Installing the rpms

Contents of this page explains installing and configuring the rh7 rpms. The same description holds for the rh9 rpms. Just make sure to use the rpms for correct platform.

Installing GPT

rpm -Uvh gpt-3.1-VDT1.3.11rh7.1.i386.rpm

Installing Globus rpms

Globus can be conceptually divided into three distinct pillars of software:

The VDT RPMs essentially correspond to these pillars:

The difference is two-fold: there is one RPM that contains the software common to each of the pillars and there is one RPM that contains the portions of Globus needed to compile new software that is linked against Globus -- such as header and library files.

The Globus packages are split into five groups of rpms

1. Globus essentials:
   

   vdt_globus_essentials-VDT1.3.11rh7-1.i386.rpm contains packages that are common to all the other packages. This rpm is a dependency for all the other globus packages.

2. Globus Data server:
   

   vdt_globus_data_server-VDT1.3.11rh7-1.i386.rpm contains globus_gridftp_server

3. Globus information services:
   

   vdt_globus_info_essentials-VDT1.3.11rh7-1.i386.rpm contains packages common to vdt_globus_info_client and vdt_globus_info_server.
   vdt_globus_info_client-VDT1.3.11rh7-1.i386.rpm contains mds_client packages
   vdt_globus_info_server-VDT1.3.11rh7-1.i386.rpm contains mds_server packages

4. Globus remote server and client:
   

   vdt_globus_rm_essentials-VDT1.3.11rh7-1.i386.rpm contains packages common to vdt_globus_rm_client and vdt_globus_rm_server
   vdt_globus_rm_client-VDT1.3.11rh7-1.i386.rpm contains Globus gram client tools related packages
   vdt_globus_rm_server-VDT1.3.11rh7-1.i386.rpm contains packages related to Globus gatekeeper, Globus GRAM reporter and fork jobmanager.
   vdt_globus_jobmanager_condor-VDT1.3.11rh7-1.i386.rpm contains the Condor jobmanager
   vdt_globus_jobmanager_pbs-VDT1.3.11rh7-1.i386.rpm contains the PBS jobmanager
   vdt_globus_jobmanager_lsf-VDT1.3.11rh7-1.i386.rpm contains the LSF jobmanager
   

5. Globus SDK:
   vdt_globus_sdk-VDT1.3.114rh7-1.i386.rpm contains Globus libraries and header files.

Installing/Compiling Globus Core rpm

vdt_compile_globus_core-VDT1.3.11-1.i386.rpm

Installing other rpms

openssh-VDT1.3.11rh7-1.i386.rpm
kx509-VDT1.3.11rh7-1.i386.rpm
myproxy-VDT1.3.11rh7-1.i386.rpm
pyglobus-VDT1.3.11rh7-1.i386.rpm
uberftp-client-VDT1.3.11rh7-1.i386.rpm

Installing Jobmanagers

The following jobmanagers for following batch systems are available in the rpm format

1. Condor: vdt_globus_jobmanager_condor-VDT1.3.11rh7-1.i386.rpm
2. PBS: vdt_globus_jobmanager_pbs-VDT1.3.11rh7-1.i386.rpm
3. LSF: vdt_globus_jobmanager_lsf-VDT1.3.11rh7-1.i386.rpm

Post-Installation Steps

Once you have installed the Globus rpms you need to configure the Globus services. If you have specified a --prefix option while installing the rpms to override the default location then set the GLOBUS_LOCATION and GPT_LOCATION accordingly.

1. Setting up the environment Set the GLOBUS_LOCATION and GPT_LOCATION environment variable

   export GLOBUS_LOCATION=/opt/globus
   export GPT_LOCATION=/opt/gpt
   

   Source the user environment

   source ${GLOBUS_LOCATION}/etc/globus-user-env.sh

2. Running GPT-Post install script

   If you have installed jobmanagers for condor or lsf or pbs please make sure that the batch-system binaries are in your path before executing the command else the gpt-postinstall will fail.

   ${GPT_LOCATION}/sbin/gpt-postinstall

   After you have installed one or more of these RPMs you must run the gpt-postinstall or your installation will not be complete.

3. Configuring Your Installation

   This section talks about how to configure the Globus Toolkit once you have it installed.

   Upgrade: If you are upgrading your installation of the Globus Toolkit it is not required that you run 'setup-gsi' below. However, you will need to migrate any manual change you made to the configuration files in your old installation to your new $GLOBUS_LOCATION.

   The first thing we need to do is complete the setup of GSI -- the security software that Globus uses. To complete the setup of the GSI software you need to run the following command as root to configure your /etc/grid-security directory:

   ${GLOBUS_LOCATION}/setup/globus/setup-gsi

   Note: If you do not have root privileges on your machine you can run setup-gsi with its '-nonroot' option. This will install the grid security directory to $GLOBUS_LOCATION/etc. The '-nonroot' option is intended to make client side installations of the Globus Toolkit possible without root access. It is not intended to provide for a mechanism to run servers from a self contained GLOBUS_LOCATION.

   When it asks you if you wish to continue hit return and then type 'q' followed by another return.
   You may exit from your root shell to continue on.

4. Starting Globus 3.2 Services

   Please refer the Globus web site for the details

   • GRAM
   • MDS
   • GridFTP