HTCondor YUM Repository

Description

Starting with HTCondor 7.4.1 and 7.5.1, we now have a HTCondor YUM repository for installing HTCondor on Red Hat Enterprise Linux and compatible distributions (such as CentOS or Scientific Linux). Please see instructions below for supported platforms. The new RPM is FHS-compliant and relocatable.

Learn more about HTCondor.

Install Instructions

Note: "root" user must be used to perform installation.

1. Note: Redhat Enterprise Linux 5 users only: in order to install HTCondor, you must have the "RHEL Virtualization" Red Hat Network channel enabled to obtain the libvirt library, which is one of HTCondor's dependencies.
2. Download and install the YUM repository file that matches your operating systems. There is a seperate repository for Development and Stable releases of HTCondor. If you just want the latest HTCondor release then please install both repositories.
   
   

   OS	Development Release	Stable Release	Supported Platforms
   Redhat Enterprise Linux 4 and compatible	htcondor-development-rhel4.repo	htcondor-stable-rhel4.repo	i386, x86_64
   Redhat Enterprise Linux 5 and compatible	htcondor-development-rhel5.repo	htcondor-stable-rhel5.repo	i386, x86_64
   Redhat Enterprise Linux 6 and compatible	htcondor-development-rhel6.repo	htcondor-stable-rhel6.repo	x86_64

   Note: Redhat 4 RPMs are created on Redhat 3

   
   Example - Redhat 5: Install latest HTCondor's release

   cd /etc/yum.repos.d
   wget http://research.cs.wisc.edu/htcondor/yum/repo.d/htcondor-development-rhel5.repo
   wget http://research.cs.wisc.edu/htcondor/yum/repo.d/htcondor-stable-rhel5.repo

   Example - Redhat 4: Install only HTCondor's stable release

   cd /etc/yum.repos.d
   wget http://research.cs.wisc.edu/htcondor/yum/repo.d/htcondor-stable-rhel4.repo

3. [Optional] Add condor user.
   
   
   The HTCondor package will automatically add a 'condor' user/group if it does not exist already. Sites with a specific security policy should add the 'condor' user/group manually before performing the installation.
   
   
4. [Optional] HTCondor RPM is relocatable. To install this RPM into other locations, please follows these instructions.
   
   
5. Install HTCondor RPM
   
   On 32-bit machines:

   yum install condor

   On 64-bit machines:

   yum install condor.x86_64

   
   
6. [Optional] Edit HTCondor's configuration file which locates at /etc/condor/condor_config.local
   
   
   This RPM is shipped with the Personal HTCondor configuration. Please do not use condor_configure or condor_install to configure HTCondor installed via this RPM.
   
   
7. Start HTCondor daemons
   

   service condor start

8. Check if HTCondor is running
   

   ps -ef | grep condor

   Expected Result:

   condor   29612     1  0 23:36 ?        00:00:01 /usr/sbin/condor_master -pidfile /var/run/condor/master.pid
   condor   29613 29612  0 23:36 ?        00:00:00 condor_collector -f
   condor   29614 29612  0 23:36 ?        00:00:00 condor_negotiator -f
   condor   29615 29612  0 23:36 ?        00:00:00 condor_schedd -f
   condor   29616 29612  1 23:36 ?        00:00:05 condor_startd -f
   root     29618 29615  0 23:36 ?        00:00:00 condor_procd -A /var/run/condor/procd_pipe.SCHEDD -S 60 -C 102
   

Release Notes

• This version of HTCondor RPM follows Filesystem Hierarchy Standard. Whereas, existing HTCondor RPM (prior to 7.5.1) install everything into /opt/condor-{version}. It is possible to install this RPM into non-stardard such as /opt/condor. Please refer to the relocatable section for more details.
  
  The following table shows path layout compared to original HTCondor's binary package.
  
  

  Orignal Location	Current Location
  bin	/usr/bin
  etc	/etc/condor/
  etc/examples	/usr/share/doc/condor-{version}/etc/examples
  examples	/usr/share/doc/condor-{version}/examples
  include	/usr/include/condor
  lib	/usr/lib/condor | /usr/lib64/condor
  libexec	/usr/libexec/condor
  local/condor_config.local	/etc/condor/
  local/execute	/var/lib/condor/execute
  local/spool	/var/lib/condor/spool
  man	/usr/share/man
  sbin	/usr/sbin
  sql	/usr/share/condor/sql
  src	/usr/src
  INIT	/etc/init.d/condor
  PID	/var/run/condor
  LOGS	/var/log/condor
  LOCK	/var/lock/condor

  
  
• When RPM is relocated, it will automatically install and update init.d script to match its new location. However, when installing the nth instance of HTCondor, it will not stop existing HTCondor or modify init.d scipt. This method should be use only for testing a new version of HTCondor only because it will not affect the running instance. However, installing HTCondor in default location and using RPM upgrade facility is more preferable for upgrading. Otherwise, please install HTCondor via tar file in order to avoid unexpected behavior of the RPM package.

Installing HTCondor into other locations

1. HTCondor RPM contains 3 prefixes that can be relocated to any locations. The RPM itself will automatically update configuration file to match the new locations.
   
   

   Prefix	Contents
   /etc	Configuration files and init script
   /usr	Binaries, scripts, documentation, examples and etc.
   /var	Log files and execute folder

   Note: Each prefix can be relocated into different folder.

2. [Optional] Install Yum's downloadonly module in order to download RPM from repository
   
   

   yum install yum-downloadonly

3. Download HTCondor RPM from yum repository to temporary folder
   
   

   yum install condor --downloadonly --downloaddir=/tmp

4. Install RPM into /opt/condor folder
   
   

   rpm -ivh /tmp/condor-7.5.1-1.rhel5.i386.rpm \
   --relocate /usr=/opt/condor-7.5.0/usr \
   --relocate /var=/opt/condor-7.5.0/var \
   --relocate /etc=/opt/condor-7.5.0/etc

   Note: "-i" option will keep the existing version of HTCondor in the system. To remove a specific instance of HTCondor, stop its processes and use rpm -e condor-{version} to remove it. Please see this section for more detail about the behavior of HTCondor RPM when multiple instances are installed

   
   
5. Start HTCondor daemons
   

   service condor start

6. Check if HTCondor is running
   

   ps -ef | grep condor

   Expected Result:

   condor   29612     1  0 23:36 ?        00:00:01 /usr/sbin/condor_master -pidfile /var/run/condor/master.pid
   condor   29613 29612  0 23:36 ?        00:00:00 condor_collector -f
   condor   29614 29612  0 23:36 ?        00:00:00 condor_negotiator -f
   condor   29615 29612  0 23:36 ?        00:00:00 condor_schedd -f
   condor   29616 29612  1 23:36 ?        00:00:05 condor_startd -f
   root     29618 29615  0 23:36 ?        00:00:00 condor_procd -A /var/run/condor/procd_pipe.SCHEDD -S 60 -C 102
   

7. [Optional] Setup environment variables

   export PATH=${PATH}:/opt/condor/usr/bin:/opt/condor/usr/sbin
   export CONDOR_CONFIG=/opt/condor/etc/condor/condor_config