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
f you don’t specify anything. We deal
with this by using job_submit.lua to require users to request at least one type.
From: slurm-users on behalf of Kevin
Van Workum
Reply-To: Slurm User Community List
Date: Wednesday, June 20, 2018 at 1:15 PM
To: Slurm User Community List
Subject: Re: [slurm-
On Wed, Jun 20, 2018 at 10:29 AM, Vicker, Darby (JSC-EG311) <
darby.vicke...@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
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
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.vicke...@nasa.gov> wrote:
> Yes, Boolean constraints do work wit
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.
