[slurm-users] Multiple job constraints

[Kevin Van Workum]

On Wed, Jun 20, 2018 at 10:29 AM, Vicker, Darby (JSC-EG311) <
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.
>

Can you also request a different job layout for each processor type? As in
the example I gave?


> On Jun 20, 2018, at 9:15 AM, Kevin Van Workum <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
>
>


-- 
Kevin Van Workum, PhD
Sabalcore Computing Inc.
"Where Data Becomes Discovery"
http://www.sabalcore.com
877-492-8027 ext. 1011

-- 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20180620/0ac82cb5/attachment.html>