On 5 Jul 2011, at 16:44, Michael Di Domenico wrote: > On Tue, Jul 5, 2011 at 9:49 AM, Danny Auble <[email protected]> wrote: >>> >>> I expect most people preload the tables because they are using >>> accounting for levee against a 'gold' system, whereas all of our users >>> are basically the same and we only want the fair-share scheduling part >>> not the 'gold' tracking part >> >> I am not sure if your assessment is correct or not. In your case where >> every user is on a flat tree I could see how this would be a nice feature >> though. You would have to live with fat finger issues though, but if you >> didn't care which account people ran in then perhaps that isn't a big deal. >> >> Currently there are no plans to add this, but we can put in on our wishlist >> of things to do. > > I worked around it currently by searching the database every so often > for the unassociated user accounts, when found we insert the user into > the db with sacct >
If you did care about the accounting and correct associations then you should probably enforce it and pre-create the associations before users are allowed to run, I guess this is a workflow thing. > I noticed the jobs still run even with the lower priority behind > everyone else, so there's no real detriment. I'd be interested to > find out how people are handling fair-share with slurm elsewhere. > At our site we are enforcing limits and associations, with a tree like this... root - project1 - user1 - user2 - user3 - project2 - user3 - user4 - user5 ... and so on, we simply just have a fairshare of 100 for the root account then a value of 1 for everyone and every account, this appears to work at our site quite well (for now), we did however had to be careful to tweak our priority weights. Users without accounts simply cannot run at our site, and when users can't run we tend to know pretty quickly and it gets resolved. Also we aren't using gold for our 'banking' needs, instead we cooked up a bunch of scripts and a workflow for doing it completely with slurm. We just turned it on for the users at our site, so we will see how good or bad our ideas are in a week or two's time. Regards, Jimmy Tang -- Trinity Centre for High Performance Computing, Lloyd Building, Trinity College Dublin, Dublin 2, Ireland. http://www.tchpc.tcd.ie/
