[Moabusers] mapping node features to a class

[Douglas Wightman]

Unfortunately there is no "|" feature available for node features.  We
have code that does this for jobs but it would have to be extended to
reservations.  

- Douglas

On Mon, 2007-05-14 at 16:33 -0600, Lloyd Brown wrote:
> That looks like it will work.  Just one additional question, though.  
> Some of the SRCFG and CLASSCFG parameters allow you to specify comma 
> separated (meaning require all of these), and pipe ("|") separated 
> (meaning require one of these) in lists.  Does nodefeatures do this?  
> You see, I oversimplified a little in my earlier description: what I 
> actually have is a set of four mutually-exclusive attributes, (featureA, 
> featureB, featureC, and featureD), and I want to add an additional one 
> as featureE.  I don't care which set of nodes a non-featureE job goes 
> to, as long as it's not featureE, but a job that requests featureE must 
> get featureE.
> 
> On our staging area, this did work:
> 
> > NODETOJOBATTRMAP        featureE
> >
> > SRCFG[batch_sr_a]       CLASSLIST=batch HOSTLIST=ALL    
> > NODEFEATURES=featureA
> > SRCFG[batch_sr_b]       CLASSLIST=batch HOSTLIST=ALL    
> > NODEFEATURES=featureB
> > SRCFG[batch_sr_c]       CLASSLIST=batch HOSTLIST=ALL    
> > NODEFEATURES=featureC
> > SRCFG[batch_sr_c]       CLASSLIST=batch HOSTLIST=ALL    
> > NODEFEATURES=featureD
> > SRCFG[test_sr]          CLASSLIST=test  HOSTLIST=ALL    
> > NODEFEATURES=featureE   JOBATTRLIST=featureE
> 
> Is there any way I can combine all those "batch_sr_?" SRCFGs into one?  
> I tried both of the following:
> 
> > NODEFEATURES=featureA,featureB,featureC,featureD
> 
> and
> > NODEFEATURES=featureA|featureB|featureC|featureD 
> 
> but neither worked.  The log looked like neither one could create the 
> combined standing reservation, the first time because no node had all 
> the features listed, and the second time because no node had the feature 
> "featureA|featureB|featureC|featureD".  I'm just speculating here, though.
> 
> Thanks,
> Lloyd
> 
> 
> 
> 
> Dave Jackson wrote:
> > Lloyd,
> >
> >   You could use a standing reservation, ie
> >
> > SRCFG[A] classlist=classA hostlist=ALL nodefeatures=featureA
> > SRCFG[B] classlist=classB hostlist=ALL nodefeatures=featureB
> >
> >   Please let us know if this will work for you.
> >
> > Dave
> >
> > On Mon, 2007-05-14 at 15:52 -0600, Lloyd Brown wrote:
> >   
> >> Hey, all.  In Moab, is there an easy way to map nodes with a specific 
> >> feature (like specified in Torque) into a class?  If, for example, all 
> >> my nodes have either "featureA" or "featureB", but never both, and I 
> >> want all the featureA nodes to be in one class/queue, and all the 
> >> featureB nodes to be in another class/queue, can I do that without using 
> >> the hostlist?  We would have a lot of hosts to put into the hostlist if 
> >> we had to list them all out; pattern matching would even be a lot of 
> >> trouble.
> >>
> >> Basically the situation is this:  we have two nodes out of a total of 
> >> 600+ that we are using to evaluate new hardware.  We want to allow our 
> >> users to request that a job use these two nodes, but if they don't 
> >> request it, the job shouldn't run on those two nodes, only on the other 
> >> 600 or so.
> >>
> >> Any suggestions or alternative approaches would be helpful.
> >>
> >>
> >> Thanks,
> >> Lloyd Brown
> >> _______________________________________________
> >> moabusers mailing list
> >> moabusers at supercluster.org
> >> http://www.supercluster.org/mailman/listinfo/moabusers
> >>     
> >
> >
> >   
> 
> _______________________________________________
> moabusers mailing list
> moabusers at supercluster.org
> http://www.supercluster.org/mailman/listinfo/moabusers