Slurm does not provide this functionality today, but it would probably
be simple to add.
Linux cgroup (and the corresponding Slurm cgroup plugins) can bind
each job to its own set of CPUs, memory, and device files (e.g. GPUs)
to avoid jobs interfering with each other. Do you really need more
than that (i.e. prevent one user from seeing another user's processors)?
Quoting Nathan Harper <[email protected]>:
although it's not something we have working, this is something I'd be keen
to have. User exclusivity on a node is something that is important to the
way that we use our clusters, so we currently use 'linear'. Most of our
jobs are parallel, so allocating a whole node isn't terrible wasteful, but
it would be nice to use con_res, then let users choose if they want to
share jobs, but only with themselves.
--
*Nathan Harper* // IT Systems Architect
*e: * [email protected] // *t: * 0117 906 1104 // *m: *
07875 510891 //
*w: * www.cfms.org.uk <http://www.cfms.org.uk%22> // [image: Linkedin grey
icon scaled] <http://uk.linkedin.com/pub/nathan-harper/21/696/b81>
CFMS Services Ltd // Bristol & Bath Science Park // Dirac Crescent
// Emersons
Green // Bristol // BS16 7FR
[image: 4.2 CFMS_Artwork_RGB] <http://www.cfms.org.uk>
------------------------------
CFMS Services Ltd is registered in England and Wales No 05742022 - a
subsidiary of CFMS Ltd
CFMS Services Ltd registered office // Victoria House // 51 Victoria Street
// Bristol // BS1 6AD
On 19 November 2014 21:36, Marcin Sliwowski <[email protected]> wrote:
Was wondering if any of SLURM's internal schedulers have the equivalent
setting as Maui's "nodeaccesspolicy singleuser".
In Maui this means that multiple jobs owned by the same user may land on a
single node.
I am using the cons_res selection plugin with shed/backfill for
SchedulerType and --exclusive only allows a single job on any given node.
Without --exclusive jobs from many users can land on a single node.
Thanks
--
Marcin Sliwowski | SysAdmin@RENCI | 919-445-0479
--
Morris "Moe" Jette
CTO, SchedMD LLC
