Installation of the glidein pool Collector

[Description |Hardware requirements |Needed software |Installation instructions ]

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 one or two fast CPUs (one for the Collector and one for the Negotiator) and a moderate amount of memory (1GB should be enough for most tasks; really big pools may need more).
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 techniques 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 Python interpreter (for the installer, v2.3.4 or above)
The OSG client software.
The Condor distribution.


4. Installation instructions

The pool Collector can be installed either as root or as a non privileged user. Either case, make sure that the user has access to the needed GSI credentials.
There is no real advantage to install as root, so non-privileged installation is recommended if installed separately.

The whole process is managed by a install script described below. You will need to provide a valid Condor tarball, so you may as well download it before starting the installer.

Move into


and execute


You will be presented with this screen:

What do you want to install?
(May select several options at one, using a , separated list)
[1] glideinWMS Collector
[2] Glidein Factory
[3] GCB
[4] pool Collector
[5] Schedd node
[6] Condor for VO Frontend
[7] VO Frontend
[8] Components

Select 4.

Now follow the instructions and install all the software components. Most of the questions should be fairly straightforward. The part that is not completely automatic is the configuration of the GSI security; you will need to provide the DN(s) of the glideins, the DNs of all the submit machines and the DN of the VO frontend.

Here a possible set of answers is presented; your setup will probably be slightly different:

Do you have already a VDT installation?: (y/n) n
Do you want to install the full OSG VDT client?: (y/n) n
Do you want to install a minimal Grid VDT client?: (y/n) y
Where do you want the VDT installed?: [/opt/vdt] /home/collector/vdt
Directory '/home/collector/vdt' does not exist, should I create it?: (y/n) y
What pacman version should I use?: [pacman-3.26] pacman-3.26

What VDT cache should I use?: []

VDT client installation tends to be very picky about the platforms it installs under
Most of the time, one needs to pretent to be one of the tested platforms
The platforms known to work are: linux-rhel-3,SL-3,linux-rhel-4,SL-4,linux-fedora-4,linux-rhel-5,SL-5
Which platform do you want to use (leave empty for autodetect): enter

VDT 1.10.1 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] y

Where would you like to install CA files?

        l (local) - install into $VDT_LOCATION/globus/share/certificates
        n (no)    - do not install

Where should I fetch the CAs from?: []

Where do you have the Condor tarball? /home/collector/Downloads/condor-7.1.3-linux-x86-rhel3-dynamic.tar.gz

Where do you want to install it?: [/opt/glidecondor] /home/collector/condor
Directory '/home/collector/condor' does not exist, should I create it?: (y/n) y
Installing condor in '/home/collector/condor'

If something goes wrong with Condor, who should get email about it?:

Do you want to split the config files between condor_config and condor_config.local?: (y/n) [y] y

To use the GSI security, you either need a valid GSI proxy or
a valid x509 certificate and relative key
The cert/proxy subject of Pool Collector will be added as the trusted daemon in
GSI_DAEMON_NAME in the condor configuration.
Will you be using a proxy or a cert? (proxy/cert) cert
Where is your certificate located?: /home/collector/grid-security/servicecert.pem
Where is your certificate key located?: /home/collector/grid-security/servicekey.pem
My DN = '/DC=org/DC=doegrids/OU=Services/CN=collector/'

You will most probably need other DNs in the condor grid mapfile
Please add all the DNs that can be used to connect to the
Condor daemons running on this node
The User Schedd and Glidein startd will connect to and act as client to the
Pool Collector. Subjects for these services should be in the gridmap file of
the Pool Collector

Please insert all such DNs, together with a user nickname.
An empty DN entry means you are done.
DN: /DC=org/DC=doegrids/OU=Services/
nickname: [condor001] submit
Is this a trusted Condor daemon?: (y/n) y
DN: /DC=org/DC=doegrids/OU=Services/CN=gfactory/
nickname: [condor002] pilot
Is this a trusted Condor daemon?: (y/n) y
DN: /DC=org/DC=doegrids/OU=Services/CN=frontend/
nickname: [condor002] frontend
Is this a trusted Condor daemon?: (y/n) n
DN: enter
What name would you like to use for this pool?: [My pool] TestPool
How many slave collectors do you want?: [10] 10

5. To Start/Stop Pool Collector

Setup the environment
source /home/collector/condor/

To start Condor run:

You should see three processes run as user condor: condor_master, condor_collector and condor_negotiator.

The log files can be found in /home/condor/condor_local/log.

To stop Condor run:
/home/condor/sbin/condor_off -master

Back to the index

glideinWMS support: