Re: [HTCondor-devel] Automatic requirements

[Todd Tannenbaum <tannenba@xxxxxxxxxxx>]

On 8/6/2014 4:30 PM, Ben Cotton wrote:
> Since nobody said "hey, this is a really dumb idea", I went ahead and
> submitted a pull request:
>
> https://github.com/htcondor/htcondor/pull/4
Very cool.  Could you please email me back a signed contributors license 
agreement ?
The PDF is at url
  http://www.cs.wisc.edu/condor/licenses/CLA-PUBLIC.pdf
Just sign, scan, and email it to me.   Then I'll merge in your code.

Thanks for the patch!!!!!


Thanks
Todd


> I don't actually know C++ and I haven't touched C in many many years,
> so it might be totally awful.
>
> On Thu, Jul 31, 2014 at 4:02 PM, Ben Cotton
> <ben.cotton@xxxxxxxxxxxxxxxxxx> wrote:
> > 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

--
Todd Tannenbaum <tannenba@xxxxxxxxxxx> University of Wisconsin-Madison
Center for High Throughput Computing   Department of Computer Sciences
HTCondor Technical Lead                1210 W. Dayton St. Rm #4257
Phone: (608) 263-7132                  Madison, WI 53706-1685