4 merge requests!368Update prace.md to document the change from qprace to qprod as the default...,!367Update prace.md to document the change from qprace to qprod as the default...,!366Update prace.md to document the change from qprace to qprod as the default...,!323extended-acls-storage-section
All IT4Innovations clusters are accessed by the SSH protocol via login nodes loginX at the address **cluster-name.it4i.cz**. The login nodes may be addressed specifically, by prepending the login node name to the address.
All IT4Innovations clusters are accessed by the SSH protocol via login nodes at the address **cluster-name.it4i.cz**. The login nodes may be addressed specifically, by prepending the loginX node name to the address.
!!! note
The **cluster-name.it4i.cz** alias is currently not available through VPN connection. Use **loginX.cluster-name.it4i.cz** when connected to VPN.
...
...
@@ -102,7 +102,7 @@ $ chmod 600 /path/to/id_rsa
On **Windows**, use the [PuTTY SSH client][2].
After logging in, you will see the command prompt
After logging in, you will see the command prompt:
```console
...
...
@@ -188,13 +188,13 @@ $ man scp
$man sshfs
```
On Windows, use the [WinSCP client][c] to transfer the data. The [win-sshfs client][d] provides a way to mount the cluster filesystems directly as an external disc.
On Windows, use the [WinSCP client][c] to transfer data. The [win-sshfs client][d] provides a way to mount the cluster filesystems directly as an external disc.
More information about the shared file systems is available [here][4].
## Connection Restrictions
Outgoing connections from cluster login nodes to the outside world, are restricted to the following ports:
Outgoing connections from cluster login nodes to the outside world are restricted to the following ports:
| Port | Protocol |
| ---- | -------- |
...
...
@@ -217,7 +217,7 @@ Outgoing connections from cluster compute nodes are restricted to the internal n
It works by tunneling the connection from cluster back to the user's workstations and forwarding from the workstation to the remote host.
Pick some unused port on the cluster login node (for example 6000) and establish the port forwarding:
Select an unused port on the cluster login node (for example 6000) and establish the port forwarding:
In this example, we establish port forwarding between port 6000 on the cluster and port 1234 on the `remote.host.com`. By accessing `localhost:6000` on the cluster, an application will see the response of `remote.host.com:1234`. The traffic will run via the user's local workstation.
Port forwarding may be done **using PuTTY** as well. On the PuTTY Configuration screen, load your cluster configuration first. Then go to *Connection->SSH->Tunnels* to set up the port forwarding. Click the Remote radio button. Insert 6000 to the Source port textbox. Insert `remote.host.com:1234`. Click the Add button, then Open.
Port forwarding may be done **using PuTTY** as well. On the PuTTY Configuration screen, load your cluster configuration first. Then go to *Connection > SSH > Tunnels* to set up the port forwarding. Click the _Remote_ radio button. Insert 6000 to the _Source port_ textbox. Insert `remote.host.com:1234`. Click _Add_, then _Open_.
Port forwarding may be established directly to the remote host. However, this requires that the user has an SSH access to `remote.host.com`.
Remote port forwarding from compute nodes allows applications running on the compute nodes to access hosts outside the cluster.
First, establish the remote port forwarding form the login node, as [described above][5].
First, establish the remote port forwarding from the login node, as [described above][5].
Second, invoke port forwarding from the compute node to the login node. Insert the following line into your jobscript or interactive shell:
...
...
@@ -257,7 +257,7 @@ Port forwarding is static; each single port is mapped to a particular port on a
!!! note
Applications with inbuilt proxy support experience unlimited access to remote hosts via a single proxy server.
To establish a local proxy server on your workstation, install and run SOCKS proxy server software. On Linux, SSHD demon provides the functionality. To establish SOCKS proxy server listening on port 1080 run:
To establish a local proxy server on your workstation, install and run the SOCKS proxy server software. On Linux, SSHD demon provides the functionality. To establish the SOCKS proxy server listening on port 1080 run:
```console
$ssh -D 1080 localhost
...
...
@@ -271,7 +271,7 @@ Once the proxy server is running, establish the SSH port forwarding from cluster
$ssh -R 6000:localhost:1080 cluster-name.it4i.cz
```
Now, configure the applications proxy settings to `localhost:6000`. Use port forwarding to access the [proxy server from compute nodes][5] as well.
Now, configure the applications proxy settings to `localhost:6000`. Use port forwarding to access the [proxy server from compute nodes][5], as well.