NEMO/Login: Difference between revisions

From bwHPC Wiki
Jump to navigation Jump to search
mNo edit summary
Line 32: Line 32:
| fr
| fr
| fr_username
| fr_username
|-
|Heidelberg
|hd
|hd_username
|-
|-
|Hohenheim
|Hohenheim
Line 61: Line 65:
|ul_username
|ul_username
|}
|}



== Allowed activities on login nodes ==
== Allowed activities on login nodes ==

Revision as of 11:23, 27 November 2015

Disclaimer

The bwForCluster ENM (NEMO) is NOT available yet! But we offer a test cluster called pre-bwForCluster ENM (NEMO) with old bwGRiD Hardware. We run the Cluster with CentOS 7.1 which is binary compatible to RHEL 7 and new configuration and concept.


Login

After registration (registration procedure at bwForCluster User Access, the bwForCluster ENM (NEMO) can be accessed via ssh.

From linux machines, you can log in using

ssh <UserID>@login.bwfor.uni-freiburg.de

To run graphical applications, you can use the -X or -Y flag to openssh:

ssh -Y <UserID>@login.bwfor.uni-freiburg.de

For better performance on slow connections you should use e.g. VNC.


About UserID / Username

<UserID> of the ssh command is a placeholder for your username at your home organization and a prefix denoting your organization. Prefixes and resulting user names are as follows:

Site Prefix Username
Freiburg fr fr_username
Heidelberg hd hd_username
Hohenheim ho ho_username
Karlsruhe ka ka_username
Konstanz kn kn_username
Mannheim ma ma_username
Stuttgart st st_username
Tübingen tu tu_username
Ulm ul ul_username

Allowed activities on login nodes

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

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

To guarantee usability for all the users of the bwForCluster you must not run your compute jobs on the login nodes. Compute jobs must be submitted as Batch Jobs. Any compute job running on the login nodes will be terminated without any notice.


Further reading