<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>The symlink method for slurm.conf is what we do as well. We have
a NFS mount from the slurm master that we host the slurm.conf on
that we then symlink slurm.conf to that NFS share.</p>
<p><br>
</p>
<p>-Paul Edmon-</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 1/4/2023 1:53 PM, Brian Andrus
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:01aeabdc-3f11-428f-ab62-c1b89ff78ada@gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>One of the simple ways I have dealt with different configs is
to symlink /etc/slurm/slurm.conf to the appropriate file (eg:
slurm-dev.conf and slurm-prod.conf)</p>
<p><br>
</p>
<p>In fact, I use the symlink for my dev and nothing (configless)
for prod. Then I can change a running node to/from dev/prod by
merely creating/deleting the symlink and restarting slurmd.</p>
<p><br>
</p>
<p>Just an option that may work for you.<br>
<br>
I also use separate repos for prod/dev when I am working on
packages/testing. I rather prefer that separation so I don't
have someone accidentally update to a package that is not
production-ready.</p>
<p><br>
</p>
<p>Brian Andrus<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 1/4/2023 9:22 AM, Groner, Rob
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:BL0PR02MB4499AE8CA4B6BDE4250E83A280F59@BL0PR02MB4499.namprd02.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<style type="text/css" style="display:none;">P {margin-top:0;margin-bottom:0;}</style>
<div class="elementToProof"><span style="font-family: Calibri,
Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0,
0, 0); background-color: rgb(255, 255, 255);">We currently
have a test cluster and a production cluster, all on the
same network. We try things on the test cluster, and then
we gather those changes and make a change to the production
cluster. We're doing that through two different repos, but
we'd like to have a single repo to make the transition from
testing configs to publishing them more seamless. The
problem is, of course, that the test cluster and production
clusters have different cluster names, as well as different
nodes within them.</span></div>
<div class="elementToProof"><span style="font-family: Calibri,
Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0,
0, 0); background-color: rgb(255, 255, 255);"><br>
</span></div>
<div class="elementToProof"><span style="font-family: Calibri,
Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0,
0, 0); background-color: rgb(255, 255, 255);">Using the
include directive, I can pull all of the NodeName lines out
of slurm.conf and put them into %c-nodes.conf files, one for
production, one for test. That still leaves me with two
problems:</span></div>
<div class="elementToProof">
<ul>
<li style="font-size: 12pt; font-family: Calibri, Arial,
Helvetica, sans-serif; color: rgb(0, 0, 0);
background-color: rgb(255, 255, 255);"> <span
style="font-family: Calibri, Arial, Helvetica,
sans-serif; font-size: 12pt; color: rgb(0, 0, 0);
background-color: rgb(255, 255, 255);">The clustername
itself will still be a problem. I WANT the same
slurm.conf file between test and production...but the
clustername line will be different for them both. Can I
use an env var in that cluster name, because on
production there could be a different env var value than
on test?</span></li>
<li style="font-size: 12pt; font-family: Calibri, Arial,
Helvetica, sans-serif; color: rgb(0, 0, 0);
background-color: rgb(255, 255, 255);"> <span
style="font-family: Calibri, Arial, Helvetica,
sans-serif; font-size: 12pt; color: rgb(0, 0, 0);
background-color: rgb(255, 255, 255);">The gres.conf
file. I tried using the same "include" trick that works
on slurm.conf, but it failed because it did not know
what the "ClusterName" was. I think that means that
either it doesn't work for anything other than
slurm.conf, or that the clustername will have to be
defined in gres.conf as well?</span></li>
</ul>
<div><span style="font-family: Calibri, Arial, Helvetica,
sans-serif; font-size: 12pt; color: rgb(0, 0, 0);
background-color: rgb(255, 255, 255);">Any other
suggestions of how to keep our slurm files in a single
source control repo, but still have the flexibility to
have them run elegantly on either test or production
systems?</span></div>
<div><span style="font-family: Calibri, Arial, Helvetica,
sans-serif; font-size: 12pt; color: rgb(0, 0, 0);
background-color: rgb(255, 255, 255);"><br>
</span></div>
<div><span style="font-family: Calibri, Arial, Helvetica,
sans-serif; font-size: 12pt; color: rgb(0, 0, 0);
background-color: rgb(255, 255, 255);">Thanks.</span></div>
<div><span style="font-family: Calibri, Arial, Helvetica,
sans-serif; font-size: 12pt; color: rgb(0, 0, 0);
background-color: rgb(255, 255, 255);"><br>
</span></div>
</div>
</blockquote>
</blockquote>
</body>
</html>