We aren't using QOS values right now, just basic node limits on accounts, but I'm guessing they shouldn't be hard to adapt. I'd certainly appreciate it if you can send them along.
Thanks! Jared On Fri, Mar 27, 2015 at 6:00 AM, Bill Wichser <[email protected]> wrote: > > Jared, > > > I have a few script to show QOS values and what is running under each. > Users can use this to see how many resources are left. Somthing like this: > > # qos > Name Priority GrpNodes GrpCPUs MaxCPUsPU MaxJobsPU MaxNodesPU > MaxSubmit > ---------- ---------- -------- -------- --------- --------- ---------- > --------- > vlong 3200 800 300 12 2000 > medium 3000 900 240 100 2000 > short 4000 240 2000 > test 6000 2 200 > > QOS: vlong 495 procs 26 jobs > ... > > If interested I can forward along directly. > > Bill > > > > On 03/27/2015 12:04 AM, Jared Casper wrote: > >> Is there a way to get a summary of resources a particular account or >> association has left before it runs into a limit? For example, if >> account TeamA has set GrpNodes=10 and is currently using 8 of them, is >> there a way to see that they only have 2 left? >> >> I haven't come up with anything looking through the docs or from >> Google. Closest I could come was squeue -A account and count things up, >> but that's pretty clunky. Apologies if I've missed something obvious or >> have a misunderstanding of how things work. Any pointers would be >> appreciated. >> >> Thanks! >> >> Jared >> >
