Actions

Difference between revisions of "Login to cluster"

From ALICE Documentation

(Login to ALICE from Linux)
Line 1: Line 1:
To login to the ALICE cluster you need to perform a hop-like login sequence. The two login node of the ALICE cluster cannot be accessed directly. So one needs to first login to an ssh gateway and then to one of the login nodes. This mechanism is required for both login and file transfer operations. Below we describe how to perform these actions from Linux and Windows, separately,
+
To login to the ALICE cluster you need to perform a hop-like login sequence. The two login nodes of the ALICE cluster cannot be accessed directly. One must first login to an ssh gateway and then to one of the login nodes. This mechanism is required for both login and file transfer operations. Below we describe how to perform these actions from Linux and Windows, separately.
  
 
===Login to ALICE from Linux===
 
===Login to ALICE from Linux===
Line 17: Line 17:
 
   User <USERNAME>
 
   User <USERNAME>
 
   ProxyJump <USERNAME>@ssh-gw.leidenuniv.nl:22
 
   ProxyJump <USERNAME>@ssh-gw.leidenuniv.nl:22
(put in your own ulcn account name instead of <USERNAME>).
+
(Replace <USERNAME> by your own ULCN account name.)
  
 
If you want to look at the monitoring tools that are running on the management node too, you could add additional tunneling commands to the config for a specific host. Do not add tunnels to all definitions as they may produce conflicts when you use the samen tunnel twice. So add the tunnel commands, for instance, to one host like:
 
If you want to look at the monitoring tools that are running on the management node too, you could add additional tunneling commands to the config for a specific host. Do not add tunnels to all definitions as they may produce conflicts when you use the samen tunnel twice. So add the tunnel commands, for instance, to one host like:
Line 47: Line 47:
 
this copies the <local_file_name> file to <remove_file_name> file in your home directory on ALICE.
 
this copies the <local_file_name> file to <remove_file_name> file in your home directory on ALICE.
  
==== Tunneling to monitors ====
+
====Tunneling to monitors====
 
Having setup the ssh tunneling required to access the monitoring tools on the cluster you are now able to access port 443 (general secure web server on the management node) and port 8081 (specific port in use by the Bright Cluster Manager monitoring tools).
 
Having setup the ssh tunneling required to access the monitoring tools on the cluster you are now able to access port 443 (general secure web server on the management node) and port 8081 (specific port in use by the Bright Cluster Manager monitoring tools).
  
Line 61: Line 61:
  
 
===Login to ALICE from Windows===
 
===Login to ALICE from Windows===
In windows you can make use of the program putty. Open the configuration and create a saved session with a name that you can rememeber. Here we choose ALICE-login01 to denote that this session will setup a login to login1.alice.universteitleiden.nl. In the Host Name field enter the the gateway to which we first have to login: sshgw.leidenuniv.nl.
+
In windows you can make use of the program putty. Open the configuration and create a saved session with a name that you can remember. Here we choose ALICE-login01 to denote that this session will setup a login to login1.alice.universteitleiden.nl. In the Host Name field enter the the gateway to which we first have to login: sshgw.leidenuniv.nl.
 
[[File:Putty1.jpg|none|thumb]]
 
[[File:Putty1.jpg|none|thumb]]
 
then go to the SSH tab en fill in:
 
then go to the SSH tab en fill in:

Revision as of 15:33, 5 July 2019

To login to the ALICE cluster you need to perform a hop-like login sequence. The two login nodes of the ALICE cluster cannot be accessed directly. One must first login to an ssh gateway and then to one of the login nodes. This mechanism is required for both login and file transfer operations. Below we describe how to perform these actions from Linux and Windows, separately.

Login to ALICE from Linux

The login nodes are named:

login1.alice.universiteitleiden.nl (10.161.0.12)
login2.alice.universiteitleiden.nl (10.162.0.13)

Setup ssh JUMP

In your linux server write in ~/.ssh/config for instance

Host hpc1 
  HostName login1.alice.universiteitleiden.nl
  User <USERNAME>
  ProxyJump <USERNAME>@ssh-gw.leidenuniv.nl:22
  
Host hpc2
  HostName login2.alice.universiteitleiden.nl
  User <USERNAME>
  ProxyJump <USERNAME>@ssh-gw.leidenuniv.nl:22

(Replace <USERNAME> by your own ULCN account name.)

If you want to look at the monitoring tools that are running on the management node too, you could add additional tunneling commands to the config for a specific host. Do not add tunnels to all definitions as they may produce conflicts when you use the samen tunnel twice. So add the tunnel commands, for instance, to one host like:

Host hpc1tunnel
  HostName login1.alice.universiteitleiden.nl
  User <USERNAME>
  ProxyJump <USERNAME>@ssh-gw.leidenuniv.nl:22
  LocalForward 8081:management.alice.universiteitleiden.nl:8081
  LocalForward 8080:management.alice.universiteitleiden.nl:443

Alternatively, if your openssh server isn't that recent and doesn't recognize the ProxyJump alias, try this:

Host hpc1 
  HostName login1.alice.universiteitleiden.nl
  ForwardX11 yes
  User <USERNAME>
  ProxyCommand ssh -X <USERNAME>@sshgw.leidenuniv.nl -W %h:%p

Login to ssh-gw.leidenuniv.nl (ssh <USERNAME>@ssh-gw.leidenuniv.nl) and put your public key in

~/.ssh/authorized_keys

Login through to the HPC login1 node ''ssh login1.alice.universiteitleiden.nl' and put the same public key in

~/.ssh/authorized_keys

Direct login to login node 1

 ssh hpc1

and you can even forward X11 now.

File transfer to login node 1

 ssh <local_file_name> hpc1:<remote_file_name>

this copies the <local_file_name> file to <remove_file_name> file in your home directory on ALICE.

Tunneling to monitors

Having setup the ssh tunneling required to access the monitoring tools on the cluster you are now able to access port 443 (general secure web server on the management node) and port 8081 (specific port in use by the Bright Cluster Manager monitoring tools).

So in a browser you could type:

https://localhost:8080

to gain access to the management main web server, or you could type:

https://localhost:8081/userportal

to gain access to the Bright Cluster Manager User Portal.

Login to ALICE from Windows

In windows you can make use of the program putty. Open the configuration and create a saved session with a name that you can remember. Here we choose ALICE-login01 to denote that this session will setup a login to login1.alice.universteitleiden.nl. In the Host Name field enter the the gateway to which we first have to login: sshgw.leidenuniv.nl.

Putty1.jpg

then go to the SSH tab en fill in:

Putty2.jpg

and fill in in the Remote command, the ssh call to the ALICE login node 1: ssh login1.alice.universiteitleiden.nl.

This way you will automatically get the login prompt to the ALICE login node 1 once you have logged in int sshgw.leidenuniv.nl.