BoilerGrid

Condor Boot Camp at Purdue

Lecture Materials

Using Condor (Powerpoint) (PDF)
Administrating Condor (Powerpoint) (PDF) (Handout)
Condor Tutorial

For More Information

Other Materials

Implementing an Industrial-Strength Academic Cyberinfrastructure at Purdue University

Implementing a Central Quill Database in a Large Condor Installation (Condor Week 2008)

Powerpoint

BoilerGrid for cyro-EM image processing (Condor Week 2008)

Powerpoint

This site is currently under construction. Please check back frequently for updates.

Technical Information - For Purdue Administrators

My department runs condor already. How can we participate?

If you operate Condor already, then you're most of the way there. Condor pools can be joined with Condor's "flocking" mechanism. To set up flocking with RCAC:

Send the DNS hostname of your Condor central manager (condor_negotiator and condor_collector) to rcac-help@purdue.edu
RCAC Condor administrators will then allow your condor pool access to RCAC pools.
Set the following variables in your condor_config file:

FLOCK_TO = emu.rcac.purdue.edu, egret.rcac.purdue.edu, \
flamingo.rcac.purdue.edu


FLOCK_FROM = *.rcac.purdue.edu

Run "condor_reconfig" on your condor servers, and your pool should be configured to flock to and from RCAC.

Or, RCAC provides a dedicated central manager to serve the Purdue campus, your department is welcome to use it rather than operating your own.

In your condor_config file, change the value for CONDOR_HOST:
```
CONDOR_HOST = egret.rcac.purdue.edu
```
We recommend using TCP updates to the Condor Collector, particularly if you are providing many Windows machines:
```
UPDATE_COLLECTOR_WITH_TCP = TRUE
```

My department does not run condor, but would be interested in providing cycles

Contact rcac-help@purdue.edu before proceeding, and your systems will be added to BoilerGrid's access control lists.

Linux

If you are installing on Linux, RCAC provides pre-packaged, fully configured binaries for common Linux flavors.

boilergrid-condor_7.0.5-1_amd64.deb - Debian Etch AMD64
boilergrid-condor_7.0.5-1_i386.deb - Debian Etch i386
boilergrid-condor_7.0.5-1_i386.deb - Ubuntu 8.04 "Hardy Heron" i386
boilergrid-condor-7.0.5-1.i386.rpm - RedHat (CentOS, Scientific Linux) version 4 - i686
boilergrid-condor-7.0.5-1.x86_64.rpm - RedHat (CentOS, Scientific Linux) version 4 - x86_64

If it does not exist, these packages will create the user "condor", with the home directory of /var/condor. If you wish to change the user condor's home directory, be sure to move the contents of /var/condor along with it.

The installation will use reasonable defaults, but if you'd like to further customize policies for starting, suspending, and preempting jobs on your execute nodes, consult the Condor manual for details.

Windows

boilergrid-condor_7.0.5.exe - Windows XP, Vista

Grid Management

All of these preconfigured installers are configured to query BoilerGrid's CycleServer management console, to facilitate grid-wide settings.

Firewalls

All preconfigured BoilerGrid installers are configured to restrict Condor's port usage to the range 50000-50100. If configured to allow it, Condor for Windows will install exceptions for Condor in the Windows firewall. Otherwise, if you use a firewall, be sure to open TCP and UDP ports 50000-50100 to *.rcac.purdue.edu or the IP space 128.211.128.0/19.

Mailing List

If your department provides more than just a couple of machines to BoilerGrid, we recommend that you join the following Mailing List to keep abreast of new developments, and collaborate with other Condor admins around campus.