...
In principle, you can do the same as under “Running Pluto on Login Node” above but using, say, n2cn0164 n2cn0216, instead of n2login. However, since you won’t always get the same compute node when requesting resources via Slurm this approach is tedious because you need to set up direct ssh access to the given compute node (n2cn0164 n2cn0216 in this example) each time.
...
| Code Block |
|---|
ssh -L 1234:127.0.0.1:1234 noctua2 ssh -L 1234:127.0.0.1:1234 -N n2cn0164n2cn0216 |
Here, noctua2 is the Noctua 2 jump host (see as specified in Access with SSH for ssh configuration) and n2cn0164 n2cn0216 is the given compute node. Hence, for different Slurm jobs, you only need to change the name of the compute node at the very end of this command (instead of modifying your ssh config).