Hi, Uwe Sauter <[email protected]> writes:
> Hi, > > accounts are structured in a tree, where every branch inherites the > limits from its parent. The leafs of such a branch then would be users. > You can then change the limit of a branch account without having to edit > every of your 300 user accounts. I have set things up such that my associations and not my accounts form a tree and this is perhaps where my problems lies. If I understand correctly, if I had organised the accounts in a tree, I would be able to create an association between the root account and a partition. Via inheritance this would automatically provide a corresponding association for each user. Looks like I might have some rearranging to do. Thanks for the clarification, Loris > A user may then also be connected to several branches, this is the point > where the tree analogy fails to apply. > > Regards, > > Uwe > > Am 14.01.2015 um 14:47 schrieb Loris Bennett: >> >> Hi, >> >> Uwe Sauter <[email protected]> >> writes: >> >>> Hi, >>> >>> an association is the combination of >>> >>> * QoS >>> * partition >>> * account >>> * cluster >> >> If I understand correctly, an association actually seems to be a >> combination of user (rather than QoS), cluster, partition, and account, >> with each association potentially supporting multiple QoS. >> >>> With that in mind you can restrict jobs per user on a partition level, >>> you just have to add the partition to the association rules. >> >> OK, so I would just set MaxJobs on all associations which contain the >> test partition. >> >> Currently I have one association per user with my 'main' partition as >> the default partition. So for each user I would have to set up a new >> association with the 'test' partition. As I have around 300 users, I'll >> have to set up 300 new associations. And if I want to change the limit >> at some point, I'll have to modify all 300 associations. This strikes >> me as a little unwieldy. >> >> It seems to me that it would be handy to be able to limit the number of >> jobs per user for a partition. But perhaps I only think this, because >> using a partition for a test queue is the wrong way to go about it. >> >> How do others set up such test queues? >> >> Cheers, >> >> Loris >> >>> >>> Regards, >>> >>> Uwe >>> >>> >>> >>> Am 14.01.2015 um 11:22 schrieb Loris Bennett: >>>> >>>> Hi Uwe, >>>> >>>> Uwe Sauter <[email protected]> >>>> writes: >>>> >>>>> Hi, >>>>> >>>>> have a look into Slurm accounting/QoS. There are options to limit jobs >>>>> per user, jobs per group, etc. pp. >>>>> >>>>> http://slurm.schedmd.com/accounting.html >>>>> http://slurm.schedmd.com/qos.html >>>> >>>> I saw that a QOS can restrict the number of jobs per user, but how can I >>>> force the jobs submitted to a given partition to use a specific QOS? >>>> >>>> Cheers, >>>> >>>> Loris >>>> >>>>> Regards, >>>>> >>>>> Uwe >>>>> >>>>> >>>>> >>>>> Am 14.01.2015 um 10:14 schrieb Loris Bennett: >>>>>> >>>>>> Hi, >>>>>> >>>>>> I have a test partition in which I would like to be able to restrict the >>>>>> maximum number of jobs a user may have running concurrently. >>>>>> >>>>>> Is this possible? >>>>>> >>>>>> Cheers, >>>>>> >>>>>> Loris >>>>>> >>>>> >>>> >>> >> -- This signature is currently under construction.
