Re: [HTCondor-users] Possible to have submit-implemented per-machine job limits?

[Joan Piles <jpiles@xxxxxxxxxxxxxxxx>]

Hi,

One thing that we'd like to see implemented, and that could potentially 
be very useful in cases like this, is some generic "custom machine 
resources" mechanism with a (ideally per-prefix) system-defined default, 
so users could define their own policies. The model would be what we 
already have with default concurrency limits (which we already use as well).

The problem with configuring specific machine attributes for single 
cases is that it doesn't really scale that well...

Best,

Joan


On 09/12/2016 08:21 PM, Todd Tannenbaum wrote:

> Doing what you want via setting up a custom machine resource (i.e.
> request_port777 = 1) is exactly what I'd suggest; scenarios like the
> above are why custom machine resources exist, since this really is a
> custom machine resource.  For instance, what if two different users both
> have an app that requires the same static slot?
>
> But given that you cannot configure the execute nodes, perhaps your job
> requirements could look at the ChildRemoteUser attribute in the
> partitionable slot?  This attribute is a classad list of all the owners
> of dynamic slots on the machine.  You could probably leverage this so
> only one job submitted by you runs on each machine...
>
> regards
> Todd

--
Dr. Joan Piles
ZWE Scientific Computing
Max Planck Institute for Intelligent Systems
(p) +49 7071 601 1750

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature