|
|
|
This guide was written for the old cluster (2015). In case it does not work with the new cluster (2024), please reach out to me via Mattermost or document an issue [here](https://gitlab.pik-potsdam.de/sdmc/cluster-wiki/-/issues) and assign me to it (@davidgo).
|
|
|
|
|
|
|
|
# Important note
|
|
|
|
If you use the VSCode Remote SSH extension, do not use cluster.pik-potsdam.de as the hostname. Instead, pick one of login01.pik-potsdam.de or login02.pik-potsdam.de. When ending a session, press CTRL + SHIFT + P and select “Kill VS Code Server on Host…” and select the same host.
|
|
|
|
If you use the VSCode Remote SSH extension, do not use "hpc.pik-potsdam.de" but "login03-24.pik-potsdam.de" as the hostname (Old cluster: login01.pik-potsdam.de or login02.pik-potsdam.de). When ending a session, press CTRL + SHIFT + P and select “Kill VS Code Server on Host…” and select the same host.
|
|
|
|
|
|
|
|
This is because “cluster” is an alias for one or other of the login nodes, selected based on which node has the lowest current load. Repeated connections to “cluster” via the Remote SSH extension fail to reuse existing vscode-server processes, which then accumulate over time. (Exerpt from [Connection failures when using VSCode Remote SSH Extension](Troubleshooting/Problems with solutions/Connection failures when using VSCode Remote SSH Extension))
|
|
|
|
This is because “clushpcter” is an alias for one or other of the login nodes, selected based on which node has the lowest current load. Repeated connections to “hpc” via the Remote SSH extension fail to reuse existing vscode-server processes, which then accumulate over time. (Exerpt from [Connection failures when using VSCode Remote SSH Extension](Troubleshooting/Problems with solutions/Connection failures when using VSCode Remote SSH Extension))
|
|
|
|
|
|
|
|
# How to connect
|
|
|
|
|
|
|
|
1. Open VSCode
|
|
|
|
2. Install the "Remote - SSH" extension
|
|
|
|
|
|
|
|
|
|
|
|
3. On the left via "Remote Explorer", you should already be able to connect to the cluster if you have have previously established a SSH connection. **If you use the VSCode Remote SSH extension, do not use cluster.pik-potsdam.de as the hostname. Instead, pick one of login01.pik-potsdam.de or login02.pik-potsdam.de.**
|
|
|
|
3. If you are not at PIK, start a VPN connection or use a proxyjump
|
|
|
|
4. On the left via "Remote Explorer", you should already be able to connect to the cluster if you have have previously established a SSH connection. **If you use the VSCode Remote SSH extension, do not use hpc.pik-potsdam.de as the hostname. Instead, pick login03-24.pik-potsdam.de.**
|
|
|
|
- in VSCode open the ssh remote commands via the shortcut `F1`,
|
|
|
|
- `Remote-SSH: Add New SSH Host...`,
|
|
|
|
- enter specific host via `ssh username@login01.pik-potsdam.de` or `ssh username@login02.pik-potsdam.de`
|
|
|
|
- enter specific host via `ssh username@login03-24.pik-potsdam.de`
|
|
|
|
- select where to store your private key (.ssh/config on your local computer)
|
|
|
|
- now you should be able to connect to a specific host
|
|
|
|
|
| ... | ... | |
