Is this a valid way to do what I'm thinking? Create two queues with the same nodes in it, where one has a different sequence of machines than the others. If all of the hosts have slots defined as a consumable resource, they shouldn't stomp over each other.
The goal I'm trying to reach is: Several departments are contributing systems to a large grid. They've agreed to share systems for processing, but each department wants to use its own stuff before moving onto the other groups systems. I'd imagine at some point I'm going to need to get the functional shares going, but for right now, I think if they launch jobs, each department wants to start on their own stuff first (best machines, worst machines, other group machines....) > Subject: Re: [gridengine users] host sequence number per user > From: [email protected] > Date: Tue, 27 Jan 2015 17:14:38 +0100 > CC: [email protected] > To: [email protected] > > Am 27.01.2015 um 16:45 schrieb Kevin Taylor <[email protected]>: > > > > I don't know if this is possible or not, but I've got a test queue set up > > with 5 hosts in it to test sequence number sorting of jobs. > > > > In the queue config, I have: > > > > seq_no 0,[hostA=110], \ > > [hostB=105], \ > > [hostC=105], \ > > [hostD=105], \ > > [hostE=105] > > > > and when submitting a job, hostA is the last one to get stuff on it, which > > is fine. > > > > Can I define this further, to say that only userA can get this type of > > sorting, everyone else will get normal load based sorting? > > No, but he can use a soft request to avoid nodeA if possible: `qsub -soft -l > 'h=!nodeA' ...` > > -- Reuti > > > > This doesn't work, but something like [userA@hostA=110], > > [userA@hostB=105], etc...? > > > > > > _______________________________________________ > > users mailing list > > [email protected] > > https://gridengine.org/mailman/listinfo/users >
_______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
