cc_staff
163
edits
SSH tunnelling: Difference between revisions
Jump to navigation
Jump to search
no edit summary
mNo edit summary |
No edit summary |
||
| Line 14: | Line 14: | ||
# Running [[Visualization|visualization software]] on a compute node that needs to be contacted by client software on a user's local computer. | # Running [[Visualization|visualization software]] on a compute node that needs to be contacted by client software on a user's local computer. | ||
# Running a [[Jupyter | Jupyter notebook]] on a compute node that needs to be contacted by the web browser on a user's local computer. | # Running a [[Jupyter | Jupyter notebook]] on a compute node that needs to be contacted by the web browser on a user's local computer. | ||
# Connecting to cedar database server from somewhere other than cedar head node, e.g., your desktop | |||
In the first case, the license server is situated outside of | In the first case, the license server is situated outside of | ||
| Line 102: | Line 103: | ||
</source> | </source> | ||
= Contacting a visualization, Jupyterhub or other server running on compute node= | = Contacting a visualization, Jupyterhub, database or other server running on compute node= | ||
SSH tunnelling can also be used in the context of Compute Canada to allow a user's computer to connect to a compute node on a cluster through an encrypted tunnel that is routed via the login node of this cluster. This technique allows graphical output of applications like a [[Jupyter | Jupyter notebook]] or [[Visualization|visualization software]] to be displayed transparently on the user's local workstation even while they are running on a compute node of a cluster. | SSH tunnelling can also be used in the context of Compute Canada to allow a user's computer to connect to a compute node on a cluster through an encrypted tunnel that is routed via the login node of this cluster. This technique allows graphical output of applications like a [[Jupyter | Jupyter notebook]] or [[Visualization|visualization software]] to be displayed transparently on the user's local workstation even while they are running on a compute node of a cluster. In case of connecting to a database server where the connection is possible though the head node only the SSH tunneling can be used to move an arbitrary port number of a compute network to head node of a cluster and bind it to the database server. | ||
== Example for a job == | == Example for a job == | ||
| Line 165: | Line 166: | ||
Replace the token in this example with the one given to you in Session 1. You can also type <code>http://localhost:8888</code> and there will be a prompt asking you for the token, which you can then copy and paste. | Replace the token in this example with the one given to you in Session 1. You can also type <code>http://localhost:8888</code> and there will be a prompt asking you for the token, which you can then copy and paste. | ||
== Example for connecting to Postgres server on cedar from a desktop == | |||
The command is | |||
<pre> | |||
ssh -2 -L 127.0.0.1:PORT:cedar-pgsql-vm.int.cedar.computecanada.ca:5432 | |||
</pre> | |||
By running this command you will be connected to cedar (like any other ssh connection). Now, you can use another x-term and connect to database server directly from your desktop. The connection requires a password which is your computecanada password. The connection will remain open as long as your have your first ssh connection. In above example "PORT" is a arbitrary port number. For cedar <pre> PORT > 40000 </pre>. Since this port number needs to be open in firewall of cedar head node, please before running this command send a request to support@computecanada.ca and we will assign a port number for you. | |||