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
The all IT4Innovations clusters are accessed by 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 loginX at the address **cluster-name.it4i.cz**. The login nodes may be addressed specifically, by prepending the login node name to the address.
!!! note
The alias **cluster-name.it4i.cz** is currently not available through VPN connection. Use **loginX.cluster-name.it4i.cz** when connected to VPN.
The **cluster-name.it4i.cz**alias is currently not available through VPN connection. Use **loginX.cluster-name.it4i.cz** when connected to VPN.
Using sshfs, the users Barbora home directory will be mounted on your local computer, just like an external disk.
Learn more about ssh, scp and sshfs by reading the manpages
Learn more about SSH, SCP, and SSHFS by reading the manpages:
```console
$man ssh
...
...
@@ -198,15 +198,15 @@ Outgoing connections, from cluster login nodes to the outside world, are restric
| Port | Protocol |
| ---- | -------- |
| 22 | ssh |
| 80 | http |
| 443 | https |
| 9418 | git |
| 22 | SSH |
| 80 | HTTP |
| 443 | HTTPS |
| 9418 | Git |
!!! note
Use **ssh port forwarding** and proxy servers to connect from cluster to all other remote ports.
Use **SSH port forwarding** and proxy servers to connect from cluster to all other remote ports.
Outgoing connections, from Cluster compute nodes are restricted to the internal network. Direct connections form compute nodes to the outside world are cut.
Outgoing connections, from cluster compute nodes are restricted to the internal network. Direct connections from compute nodes to the outside world are cut.
## Port Forwarding
...
...
@@ -223,11 +223,11 @@ Pick some unused port on the cluster login node (for example 6000) and establis
In this example, we establish port forwarding between port 6000 on cluster and port 1234 on the remote.host.com. By accessing localhost:6000 on cluster, an application will see the response of remote.host.com:1234. The traffic will run via the user's local workstation.
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 Remote radio button. Insert 6000 to theSource 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 theSource port textbox. Insert remote.host.com:1234. Click the Add button, then Open.
Port forwarding may be established directly to the remote host. However, this requires that the user has ssh access to remote.host.com
Port forwarding may be established directly to the remote host. However, this requires that the user has an SSH access to remote.host.com.
Port number 6000 is chosen as an example only. Pick any free port.
### Port Forwarding From Compute Nodes
### Port Forwarding from Compute Nodes
Remote port forwarding from compute nodes allows applications running on the compute nodes to access hosts outside the cluster.
...
...
@@ -252,12 +252,12 @@ In this example, we assume that port forwarding from `login1:6000` to `remote.ho
### Using Proxy Servers
Port forwarding is static, each single port is mapped to a particular port on a remote host. Connection to another remote host requires a new forward.
Port forwarding is static; each single port is mapped to a particular port on a remote host. Connection to another remote host requires a new forward.
!!! 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 SOCKS proxy server software. On Linux, SSHD demon provides the functionality. To establish SOCKS proxy server listening on port 1080 run:
```console
$ssh -D 1080 localhost
...
...
@@ -265,7 +265,7 @@ $ ssh -D 1080 localhost
On Windows, install and run the free, open source [Sock Puppet][e] server.
Once the proxy server is running, establish ssh port forwarding from cluster to the proxy server, port 1080, exactly as [described above][5]:
Once the proxy server is running, establish the SSH port forwarding from cluster to the proxy server, port 1080, exactly as [described above][5]:
```console
$ssh -R 6000:localhost:1080 cluster-name.it4i.cz
...
...
@@ -275,7 +275,7 @@ Now, configure the applications proxy settings to **localhost:6000**. Use port f
## Graphical User Interface
* The [X Window system][6] is the principal way to get GUI access to the clusters.
* The [X Window system][6] is the principal way to get a GUI access to the clusters.
*[Virtual Network Computing][7] is a graphical [desktop sharing][f] system that uses the [Remote Frame Buffer protocol][g] to remotely control another [computer][h].
