Hello, Thank you for your reply, however I’m afraid that Shared=exclusive didn’t work. I noticed that another user asked the same question a while ago (https://groups.google.com/forum/#!topic/slurm-devel/q063AW5SABM), and at the time there was no internal mechanism to enable exclusive user access to a single node (that is multiple jobs on a single all owned by a single user – no access to other users while the node is allocated). I’m not convinced that things have moved on since then, however I could be missing something fundamental. As I say, --exclusive=user will work, however we’d have to train users to do that in their jobs, and so it would be good if there was a setting that we could apply in the slurm.conf.
Best regards, David. From: [email protected] [mailto:[email protected]] Sent: Tuesday, February 09, 2016 2:14 PM To: slurm-dev <[email protected]> Subject: [slurm-dev] Re: Implementing a single node policy with slurm Hi David - When you define your partition you can state SHARED=exclusive, so when a node is allocated only that user will have access to it. Kelly On 02/09/16, Baker D.J.<[email protected]<mailto:[email protected]>> wrote: Hello, I’m starting to evaluate slurm and I’m coming from a torque/moab background. On our clusters we operate a single user policy. That is, a compute node can only be used by a single user – only they can put jobs on to that node once it’s allocated. I would like to do the same thing in slurm. I’m aware that we could submit each job using “—exclusive=user”, however how can we make that the default? Offhand I can see that we could write a wrapper script for sbatch, however is there a better way to achieve this? Also, as an aside, when a user runs “squeue” is there a way to configure that command so that it only shows jobs belonging to that user. Is there a nice way to do this? Any advice would be appreciated, please. Best regards, David.
