next part --
An HTML attachment was scrubbed...
URL:
<https://urldefense.com/v3/__http://lists.schedmd.com/pipermail/slurm-users/attachments/20230827/fa37f4ae/attachment-0001.htm__;!!Mih3wA!H6jtRH1Co7St0JJ5HiauL4ay4-Eh6LH0U82KsCeTJHkkjp-ljokZ6CgLmcjQ0N_QpvgxDYbrcQv4bQYRUvStqM0vuZcLCGlWVg$
>
End of slurm-users Digest, Vol 70, Issue 36
***
gt;
> > My fall back solution is to use ssh to connect to the slurm head node and
> > run jobs there, but that seems kludgy.
> >
> > -steve
> >
> -- next part --
> An HTML attachment was scrubbed...
> URL: <
> https://urldefense.com/v3/__http://lists.schedmd.com/pipermail/slurm-users/attachments/20230827/fa37f4ae/attachment-0001.htm__;!!Mih3wA!H6jtRH1Co7St0JJ5HiauL4ay4-Eh6LH0U82KsCeTJHkkjp-ljokZ6CgLmcjQ0N_QpvgxDYbrcQv4bQYRUvStqM0vuZcLCGlWVg$
> >
>
> End of slurm-users Digest, Vol 70, Issue 36
> ***
>
gt;
> > My fall back solution is to use ssh to connect to the slurm head node and
> > run jobs there, but that seems kludgy.
> >
> > -steve
> >
> -- next part --
> An HTML attachment was scrubbed...
> URL: <
> https://urldefense.com/v3/__http://lists.schedmd.com/pipermail/slurm-users/attachments/20230827/fa37f4ae/attachment-0001.htm__;!!Mih3wA!H6jtRH1Co7St0JJ5HiauL4ay4-Eh6LH0U82KsCeTJHkkjp-ljokZ6CgLmcjQ0N_QpvgxDYbrcQv4bQYRUvStqM0vuZcLCGlWVg$
> >
>
> End of slurm-users Digest, Vol 70, Issue 36
> ***
>
The machine that runs the CLI isn't usually a cluster node or run slurmd.
The control node has to accept the user is who they claim and AFAIK that is
the job of munge. And your onboard and external firewalls must allow the
requisite ports.
We used Galaxy (see galaxy.eu if unfamiliar) and could s