Note: This web site is only kept up to date for OSG Software
1.2 (VDT 2.0.0). If you are looking for information for the most recent
release, the RPM-based OSG Software 3.0, please see
the OSG documentation web site
Note: This version of the VDT (1.2.3) 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.2.3
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.
- Would you like to install as root or non-root?
You can install as any user but we recommend installing as root
(as it will simplify installation and post-configuration). However,
you can always install as non-root and perform all the necessary
subsequent re-configuration as root later.
- Where would you like to install CA files? (details)
- Do you want to install the complete VDT or some subset of it?
- Thing twice about installing on NFS
- Do you wish to use an existing external installation of Condor?
- Would you like an automatic (non-interactive) installation? (details)
- Create a
condor user if you are going to use Condor
as your batch system.
It is common to set up a Condor cluster with a condor user. 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. If you like you can
read about it in the Condor manual
- Create a
monalisa user if you will use MonaLisa and you
will install as root.
You don't have to create a monalisa user--it ist just a common practice.
If you install as root the daemon user will be used if the monalisa
doesn't exist and you can change it later with the configure_monalisa.sh
- RLS has been updated and has a new schema. Do you need to update
it? If you don't know then you don't need to update it. (details)
- For the VDS: An upgrading VDC user who uses an rDBMS needs to
upgrade his properties too. All properties starting with
vds.db.driver need to be renamed vds.db.*.driver will suffice. For
more information contact email@example.com.
- Install Pacman:
- 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
- Create the directory and change into it:
- Install the VDT:
- If your system is running behind a Web proxy tell Pacman
Of course, subsitute the name and port number of your proxy.
- Tell Pacman where the VDT can be gotten from:
- Install VDT:
pacman -get 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.2.3 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.
- See what happened:
- Do an 'ls' command. You should see a number of directories
with Globus, Condor, and the rest of the software
- 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
- source $VDT_LOCATION/setup.sh
- This will set all the appropriate environment variables used by VDT components
- You should do this before using any VDT components (Globus, Condor, MonaLisa, etc)
setup.sh / setup.csh / setup.ksh based on your shell
- Be careful about modifying these files. Any subsequent Pacman installation will erase your changes
- Setup Globus services to run via xinetd
- If you installed as root you were given a chance to setup the
Globus gatekeeper, GridFTP, and MDS to run from xinetd, which is
the recommended way. If you want to change which of these
service are run from xinetd use the configure_globus script to
enable/disable these componetns in xinetd.
- Configure Condor
- 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.
- By default Condor is configured to run as a personal Condor -- i.e. a one-node pool which runs jobs regardless of whether the user is using the machine or not. You might wish to change that.
- You might want to configure your Condor installation to
join your existing Condor pool. Generally this is done with
condor_configure --central-manager=... command. See condor_configure for more info
- Enable submitting to other batch systems (PBS, LSF, FBSng)
- Configure MonaLisa
- If you're planning to use MonaLisa please run
$VDT_LOCATION/vdt/setup/configure_monalisa.sh. This will prompt you for some information which is needed in order to for MonaLisa to report information correctly. (During installation VDT configures MonaLisa with workable defaults but they're likely to be inaccurate).
- Get certificates:
- You generally need a host certificate for your machine and user certificate(s) for all individual user(s) of Grid services.
- See Requesting Certificates for more information
- Configure Globus Gridmap file
- Get more information:
- Install other software
- Will you compile against the Globus installed by the VDT? If
so you will want to install one more package:
pacman -get Globus-2-Core
The RLS client and server are installed by default in
the VDT but the RLS server will not function properly until it's configured to run against a specific database service. We recommend the following procedure for setting up a database back-end for RLS.
If you're upgrading from and older RLS server please follow these RLS upgrade instructions
The Berkeley DRM can be installed with
pacman -get DRM
This software installation is still very new. There is little
documentation and little assistance from the VDT in configuring
DRM. We expect this to change in the near future. You can read
Server manual and the DataMover
userguide (the user tools).
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.