We went through a similar migration in 2014 and also have the complication of supporting OSG which at this time uses the qsub wrapper and thus can't specify a QOS. Our solution was to not require a QOS, but instead assign a QOS based on the requested partition using the Lua job submit plugin.
- 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 Thu, Jan 28, 2016 at 3:46 PM, Timothy Gray <[email protected]> wrote: > Hi, > > I'm working on moving our clusters from torque/maui to slurm and we have > decided to use QOS to replace the notion of queues that we had in PBS; > however, we are unsure about the best way to reveal available QOS to users > of the cluster. We are trying to be as user friendly as possible since we > have many different skill levels amongst our user base, so we'd prefer to > have a command that will show a user just the relevant information (things > we've set) and allow them to view other options if they want to, but by > default sacctmgr shows everything which is very unreadable. I was thinking > about writing an alias or a wrapper script called showqos or sqos that > would run sacctmgr with the format options we provide; however I was > wondering if anyone has dealt with this already and can share how they deal > with this issue at their site? > > On a related note, I noticed that sacct has an environment variable called > SACCT_FORMAT which sets the default formatting string which seems very > useful; does anyone know if there's a good reason why there aren't more of > these variables for sstat, squeue, sinfo, and the various sacct show/list > queries? Is this just on the bottom of a to do list? If so I may be willing > to contribute to get this functionality if it just needs doing. > > Thanks, > Tim Gray > > >
