8.3 Development Release Series 7.1

This is the development release series of Condor. The details of each version are described below.

Version 7.1.0

Release Notes:

• Upgrading to 7.1.0 from previous versions of Condor will make existing Standard Universe jobs that have already run fail to match to machines running Condor 7.1.0 unless the job previously ran on a machine using the Red Hat 5.0 release of Condor. This is because the value of the CheckpointPlatform attribute of the machine ClassAd has changed in order to better represent checkpoint compatibility. If this affects you, you can use condor_ qedit to change the LastCheckpointPlatform attribute of existing Standard Universe jobs to match the new CheckpointPlatform advertised by the machine ClassAd where the job last ran.

• Condor no longer supports root configuration files (for example, /etc/condor/condor_config.root,  condor/condor_config.root, and the file defined by the configuration variable LOCAL_ROOT_CONFIG_FILE). This feature was intended to give limited powers to a Unix administrator to configure some aspects of Condor without gaining root powers. However, given the flexibility of the configuration system, we decided that this was not practical. As long as Condor is started up as root, it should be clearly understood that whoever has the ability to edit the Condor configuration files can effectively run arbitrary programs as root.

New Features:

• In the past, Condor has always sent work to the execute machines by pushing jobs to the condor_ startd, either from the condor_ schedd or via condor_ cod. As of version 7.1.0, The condor_ startd now has the ability to pull work by fetching jobs via a system of plug-ins or hooks. Additional hooks are invoked by the condor_ starter to help manage work (especially for fetched jobs, but the condor_ starter hooks can be defined and invoked for other kinds of jobs as well). For a complete description of the new hook system, read section 4.4 on page .

• Added the capability to insert commands into the .condor.sub file produced by condor_ submit_dag with the -append and -insert_sub_file command-line arguments to condor_ submit_dag and the DAGMAN_INSERT_SUB_FILE configuration variable. See the condor_ submit_dag manual page on page  and the configuration variable definition on page  for more information.

• For platforms running a Windows operating system, the Arch machine ClassAd attribute more correctly reflects the architectures supported. Instead of values "INTEL" and "UNDEFINED", the values will now be: "INTEL" for x86, "IA64" for Intel Itanium, and "X86_64" for both AMD and Intel 64-bit processors. These values are listed in the unnumbered subsection labeled Machine ClassAd Attributes on page .

• The Windows MSI installer now supports extended vm universe options. These new options include: the ability to set the networking type, how much memory the vm universe can use on a host, and the ability to set the version of VMware installed on the host.

• The condor_ status and condor_ q command line tools now have a version option which prints the version of those specific tools. This can be useful when multiple versions of Condor are installed on the same machine.

• The configuration variable CONDOR_VIEW_HOST may now contain a port number and may (if desired) refer to a condor_ collector daemon running on the same host as the condor_ collector that is forwarding ads. It is also now possible to use the forwarded ads for matchmaking purposes. For example, several collectors could forward ads to a single aggregating collector which a condor_ negotiator then uses as its source of information for matchmaking.

• Added client-side authorization controls ALLOW_CLIENT, DENY_CLIENT. When using a mutual authentication method (e.g. GSI, SSL, Kerberos), this allows you to specify what authenticated servers Condor tools and daemons should trust when they form a connection to the server. This deprecates GSI_DAEMON_NAME, which provided rudimentary support for client-side authorization in a GSI-specific way.

• condor_ dagman deals with rescue DAGs in a more sophisticated way; this is especially helpful for nested DAGs. See the rescue DAG subsection  of the condor_ dagman manual section for more information.

• A new (optional) daemon named condor_ job_router has been added, so far only on unix. It may be configured to transform vanilla universe jobs into grid universe jobs, for example to send excess jobs to other sites via Condor-C or Condor-G. For details, see page .

• Previously, condor_ q -better-analyze was supported on most but not all versions of Linux. It is now supported on all Unix platforms but not yet on Windows.

Configuration Variable Additions and Changes:

• Added the DAGMAN_INSERT_SUB_FILE variable, which allows a file of commands to be inserted into .condor.sub files generated by condor_ submit_dag. See page  for more information.

• The semantics of CLAIM_WORKLIFE were previously not clearly defined before the start of the first job. A delay between the condor_ schedd claiming a slot and the condor_ shadow starting a job could be caused by the submit machine being very busy or by JOB_START_DELAY. Previously, such a delay would unpredictably result in the first job being rejected if CLAIM_WORKLIFE expired during that time. Now, CLAIM_WORKLIFE is defined to apply only after the first job has started. Therefore, setting it to zero has the effect of allowing exactly one job per claim to run. The default is still the special value -1, which places no limit on how long the slot may continue accepting new jobs from the condor_ schedd that claimed it.

• Added the DAGMAN_OLD_RESCUE variable, which controls whether condor_ dagman writes rescue DAGs in the old way. See page  for more information.

• Added the DAGMAN_AUTO_RESCUE variable, which controls whether condor_ dagman automatically runs an existing rescue DAG. See page  for more information.

• Added the DAGMAN_MAX_RESCUE_NUM variable, which controls the maximum "new-style" rescue DAG number written or automatically run by condor_ dagman. See page  for more information.

Bugs Fixed:

• The Condor Build ID is now printed by condor_ version and placed in the logs for machines running a Windows operating system.

• condor_ quill and the condor_ dbmsd correctly register themselves with the Windows firewall.

• condor_ submit_dag now avoids possibly running off the end of the argument list if an argument requiring a value does not have one.

• The condor_ submit_dag -debug argument now must be specified with at least -de to avoid conflict with the -dagman argument.

• Added missing information about the -config argument to condor_ submit_dag's usage message.

• condor_ dagman no longer considers duplicate edges in a DAG a fatal error (it is now a warning).

Known Bugs:

• No hook is invoked if a fetched job does not contain enough data to be spawned by a condor_ starter or if other errors prevent the job from being run after the condor_ startd agrees to accept the work. This limitation will be addressed in a future version of Condor, most likely via the addition of a new hook invoked whenver the condor_ starter fails to spawn a job. For more information about the new hook system included in Condor version 7.1.0, read section 4.4 on page .

Additions and Changes to the Manual:

• Added "WINNT60" for the Vista operating system to the documented list of possible values for the machine ClassAd attribute OpSys.