[slurm-users] Multiple job constraints

[John DeSantis]

Hello,

> You will get whatever cores Slurm can find which will be an
> assortment of hosts.

We use SLURM's topology features to not only keep disparate hardware
separate, but to also present a "single" default partition to our users.

The benefits are that users do not need to specify a CPU model unless
they need to, and users do not need explicitly request a partition.
For the majority of our non contributing users, this works quite well
for them.

Of course, the immediate negatives to this type of configuration are
that users will ask why their jobs aren't running, despite "idle"
resources, and maintenance of the topology.conf file.

John DeSantis 

On Wed, 20 Jun 2018 12:16:59 -0400
Paul Edmon <pedmon at cfa.harvard.edu> wrote:

> You will get whatever cores Slurm can find which will be an
> assortment of hosts.
> 
> -Paul Edmon-
> 
> 
> On 6/20/2018 11:01 AM, Nathan Harper wrote:
> > sorry to hijack, but we've been considering a similar
> > configuration, but I was wondering what happens if you don't set a
> > processor type? Will it scatter across types?
> >
> > On Wed, 20 Jun 2018 at 15:30, Vicker, Darby (JSC-EG311) 
> > <darby.vicker-1 at nasa.gov <mailto:darby.vicker-1 at nasa.gov>> wrote:
> >
> >     Yes, Boolean constraints do work with minimal configuration. We
> >     run mostly MPI jobs on our cluster and want our jobs to run on a
> >     single processor type. We assign the processor types as a
> > feature and then the sbatch requests —constraint=[wes|san|has|bro]
> > to run on whatever processor type is free. Works great.
> >
> >     On Jun 20, 2018, at 9:15 AM, Kevin Van Workum
> > <vanw at sabalcore.com <mailto:vanw at sabalcore.com>> wrote:
> >  
> >>     Hello,
> >>
> >>     We currently use an in-house customized version of Torque and
> >> an in-house scheduler. I'm now considering Slurm instead. We have a
> >>     feature in our scheduler where by users can submit jobs with
> >>     multiple-prioritized job specifications (constraints). For
> >>     example, a job can request 4 nodes of type X with 16 cores per
> >>     node OR 2 nodes of type Y with 20 cores per node. The scheduler
> >>     will prefer the first job spec but may use the second job spec
> >> if the first can not be satisfied within certain QoS limits.
> >>
> >>     I saw some ability to use boolean constraints in the docs for
> >>     Slurm, but would like to know if this behavior is possible out
> >> of the box.
> >>
> >>     Thanks,
> >>
> >>     Kevin
> >>
> >>     -- 
> >>     Kevin Van Workum, PhD
> >>     Sabalcore Computing Inc.
> >>     "Where Data Becomes Discovery"
> >>     http://www.sabalcore.com
> >>     877-492-8027 ext. 1011
> >>  
> >
> >
> > -- 
> > *NathanHarper* // IT Systems Lead
> >
> > <https://cfms.org.uk/news-events/events/2018/july/farnborough-international-airshow-2018/>
> >
> > *e: *nathan.harper at cfms.org.uk <mailto:nathan.harper at cfms.org.uk> 
> > *t*: 0117 906 1104 *m*:0787 551 0891 *w: *www.cfms.org.uk 
> > <http://www.cfms.org.uk/>
> > CFMS Services Ltd // Bristol & Bath Science Park // Dirac
> > Crescent // Emersons Green // Bristol // BS16 7FR
> > CFMS Services Ltd is registered in England and Wales No 05742022 -
> > a subsidiary of CFMS Ltd
> > CFMS Services Ltd registered office // 43 Queens Square //
> > Bristol // BS1 4QP  
>