[HTCondor-devel] Automatic requirements


Date: Thu, 31 Jul 2014 16:02:49 -0400
From: Ben Cotton <ben.cotton@xxxxxxxxxxxxxxxxxx>
Subject: [HTCondor-devel] Automatic requirements
For discussion:

I recently noticed that specifying OpSysAndVer in a job's requirements
still results in the automatic "helpful" addition of the host's OpSys.

The behavior I would expect is that specifying one of OpSysAndVer,
OpSysLongName, OpSysName, OpSysShortName would squelch the automatic
insertion of OpSys. (I'd argue that OpSysMajorVersion and OpSysVer are
ambiguous enough that HTCondor should still be helpful). I can imagine
a user submitting from a Linux machine wanting to submit a Windows job
with

  Requirements = OpSysAndVer == "WINDOWS601"

being confused as to why the job never matches. I propose that the
attributes above should be sufficient to prevent the automatic
insertion of OpSys. Thoughts?


Thanks,
BC
-- 
Ben Cotton
main: 888.292.5320

Cycle Computing
Leader in Utility HPC Software

http://www.cyclecomputing.com
twitter: @cyclecomputing
[← Prev in Thread] Current Thread [Next in Thread→]
  • [HTCondor-devel] Automatic requirements, Ben Cotton <=