bwHPC Wiki - User contributions [en]

BwUniCluster 2.0 User Access

2020-10-21T14:44:23Z

J Krueger: /* Step A: bwUniCluster entitlement for registration */

[[bwUniCluster_2.0|bwUniCluster 2.0]] is Baden-Württemberg's general purpose tier 3 high performance computing (HPC)
cluster co-financed by Baden-Württemberg's ministry of science, research and arts and the shareholders:

* Albert Ludwig University of Freiburg
* Eberhard Karls University, Tübingen
* Karlsruhe Institute of Technology (KIT)
* Heidelberg University (Ruprecht-Karls-Universität Heidelberg)
* Ulm University
* University of Hohenheim
* University of Konstanz
* University of Mannheim
* University of Stuttgart
* HAW BW e.V. (an association of university of applied sciences in Baden-Württemberg)
 
To '''log on''' [[bwUniCluster_2.0|bwUniCluster 2.0]] a user account is required. All members of the shareholder
universities can apply for an account.
 

{| style="width: 100%; border-spacing: 5px;"
| style="text-align:left; color:#000;vertical-align:top;" |__TOC__
| [[File:bwUniCluster_17Jan2014_p044-rot_t10.10.00.jpg|center|border|250px|bwUniCluster wiring by Holger Obermaier, copyright: KIT (SCC)]] bwUniCluster wiring © KIT (SCC)
|}

= Registration =

