Versions Compared

Old Version 5

changes.mady.by.user Malte Thoma

Saved on

compared with

New Version Current

changes.mady.by.user Miguel Andrés-Martínez

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

External sources

The following external sources provide a great deal of information about HPCs. If you are new to HPCs, please use these sources (and other information on the web) to fill up the knowledge gaps:

Using the shell

To access and use AWI's HPC systems login via a terminal is needed, using ssh.

...

Tip

We advise all new users, who have never worked in a shell on a Unix-like system, to go through this nice introduction: 

https://swcarpentry.github.io/shell-novice/

This tutorial is a good starting point where you learn to navigate in the filesystem, manipulate files, and create and run scripts.


Login with ssh-keys

Resources

Example:

...

Albedo

Here is an example for my (Natalja's) desktop a user named "user" and a desktop named "desktop" connecting to NEC SX-ACE StanAlbedo. Please replace username and remote machine accordingly!

  • Generate a key on your local desktop or whatever machine you want to connect to stan0 albedo0 and stan1albedo1

    rakowsky@binf02l006
    user@desktop:~$ ssh-keygen -t ed25519 -a 100 -f ~/.ssh/id_
    rsa_awihome-stan -t rsa -b 4096
    Here, we stick to rsa to be on the safe side to generate a portable key. For more recent machines, ssh.com recommends ecdsa: ssh-keygen -t ecdsa -b 521
    ed25519_albedo

    You are asked for a passphrase. A passphrase increases the security in case your account is hacked or your notebook gets lost, and it is a must for connections between systems at different locations, e.g., from AWI to HLRN or from home to AWI. Please use a strong passphrase to secure your key.
    Two files are generated

    1. the private key ~/.ssh/id_rsaed25519_awihome-stan albedo remains on your local machine,

    2. the public key ~/.ssh/id_rsaed25519_awihome-stanalbedo.pub is copied to the remote machine.

  • Our recommendation is to have a pair of private+public keys for each local+remote connection. It helps to keep an overview and a good naming scheme helps to prevent the danger of overwriting an existing key.
  • Make sure you are connected to the AWI network (via ethernet or VPN)

  • Copy the public key to StanAlbedo, here to stan1albedo1, this also makes the key available on stan0albedo0, as they share the home directory:

    rakowsky@binf02l006
    user@desktop:~$ ssh-copy-id -i ~/.ssh/id_
    rsa
    ed25519_
    awihome-stan
    albedo.pub
    rakowsky@stan1
    <your_username>@albedo1.dmawi.de

    For some destinations, to increase the security, the public key has to be uploaded in a web portal, and it is not placed in your remote home directory.  For Albedo the command above is all you need.

  • Log in to stan0 albedo0 or stan1 albedo1 with

    rakowsky@binf02l006
    user@desktop:~$ ssh -i ~/.ssh/id_
    rsa
    ed25519_
    awihome-stan
    albedo -Y
    rakowsky@stan0
    <your_username>@albedo0.dmawi.de


  • Or, for convenience, add an entry to ~/.ssh/config on your local desktop. Generate this file, if not yet present.

    rakowsky@binf02l006
    user@desktop:~$ cat ~/.ssh/config
    Host
    stan
    albedo0
       Hostname
    Hostname stan.awi
    albedo0.dmawi.de
       IdentityFile
    IdentityFile 
    ~/.ssh/id_
    rsa
    ed25519_
    awihome-stan
    albedo
    User rakowsky
     user <your_username>

    and log in with

    rakowsky@binf02l006
    user@desktop:~$ ssh -Y
    stan
    albedo0

For more details about ssh have a look at SSH.