Version 15.08 I believe may solve this problem, as it allows you to map a QOS' limits to a partition. That version is still in development I believe. I've tested that MaxJobs and other limits set in a QOS do get applied to a partition in 15.08pre5. If this kind of feature is important then you may want to focus your testing on the pre-releases of 15.08.
In production we are on 14.03 and map a list of QOS to each account. Then each partition has AllowQOS set to a specific QOS that corresponds to the limits we want to enforce on that partition. We also use the Lua job submit plugin to set a QOS for every job as we don't enforce the setting of a QOS by a user since some of our supported users (like OSG & CMS) don't have a means to specify a QOS. - Trey ============================= Trey Dockendorf Systems Analyst I Texas A&M University Academy for Advanced Telecommunications and Learning Technologies Phone: (979)458-2396 Email: [email protected] Jabber: [email protected] On Fri, Jul 31, 2015 at 1:12 PM, Cooper, Trevor <[email protected]> wrote: > > Derek, > > Look at the docs[1] for QOS. > > You have many controls there that can be attached to associations in > various ways. > > -- Trevor > > [1] - http://slurm.schedmd.com/qos.html > > > On Jul 31, 2015, at 10:10 AM, Derek Yarnell <[email protected]> > wrote: > > > > > > Hi, > > > > We are in the process of migrating from a Torque/Maui setup where we > > have used a max user run limit on a queue. We have been trying to map > > this into Slurm and maybe we are missing something but I can't seem to > > apply this at a global partition level. > > > > We see we can do this by creating a association with MaxJobs applied to > > the tuple of cluster, user, account, partition. Is this the only option > > we have? Creating these associations when new users are added (or > > removing them) will be a much more complicated process. > > > > Thanks, > > derek > > > > -- > > Derek T. Yarnell > > University of Maryland > > Institute for Advanced Computer Studies >