Granting access and issuing a user account for '''bwUniCluster 2.0''' requires the registration at the KIT service website [https://bwidm.scc.kit.edu/ https://bwidm.scc.kit.edu] (step B). However, this registration depends on the '''bwUniCluster entitlement''' issued by your university (step A).
 

== Step A: bwUniCluster entitlement for registration ==
'''The entitlement is called bwUniCluster (not bwUniCluster 2.0)''' and each university issues the bwUniCluster entitlement '''only''' for their own respective members. Some have established on-line processes or provide downloads of the entitlement application forms. If there is no link behind the name of an institution in the following list, please contact the local IT support services:

* [[BwCluster_User_Access_Uni_Freiburg|Albert Ludwig University of Freiburg]]
* [https://bwunicluster.urz.uni-heidelberg.de/ Heidelberg University]
* [https://kim.uni-hohenheim.de/bwhpc-account University of Hohenheim]
* [http://www.scc.kit.edu/downloads/sdo/Antrag_Benutzernummer_bwUniCluster.pdf Karlsruhe Institute of Technology (KIT)]
* [[BWUniCluster_User_Access_Members_Uni_Konstanz|University of Konstanz]]
* [[BWUniCluster_User_Access_Members_Uni_Mannheim|University of Mannheim]]
* [https://www.hlrs.de/solutions-services/academic-users/bwunicluster-access/ University of Stuttgart]
* [https://uni-tuebingen.de/de/155157 Eberhard Karls University Tübingen]
* [[BWUniCluster_User_Access_Members_Uni_Ulm|Ulm University]]
* Hochschule Aalen
* Hochschule Albstadt-Sigmaringen
* Hochschule Esslingen
* Hochschule Furtwangen
* Hochschule Karlsruhe
* Hochschule Konstanz
* Hochschule Reutlingen
* Hochschule Rottenburg
* Hochschule Stuttgart (HfT)
* Hochschule Ulm
 

== Step B: Web Registration, service password and 2-factor authentication ==

After completing step A, i.e., after successfull issueing of the bwUniCluster entitlement, you have to register yourself for the service. To do so please visit [https://bwidm.scc.kit.edu/ https://bwidm.scc.kit.edu] and complete the following steps.

1. Select your home organization from the list on the main page and click '''Proceed''' or '''Fortfahren'''.

[[File:BwUniCluster 2.0 access login bwidm select institution.png|center|border|]]
 

2. You will be directed to the ''Identity Provider'' of your home organisation. Enter the user ID / username and password of your home organisation - this is usually the same password used for your e-mail account and other services - and click on '''Login''', '''Einloggen''' or something similar.
 

3. You will be redirected back to the registration website [https://bwidm.scc.kit.edu/ https://bwidm.scc.kit.edu/]. If you are logging into bwIDM for the first time, there will be a summary screen which shows the account details your home institution is providing to the central system. Please check that all data is valid and then click on '''Continue''' or '''Weiter'''.
 

4. Once you have successfully logged into the bwIDM system, you will be greeted by a home screen showing all state-wide services you have access to. There will be a box labelled "bwUniCluster". Click on '''Register''' or '''Registrieren''' to start the registration process.

[[File:BwUniCluster 2.0 access login bwidm service list.png|center|border|]]
 

5. Since August 13, 2020 a '''2-factor authentication''' mechanism (2FA) is being enforced to improve security. If you have never registered a 2FA token on bwIDM before, the following error message will appear:

[[File:BwUniCluster 2.0 access login bwidm registration requirements 2fa.png|center|]]

Click on the [https://bwidm.scc.kit.edu/user/twofa.xhtml Link] or on the '''My Tokens''' link in the main menu. The instructions for registering a new 2FA token can be found on the following page: [[bwUniCluster 2.0 User Access/2FA Tokens]]. Please complete them before proceeding.
 

6. Make sure all requirements are met by checking the '''Requirements''' box at the top. If the requirements are not met you might be able to correct the issure by following the instructions. In all other cases please [[Registration_Support_-_bwUniCluster|contact your local hotline]].

[[File:BwUniCluster 2.0 access login bwidm registration requirements.png|center|border|]]
 

7. Read the Terms of Use ('''Nutzungsbedingungen und -richtlinien'''), check the box besides '''I have read and accepted the terms of use''' and click on '''Register''' or '''Registrieren'''.
 

8. Set a service password for the bwUniCluster and click on '''Save''' or '''Speichern'''. Logging in with the password of your home organisation, like on the former bwUniCluster 1, is no longer possible. Please make sure to use a strong password which is different from any other password you are currently using or have used on other systems. You will also be asked to change the service password regularly.

[[File:BwUniCluster 2.0 access login bwidm service password.png|center|]]
 
 

== Step C: Fill out the bwUniCluster questionnaire ==

Filling out the bwUniCluster questionaire on

https://zas.bwhpc.de/shib/en/bwunicluster_survey.php

is mandatory for all users. The input is solely used to improve our support activities and for capacity planning of future HPC resources. '''If the questionaire is not filled out, access to bwUniCluster 2.0 is blocked 14 days after the registration.'''
 
 

== Changing the Service Password ==

Your bwUniCluster 2.0 '''password''' is the service password you set during the web registration (compare step 7 of chapter 1.2). At any time, you can set a new bwUniCluster 2.0 password via the registration website [https://bwidm.scc.kit.edu/ https://bwidm.scc.kit.edu] by carrying out the following steps:
# Go to [https://bwidm.scc.kit.edu/ https://bwidm.scc.kit.edu] and select your home organization
# Authenticate yourself via the user id / username and password provided by your home institution
# Find the entry '''bwUniCluster''' and select '''Set Service Password'''
# Enter the new password, repeat it and click '''Save''' button.
# If the change was sucessfull, the message "Das Passwort wurde bei dem Dienst geändert" ("Password has been changed") will be shown
# Proceed to log in using the new password
 
 
== Contact / Support ==
If you have questions or problems concerning the bwUniCluster (2.0) registration, please [[bwUniCluster 2.0 Support|contact your local hotline]].
 
 

= Establishing network access =

Access to bwUniCluster 2.0 is '''limited to IP addresses from the so-called BelWü networks'''. All home institutions of our current users are connected to BelWue, 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 bwUniCluster 2.0 without restrictions. If you are outside of one of the BelWue networks (e.g. in your home office instead of in your campus office), a VPN connection to your home institution has to be established first (see e.g. [1] for the KIT).
 
 

= Login =

After finishing the web registration and making sure that you are on a network from which you have access to bwUniCluster 2.0 (e.g. by establishing a VPN connection), the HPC cluster is ready for your '''SSH''' based login. Recommended SSH clients applications are:

* the ssh (OpenSSH) command included in all Linux distributions and macOS, -in command under Linux and macOS using the application ''terminal''
* [http://mobaxterm.mobatek.net/ MobaXterm] under Windows
 

== Hostnames ==

The main hostname required to connect to bwUniCluster 2.0 is '''bwunicluster.scc.kit.edu''' or '''uc2.scc.kit.edu'''. The system has four login nodes and we use so-called ''DNS round-robin scheduling'' to load-balance the incoming connections between the nodes. If you open multiple SSH sessions to bwUniCluster 2.0, these sessions will be established to different login nodes, so processes started in one session might not be visible in other sessions.

The older Broadwell extension partition of the former bwUniCluster 1 is connected to bwUniCluster 2.0. You can use the hostname '''uc1e.scc.kit.edu''' to connect to the login nodes of this partition.

If you need to connect to specific login nodes, you can use the following hostnames:

{| class="wikitable"
! Hostname !! Node type
|-
| '''uc2-login1.scc.kit.edu''' || bwUniCluster 2.0, first login node
|-
| '''uc2-login2.scc.kit.edu''' || bwUniCluster 2.0, second login node
|-
| '''uc2-login3.scc.kit.edu''' || bwUniCluster 2.0, third login node
|-
| '''uc2-login4.scc.kit.edu''' || bwUniCluster 2.0, fourth login node
|-
| '''uc1e-login1.scc.kit.edu''' || Broadwell partition, first login node
|-
| '''uc1e-login2.scc.kit.edu''' || Broadwell partition, second login node
|-
|}

Only the secure shell ''SSH'' is allowed to login. Other protocols like ''telnet'' or ''rlogin'' are not allowed for security reasons.
 

== Usernames ==

Your username will be the same as the one provided by your home institution, but '''prefixed''' with two characters and an underscore indicating your home institution. For example: If you are a member of the university of Konstanz and your local username is ab1234, your username on bwUniCluster 2.0 is kn_ab1234.

The following list contains all prefixes currently in use:

{| class="wikitable"
! Home organization !! <UserID>
|-
| Universität Freiburg || ''fr_''username
|-
| Universität Heidelberg || ''hd_''username
|-
| Universität Hohenheim || ''ho_''username
|-
| KIT || username ''(without any prefix)''
|-
| Universität Konstanz || ''kn_''username
|-
| Universität Mannheim || ''ma_''username
|-
| Universität Stuttgart || ''st_''username
|-
| Universität Tübingen || ''tu_''username
|-
| Universität Ulm || ''ul_''username
|-
| Hochschule Aalen || ''aa_''username
|-
| Hochschule Albstadt-Sigmaringen || ''as_''username
|-
| Hochschule Esslingen || ''es_''username
|-
| Hochschule Furtwangen || ''hf_''username
|-
| Hochschule Karlsruhe || ''hk_''username
|-
| HTWG Konstanz || ''ht_''username
|-
| Hochschule Reutlingen || ''hr_''username
|-
| Hochschule Rottenburg || ''ro_''username
|-
| Hochschule für Technik Stuttgart || ''hs_''username
|-
| Hochschule Ulm || ''hu_''username
|-
|}
 

== Client application: OpenSSH ==

Most Unix and Unix-like operating systems like Linux, macOS and *BSD come with a built-in SSH client provided by the OpenSSH project. More recent versions of Windows 10 and the Windows Subsystem for Linux also come with a built-in OpenSSH client.

To use this client, simply open a command line terminal (the exact process differs on every operating system, but usually involves starting an application called '''Terminal''' or '''Command Prompt''') and enter the following command to connect to bwUniCluster 2.0:

<pre>
$ ssh <UserID>@bwunicluster.scc.kit.edu
</pre>

If you are on a Linux or Unix system running the X Window System (X11) and want to use a GUI-based application on bwUniCluster 2.0, you can use the ''-X'' option for the ssh command to set up X11 forwarding:

<pre>
$ ssh -X <UserID>@uc2.scc.kit.edu
</pre>

Windows users requiring X11 forwarding for graphical applications should use '''MobaXterm''' instead.
 

== Client application: MobaXterm ==

The bwHPC-C5 support team strongly recommends to use [http://mobaxterm.mobatek.net/ MobaXterm] instead of ''PuTTY'' or ''WinSCP'' on Windows. ''MobaXterm'' provides a built-in X11 server allowing to start GUI based software.

Start ''MobaXterm'', fill in the following fields:
<pre>
Remote name : uc2.scc.kit.edu # or uc1e.scc.kit.edu
Specify user name : <UserID>
Port : 22
</pre>

After that click on 'ok'. Then a terminal will be opened and there you can enter your credentials.
 

== Example login process ==

After the connection has been initiated, a successful login process will go through the following three steps:

1. The system asks for a '''One-Time Password'''. Generate one using the Software or Hardware Token registered on the bwIDM system (see [[bwUniCluster 2.0 User Access/2FA Tokens]]) and enter it after the '''Your OTP:''' prompt.

2. The systems asks for your service password. Enter it after the '''Password:''' prompt.

3. You are greeted by the bwUniCluster 2.0 banner followed by a shell.

The result should look like this:

[[File:BwUniCluster 2.0 access login example.png|center|]]
 

== Troubleshooting ==

'''Issue: The "Your OTP:" prompt never appears and the connection hangs/times out instead'''

Likely cause: You are most likely not on a network from which access to the bwUniCluster 2.0 system is allowed. Please check if you might have to establish a VPN connection first.

 

'''Issue: The system asks for the One-Time Password multiple times'''

Likely cause: Make sure you are using the correct Software Token to generate the One-Time Password.

 

'''Issue: The system asks for the service password multiple times'''

Likely cause: Make sure you are using the service password set on bwIDM and not the password valid for your home institution. Unlike the bwUniCluster 1, the bwUniCluster 2.0 only accepts the service password.

 

'''Issue: There is an error message by the pam_ses_open.sh skript'''

Likely cause: Your account is in the "LOST_ACCESS" state because the entitlement is no longer valid, the questionaire was not filled out or there was a problem during the communication between your home institution and the central bwIDM system. Please try the following steps:

* Log into [https://bwidm.scc.kit.edu bwIDM], look for the bwUniCluster entry and click on '''Registry info'''. Your "Status:" should be "ACTIVE". If it is not, please wait for ten minutes since logging into the bwIDM causes a refresh and the problem might fix itself. If the status does not change to ACTIVE after a longer amount of time, please contact the support channels.

* If you have not filled out the questionaire, please do so on [https://zas.bwhpc.de/shib/en/bwunicluster_survey.php https://zas.bwhpc.de/shib/en/bwunicluster_survey.php] and then wait for about ten minutes before attempting to log into the HPC system again.
 
 

== Allowed activities on login nodes ==

The login nodes of bwUniCluster 2.0 are the access point to the compute system and to your bwUniCluster 2.0 $HOME directory. The login nodes are shared with all the users of bwUniCluster 2.0. 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 postprocessing of your batch jobs.

To guarantee usability for all the users of bwUniCluster 2.0 '''you must not run your compute jobs on the login nodes'''. Compute jobs must be submitted to the
[[bwUniCluster Batch Jobs|queueing 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 postprocessing of batch jobs must also be submitted to the [[bwUniCluster Batch Jobs|queueing system]].
 
 

== SSH Keys ==

In contrast to the bwUniCluster 1 and many other HPC systems it is '''no longer possible to self-manage your SSH Keys by adding them to the ~/.ssh/authorized_keys file'''. Existing files will no longer be evaluated. SSH Keys have to be managed via the central bwIDM system instead. Please refer to the user guide for this functionality:

[[bwUniCluster 2.0 User Access/SSH Keys]]
 
 

= [[First_Steps_on_bwHPC_cluster|First steps on bwUniCluster]] =

First and some important steps on bwUniCluster 2.0 can be found [[First_Steps_on_bwHPC_cluster|here]].
 
 

= Deregistration =
If you plan to permanently leave the bwUniCluster 2.0, follow the deregister checklist:
# Transfer all your data in $HOME and workspace to your local computer/storage and after that clear off all your data
# Visit [https://bwidm.scc.kit.edu/ https://bwidm.scc.kit.edu]
#* Select your home organization from the list and click '''Proceed'''
#* Enter your home-organisational user ID / username and your home-organisational password and click '''Login''' button
#* You will be redirected back to the registration website [https://bwidm.scc.kit.edu/ https://bwidm.scc.kit.edu/]
#* <div>Select '''Registry Info''' of the service '''bwUniCluster''' (on the left hand side) [[File:bwUniCluster_registration_sidebar.png|center|border|]]</div>
#* Click '''Deregister'''
Note that Step 2 will automatically unsubscribe you from the bwunicluster mail list.

BwForCluster User Access

2019-02-01T12:03:41Z

J Krueger: /* Personal registration at bwForCluster */

The usage of bwForCluster is free of charge. bwForClusters are customized to the requirements of particular research areas.
Each bwForCluster is/will be financed by the DFG (German Research Foundation) and by the Ministry of Science, Research and Arts of Baden-Württemberg based on scientifc grant proposal (compare proposals guidelines as per Art. 91b GG).

{| style="width: 100%; border-spacing: 5px;"
| style="text-align:center; color:#000;vertical-align:middle;font-size:75%;" |[[File:Bwforreg.svg|center|border|500px|]]
|-
| style="text-align:center; color:#000;vertical-align:middle;" |
|}

Granting user access to a bwForCluster requires 3 steps:

# Registration of a new or joining an already existing ''rechenvorhaben (RV)'' at [https://www.bwhpc-c5.de/en/ZAS/zas_overview.php "Zentrale Antragsseite (ZAS)"]. An ''RV'' defines the planned compute activities of a group of researchers. As coworker of this group you only need to register your membership in the corresponding ''RV''.
# Application for a [[#Issuing bwForCluster entitlement | bwForCluster entitlement]] issued by your university.
# [[#Personal registration at bwForCluster | Personal registration at assigned cluster site ]] based on approved ''RV'' [[File:Zas assignment icon.svg|25px|]] and issued bwForCluster entitlement [[File:bwfor entitlement icon.svg|25px|]].

 
Step 1 and 2 are pre-steps and requirements of step 3. Moreover, steps 1 and 2 can be done in parallel. The question, at which bwForCluster site to do step 3, will be answered by the cluster assignment team (CAT) based on the data of step 1, i.e. at ''ZAS''.

= ''RV'' registration at ''ZAS'' =

The ''rechenvorhaben (RV)'' registration at ''ZAS'' does '''not''' correspond to typical compute project proposals as for other HPC clusters, since:
* there is no scientific reviewing process
* the registration inquires only brief details and
* it covers a group of coworkers, and
* only the ''RV'' responsible must submit the ''RV''.
 

== How to register? ==
=== Register a new ''RV'' ===
Typically only the leader of a scientific work group or the senior scientist of a research group/collaboration needs to login at
* https://www.bwhpc-c5.de/en/ZAS/bwforcluster_rv_registration.php
and to fill in all mandatory fields of the given web form. Please note that for your convenience you can also switch to the [https://www.bwhpc-c5.de/ZAS/bwforcluster_rechenvorhaben.php german version] of the web form. The submitter of the ''rechenvorhaben (RV)'' will be assigned the role ''RV'' responsible.

The web form consists of the following fields to be filled:
{| style="width:100%;border:3px solid darkgray; margin: 1em auto 1em auto;"
|-
! style="width:25%;padding:2px;margin:3px; background:#AAA; font-size:100%; font-weight:bold; border:1px solid #BBBBBB; text-align:left; color:#000; padding:0.2em 0.4em;"| Field
! style="padding:2px;margin:3px; background:#AAA; font-size:100%; font-weight:bold; border:1px solid #BBBBBB; text-align:left; color:#000; padding:0.2em 0.4em;" | Explanation
|-
!scope="column" {{Lightgray_small}}| RV Title
|scope="column" {{Tab element}} | Define a short title of your planned compute activities, maximum of 255 characters including spaces.
|-
!scope="column" {{Lightgray_small}}| RV Description
|scope="column" {{Tab element}} | Write a short abstract about your planned compute activities (maximum of 2048 characters including spaces). Research groups that contributed to the DFG grant proposal (Art. 91b GG) of the corresponding bwForCluster only need to give reference to that particular proposal.
|-
!scope="column" {{Lightgray_small}}| Scientific field
|scope="column" {{Tab element}} | Tick one or several scientific fields. Once all bwForClusters are up and running the full list of given scientific fields are supported and hence for ''rechenvorhaben (RV)'' applicable. If your ''RV'' does not match any given scientific field, please state your scientific field in the given text box. Grayed out scientific fields indicate that the corresponding bwForCluster(s) is/are not operational yet.
|-
!scope="column" {{Lightgray_small}}| Field of activity
|scope="column" {{Tab element}} | Define if your ''RV'' is primarily for research and/or teaching. If not applicable, use text box.
|-
!scope="column" {{Lightgray_small}}| Parallel paradigm
|scope="column" {{Tab element}} | State what parallel paradigm your code or application uses. Multiple ticks are allowed. Further information can be provided via text box. If you are not sure about it, please state the software you are using.
|-
!scope="column" {{Lightgray_small}}| Programming language
|scope="column" {{Tab element}} | State the programming language(s) of your code or application.
|-
!scope="column" {{Lightgray_small}}| Numerical methods
|scope="column" {{Tab element}} | State the numerical or "calculation" methods your code or application utilises. If you do not know, write "unknown".
|-
!scope="column" {{Lightgray_small}}| Software packages
|scope="column" {{Tab element}} | State all software package you will or want to use for your ''RV''. Also include compiler, MPI and numerical packages (e.g. MKL, FFTW).
|-
!scope="column" {{Lightgray_small}}| Estimated requested computing resources
|scope="column" {{Tab element}} | Roughly estimate how many CPU hours are required to finish your ''RV''. To calculate "CPU hours" multiply "elapsed parallel computing time" with "number of CPU core" per job.
''Example: Your code uses 4 CPU cores and has a wall time of 1h. This makes 4 CPU hours.''
|-
!scope="column" {{Lightgray_small}}| Planned maximum number of parallel used CPU cores per job
|scope="column" {{Tab element}} | Give an upper limit of how many CPU cores per job are required. Please cross-check with your statement about parallel paradigm.
''Obviously, a sequential code can only use 1 CPU core per job.''
|-
!scope="column" {{Lightgray_small}}| Estimated maximal memory requirements per CPU core
|scope="column" {{Tab element}} | Give an upper limit of how much RAM per CPU core your jobs require. Please give a value in GigaBytes.
|-
!scope="column" {{Lightgray_small}}| Estimated requested persistent disk space for the ''RV''
|scope="column" {{Tab element}} | State how much disk space in total you need for your ''RV''. Please give a value in GigaBytes.
''Example: If your RV has 4 more coworker and each of you produces until the end of your RV 20 GigaByte of output, your maximum disk space is 100 GigaByte.''
|-
!scope="column" {{Lightgray_small}}| Estimated maximal temporary disk space per job
|scope="column" {{Tab element}} | State how much space your intermediate files require during a job run. Please give a value in GigaBytes.
''Example: Your final output of your job is 0.1 GigaByte, but during your job 10 temporary files, each with a size of 1 GigaByte, are written to disk, hence your correct answer is 10 GigaByte.''
|-
!scope="column" {{Lightgray_small}}| Institute
|scope="column" {{Tab element}} | State the full name of your Institute.
|-
|}
Note that the fields - name, firstname, organization, mail, und EPPN - are auto-filled and can not be changed. These are your credentials as given by your home organization.

Response
# After submitting you will get an email from ''ZAS'' confirming your submission. With this email you are given an unique * acronym * password Please keep the password enclosed. Only with both, acronym and password, [[BwForCluster_User_Access#Register_for_an_RV_as_coworker | coworkers ]] can be added to your ''rechenvorhaben''.
# The cluster assignment team will be notified immediately about your submission.
# The cluster assignment team decides based on your submitted data which bwForCluster most fits, and submits its decision to ''ZAS''.
# ''ZAS'' notifies you in an email about your assigned bwForCluster and provides website details for [[BwForCluster_User_Access#Personal_registration_at_bwForCluster | step 3 ]].

 

=== Register for an ''RV'' as coworker ===

Each coworker must add herself/himself to a ''rechenvorhaben (RV)''.
To become coworker of an ''RV'', please login at
* https://www.bwhpc-c5.de/en/ZAS/bwforcluster_collaboration.php
and provide the
* acronym
* password
of the ''RV''. Your ''RV'' responsible will provide you with that information.
You will be assigned to role ''RV'' member.

Response
# After submitting the request for participating in an ''RV'', the coworker will receive an email from ''ZAS'' about the further steps (i.e. [[#Personal registration at bwForCluster | personal registration at assigned bwForCluster]]). The membership status in the ''RV'' is set active by default.
# Each person with role ''RV'' responsible or ''RV'' manager will be notified automatically. They can check the list of ''RV'' members at https://www.bwhpc-c5.de/en/ZAS/info_rv.php by clicking on the ''RV'' acronym.
# The ''RV'' responsible can set any ''RV'' coworker to ''RV'' manager and vice versa as well as deactivate/reactivate any ''RV'' coworker or ''RV'' manager.
# An ''RV'' manager can deactivate/reactivate any ''RV'' coworker.



== Roles in an ''RV'' ==
{| style="width:100%;border:3px solid darkgray; margin: 1em auto 1em auto;"
|-
! style="width:25%;padding:2px;margin:3px; background:#AAA; font-size:100%; font-weight:bold; border:1px solid #BBBBBB; text-align:left; color:#000; padding:0.2em 0.4em;"| Role
! style="padding:2px;margin:3px; background:#AAA; font-size:100%; font-weight:bold; border:1px solid #BBBBBB; text-align:left; color:#000; padding:0.2em 0.4em;" | Explanation
|-
!scope="column" {{Lightgray_small}}| RV responsible
|scope="column" {{Tab element}} | Registers the ''rechenvorhaben (RV)'', i.e. the planned compute activities. Can deactivate but also reactivate ''RV'' managers and coworkers. Can promote coworkers to mangers and vice versa.
|-
!scope="column" {{Lightgray_small}}| RV manager
|scope="column" {{Tab element}} | ''RV'' coworker with elevated rights to deactivate and reactivate other ''RV'' coworkers.
|-
!scope="column" {{Lightgray_small}}| RV coworker
|scope="column" {{Tab element}} | Typical user who has registered her/himself via ''RV'' acronym and password.
|-
|}

 

= Issuing bwForCluster entitlement =

Each university issues the bwForCluster entitlement
<pre>http://bwidm.de/entitlement/bwForCluster</pre>
only for their own members.

The bwForCluster entitlement issued by a university assures the operator of a bwForCluster that its university member's compute activities comply with the German Foreign Trade Act (Außenwirtschaftsgesetz - AWG) und German Foreign Trade Regulations (Außenwirtschaftsverordnung - AWV).

The following unversities have already established a process to issue the bwForCluster entitlement:

* [[BwForCluster User Access Members Hochschule Esslingen|Hochschule Esslingen]]
* [[BwCluster User Access Uni Freiburg|University of Freiburg]]
* [[BwForCluster User Access Members Uni Heidelberg|University of Heidelberg]]
* University of Hohenheim
* [http://www.scc.kit.edu/downloads/sdo/Antrag_Zugangsberechtigung_bwForCluster.pdf Karlsruhe Institute of Technology (KIT)]
* [[BwForCluster User Access Members Uni Konstanz|University of Konstanz]]
* [[BwForCluster User Access Members Uni Mannheim|University of Mannheim]]
* [https://www.hlrs.de/solutions-services/academic-users/bwforcluster-access/ University of Stuttgart]
* [[BwForCluster User Access Members Uni Tübingen|University of Tübingen]]
* [[BwForCluster User Access Members Uni Ulm|University of Ulm]]

If you do not find your university in the list above, please contact your local service desk.

= Personal registration at bwForCluster =

Once you have registered your own RV (''rechenvorhaben'')
or a membership in an RV, the cluster assignment team will provide
you with information about your designated cluster. You will receive
an email with a website to create an account for yourself
on that cluster.

Available bwForCluster registration servers (service providers):
{| style="border:3px solid darkgray; margin: 1em auto 1em auto;" width="72%"
|-
!scope="row" {{Darkgray}} | Cluster topic and location
!scope="row" {{Darkgray}} | Registration server
|-
| bwForCluster Chemistry JUSTUS Ulm
| http://bwidm.rz.uni-ulm.de
|-
| bwForCluster MLS&WISO (Production and Development)
| https://bwservices.uni-heidelberg.de
|-
| bwForCluster NEMO Freiburg
| https://bwservices.uni-freiburg.de
|-
| bwForCluster BinAC Tübingen
| https://bwservices.uni-tuebingen.de
|}

Please note, this step is different to your registration at ZAS since
here you register yourself as a person. Only based on your personal credentials
a user account can be generated. However, resource requests of the RV in ZAS
will be cross-checked with the resources consumed by you and your RV coworkers
on this cluster.

After steps 1 and 2 (RV approval and bwForCluster entitlement) please visit the

* bwForCluster ''service provider'' registration website (see table above or email after RV approval):
*# Select your home organization from the list of organizations and click '''Proceed'''.
*# You will be redirected to the ''Identity Provider'' of your home organization.
*# Enter your home-organizational user ID (might be user name, email, ...) and password and click '''Login''' or '''Anmelden'''.
*# When doing this for the first time you need to accept that your personal data is transferred to the ''service provider''.
*# You will be redirected back to the cluster registration website.
*# Select '''Service Description''' of the designated cluster.
*# Click on '''Register''' link to register for this cluster.
*# Read and accept the terms and conditions of use and click on button '''Register'''.
*# Finally you will receive an email with instructions how to login to the cluster (please wait ~15 minutes before trying).
*# Click on '''Set Service Password''' and set a password for the cluster.
*# '''Note: Users from Tübingen accessing the BinAC do not set a separate service password''' and have to use their local account credentials instead.
*# '''Note:''' You can return to the registration website at any time, in order to review your registration details, change/reset your service password or deregister from the service by yourself.

= Login to bwForCluster =

Personalized details about how to login to the cluster are included
in an email send after registration at the bwForCluster service provider.

General instructions for the bwForCluster login can be found here:
{| style="border:3px solid darkgray; margin: 1em auto 1em auto;" width="73%"
|-
!scope="row" {{Darkgray}} | Cluster topic and location
!scope="row" {{Darkgray}} | Login instructions
|-
| bwForCluster Chemistry JUSTUS Ulm
| [[BwForCluster_Chemistry_Login|bwForCluster Chemistry Login]]
|-
| bwForCluster MLS&WISO Production
| [[BwForCluster_MLS&WISO_Production_Login|bwForCluster MLS&WISO Production Login]]
|-
| bwForCluster MLS&WISO Development
| [[BwForCluster_MLS&WISO_Development_Login|bwForCluster MLS&WISO Development Login]]
|-
| bwForCluster NEMO Freiburg
| [[bwForCluster NEMO Login]]
|-
| bwForCluster BinAC Tübingen
| [[bwForCluster BinAC Login]]

|}

 

----
[[Category:Access|bwForCluster]][[Category:bwForCluster_Chemistry]][[Category:bwForCluster_MLS&WISO_Production]][[Category:bwForCluster_MLS&WISO_Development]]

BwForCluster User Access

2019-02-01T12:02:58Z

J Krueger:

The usage of bwForCluster is free of charge. bwForClusters are customized to the requirements of particular research areas.
Each bwForCluster is/will be financed by the DFG (German Research Foundation) and by the Ministry of Science, Research and Arts of Baden-Württemberg based on scientifc grant proposal (compare proposals guidelines as per Art. 91b GG).

{| style="width: 100%; border-spacing: 5px;"
| style="text-align:center; color:#000;vertical-align:middle;font-size:75%;" |[[File:Bwforreg.svg|center|border|500px|]]
|-
| style="text-align:center; color:#000;vertical-align:middle;" |
|}

Granting user access to a bwForCluster requires 3 steps:

# Registration of a new or joining an already existing ''rechenvorhaben (RV)'' at [https://www.bwhpc-c5.de/en/ZAS/zas_overview.php "Zentrale Antragsseite (ZAS)"]. An ''RV'' defines the planned compute activities of a group of researchers. As coworker of this group you only need to register your membership in the corresponding ''RV''.
# Application for a [[#Issuing bwForCluster entitlement | bwForCluster entitlement]] issued by your university.
# [[#Personal registration at bwForCluster | Personal registration at assigned cluster site ]] based on approved ''RV'' [[File:Zas assignment icon.svg|25px|]] and issued bwForCluster entitlement [[File:bwfor entitlement icon.svg|25px|]].

 
Step 1 and 2 are pre-steps and requirements of step 3. Moreover, steps 1 and 2 can be done in parallel. The question, at which bwForCluster site to do step 3, will be answered by the cluster assignment team (CAT) based on the data of step 1, i.e. at ''ZAS''.

= ''RV'' registration at ''ZAS'' =

The ''rechenvorhaben (RV)'' registration at ''ZAS'' does '''not''' correspond to typical compute project proposals as for other HPC clusters, since:
* there is no scientific reviewing process
* the registration inquires only brief details and
* it covers a group of coworkers, and
* only the ''RV'' responsible must submit the ''RV''.
 

== How to register? ==
=== Register a new ''RV'' ===
Typically only the leader of a scientific work group or the senior scientist of a research group/collaboration needs to login at
* https://www.bwhpc-c5.de/en/ZAS/bwforcluster_rv_registration.php
and to fill in all mandatory fields of the given web form. Please note that for your convenience you can also switch to the [https://www.bwhpc-c5.de/ZAS/bwforcluster_rechenvorhaben.php german version] of the web form. The submitter of the ''rechenvorhaben (RV)'' will be assigned the role ''RV'' responsible.

The web form consists of the following fields to be filled:
{| style="width:100%;border:3px solid darkgray; margin: 1em auto 1em auto;"
|-
! style="width:25%;padding:2px;margin:3px; background:#AAA; font-size:100%; font-weight:bold; border:1px solid #BBBBBB; text-align:left; color:#000; padding:0.2em 0.4em;"| Field
! style="padding:2px;margin:3px; background:#AAA; font-size:100%; font-weight:bold; border:1px solid #BBBBBB; text-align:left; color:#000; padding:0.2em 0.4em;" | Explanation
|-
!scope="column" {{Lightgray_small}}| RV Title
|scope="column" {{Tab element}} | Define a short title of your planned compute activities, maximum of 255 characters including spaces.
|-
!scope="column" {{Lightgray_small}}| RV Description
|scope="column" {{Tab element}} | Write a short abstract about your planned compute activities (maximum of 2048 characters including spaces). Research groups that contributed to the DFG grant proposal (Art. 91b GG) of the corresponding bwForCluster only need to give reference to that particular proposal.
|-
!scope="column" {{Lightgray_small}}| Scientific field
|scope="column" {{Tab element}} | Tick one or several scientific fields. Once all bwForClusters are up and running the full list of given scientific fields are supported and hence for ''rechenvorhaben (RV)'' applicable. If your ''RV'' does not match any given scientific field, please state your scientific field in the given text box. Grayed out scientific fields indicate that the corresponding bwForCluster(s) is/are not operational yet.
|-
!scope="column" {{Lightgray_small}}| Field of activity
|scope="column" {{Tab element}} | Define if your ''RV'' is primarily for research and/or teaching. If not applicable, use text box.
|-
!scope="column" {{Lightgray_small}}| Parallel paradigm
|scope="column" {{Tab element}} | State what parallel paradigm your code or application uses. Multiple ticks are allowed. Further information can be provided via text box. If you are not sure about it, please state the software you are using.
|-
!scope="column" {{Lightgray_small}}| Programming language
|scope="column" {{Tab element}} | State the programming language(s) of your code or application.
|-
!scope="column" {{Lightgray_small}}| Numerical methods
|scope="column" {{Tab element}} | State the numerical or "calculation" methods your code or application utilises. If you do not know, write "unknown".
|-
!scope="column" {{Lightgray_small}}| Software packages
|scope="column" {{Tab element}} | State all software package you will or want to use for your ''RV''. Also include compiler, MPI and numerical packages (e.g. MKL, FFTW).
|-
!scope="column" {{Lightgray_small}}| Estimated requested computing resources
|scope="column" {{Tab element}} | Roughly estimate how many CPU hours are required to finish your ''RV''. To calculate "CPU hours" multiply "elapsed parallel computing time" with "number of CPU core" per job.
''Example: Your code uses 4 CPU cores and has a wall time of 1h. This makes 4 CPU hours.''
|-
!scope="column" {{Lightgray_small}}| Planned maximum number of parallel used CPU cores per job
|scope="column" {{Tab element}} | Give an upper limit of how many CPU cores per job are required. Please cross-check with your statement about parallel paradigm.
''Obviously, a sequential code can only use 1 CPU core per job.''
|-
!scope="column" {{Lightgray_small}}| Estimated maximal memory requirements per CPU core
|scope="column" {{Tab element}} | Give an upper limit of how much RAM per CPU core your jobs require. Please give a value in GigaBytes.
|-
!scope="column" {{Lightgray_small}}| Estimated requested persistent disk space for the ''RV''
|scope="column" {{Tab element}} | State how much disk space in total you need for your ''RV''. Please give a value in GigaBytes.
''Example: If your RV has 4 more coworker and each of you produces until the end of your RV 20 GigaByte of output, your maximum disk space is 100 GigaByte.''
|-
!scope="column" {{Lightgray_small}}| Estimated maximal temporary disk space per job
|scope="column" {{Tab element}} | State how much space your intermediate files require during a job run. Please give a value in GigaBytes.
''Example: Your final output of your job is 0.1 GigaByte, but during your job 10 temporary files, each with a size of 1 GigaByte, are written to disk, hence your correct answer is 10 GigaByte.''
|-
!scope="column" {{Lightgray_small}}| Institute
|scope="column" {{Tab element}} | State the full name of your Institute.
|-
|}
Note that the fields - name, firstname, organization, mail, und EPPN - are auto-filled and can not be changed. These are your credentials as given by your home organization.

Response
# After submitting you will get an email from ''ZAS'' confirming your submission. With this email you are given an unique * acronym * password Please keep the password enclosed. Only with both, acronym and password, [[BwForCluster_User_Access#Register_for_an_RV_as_coworker | coworkers ]] can be added to your ''rechenvorhaben''.
# The cluster assignment team will be notified immediately about your submission.
# The cluster assignment team decides based on your submitted data which bwForCluster most fits, and submits its decision to ''ZAS''.
# ''ZAS'' notifies you in an email about your assigned bwForCluster and provides website details for [[BwForCluster_User_Access#Personal_registration_at_bwForCluster | step 3 ]].

 

=== Register for an ''RV'' as coworker ===

Each coworker must add herself/himself to a ''rechenvorhaben (RV)''.
To become coworker of an ''RV'', please login at
* https://www.bwhpc-c5.de/en/ZAS/bwforcluster_collaboration.php
and provide the
* acronym
* password
of the ''RV''. Your ''RV'' responsible will provide you with that information.
You will be assigned to role ''RV'' member.

Response
# After submitting the request for participating in an ''RV'', the coworker will receive an email from ''ZAS'' about the further steps (i.e. [[#Personal registration at bwForCluster | personal registration at assigned bwForCluster]]). The membership status in the ''RV'' is set active by default.
# Each person with role ''RV'' responsible or ''RV'' manager will be notified automatically. They can check the list of ''RV'' members at https://www.bwhpc-c5.de/en/ZAS/info_rv.php by clicking on the ''RV'' acronym.
# The ''RV'' responsible can set any ''RV'' coworker to ''RV'' manager and vice versa as well as deactivate/reactivate any ''RV'' coworker or ''RV'' manager.
# An ''RV'' manager can deactivate/reactivate any ''RV'' coworker.



== Roles in an ''RV'' ==
{| style="width:100%;border:3px solid darkgray; margin: 1em auto 1em auto;"
|-
! style="width:25%;padding:2px;margin:3px; background:#AAA; font-size:100%; font-weight:bold; border:1px solid #BBBBBB; text-align:left; color:#000; padding:0.2em 0.4em;"| Role
! style="padding:2px;margin:3px; background:#AAA; font-size:100%; font-weight:bold; border:1px solid #BBBBBB; text-align:left; color:#000; padding:0.2em 0.4em;" | Explanation
|-
!scope="column" {{Lightgray_small}}| RV responsible
|scope="column" {{Tab element}} | Registers the ''rechenvorhaben (RV)'', i.e. the planned compute activities. Can deactivate but also reactivate ''RV'' managers and coworkers. Can promote coworkers to mangers and vice versa.
|-
!scope="column" {{Lightgray_small}}| RV manager
|scope="column" {{Tab element}} | ''RV'' coworker with elevated rights to deactivate and reactivate other ''RV'' coworkers.
|-
!scope="column" {{Lightgray_small}}| RV coworker
|scope="column" {{Tab element}} | Typical user who has registered her/himself via ''RV'' acronym and password.
|-
|}

 

= Issuing bwForCluster entitlement =

Each university issues the bwForCluster entitlement
<pre>http://bwidm.de/entitlement/bwForCluster</pre>
only for their own members.

The bwForCluster entitlement issued by a university assures the operator of a bwForCluster that its university member's compute activities comply with the German Foreign Trade Act (Außenwirtschaftsgesetz - AWG) und German Foreign Trade Regulations (Außenwirtschaftsverordnung - AWV).

The following unversities have already established a process to issue the bwForCluster entitlement:

* [[BwForCluster User Access Members Hochschule Esslingen|Hochschule Esslingen]]
* [[BwCluster User Access Uni Freiburg|University of Freiburg]]
* [[BwForCluster User Access Members Uni Heidelberg|University of Heidelberg]]
* University of Hohenheim
* [http://www.scc.kit.edu/downloads/sdo/Antrag_Zugangsberechtigung_bwForCluster.pdf Karlsruhe Institute of Technology (KIT)]
* [[BwForCluster User Access Members Uni Konstanz|University of Konstanz]]
* [[BwForCluster User Access Members Uni Mannheim|University of Mannheim]]
* [https://www.hlrs.de/solutions-services/academic-users/bwforcluster-access/ University of Stuttgart]
* [[BwForCluster User Access Members Uni Tübingen|University of Tübingen]]
* [[BwForCluster User Access Members Uni Ulm|University of Ulm]]

If you do not find your university in the list above, please contact your local service desk.

= Personal registration at bwForCluster =

Once you have registered your own RV (''rechenvorhaben'')
or a membership in an RV, the cluster assignment team will provide
you with information about your designated cluster. You will receive
an email with a website to create an account for yourself
on that cluster.

Available bwForCluster registration servers (service providers):
{| style="border:3px solid darkgray; margin: 1em auto 1em auto;" width="72%"
|-
!scope="row" {{Darkgray}} | Cluster topic and location
!scope="row" {{Darkgray}} | Registration server
|-
| bwForCluster Chemistry JUSTUS Ulm
| http://bwidm.rz.uni-ulm.de
|-
| bwForCluster MLS&WISO (Production and Development)
| https://bwservices.uni-heidelberg.de
|-
| bwForCluster NEMO Freiburg
| https://bwservices.uni-freiburg.de
|-
| bwForCluster BinAC Tübingen
| https://bwservices.uni-tuebingen.de
|}

Please note, this step is different to your registration at ZAS since
here you register yourself as a person. Only based on your personal credentials
a user account can be generated. However, resource requests of the RV in ZAS
will be cross-checked with the resources consumed by you and your RV coworkers
on this cluster.

After steps 1 and 2 (RV approval and bwForCluster entitlement) please visit the

* bwForCluster ''service provider'' registration website (see table above or email after RV approval):
*# Select your home organization from the list of organizations and click '''Proceed'''.
*# You will be redirected to the ''Identity Provider'' of your home organization.
*# Enter your home-organizational user ID (might be user name, email, ...) and password and click '''Login''' or '''Anmelden'''.
*# When doing this for the first time you need to accept that your personal data is transferred to the ''service provider''.
*# You will be redirected back to the cluster registration website.
*# Select '''Service Description''' of the designated cluster.
*# Click on '''Register''' link to register for this cluster.
*# Read and accept the terms and conditions of use and click on button '''Register'''.
*# Finally you will receive an email with instructions how to login to the cluster (please wait ~15 minutes before trying).
*# Click on '''Set Service Password''' and set a password for the cluster.
*# '''Note: Tübinger users accessing the BinAC do not set a separate service password''' and have to use their local account credentials instead.
*# '''Note:''' You can return to the registration website at any time, in order to review your registration details, change/reset your service password or deregister from the service by yourself.

= Login to bwForCluster =

Personalized details about how to login to the cluster are included
in an email send after registration at the bwForCluster service provider.

General instructions for the bwForCluster login can be found here:
{| style="border:3px solid darkgray; margin: 1em auto 1em auto;" width="73%"
|-
!scope="row" {{Darkgray}} | Cluster topic and location
!scope="row" {{Darkgray}} | Login instructions
|-
| bwForCluster Chemistry JUSTUS Ulm
| [[BwForCluster_Chemistry_Login|bwForCluster Chemistry Login]]
|-
| bwForCluster MLS&WISO Production
| [[BwForCluster_MLS&WISO_Production_Login|bwForCluster MLS&WISO Production Login]]
|-
| bwForCluster MLS&WISO Development
| [[BwForCluster_MLS&WISO_Development_Login|bwForCluster MLS&WISO Development Login]]
|-
| bwForCluster NEMO Freiburg
| [[bwForCluster NEMO Login]]
|-
| bwForCluster BinAC Tübingen
| [[bwForCluster BinAC Login]]

|}

 

----
[[Category:Access|bwForCluster]][[Category:bwForCluster_Chemistry]][[Category:bwForCluster_MLS&WISO_Production]][[Category:bwForCluster_MLS&WISO_Development]]

BwUniCluster 2.0 User Access

2018-03-06T09:41:54Z

J Krueger: /* Step A: bwUniCluster entitlement for registration */