Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

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:

Host noctua-jumphost
  Hostname fe.noctua1.pc2.uni-paderborn.de
  User [USERNAME]
  IdentityFile [PATH TO PRIVATE KEY]
  IdentitiesOnly yes

Host noctua-ln1
  Hostname ln-0001
  User [USERNAME]
  ProxyJump noctua-jumphost
  IdentityFile [PATH TO PRIVATE KEY]
  IdentitiesOnly yes

Host noctua-ln2
  Hostname ln-0002
  User [USERNAME]
  ProxyJump noctua-jumphost
  IdentityFile [PATH TO PRIVATE KEY]
  IdentitiesOnly yes

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:

Host n2-jumphost
  Hostname fe.noctua2.pc2.uni-paderborn.de
  User [USERNAME]
  IdentityFile [PATH TO PRIVATE KEY]
  IdentitiesOnly yes

Host n2login1
  Hostname n2login1.ab2021.pc2.uni-paderborn.de
  User [USERNAME]
  ProxyJump n2-jumphost
  IdentityFile [PATH TO PRIVATE KEY]
  IdentitiesOnly yes

Host n2login2 
  Hostname n2login2.ab2021.pc2.uni-paderborn.de 
  User [USERNAME]
  ProxyJump n2-jumphost
  IdentityFile [PATH TO PRIVATE KEY]
  IdentitiesOnly yes

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. 

  • No labels