Contents

• Contents
  • Copyright and Disclaimer
  • Academic Object Code Use License for Condor
• 1 Overview
  • 1.1 What is High-Throughput Computing (HTC) ?
  • 1.2 HTC and Distributed Ownership
  • 1.3 What is Condor ?
    • 1.3.1 A Hunter of Available Workstations
    • 1.3.2 Effective Resource Management
  • 1.4 Distinguishing Features
  • 1.5 Current Limitations
  • 1.6 Availability
  • 1.7 Future Work
  • 1.8 Contact Information
• 2 Users' Manual
  • 2.1 Welcome to Condor
  • 2.2 What does Condor do?
  • 2.3 Condor Matchmaking with ClassAds
    • 2.3.1 Inspecting Machine ClassAds with condor_status
  • 2.4 Road-map for running jobs with Condor
  • 2.5 Job Preparation
    • 2.5.1 Batch Ready
    • 2.5.2 Choosing a Condor Universe
      • Standard Universe
      • Vanilla Universe
    • 2.5.3 Relinking for the Standard Universe
  • 2.6 Submitting a Job to Condor
    • 2.6.1 Sample submit-description files
      • Example 1
      • Example 2
      • Example 3
    • 2.6.2 More about Requirements and Rank
    • 2.6.3 Hetrogeneous submit: submit to a different architecture
  • 2.7 Managing a Condor Job
    • 2.7.1 Checking on the progress of your jobs
    • 2.7.2 Removing the job from the queue
    • 2.7.3 While your job is running ...
    • 2.7.4 Changing the priority of jobs
    • 2.7.5 Why won't my job run?
  • 2.8 Priorities in Condor
    • 2.8.1 Job Priority
    • 2.8.2 User priority
  • 2.9 Parallel Applications in Condor: Condor-PVM
    • 2.9.1 What does Condor-PVM do?
    • 2.9.2 The Master-Worker Paradigm
    • 2.9.3 Binary Compatibility
    • 2.9.4 Runtime differences between Condor-PVM and regular PVM
    • 2.9.5 A Sample PVM program for Condor-PVM
    • 2.9.6 Sample PVM submit file
  • 2.10 Interjob Dependencies: DAGman metascheduler
  • 2.11 More about how Condor vacates a job
  • 2.12 Special Environment Considerations
    • 2.12.1 AFS
    • 2.12.2 NFS Automounter
    • 2.12.3 Condor Daemons running as Non-root
  • 2.13 Potential Problems
    • 2.13.1 Renaming of argv[0]
• 3 Administrators' Manual
  • 3.1 Introduction
    • 3.1.1 The Different Roles a Machine Can Play
    • 3.1.2 The Condor Daemons
  • 3.2 Installation of Condor
    • 3.2.1 Preparing to Install Condor
      • What machine will be the Central Manager?
      • Will Condor run as root or not?
      • Who will be administering Condor on the machines in your pool?
      • Will you have a 'condor' user and will it's home directory be shared?
      • Where should the machine-specific directories for Condor go?
      • Where should the parts of the Condor system be installed?
      • Am I using AFS?
      • Do I have enough disk space for Condor?
    • 3.2.2 Installation Procedure
      • condor_install, step-by-step
      • Full Install
      • Submit Only
    • 3.2.3 Condor is installed... now what?
    • 3.2.4 Starting up the Condor daemons
    • 3.2.5 The Condor daemons are running... now what?
  • 3.3 Configuring Condor
    • 3.3.1 Introduction to Config Files
      • Config File Macros
      • Config File Expressions
      • Other Syntax
      • Pre-Defined Macros and Expressions
      • Condor Subsystem Names
    • 3.3.2 Condor-wide Config File Entries
    • 3.3.3 Daemon Logging Config File Entries
    • 3.3.4 DaemonCore Config File Entries
    • 3.3.5 Shared Filesystem Config File Entries
    • 3.3.6 Checkpoint Server Config File Entries
    • 3.3.7 condor_master Config File Entries
    • 3.3.8 condor_startd Config File Entries
    • 3.3.9 condor_schedd Config File Entries
    • 3.3.10 condor_shadow Config File Entries
    • 3.3.11 condor_shadow.pvm Config File Entries
    • 3.3.12 condor_starter Config File Entries
    • 3.3.13 condor_submit Config File Entries
    • 3.3.14 condor_preen Config File Entries
    • 3.3.15 condor_collector Config File Entries
    • 3.3.16 condor_negotiator Config File Entries
  • 3.4 Configuring The Startd Policy
    • 3.4.1 Startd ClassAd Attributes
    • 3.4.2 Job ClassAd Attributes
    • 3.4.3 condor_startd START expression
    • 3.4.4 condor_startd RANK expression
    • 3.4.5 condor_startd States
    • 3.4.6 condor_startd Activities
    • 3.4.7 condor_startd State and Activity Transitions
      • Owner State
      • Unclaimed State
      • Matched State
      • Claimed State
      • Preempting State
    • 3.4.8 condor_startd State/Activity Transition Expression Summary
    • 3.4.9 Example Policy Settings
      • Default Policy Settings
      • UW-Madison CS Condor Pool Policy Settings
  • 3.5 DaemonCore
    • 3.5.1 DaemonCore and UNIX signals
    • 3.5.2 DaemonCore and Command-line Arguments
  • 3.6 Setting Up IP/Host-Based Security in Condor
    • 3.6.1 How does it work?
    • 3.6.2 Security Access Levels
    • 3.6.3 Configuring your Pool
    • 3.6.4 Access Levels each Daemons Uses
    • 3.6.5 Access Level Examples
  • 3.7 Setting up Condor for Special Environments
    • 3.7.1 Using Condor with AFS
      • AFS and Condor for Administrators
      • AFS and Condor for Users
    • 3.7.2 Full Installation of condor_compile
    • 3.7.3 Installing the condor_kbdd
    • 3.7.4 Installing a Checkpoint Server
    • 3.7.5 Installing PVM Support in Condor
  • 3.8 Security In Condor
    • 3.8.1 Running Condor as Non-Root
    • 3.8.2 UIDs in Condor
    • 3.8.3 Root Config Files
