DACHS/Login

From bwHPC Wiki
< DACHS
Revision as of 23:53, 11 November 2024 by M Kunzelmann (talk | contribs) (add university prefix table of universities)
Jump to navigation Jump to search
Attention.svg

Access to DACHS is limited to IP addresses from the BelWü network. All home institutions of our current users are connected to BelWü, so if you are on your campus network (e.g. in your office or on the Campus WiFi) you should be able to connect to DACHS without restrictions. If you are outside one of the BelWü networks (e.g. at home), a VPN connection to the home institution or a connection to an SSH jump host at the home institution must be established first.

The login nodes of the DACHS cluster are the access points to the compute system, your $HOME directory and your workspaces. All users must log in through these nodes to submit jobs to the cluster.

Prerequisites for successful login:

You need to have


Login to the DACHS

Login to the DACHS is only possible with a Secure Shell (SSH) client for which you must know your username on the cluster and the hostname of the login nodes. For more general information on SSH clients, visit the SSH clients Guide.

Username

If you want to use DACHS, you need to add a prefix to your local username.


Allowed Activities on Login Nodes

Attention.svg

To guarantee usability for all the users of clusters you must not run your compute jobs on the login nodes. Compute jobs must be submitted to the queuing system. Any compute job running on the login nodes will be terminated without any notice. Any long-running compilation or any long-running pre- or post-processing of batch jobs must also be submitted to the queuing system.

The login nodes of the DACHS cluster are the access point to the compute system, your $HOME directory and your workspaces. These nodes are shared with all the users therefore, your activities on the login nodes are limited to primarily set up your batch jobs. Your activities may also be:

  • short compilation of your program code and
  • short pre- and post-processing of your batch jobs.

TODO: We advise users to use interactive jobs for compute and memory intensive tasks like compiling.


Related Information