Generally, the add, modify, etc sacctmgr commands want an "user" or "account" entity, but can modify associations though this.
E.g., if user baduser should have GrpTRESmin of cpu=1000 set on partition special, use something like sacctmgr add user name=baduser partition=special account=testacct grptresmin=cpu=1000 if there is no association for that user, account and partition already, or sacctmgr modify user where user=baduser partition=special set grptresmin=cpu=1000 To place the restriction on an account instead, add/modify the account with a partition field. On Tue, Jan 15, 2019 at 11:33 AM Skouson, Gary <gb...@psu.edu> wrote: > Slurm accounting info is stored based on user, cluster, partition and > account. I'd like to be able to enforce limits for an account based on the > partition it's running in. > > Sadly, I'm not seeing how to use sacctmgr to change the partition as part > of the association. The add, modify and delete seem to only apply to user, > account and cluster entities. How do I add a partition to a particular > account association, and set GrpTRES for an association that includes a > partition. > > I know I can change the partition configuration in slurm.conf and use > AllowAccounts, but that doesn't change the usage limits on a partition for > a particular account. > > Maybe there's another way to work around this that I'm missing. > > I'd like to be able to use GrpTRESMins to limit overall cumulative account > usage. I also want to limit accounts to differing resources (GrpTRES) on > some partitions (for preemption/priority etc.) > > Thoughts? > > ----- > Gary Skouson > > > > > -- Tom Payerle DIT-ACIGS/Mid-Atlantic Crossroads paye...@umd.edu 5825 University Research Park (301) 405-6135 University of Maryland College Park, MD 20740-3831