• 4 Miscellaneous Concepts
  • 4.1 An Introduction to Condor's ClassAd Mechanism
    • 4.1.1 Syntax
      • Literals
      • Attributes
      • Operators
    • 4.1.2 Evaluation Semantics
      • Literals
      • Attribute References
      • Operators
    • 4.1.3 ClassAds in the Condor System
      • Requirements and Ranks
      • Querying with ClassAd Expressions
• 5 Command Reference Manual (man pages)

Copyright and Disclaimer

 Copyright © 1990-1998 Condor Team, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved. No use of the Condor Software Program Object Code (Condor) is authorized without the express consent of the Condor Team. For more information contact: Condor Team, Attention: Professor Miron Livny, 7367 Computer Sciences, 1210 W. Dayton St., Madison, WI 53706-1685, (608) 262-0856 or miron@cs.wisc.edu.

Allowed Uses: User may use Condor for research, educational, or other non-commercial purposes only. User acknowledges and agrees that the Condor Team grants no rights whatsoever for commercial use of Condor or in any commercial version(s) of Condor.

Use Restrictions: User may not and User may not permit others to (a) decipher, disassemble, decompile, translate, reverse engineer or otherwise derive source code from Condor, (b) modify or prepare derivative works of Condor, (c) copy Condor, except to make a single copy for archival purposes only, (d) rent or lease Condor, (e) distribute Condor electronically, (f) use Condor in any manner that infringes the intellectual property or rights of another party, or (g) transfer Condor or any copy thereof to another party.

Warranty Disclaimer: USER ACKNOWLEDGES AND AGREES THAT: (A) NEITHER THE Condor TEAM NOR THE BOARD OF REGENTS OF THE UNIVERSITY OF WISCONSIN SYSTEM (REGENTS) MAKE ANY REPRESENTATIONS OR WARRANTIES WHATSOEVER ABOUT THE SUITABILITY OF Condor FOR ANY PURPOSE; (B) Condor IS PROVIDED ON AN "AS IS, WITH ALL DEFECTS" BASIS WITHOUT EXPRESS OR IMPLIED WARRANTIES, INCLUDING WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT; (C) NEITHER THE Condor TEAM NOR THE REGENTS SHALL BE LIABLE FOR ANY DAMAGE OR LOSS OF ANY KIND ARISING OUT OF OR RESULTING FROM USER’S POSSESSION OR USE OF Condor (INCLUDING DATA LOSS OR CORRUPTION), REGARDLESS OF WHETHER SUCH LIABILITY IS BASED IN TORT, CONTRACT, OR OTHERWISE; AND (D) NEITHER THE Condor TEAM NOR THE REGENTS HAVE AN OBLIGATION TO PROVIDE DEBUGGING, MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.

Damages Disclaimer: USER ACKNOWLEDGES AND AGREES THAT IN NO EVENT WILL THE Condor TEAM OR THE REGENTS BE LIABLE TO USER FOR ANY SPECIAL, CONSEQUENTIAL, INDIRECT OR SIMILAR DAMAGES, INCLUDING ANY LOST PROFITS OR LOST DATA ARISING OUT OF THE USE OR INABILITY TO USE Condor EVEN IF THE Condor TEAM OR THE REGENTS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Attribution Requirement: User agrees that any reports, publications, or other disclosure of results obtained with Condor will attribute its use by an appropriate citation. The appropriate reference for Condor is "The Condor Software Program (Condor) was developed by the Condor Team at the Computer Sciences Department of the University of Wisconsin-Madison. All rights, title, and interest in Condor are owned by the Condor Team."

