Hello Slurm folks, I would like to take advantage of the scheduling priorities and limits associated with QOS values, without having to explicitly add every single user to to the accounting database. Is this possible? I don't need the other accounting attributes per se, like bookkeeping against various bank accounts, etc. The limits, priorities, and pre-emption settings available via QOS entries are enough for our needs. Can QOS be done without explicitly identifying whole associations? I'm even prepared to not use AccountingStorageEnforce, so long as I'd be able to set a default QOS for users that don't supply a QOS value when they submit jobs.
I realize that enforcing explicit user permissions serves as a form of access control many administrators would want, but in our use case it wouldn't be necessary. Or if this is unavoidable, can Unix groups be used in lieu of explicitly adding individual users? Thank you, V. Ram -- http://www.fastmail.fm - Same, same, but different...
