SSH tunnel to a certain node: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(Use ProxyJump, makes it easier than port forwarding.) |
||
Line 1: | Line 1: | ||
* Submit a slurm job, or start an interactive job on a node. | |||
sinteractive | sinteractive | ||
* Check on which node this job has landed | |||
squeue -u $USER -l | |||
* Add this to your machines ssh config in ~/.ssh/config | |||
Host node*,gpu* | |||
ProxyJump login.anunna.wur.nl | |||
User your_user_id | |||
* You can now use your local terminal connecting to e.g. node201 directly, by: | |||
ssh node201 | |||
* In VSCode : | |||
in the VSCode GUI -> Open a remote Window -> Connect to Host...,type in the nodename. After a few seconds, VSCode is connected to the node. | |||
Please be aware that once the slurm job finishes, the connection will be lost and your running processes will be killed. | |||
Besides that, you are limited to the amount of RAM that you requested. | |||
Please be aware that once the slurm job finishes, the connection will be lost. |
Latest revision as of 16:03, 16 April 2024
- Submit a slurm job, or start an interactive job on a node.
sinteractive
- Check on which node this job has landed
squeue -u $USER -l
- Add this to your machines ssh config in ~/.ssh/config
Host node*,gpu* ProxyJump login.anunna.wur.nl User your_user_id
- You can now use your local terminal connecting to e.g. node201 directly, by:
ssh node201
- In VSCode :
in the VSCode GUI -> Open a remote Window -> Connect to Host...,type in the nodename. After a few seconds, VSCode is connected to the node.
Please be aware that once the slurm job finishes, the connection will be lost and your running processes will be killed. Besides that, you are limited to the amount of RAM that you requested.