Compliance with Applicable Laws: User agrees to abide by copyright law and all other applicable laws of the United States including, but not limited to, export control laws. User acknowledges that Condor in source code form remains a confidential trade secret of the Condor Team and/or its licensors and therefore User agrees not to modify Condor or attempt to decipher, decompile, disassemble, translate, or reverse engineer Condor, except to the extent applicable laws specifically prohibit such restriction.

U.S. Government Rights Restrictions: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of Commercial Computer Software-Restricted Rights at 48 CFR 52.227-19, as applicable, Condor Team, Attention: Professor Miron Livny, 7367 Computer Sciences, 1210 W. Dayton St., Madison, WI 53706-1685, (608) 262-0856 or miron@cs.wisc.edu.

Academic Object Code Use License for Condor

This is an Academic Object Code Use License for Condor. This license is between you (the "RECIPIENT"), and the Condor Team at the Computer Sciences Department of the University of Wisconsin-Madison (the "PROVIDER"). The Condor software program was developed by the Condor Team. All rights, title, and interest in Condor are owned by the Condor Team. The subject computer program, including executables and supporting documentation, shall be referred to as the "SOFTWARE".

RECIPIENT and PROVIDER agree as follows:

1.

A non-exclusive, non-transferable academic use license is granted to the RECIPIENT to install and use the SOFTWARE on any appropriate computer systems located at the RECIPIENT’s institution to which the RECIPIENT has authorized access. Use of the SOFTWARE is restricted to the RECIPIENT and collaborators at RECIPIENT’s institution who have agreed to accept the terms of this license.

2.

The PROVIDER shall retain ownership of all materials (including magnetic tape, unless provided by the RECIPIENT) and SOFTWARE delivered to the RECIPIENT. Any modifications or derivative works based on the SOFTWARE shall be considered part of the SOFTWARE and ownership thereof shall be retained by the PROVIDER and shall be made available to the PROVIDER upon request.

3.

The RECIPIENT may make a reasonable number of copies of the SOFTWARE for the purpose of backup and maintenance of the SOFTWARE, or for development of derivative works based on the SOFTWARE. The RECIPIENT agrees to include all copyright or trademark notices on any copies of the SOFTWARE or derivatives thereof. All copies of the SOFTWARE, or derivatives thereof, shall be destroyed by the RECIPIENT upon termination of this license.

4.

The RECIPIENT shall use the SOFTWARE for research, educational, or other non-commercial purposes only. The RECIPIENT acknowledges that this license grants no rights whatsoever for commercial use of the SOFTWARE or in any commercial version(s) of the SOFTWARE. The RECIPIENT is strictly prohibited from deciphering, disassembling, decompiling, translating, reverse engineering or otherwise deriving source code from the SOFTWARE, except to the extent applicable laws specifically prohibit such restriction.

5.

The RECIPIENT shall not disclose in any form either the delivered SOFTWARE or any modifications or derivative works based on the SOFTWARE to any third party without prior express authorization from the PROVIDER.

6.

If the RECIPIENT receives a request to furnish all or any portion of the SOFTWARE to any third party, RECIPIENT shall not fulfill such a request, and further agrees to refer the request to the PROVIDER.

7.

The RECIPIENT agrees that the SOFTWARE is furnished on an "as is, with all defects" basis, without maintenance, debugging, support or improvement, and that neither the PROVIDER nor the Board of Regents of the University of Wisconsin System warrant the SOFTWARE or any of its results and are in no way liable for any use that the RECIPIENT makes of the SOFTWARE.

8.

The RECIPIENT agrees that any reports, publications, or other disclosure of results obtained with the SOFTWARE will acknowledge its use by an appropriate citation. The appropriate reference for the SOFTWARE is "The Condor Software Program (Condor) was developed by the Condor Team at the Computer Sciences Department of the University of Wisconsin-Madison. All rights, title, and interest in Condor are owned by the Condor Team."

9.

The term of this license shall not be limited in time. However, PROVIDER may terminate RECIPIENT’s license without cause at any time.

10.

Source code for the SOFTWARE is available upon request and at the sole discretion of the PROVIDER.

11.

This license shall be construed and governed in accordance with the laws of the State of Wisconsin.

For more information:

Condor Team
Attention: Professor Miron Livny
7367 Computer Sciences
1210 W. Dayton St.
Madison, WI 53706-1685
miron@cs.wisc.edu
http://www.cs.wisc.edu/~miron/miron.html