Remote*: Tips and Tricks#
Some workarounds related to remote development/debugging on Levante. These workarounds are not tested on all available remote tools but often specific to a certain IDE. We encourage you to test on your favorite IDE and report issues to email@example.com.
Connect to a previously allocated compute node#
Tested on VSCode
[Levante] Allocate a compute node with salloc (see here)
$HOME/.ssh/configand add this:
Host *.lvt.dkrz.de ProxyJump levante.dkrz.de
[Local] Add pub key to
~/.ssh/authorized_keys(only for the first time)
cat ~/.ssh/abcd.pub | ssh firstname.lastname@example.org 'cat >> .ssh/authorized_keys'
[Local] From VSCode: (
Ctrl+Shift+P) –> Connect to Host and then you have to manually specify username@computeNodeName.lvt.dkrz.de.
We assume that you did set up ssh following this link.
Alternative content for 2)#
You can also use the following configuration:
Host computeNodeName.lvt.dkrz.de HostName computeNode.lvt.dkrz.de User username ProxyCommand ssh email@example.com -W %h:%p
computeNodeName from 1.