Condor v7.0.5 installation

1. Description

This document describes how to install Condor v7.0.5.
Only minimal configuration will be done; that part is described in other documents.

2. Required software

Any Condor-supported OS.
The Condor distribution.

3. Installation instructions

The installation will assume you install Condor v7.0.5 on a Linux machine, from tarballs, as root.
The install directory will be /opt/glidecondor and the machine name is mymachine.fnal.gov.
If you want to use a different setup, make the necessary changes.

3.1 Obtain Condor binaries

The Condor binaries can be downloaded from http://www.cs.wisc.edu/condor/downloads/.
Choose the v7.0.5 link, read the license, insert your name and affiliation, and proceed to the real download page.
Download dynamic tarball for Red Hat Enterpise Linux 4 (you will get condor-7.0.5-linux-x86-rhel3-dynamic.tar.gz).

3.2 Create the condor user

If you do not already have a local UID named condor,  create one.
It can be a nologin one, but it must have a valid home directory.

3.3 Install Condor

First of all, create the user condor. It can be a nologin account, but it does need to have a valid home directory.

Next, as root, execute the following commands; the commented part is the interactive exchange with the installation script.
tar -xzf  condor-7.0.5-linux-x86-rhel3-dynamic.tar.gz
cd condor-7.0.5/
./condor_install
#Would you like to do a full installation of Condor? [yes]
#Are you planning to setup Condor on multiple machines? [yes] no
#Have you installed a release directory already? [no]  no
#Where would you like to install the Condor release directory?
#[/usr/local/condor] /opt/glidecondor
#That directory doesn't exist, should I create it now? [yes] yes
#If something goes wrong with Condor, who should get email about it?
#[root@mymachine.fnal.gov]<your email here>
#What is the full path to a mail program that understands "-s" means
#you want to specify a subject? [/bin/mailx]
#Do all of the machines in your pool from your domain ("fnal.gov")
#share a common filesystem? [no]  no
#Do all of the users across all the machines in your domain have a unique
#UID (in other words, do they all share a common passwd file)? [no] no
#Enable Java Universe support? [yes] no
#Shall I create links in some other directory? [yes] no
#What is the full hostname of the central manager?
#[mymachine.fnal.gov]
#You have a "condor" user on this machine.  Do you want to put all the
#Condor directories in /home/condor? [yes] no
#Do you want to put all the Condor directories in
#/opt/glidecondor/home? [yes] no
#Where do you want the Condor directories?
#/opt/glidecondor/condor_local
#Should I put a "condor_config.local" file in /opt/glidecondor/condor_local?
#[yes] yes
#What name would you like to use for this pool? ...
#<your name here, something like glidein-1>
#Should I put in a soft link from /home/condor/condor_config to
#/opt/glidecondor/etc/condor_config [yes] no
#Should I put in a soft link from /etc/condor/condor_config to
#/opt/glidecondor/etc/condor_config [yes] yes

At this point, you can remove both the tarball (condor-7.0.5-linux-x86-rhel3-dynamic.tar.gz) and the temporary directory you used from installation (condor-7.0.5)

3.4 Put Condor in the path

Create the file /etc/profile.d/condor.sh, containing
if ! echo ${PATH} | grep -q /opt/glidecondor/bin ; then
        PATH=${PATH}:/opt/glidecondor/bin
fi
and make it executable:
chmod a+x /etc/profile.d/condor.sh

The file can be also downloaded from example-config/condor_install/condor.sh.

4 Further configuration

Further condor configuration is beyond the scope of this document.
If you got to this page from another document, go back to that one to continue the configuration.

Else, a few related documents in this collection are:

5 Condor startup

After you have configured condor, you can start Condor by running:
/opt/glidecondor/sbin/condor_master

glideinWMS support: glideinwms-support@fnal.gov