On 17 February 2017 at 03:02, Baker D.J. <[email protected]> wrote:
> Hello, > > > > Thank you for the reply. There are two accounts on this cluster. What I > was primarily trying to do was define a default QOS with a partition. My > idea was to use sacctmgr to create an association between the partition, > the QOS and a group of users. In other words to place this group of users > in the same account – with access to the gpu partition and a specific QOS. > This does appear to work, however perhaps I don’t fully understand the > logic. So, when I submit using… > > > > sbatch -A gpuusers -p gpus slurm.serial -- that works as expected and the > correct QOS is selected > > > > sbatch -A gpuusers slurm.serial -- that fails since the cluster assumes > that the default partition is called batch (and submission to batch are not > allowed for users in “gpuusers”). So that does make sense, however I had > hoped that the command.. > > > > sacctmgr add user=djb1 account=gpuusers Partition=gpus > > > > would assign the “gpus” as the default partition for users in the > “gpuusers” group. However, that idea doesn’t appear to work.. Does anyone > please have any comments? Am I going about this in the wrong way? > > > > Best regards, > > David > > > Remember: everything happens at the Association level. That tuple of cluster, account, user and (optional) partition. An Association can have a default QOS, and users can belong to multiple associations differentiated by partition. So if you create an Association with Account=gpuusers and partition=gpus and DefaultQOS= (note: you can also give an association CPUlimits or TRES limits or...) and then add users to that association, the users can "use" that association by sending jobs to that partition. Does that make sense? I can re articulate more eloquently after my second coffee. cheers L. ------ The most dangerous phrase in the language is, "We've always done it this way." - Grace Hopper
