rsnt_translations
57,772
edits
mNo edit summary |
No edit summary |
||
Line 12: | Line 12: | ||
<!--T:3--> | <!--T:3--> | ||
In the context of | In the context of the Alliance, SSH tunnelling is necessary in certain cases, | ||
because compute nodes on [[Niagara]], [[Béluga]] and [[Graham]] do not have direct access to | because compute nodes on [[Niagara]], [[Béluga]] and [[Graham]] do not have direct access to | ||
the internet, nor can the compute nodes be contacted directly from the internet. | the internet, nor can the compute nodes be contacted directly from the internet. | ||
Line 137: | Line 137: | ||
<!--T:26--> | <!--T:26--> | ||
SSH tunnelling can also be used in | SSH tunnelling can also be used in our context 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 cluster's compute node. When connecting to a database server where the connection is only possible through the head node, SSH tunnelling can be used to bind an external port to the database server. | ||
<!--T:32--> | <!--T:32--> | ||
Line 204: | Line 204: | ||
<!--T:48--> | <!--T:48--> | ||
These commands connect port number PORT on your local host to PostgreSQL or MySQL database servers respectively. The port number you choose (PORT) should not be bigger than 32768 (2^15). In this example, "someuser" is your | These commands connect port number PORT on your local host to PostgreSQL or MySQL database servers respectively. The port number you choose (PORT) should not be bigger than 32768 (2^15). In this example, "someuser" is your account username. The difference between this connection and an ordinary SSH connection is that you can now use another terminal to connect to the database server directly from your desktop. On your desktop, run one of these commands for PostgreSQL or MySQL as appropriate: | ||
<!--T:49--> | <!--T:49--> |