Merge branch 'content_revision' into 'master'

Content revision

See merge request !15

docs.it4i/anselm-cluster-documentation/accessing-the-cluster/outgoing-connections.md

-Outgoing connections
-====================
-
-Connection restrictions
------------------------
-Outgoing connections, from Anselm Cluster login nodes to the outside world, are restricted to following ports:
-
-|Port|Protocol|
-|---|---|
-|22|ssh|
-|80|http|
-|443|https|
-|9418|git|
-
-!!! Note "Note"
-	Please use **ssh port forwarding** and proxy servers to connect from Anselm to all other remote ports.
-
-Outgoing connections, from Anselm Cluster compute nodes are restricted to the internal network. Direct connections form compute nodes to outside world are cut.
-
-Port forwarding
----------------
-
-### Port forwarding from login nodes
-
-!!! Note "Note"
-	Port forwarding allows an application running on Anselm to connect to arbitrary remote host and port.
-
-It works by tunneling the connection from Anselm back to users workstation and forwarding from the workstation to the remote host.
-
-Pick some unused port on Anselm login node  (for example 6000) and establish the port forwarding:
-
-```bash
-local $ ssh -R 6000:remote.host.com:1234 anselm.it4i.cz
-```
-
-In this example, we establish port forwarding between port 6000 on Anselm and port 1234 on the remote.host.com. By accessing localhost:6000 on Anselm, an application will see response of remote.host.com:1234. The traffic will run via users local workstation.
-
-Port forwarding may be done **using PuTTY** as well. On the PuTTY Configuration screen, load your Anselm configuration first. Then go to Connection->SSH->Tunnels to set up the port forwarding. Click Remote radio button. Insert 6000 to Source port textbox. Insert remote.host.com:1234. Click Add button, then Open.
-
-Port forwarding may be established directly to the remote host. However, this requires that user has ssh access to remote.host.com
-
-```bash
-$ ssh -L 6000:localhost:1234 remote.host.com
-```
-
-Note: Port number 6000 is chosen as an example only. Pick any free port.
-
-### Port forwarding from compute nodes
-
-Remote port forwarding from compute nodes allows applications running on the compute nodes to access hosts outside Anselm Cluster.
-
-First, establish the remote port forwarding form the login node, as [described
-above](outgoing-connections.html#port-forwarding-from-login-nodes).
-
-Second, invoke port forwarding from the compute node to the login node. Insert following line into your jobscript or interactive shell
-
-```bash
-$ ssh  -TN -f -L 6000:localhost:6000 login1
-```
-
-In this example, we assume that port forwarding from login1:6000 to remote.host.com:1234 has been established beforehand. By accessing localhost:6000, an application running on a compute node will see response of remote.host.com:1234
-
-### Using proxy servers
-
-Port forwarding is static, each single port is mapped to a particular port on remote host. Connection to other remote host, requires new forward.
-
-!!! Note "Note"
-	Applications with inbuilt proxy support, experience unlimited access to remote hosts, via single proxy server.
-
-To establish 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:
-
-```bash
-local $ ssh -D 1080 localhost
-```
-
-On Windows, install and run the free, open source [Sock Puppet](http://sockspuppet.com/) server.
-
-Once the proxy server is running, establish ssh port forwarding from Anselm to the proxy server, port 1080, exactly as [described above](outgoing-connections/#port-forwarding-from-login-nodes).
-
-```bash
-local $ ssh -R 6000:localhost:1080 anselm.it4i.cz
-```
-
-Now, configure the applications proxy settings to **localhost:6000**. Use port forwarding  to access the [proxy server from compute nodes](outgoing-connections/#port-forwarding-from-compute-nodes) as well .

docs.it4i/anselm-cluster-documentation/accessing-the-cluster/shell-and-data-access.md → docs.it4i/anselm-cluster-documentation/shell-and-data-access.md

-Shell access and data transfer
+Shell access, data transfer and outgoing connections
 ==============================
 
 Interactive Login
@@ -120,3 +120,86 @@ $ man sshfs
 On Windows, use [WinSCP client](http://winscp.net/eng/download.php) to transfer the data. The [win-sshfs client](http://code.google.com/p/win-sshfs/) provides a way to mount the Anselm filesystems directly as an external disc.
 
 More information about the shared file systems is available [here](../../storage/storage/).
+
+
+Connection restrictions
+-----------------------
+Outgoing connections, from Anselm Cluster login nodes to the outside world, are restricted to following ports:
+
+|Port|Protocol|
+|---|---|
+|22|ssh|
+|80|http|
+|443|https|
+|9418|git|
+
+!!! Note "Note"
+	Please use **ssh port forwarding** and proxy servers to connect from Anselm to all other remote ports.
+
+Outgoing connections, from Anselm Cluster compute nodes are restricted to the internal network. Direct connections form compute nodes to outside world are cut.
+
+Port forwarding
+---------------
+
+### Port forwarding from login nodes
+
+!!! Note "Note"
+	Port forwarding allows an application running on Anselm to connect to arbitrary remote host and port.
+
+It works by tunneling the connection from Anselm back to users workstation and forwarding from the workstation to the remote host.
+
+Pick some unused port on Anselm login node  (for example 6000) and establish the port forwarding:
+
+```bash
+local $ ssh -R 6000:remote.host.com:1234 anselm.it4i.cz
+```
+
+In this example, we establish port forwarding between port 6000 on Anselm and port 1234 on the remote.host.com. By accessing localhost:6000 on Anselm, an application will see response of remote.host.com:1234. The traffic will run via users local workstation.
+
+Port forwarding may be done **using PuTTY** as well. On the PuTTY Configuration screen, load your Anselm configuration first. Then go to Connection->SSH->Tunnels to set up the port forwarding. Click Remote radio button. Insert 6000 to Source port textbox. Insert remote.host.com:1234. Click Add button, then Open.
+
+Port forwarding may be established directly to the remote host. However, this requires that user has ssh access to remote.host.com
+
+```bash
+$ ssh -L 6000:localhost:1234 remote.host.com
+```
+
+Note: Port number 6000 is chosen as an example only. Pick any free port.
+
+### Port forwarding from compute nodes
+
+Remote port forwarding from compute nodes allows applications running on the compute nodes to access hosts outside Anselm Cluster.
+
+First, establish the remote port forwarding form the login node, as [described
+above](outgoing-connections.html#port-forwarding-from-login-nodes).
+
+Second, invoke port forwarding from the compute node to the login node. Insert following line into your jobscript or interactive shell
+
+```bash
+$ ssh  -TN -f -L 6000:localhost:6000 login1
+```
+
+In this example, we assume that port forwarding from login1:6000 to remote.host.com:1234 has been established beforehand. By accessing localhost:6000, an application running on a compute node will see response of remote.host.com:1234
+
+### Using proxy servers
+
+Port forwarding is static, each single port is mapped to a particular port on remote host. Connection to other remote host, requires new forward.
+
+!!! Note "Note"
+	Applications with inbuilt proxy support, experience unlimited access to remote hosts, via single proxy server.
+
+To establish 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:
+
+```bash
+local $ ssh -D 1080 localhost
+```
+
+On Windows, install and run the free, open source [Sock Puppet](http://sockspuppet.com/) server.
+
+Once the proxy server is running, establish ssh port forwarding from Anselm to the proxy server, port 1080, exactly as [described above](outgoing-connections/#port-forwarding-from-login-nodes).
+
+```bash
+local $ ssh -R 6000:localhost:1080 anselm.it4i.cz
+```
+
+Now, configure the applications proxy settings to **localhost:6000**. Use port forwarding  to access the [proxy server from compute nodes](outgoing-connections/#port-forwarding-from-compute-nodes) as well .

docs.it4i/get-started-with-it4innovations/accessing-the-clusters/introduction.md

@@ -4,7 +4,7 @@ Accessing the Clusters
 The IT4Innovations clusters are accessed by SSH protocol via login nodes.
 
 !!! Note "Note"
-	Read more on [Accessing the Salomon Cluster](../../salomon/accessing-the-cluster/accessing-the-cluster/)r or [Accessing the Anselm Cluster](../../anselm-cluster-documentation/accessing-the-cluster/shell-and-data-access/) pages.
+	Read more on [Accessing the Salomon Cluster](../../salomon/accessing-the-cluster/accessing-the-cluster/)r or [Accessing the Anselm Cluster](../../anselm-cluster-documentation/shell-and-data-access.md/) pages.
 
 PuTTY
 -----

mkdocs.yml

@@ -26,15 +26,13 @@ pages:
   - Anselm Cluster:
     - Introduction: anselm-cluster-documentation/introduction.md
     - Hardware Overview: anselm-cluster-documentation/hardware-overview.md
+    - Shell and Data Access: anselm-cluster-documentation/shell-and-data-access.md
+    - VPN Access: anselm-cluster-documentation/vpn-access.md
     - Environment and Modules: anselm-cluster-documentation/environment-and-modules.md
     - Compute Nodes: anselm-cluster-documentation/compute-nodes.md
     - Remote visualization: anselm-cluster-documentation/remote-visualization.md
     - Network: anselm-cluster-documentation/network.md
     - PRACE User Support: anselm-cluster-documentation/prace.md
-  - Anselm Cluster Access:
-    - Outgoing Connections: anselm-cluster-documentation/accessing-the-cluster/outgoing-connections.md
-    - VPN Access: anselm-cluster-documentation/accessing-the-cluster/vpn-access.md
-    - Shell and Data Access: anselm-cluster-documentation/accessing-the-cluster/shell-and-data-access.md
   - Anselm Cluster Resource Allocation and Job Execution:
     - Introduction: anselm-cluster-documentation/resource-allocation-and-job-execution/introduction.md
     - Job Priority: anselm-cluster-documentation/resource-allocation-and-job-execution/job-priority.md