The Condor resource manager provides a basic mechanism for computation resources to be made available for use by applications and other system elements. While similar in principle to other local schedulers or queueing systems, it includes a set of features that allow it to be used in unique and useful ways.
Condor's resource manager can be configured to make the resource available for remote use only when it is not otherwise occupied with local tasks. This allows pools of Condor-managed resources to be put to work when they otherwise would be idle. Condor's ClassAd feature allows a "matchmaking" algorithm to match requests for resources with available resources in a highly flexible manner. Condor also provides checkpointing and job migration features.
Condor's "flocking" mechanism allows multiple Condor pools to be linked together so that job requests received by one pool can be executed on another pool. Condor can be used in "glide-in" mode, where a "master job" is submitted to a system and when the job runs, the Condor service is started and Condor tasks can be submitted to it as long as the master job runs.
Condor is often run in conjunction with GRAM services. A GRAM service can provide the standard GRAM interface to a Condor pool (accepting job requests that are then executed on the pool). Or, compute resources that provide a GRAM interface can be added to a Condor pool so that Condor jobs can be executed on them.
|Developed by:||The Condor Project|
Download from the Condor Project
(must be subscribed before posting)