feature, then release it.
>>
>>
>>
>> sbatch -p normal -C branch-B -D /data -H test.sh
>>
>> scontrol release
>>
>>
>>
>> This should place an unallocated job into the queue with a reason of
>> BadConstraints.
>>
>>
unity List
Subject: Re: [slurm-users] How to queue jobs based on non-existent features
I have not had a chance to look at you rcode, but find it intriguing, although
I am not sure about use cases. Do you do anything to lock out other jobs from
the affected node?
E.g., you submit a job with uns
;
>
> scontrol update NodeName=c1 AvailableFeatures=platform-test,branch-B
> ActiveFeatures=platform-test,branch-B
>
>
>
>
>
> Hopefully that little demo works for you. We have been running with this
> change in a small test cluster for about 2 weeks and so far no kn
(408) 230-8531
From: slurm-users on behalf of Alex
Chekholko
Reply-To: Slurm User Community List
Date: Friday, July 10, 2020 at 11:37 AM
To: Slurm User Community List
Subject: Re: [slurm-users] How to queue jobs based on non-existent features
Hey Raj,
To me this all sounds, at a high level,
| *m. +1 (408) 230-8531
>
>
>
> *From: *slurm-users on behalf of
> Paddy Doyle
> *Reply-To: *Slurm User Community List
> *Date: *Friday, July 10, 2020 at 10:31 AM
> *To: *Slurm User Community List
> *Subject: *Re: [slurm-users] How to queue jobs based on non-exist
: [slurm-users] How to queue jobs based on non-existent features
Hi Raj,
It sounds like you might be coming from a CI/CD pipeline setup, but just in
case you're not, would you consider something like Jenkins or Gitlab CI
instead of Slurm?
The users could create multi-stage pipelines, with the &
Hi Raj,
It sounds like you might be coming from a CI/CD pipeline setup, but just in
case you're not, would you consider something like Jenkins or Gitlab CI
instead of Slurm?
The users could create multi-stage pipelines, with the 'build' stage
installing the required software version, and then mul
ubject: Re: [slurm-users] How to queue jobs based on non-existent features
Another option would be to use the license feature and just set licenses to 0
when they aren't available.
-Paul Edmon-
On 7/10/2020 12:42 PM, Raj Sahae wrote:
Hi Brian and Paul,
You both sent me suggestions about u
Another option would be to use the license feature and just set licenses
to 0 when they aren't available.
-Paul Edmon-
On 7/10/2020 12:42 PM, Raj Sahae wrote:
Hi Brian and Paul,
You both sent me suggestions about using an offline dummy node with
all features set. Thanks for your ideas but t
Hi Brian and Paul,
You both sent me suggestions about using an offline dummy node with all
features set. Thanks for your ideas but this won’t work for me as it’s not
practical. We want to allow users to queue for all supported software versions
and that easily numbers in the thousands or tens o
You could set up an dummy node that has the features that are not active
but not allow jobs to schedule to that node by setting it to DOWN. That
would be a hacky way of accomplishing this.
-Paul Edmon-
On 7/9/2020 7:15 PM, Raj Sahae wrote:
Hi all,
My apologies if this is sent twice. The fi
11 matches
Mail list logo
