2014-02-14 4:50 GMT+01:00 Christopher Samuel <[email protected]>: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi there, > > I'm looking at tweaking our Slurm config to get it to handle our > workload better and it seems to be doing pretty well, but there's one > thing missing that I'd like to get going. > > When we had Torque and Moab (and I used to do the same with Maui at > $JOB--) we had a standing reservation that would reserve a node on the > cluster for jobs of less than 15 minutes between 8am and 8pm for testing. > > Basically any job that fitted the criteria would get attracted into > the reservation and run there in preference to other nodes and those > that didn't would be kept off it so people could get quick turnarounds. > > We can't use partitions for this as the user shouldn't need to know > about this (and has never needed to know in the past, so it'd be a > regression from their point of view) plus we'd need to have scripts to > shuffle short jobs between partitions at 8am and 8pm and bring that > partition up/down as appropriate. > > My reading of the manual page isn't encouraging, but I could just be > not seeing the wood for the trees. Any ideas please? >
You can create a reservation for the root ( I mean a parent of all ) account and write your job submit plugin to add this reservation to jobs shorter than 15minutes and remove (if setted by user) this reservation for jobs longer than 15 minutes. cheers, marcin
