<div dir="ltr"><div dir="ltr"><div dir="ltr"><div><br></div><div>There's one thing that no one seems to have mentioned - I think you will need to list it as an AllocNode in the Partition that you want it to be able to allocate jobs to.</div><div><br></div><div><a href="https://slurm.schedmd.com/slurm.conf.html#OPT_AllocNodes">https://slurm.schedmd.com/slurm.conf.html#OPT_AllocNodes</a></div><div><br></div><div>Eg in my conf we have one partition that looks like</div><div><br></div><div>PartitionName=reserved Nodes=papr-res-compute[201-211] MaxTime=14-0 DefaultTime=0:40:0 State=UP AllocNodes=vmpr-res-head-node,vmpr-res-cluster1<br></div><div><br></div><div>You will see that </div><div>vmpr-res-head-node <- our head node/cluster manager, only admins have access. Doesn't run jobs.<br></div><div>vmpr-res-cluster1 <- login node, for the users. Doesn't run jobs.</div><div><br></div><div>Cheers</div><div>L.<br></div><div><br></div></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Sat, 13 Oct 2018 at 04:05, Christopher Benjamin Coffey <<a href="mailto:Chris.Coffey@nau.edu">Chris.Coffey@nau.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">In addition, fwiw, this login node will have a second network connection of course for campus with firewall setup to only allow ssh (and other essential) from campus. Also you may consider having some script developed to prevent folks from abusing the login node instead of using slurm for their computations. We have a policy that allows for user processes to only consume 30 min of cpu time before they are killed. We have an exception list of course. Also, our login node has lots of devel packages to allow folks to compile software, etc. You may want to have a motd on the login node to announce changes, or offer tips. Also, the login node doesn't need to have the slurm service running, but needs the slurm s/w, current slurm.conf, and munge keys.<br>
<br>
Just some things off the top of my head.<br>
<br>
Best,<br>
Chris<br>
<br>
—<br>
Christopher Coffey<br>
High-Performance Computing<br>
Northern Arizona University<br>
928-523-1167<br>
<br>
<br>
On 10/12/18, 6:33 AM, "slurm-users on behalf of Michael Gutteridge" <<a href="mailto:slurm-users-bounces@lists.schedmd.com" target="_blank">slurm-users-bounces@lists.schedmd.com</a> on behalf of <a href="mailto:michael.gutteridge@gmail.com" target="_blank">michael.gutteridge@gmail.com</a>> wrote:<br>
<br>
I'm unaware of specific docs, but I tend to think of these simply as daemon nodes that aren't listed in slurm.conf. We use Ubuntu and the packages we install are munge, slurm-wlm, and slurm-client (which<br>
drags in libslurmXX and slurm-wlm-basic-plugins). <br>
<br>
<br>
Then the setup is very similar to slurmd nodes- you need matching UIDs and the same munge key. Access to the same file systems at the same locations as on daemon nodes is also advisable.<br>
<br>
<br>
Hope this helps.<br>
<br>
<br>
Michael<br>
<br>
On Fri, Oct 12, 2018 at 3:38 AM Aravindh Sampathkumar <<a href="mailto:aravindh@fastmail.com" target="_blank">aravindh@fastmail.com</a>> wrote:<br>
<br>
<br>
Hello.<br>
<br>
<br>
<br>
I built a simple 2 node SLURM cluster for the first time, and I'm able to run jobs on the lone compute node from the node that runs Slurmctl. <br>
<br>
However, I'd like to setup a "login node" which only allows users to submit jobs to the SLURM cluster and not act as SLURM controller or as a compute node. I'm struggling to find documentation about what needs to be installed and<br>
configured on this login node to be able to submit jobs to the cluster. <br>
<br>
<br>
<br>
console(login node) ----> slurm controller(runs slurmctld and slurmdbd) ----> compute node (runs slurmd)<br>
<br>
<br>
<br>
Can anybody point me to any relevant docs to configure the login node?<br>
<br>
<br>
<br>
Thanks,<br>
<br>
<br>
--<br>
<br>
Aravindh Sampathkumar<br>
<br>
<br>
<a href="mailto:aravindh@fastmail.com" target="_blank">aravindh@fastmail.com</a> <mailto:<a href="mailto:aravindh@fastmail.com" target="_blank">aravindh@fastmail.com</a>><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>------<br></div><div>'...postwork futures are dismissed with the claim that "it is not in our nature to be idle", thereby demonstrating at once an essentialist view of labor and an impoverished imagination of the possibilities of nonwork.'</div><div><br></div><div>Kathi Weeks, <a href="https://www.dukeupress.edu/The-Problem-with-Work/" target="_blank"><i>The Problem with Work: Feminism, Marxism, Antiwork Politics and Postwork Imaginaries</i></a><br></div></div></div></div></div></div></div></div></div></div></div></div></div>