Re: [Moabusers] Node priorities

Hi Steve,

On another cluster with Maui we are doing something similar by using
different queues. I think the logic for MOAB will be the same:

1. We assign nodes to different queues at Torque level (via node
features).
2. We use something like this in maui.cfg:

QOSWEIGHT 1
###requeue low priority jobs 
PREEMPTPOLICY  REQUEUE

SYSCFG QLIST=idle,private
###idle###############
QOSCFG[idle] PRIORITY=-1
QOSCFG[idle] QFLAGS=PREEMPTEE 
###private###############
QOSCFG[private] PRIORITY=1
QOSCFG[private] QFLAGS=PREEMPTOR,RESTARTPREEMPT
QOSCFG[private] FSTARGET=17.02

CLASSCFG[idle] QDEF=idle NODEFEATURE=idle
CLASSCFG[private] QDEF=private NODEFEATURE=private



On Mon, 18 Apr 2011 16:15:23 -0400
Steve Crusan wrote:

> Hi all,
> 
> 
>     I was wondering how other admins deal with the following:
> 
> In our cluster, we have a mix of shared and privately funded
> hardware. I'm in the process of setting up a QoS for users that will
> allow them to use the private hardware, provided they are okay with
> their job being preempted. That all works fine.
> 
> What I would like to do is set node priorities, meaning that I'd
> rather have jobs run on a certain set of hardware first, and then go
> down the line, ex:
> 
> Highmem nodes have a 50 priority
> Shared nodes have a 25 priority, etc.
> 
> This is all possible via the:
> NODEALLOCATIONPOLICY    PRIORITY
> NODECFG[bh001]          PRIORITY=100
> NODECFG[private-01]     PRIORITY=10
> ...
> 
> The problem I have is that when one has hundreds of nodes, I don't
> really want to put them all in the moab.cfg file.
> 
> Does anyone do anything similar to this, that possibly uses a better
> method than what I'm doing now?
> 
> 


_______________________________________________
moabusers mailing list
[EMAIL PROTECTED]
http://www.supercluster.org/mailman/listinfo/moabusers