SSH Configuration

Noctua 1

For programs like Visual Studio Code that support remote development via ssh, you need a different ssh-config to deal with the load-balancer. You can add the following blocks to your ssh-config:

...

This will instruct ssh to use the host noctua-jumphost as a proxy when trying to connect to one of the frontends noctua-ln1 or noctua-ln2. We recommend to explicitly choose a frontend here because programs like Visual Studio Code run a daemon on the remote host and by explicitly choosing a frontend you avoid issues if you want to use multiple program instances. In programs like Visual Studio Code you can then simply select to ssh configuration noctua-ln1 or noctua-ln2 to connect to. Please don't use this way for interactive sessions.

Noctua 2

For programs like Visual Studio Code that support remote development via ssh, you need a different ssh-config to deal with the load-balancer. You can add the following blocks to your ssh-config:

...

This will instruct ssh to use the host n2-jumphost as a proxy when trying to connect to one of the frontends n2login1 or n2login2. We recommend to explicitly choose a frontend in this case because programs like Visual Studio Code run a daemon on the remote host and by explicitly choosing a frontend you avoid issues if you want to use multiple program instances. In programs like Visual Studio Code you can then simply select to ssh configuration n2login1 or n2login2 to connect to. Please don't use this way for interactive sessions. Noctua 2 has up to six login nodes. You might want to configure all of them to choose the login node with the lowest load. 

...

Compute nodes

We recommend the following two-step process

...