Installation of the glidein pool Collector

1. Description

The glidein pool Collector node will be the Condor Central Manager for the glidein pool, i.e. it  will run the Condor Collector and Negotiator daemons.
These daemons define the glidein pool; if this node dies, the pool dies with it.

2. Hardware requirements

This machine needs 2 fast CPUs (one for the Collector and one for the Negotiator) and a moderate amount of memory (512MB should be enough).
It must have reliable network connectivity and must be on the public internet, with no firewalls; all worker nodes will be continuously sending UDP packets to the Collector.
The machine must be very stable; if the Collector dies, the glidein pool dies with it (There are Condor technickes to minimize this damage, but you should still try to choose the stablest machine you can afford.)
The disk needed is just for Condor binaries and log files (5GB should be enough)

3. Needed software

Any Condor-supported OS.
The OSG client software.
The Condor distribution.

4. Installation instructions

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

4.1 Install Condor

Follow instructions in the Condor v6.9.2 installation document.

4.2 Disable schedd and startd on this node

Unless you plan to use this node for other purpuses, too, change DAEMON_LIST in /opt/glidecondor/condor_local/condor_config.local, to:
DAEMON_LIST   = MASTER, COLLECTOR, NEGOTIATOR

4.3 Configure Condor Negotiator

UDP packets over WAN tend to get lost. Force Negotiator to prefer resources that recently announced themselves, by adding the following lines in /opt/glidecondor/condor_local/condor_config.local:
############################################################
## Tuning
############################################################
NEGOTIATOR_POST_JOB_RANK = MY.LastHeardFrom

4.4 Configure Condor security

Follow instructions in the Configuring GSI security in Condor document.

The /opt/glidecondor/certs/grid-mapfile must be populated with the pool service proxy DN, as well as the DNs of all the used schedds and glidein factories (i.e. glideins).
Assuming the local service proxy DN is "/DC=org/DC=doegrids/OU=Service/CN=glide1", you have two schedds sharing the same DN "/DC=org/DC=doegrids/OU=Service/CN=schedd1", and that glideins use the DN "/DC=org/DC=doegrids/OU=Service/CN=gwn2", the grid-mapfile would contain something like:
"/DC=org/DC=doegrids/OU=Service/CN=glide1" ccondor
"/DC=org/DC=doegrids/OU=Service/CN=schedd1" scondor1
"/DC=org/DC=doegrids/OU=Service/CN=gwn2" wcondor
The names you specify after the DN are not important, but they must differ one from another.

4.5 Example config files

You can find the complete config files in
example-config/glide-pool-collector/mymachine/condor_config
and
example-config/glide-pool-collector/mymachine/condor_config.local

5. Starting condor

To start Condor, login as root in a fresh terminal, and issue:
/opt/glidecondor/sbin/condor_master
You should see three processes run as user condor: condor_master, condor_collector and condor_negotiator.

The log files can be found in /opt/glidecondor/condor_local/log.


Back to the index