Requirementsexpression of the job so that it only matches those machines. Knowing ahead of time is problematic and difficult to maintain as the pool changes. A better solution uses this two-step process.
First, each machine that has the special software installed needs to advertise its availability in its machine ClassAd . Second, the job identifies in its submit description file that it requires a machine that has the special software.
A machine advertises the presence of special software in its local configuration file, as in this example:
HAS_MY_SOFTWARE = True
is already defined in that file, add
to the list. If
is not already in
that local configuration file, add the line:
STARTD_ATTRS = HAS_MY_SOFTWARE, $(STARTD_ATTRS)
For this configuration change to take effect, the condor_startd on that machine
needs to be reconfigured. Use
. Each machine with
the configuration change must be reconfigured.
Double check that this has been correctly implemented by running the condor_status command:
condor_status -constraint HAS_MY_SOFTWARE
Jobs that need to run on the machines with the special software installedadd a
command to their submit description file:
Requirements = (HAS_MY_SOFTWARE =?= True)
Be sure to use
, so that if a machine does not have
configuration variable defined, the job's
expression will not evaluate to
, preventing the job from