HTCondor Project List Archives



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-devel] Per machine resource limits in 7.6/7.8



On 5/1/2012 3:52 PM, Alan De Smet wrote:
I had an interesting chat with a Condor Week attendee who has
some challenges that I'm not sure how to handle.  They have
various limited resources (software licenses) , but the limits
aren't global, they're per machine, so the concurrency limits
aren't a good fit.  Furthermore a job might claim multiple
identical resources at once, in much the same way a single job
might claim multiple cores.

Maybe something like so in the job submit file:

  concurrency_limits = licenseX_$$(Machine), licenseY_$$(Machine)

Actually, the above likely will not work because $$() is not expanded in the matchmaker... but if concurrency_limits is evaluated, perhaps you could do the above idea but via ClassAd string cat functions.

Todd


Custom resource limits per eje's proposal
(https://condor-wiki.cs.wisc.edu/index.cgi/tktview?tn=2905) seem
like a good fit, and he was open to the idea.  However, that's
7.9 territory, and they'd prefer to not use a development
release.

Is there a good solution for 7.6 or 7.8?  All I've got in having
slots START expressions total up usage by other slots and testing
against the limit, which seems clumsy.



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