Difference between revisions of "Accessing the cluster"
From ScientificComputing
Line 37: | Line 37: | ||
* Start your SSH client | * Start your SSH client | ||
* Use ssh command to connect to the login node of Euler | * Use ssh command to connect to the login node of Euler | ||
− | ssh username@euler.ethz.ch | + | $ ssh username@euler.ethz.ch |
* Use your ETH credentials to log in | * Use your ETH credentials to log in | ||
<table style="width: 100%;"> | <table style="width: 100%;"> | ||
Line 66: | Line 66: | ||
**For Windows users, X11 is already included and enabled in MobaXterm. | **For Windows users, X11 is already included and enabled in MobaXterm. | ||
**Linux and macOS users have to enable X11 forwarding when log in | **Linux and macOS users have to enable X11 forwarding when log in | ||
− | ssh -Y username@euler.ethz.ch | + | $ ssh -Y username@euler.ethz.ch |
* After a successful login with password, [[Accessing_the_clusters#SSH_keys|generate SSH keys for passwordless login]] | * After a successful login with password, [[Accessing_the_clusters#SSH_keys|generate SSH keys for passwordless login]] |
Revision as of 14:42, 14 July 2021
< Home |
Prerequisites
|
How to access the cluster
- Start your SSH client
- Use ssh command to connect to the login node of Euler
$ ssh username@euler.ethz.ch
- Use your ETH credentials to log in
For new users and unverified accounts
An access code has been sent to your ETH email address. Enter the access code at the prompt below. If you do not receive the access code within a few minutes, then contact us by opening a ticket at http://smartdesk.ethz.ch Access code (ending in ******Ls): |
Login options
$ ssh -Y username@euler.ethz.ch
|
Who can access the cluster
|
External collaboratorsMembers of other institutions who have a collaboration with a research group at ETH may use the clusters for the purpose of said collaboration
|
Security
module load eth_proxy Legal ComplianceThe HPC clusters are subject to ETH’s acceptable use policy for IT resources (Benutzungsordnung für Telematik (BOT)), in particular:
|
Consequences:
- In case of abuse, the offender’s account may be blocked temporarily or closed
- System administrators are obliged by law to investigate abusive or illegal activities and report them to the relevant authorities
SSH Keys
- SSH keys allows passwordless login which is useful for file transfers and automated tasks
- When used properly, SSH keys are much safter than passwords
- SSH keys always come in pairs:
- A private key, stored on your local workstation (and nowhere else!)
- A public key, stored on the computer(s) you want to connect to
- You can generate as many pairs as you like, e.g., one for each computer you intend to connect to
- Keys should be protected with a passphrase
- SSH key management
Step 1: Create your keys
$ ssh-keygen -t ed25519 -f $HOME/.ssh/id_ed25519_euler
|
Step 2: Copy the public key to the cluster
$ ssh-copy-id -i $HOME/.ssh/id_ed25519_euler.pub username@euler.ethz.ch |
Step 3: Use keys with non-default names
The login commands become: $ ssh -i $HOME/.ssh/id_ed25519_euler username@euler.ethz.ch Alternatively, SSH clients can use this option automatically by adding the option IdentityFile in your $HOME/.ssh/config file, e.g.: Host euler HostName euler.ethz.ch User username IdentityFile ~/.ssh/id_ed25519_euler Next time you login, you can type $ ssh euler |
Further reading
< Home |