be able to queue versions that are not yet installed anywhere in the cluster.
Does that make sense?
Raj Sahae | m. +1 (408) 230-8531
From: slurm-users on behalf of "Thomas
M. Payerle"
Reply-To: Slurm User Community List
Date: Thursday, August 13, 2020 at 6:21 PM
To: Slurm User Comm
heduled to
run.
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 known issues.
Thanks,
Raj Sahae | m. +1
reasonably well.
Now I’m trying to move beyond feature parity and am having trouble doing so.
Thanks,
Raj Sahae | 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
Interesting, I had not read the Licenses feature docs but I will look through
that, thanks.
Raj Sahae | m. +1 (408) 230-8531
From: slurm-users on behalf of Paul
Edmon
Reply-To: Slurm User Community List
Date: Friday, July 10, 2020 at 10:09 AM
To: "slurm-users@lists.schedmd.com"
S
of thousands (every branch,
every commit). If I could make this solution work, I would simply set the
Available features for all nodes but this feels like it won’t scale well, or is
an improper use of the Feature capability.
Thanks,
Raj Sahae | m. +1 (408) 230-8531
From: Raj Sahae
Date
to be
AvailableFeatures, as our branch ecosystem is quite large and the maintenance
of that approach would not scale well.
Thanks,
Raj Sahae | Manager, Software QA
3500 Deer Creek Rd, Palo Alto, CA 94304
m. +1 (408) 230-8531 |
rsa...@tesla.commailto:rsa...@tesla.com%3E>
[cid:image001.png@01D6560C.
