Hey Mark, > -----Original Message----- > From: [email protected] [mailto:owner-slurm- > [email protected]] On Behalf Of Mark Nelson > Sent: Monday, April 11, 2011 7:12 PM > To: [email protected] > Subject: [slurm-dev] Question about accounting: setting quotas on accounts > > Hi there, > > At the moment we are using SLURM with Moab (for scheduling) and Gold > (for accounting), but I'm having a look at whether we can move to an > all-SLURM setup to do the same thing. > > In order to play/learn, I've got a test system set up with SLURM > emulating a Blue Gene /P and so far I've set up SLURM's accounting to > add a few test users and I've associated them with a handful of > accounts. > > Using this fairly simple setup I can enforce user's jobs to be run > against only accounts that they're associated with. The next thing I > need to do (that I'm currently stuck on) is work out how to assign > quotas to these accounts (a number of Core-Hours if you like) that > decrease by an appropriate amount every time a job is run. The > documentation often refers to accounts as "bank accounts" which makes > me think that this can be done and I just haven't work out how to yet.
What documentation are you looking at is one question. You can probably look at https://computing.llnl.gov/linux/slurm/accounting.html to get a good idea how to do what you want. Each association and QOS have a GrpCPUMin limit. If you decide you don't want to do fairshare (the preferred way of doing things) you can do the hard limit stuff using the this limit along with the priority/multifactor plugin explained here https://computing.llnl.gov/linux/slurm/priority_multifactor.html. Look primarily at the PriorityDecayHalfLife and PriorityUsageResetPeriod options for the slurm.conf. Let us know if you have any other questions. Danny > > Any help would be greatly appreciated! > > Many thanks! > Mark
