<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>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).</p>
<p>-Paul Edmon-<br>
</p>
<div class="moz-cite-prefix">On 12/4/2020 3:39 PM, Jason Simms
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAP7JYwfmsAnwzXHBgdbi_SaB_ivgcKXcDL3y3kJ1h2sZD2tGsg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Dear Ole,
<div><br>
</div>
<div>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 did
base it off of created RPMs. I've reached out to them to see
whether they used a modified slurm.spec file, which I suspect
they did, given that Slurm is installed in /opt/slurm (which
seems like a modified prefix, if nothing else).</div>
<div><br>
</div>
<div>The fundamental question is, if I am performing a yum
update, and I don't adjust any settings in the
default slurm.spec file, will it upgrade everything properly
where they currently "live," or will it install new files in
standard locations? It's a question of whether "yum update" is
"smart enough" to figure out what was done before and go with
that, or whether I must specify all relevant information in
the slurm.spec file each time? Based on Paul's reply, it seems
we do need an updated slurm.spec file that reflects our
environment, each time we upgrade.</div>
<div><br>
</div>
<div>Jason</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Dec 4, 2020 at 3:13 PM
Ole Holm Nielsen <<a
href="mailto:Ole.H.Nielsen@fysik.dtu.dk"
moz-do-not-send="true">Ole.H.Nielsen@fysik.dtu.dk</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi
Jason,<br>
<br>
Slurm upgrading should be pretty simple, IMHO. I've been
through this <br>
multiple times, and my Slurm Wiki has detailed upgrade
documentation:<br>
<a
href="https://wiki.fysik.dtu.dk/niflheim/Slurm_installation#upgrading-slurm"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://wiki.fysik.dtu.dk/niflheim/Slurm_installation#upgrading-slurm</a><br>
<br>
Building RPMs is described in this page as well:<br>
<a
href="https://wiki.fysik.dtu.dk/niflheim/Slurm_installation#build-slurm-rpms"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://wiki.fysik.dtu.dk/niflheim/Slurm_installation#build-slurm-rpms</a><br>
<br>
I hope this helps.<br>
<br>
/Ole<br>
<br>
<br>
On 04-12-2020 20:36, Jason Simms wrote:<br>
> Thank you for being such a helpful resource for All
Things Slurm; I <br>
> sincerely appreciate the helpful feedback. Right now, we
are running <br>
> 20.02 and considering upgrading to 20.11 during our next
maintenance <br>
> window in January. This will be the first time we have
upgraded Slurm, <br>
> so understandably we are somewhat nervous and have some
questions.<br>
> <br>
> I am able to download the source and build RPMs
successfully. What is <br>
> unclear to me is whether I have to adjust anything in the
slurm.spec <br>
> file or use a .rpmmacros file to control certain aspects
of the <br>
> installation. Since this would be an upgrade, rather than
a new install, <br>
> do I have to adjust, e.g., the --prefix value, and all
other settings <br>
> (X11 support, etc.)? Or, will a yum update "correctly"
put the files <br>
> where they are on my system, using settings from the
existing 20.02 version?<br>
> <br>
> We purchased the system from a vendor, and of course they
use custom <br>
> scripts to build and install Slurm, and those are
tailored for an <br>
> initial installation, not an upgrade. Their advice to us
was, don't <br>
> upgrade if you don't need to, which seems reasonable,
except that many <br>
> of you respond to initial requests for help by
recommending an upgrade. <br>
> And in any case, Slurm doesn't upgrade nicely from more
than two major <br>
> versions back, so I'm hesitant to go too long without
patching.<br>
> <br>
> I'm terribly sorry for my ignorance of all this. But I
really lament how <br>
> terrible most resources are about all this. They assume
that you have <br>
> built the RPMs already, without offering any real
guidance as to how to <br>
> adjust relevant options, or even whether that is a
requirement for an <br>
> upgrade vs. a fresh installation.<br>
> <br>
> Any guidance would be most welcome.<br>
<br>
<br>
<br>
</blockquote>
</div>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr" class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div
style="color:rgb(0,0,0);font-family:Helvetica;font-size:14px;margin:0px"><span
style="color:rgb(130,36,51)"><font
face="Century Gothic"><b>Jason L. Simms,
Ph.D., M.P.H.</b></font></span></div>
<div
style="color:rgb(0,0,0);font-family:Helvetica;font-size:14px;margin:0px"><font
face="Century Gothic"><span>Manager of
Research and High-Performance Computing</span></font></div>
<div
style="color:rgb(0,0,0);font-family:Helvetica;font-size:14px;margin:0px"><font
face="Century Gothic"><span>XSEDE Campus
Champion<br>
</span><span style="color:gray">Lafayette
College<br>
Information Technology Services<br>
710 Sullivan Rd | Easton, PA 18042<br>
Office: 112 Skillman Library<br>
p: (610) 330-5632</span></font></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</body>
</html>