Hi Jason,
Paul is right, so I guess you need to make a decision: 1) Keep your
vendor's customized Slurm setup going forward with future upgrades, or
2) alternatively remove the vendor's Slurm installation and install
standard RPMs as offered by SchedMD's tar-balls.
If you choose 2) you need
It won't figure it out automatically no. You will need to ensure that
the spec is installing to the same locale as your vendor installed it if
they didn't put it in the default location (/opt isn't the default).
-Paul Edmon-
On 12/4/2020 3:39 PM, Jason Simms wrote:
Dear Ole,
Thanks. I've re
Dear Ole,
Thanks. I've read through your docs many times. The relevant upgrade
section begins with the assumption that you have properly configured RPMs,
so all I'm trying to do is ensure I get to that point. As I noted, a vendor
installed Slurm initially through a proprietary script, though they
Hi Jason,
Slurm upgrading should be pretty simple, IMHO. I've been through this
multiple times, and my Slurm Wiki has detailed upgrade documentation:
https://wiki.fysik.dtu.dk/niflheim/Slurm_installation#upgrading-slurm
Building RPMs is described in this page as well:
https://wiki.fysik.dtu.d
Usually the slurm.spec file provided doesn't change that much between
versions. What we do here is that we maintain a git repository of our
slurm.spec that we use with our modifications. Then each time Slurm is
released we compare ours against what is provided, and simply modify the
provided o
Hello all,
Thank you for being such a helpful resource for All Things Slurm; I
sincerely appreciate the helpful feedback. Right now, we are running 20.02
and considering upgrading to 20.11 during our next maintenance window in
January. This will be the first time we have upgraded Slurm, so
underst
