= Access to bwForCluster for members of Tübingen University =

== Login prerequisites ==

* A valid ZDV account is required for access to the bwForCluster.

* As part of the login procedure, you will get a page that shows the data on your account that will be transferred from Tübingen University to the cluster. This page shows your entitlements. It should list the entitlement: <pre>http://bwidm.de/entitlement/bwForCluster </pre> If it does not, please write an email to hpcmaster(AT)uni-tuebingen.de to receive the entitlement.

== ZDV Account ==

Enrolled students of Tübingen University usually have a ZDV account
granting access to ZDV compute resources such as the bwUniCluster.

Faculty and staff members of Tübingen University can receive this account upon
request of their department head (if they don't already have it).

For more information please visit the related ZDV web pages: http://www.zdv.uni-tuebingen.de/kontakt-antraege-beratung/antraege.html

== Terms of Use ==

As with any other ZDV service, users of bwForCluster must strictly adhere to the [http://www.zdv.uni-tuebingen.de/wir-ueber-uns/benutzungsordnung.html ZDV terms of use].

BwForCluster User Access

2014-12-17T10:54:21Z

M Dynowski: /* Issueing bwForCluster entitlement */

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 your '''''Rechenvorhaben''''' at [https://www.bwhpc-c5.de/ZAS/zas_uebersicht.php "Zentrale Antragsseite (ZAS)"]. A ''rechenvorhaben'' (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 [[#Issueing bwForCluster entitlement | bwForCluster entitlement]] issued by your university,
# 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 ''rechenvorhaben''.
 

== How to register? ==
=== 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 '''''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'' applicable. If your ''rechenvorhaben'' 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 ''rechenvorhaben''
|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#Coworkers|coworkers]] can be added to your ''rechenvorhaben''.
# The cluster assignment team will be notified immediately about your submission.
# The cluster assignment team decides within 2 working days and 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]].
 

=== Coworkers ===
Important, each coworker must add herself/himself to a ''rechenvorhaben'', since only via personal authentication the correctness of personal credentials (provided by your home organization) can be guaranteed. To become coworker of a ''rechenvorhaben'', please login at
* https://www.bwhpc-c5.de/en/ZAS/bwforcluster_collaboration.php
and provide correct
* password
* acronym
of the ''rechenvorhaben''. Your RV responsible will provide you with that information. The submitter will be assigned the role '''RV member'''.
 
Response
# After submitting the request for participating a '''RV''', the coworker will receive an email from ZAS about the process. The membership status in the '''RV''' is set active by default.
# Each person with the role of '''RV responsible''' or '''RV manager''' will be notified. Any of these persons can crosscheck via https://www.bwhpc-c5.de/en/ZAS/info_compute_project.php and clicking on the correct RV acronym the correctness of the process.
# 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'''.
# Any RV manager can deactivate/reactivate any '''RV coworker'''.
 



== Roles in a 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}} | Defines a RV coworker with rights to deactivate and reactivate RV coworkers.
|-
!scope="column" {{Lightgray_small}}| RV coworker
|scope="column" {{Tab element}} | Registers her/his membership via RV acronym and password.
|-
|}

 

= Issueing bwForCluster entitlement =

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

The following unversities have already established a process to issue the bwForCluster entitlement:
* [http://www.scc.kit.edu/downloads/sdo/Antrag_Zugangsberechtigung_bwForCluster_v2.pdf KIT]
* [[BwForCluster User Access Members Uni Ulm|Ulm University]]
* [[BwForCluster User Access Members Uni Tübingen|Tübingen University]]
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 at ZAS, the cluster assignment team will provide you with information about your designated cluster. You will receive an email providing you with the website to finally register yourself for the this cluster.

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

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

* ''Service provider'' cluster registration website (link to this website in 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).
*# Optionally but strongly recommended: Click on '''Set Service Password''' and set a password for this cluster.

----
[[Category:Access|bwForCluster]][[Category:bwForCluster_Chemistry]]

BwUniCluster 2.0 User Access

2014-02-12T15:41:50Z

M Dynowski: /* Step A: bwUniCluster entitlement for registration */

{| style="border-style: solid; border-width: 1px"
! Navigation: [[BwHPC_Best_Practices_Repository|bwHPC BPR]] / [[BwUniCluster_User_Guide|bwUniCluster]]
|}



'''''bwUniCluster''''' 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)
* Ruprecht-Karls-Universität Heidelberg
* Ulm University
* University of Hohenheim
* University of Konstanz
* University of Mannheim
* University of Stuttgart
 
To log on '''''bwUniCluster''''' an 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''''' 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 ==
Each university issues the bwUniCluster entitlement '''only''' for their own members. Details on the issuing process and/or the entitlement application forms are listed hereafter:
* [https://www.bwhpc-c5.uni-freiburg.de/bwunicluster/freischaltung-uni-account Albert Ludwig University of Freiburg]
* [http://www.zdv.uni-tuebingen.de/dienstleistungen/computing/zugang-zu-den-ressourcen.html Eberhard Karls University of Tübingen]
* [http://www.scc.kit.edu/downloads/sdo/Antrag_Benutzernummer_bwUniCluster.pdf KIT]
* [[Media:unknown.pdf‎|Ruprecht-Karls-Universität Heidelberg]]
* [[BWUniCluster_User_Access_Members_Uni_Ulm|Ulm University]]
* [http://www.rz.uni-hohenheim.de/bwhpc University of Hohenheim]
* [[BWUniCluster_User_Access_Members_Uni_Konstanz|University of Konstanz]]
* [[Media:unknown.pdf‎|University of Mannheim]]
* [[Media:unknown.pdf‎|University of Stuttgart]]
 

== Step B: Web Registration ==
After step A, i.e., after issueing the bwUniCluster entitlement, please visit:
* [https://bwidm.scc.kit.edu/ https://bwidm.scc.kit.edu]
*# Select your home organization from the list and click '''Proceed'''
*# You will be directed to the ''Identity Provider'' of your home organisation
*# 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 '''bwUniCluster Service Description''' (on the left hand side) [[File:bwUniCluster_registration_sidebar.png|center|border|]]</div>
*# Click '''Register'''
*# Finally
*#* for all non-KIT members '''mandatorily''' set a service password for authentication on bwUniCluster
*#* for KIT members '''optionally''' set a service password for authentication on bwUniCluster


 

== Changing Password ==
By default, for KIT members your bwUniCluster '''password''' to log on matches that one of your KIT
account, while for all non-KIT members your bwUniCluster '''password''' is that one you saved during the web registration (compare step 7 of chapter 1.2).
At any time, you can set a new bwUniCluster password via the registration website [https://bwidm.scc.kit.edu/ https://bwidm.scc.kit.edu] by carrying out the following steps:
# visit [https://bwidm.scc.kit.edu/ https://bwidm.scc.kit.edu] and select your home organization
# authenticate yourself via your home-organizational user id / username and your home-organizational password
# find on the left side '''bwUniCluster''' and select '''Set Service Password'''
# set new service, i.e. bwUniCluster, password, repeat it and click '''Save''' button.
# the page answers e.g. "Das Passwort wurde bei dem Dienst geändert" ("password has been changed")
# proceed to log in using the new password in the next step
 

== Contact ==
If you have questions or problems concerning registration, please [[BwUniCluster_Contact_and_Support#Registration|contact your local hotline]].
 

= Login =
After finishing the web registration '''''bwUniCluster''''' is ready for your '''SSH''' based login.
'''''bwUniCluster''''' has two dedicated login nodes. The selection of the login node is done automatically and is based on a round-robin scheduling. Logging in another time the session might run
on the other login node.

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

A connection to '''''bwUniCluster''''' can be established by the command:

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

If you are using '''OpenSSH''' (usually installed on Linux based systems) and you want to use a GUI-based application on '''''bwUniCluster''''' you should use the
''ssh'' command with the option ''-X''

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

== About UserID / Username ==

'''<UserID>''' of the ssh command is a placeholder for your '''''username''''' at your home
organization together with a '''''prefix''''' as followed:

* Freiburg: <UserID> = fr_username
* Heidelberg: <UserID> = hd_username
* Hohenheim: <UserID> = ho_username
* KIT: <UserID> = username ''(without any prefix)''
* Konstanz: <UserID> = kn_username
* Mannheim: <UserID> = ma_username
* Stuttgart: <UserID> = st_username
* Tübingen: <UserID> = tu_username
* Ulm: <UserID> = ul_username

== Allowed activities on login nodes ==

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

= First steps on bwUniCluster =

For setting up your environment to use compilers and installed software please visit:
* [[BwUniCluster_Environment_Modules|bwUniCluster user environment]]

For guides on how to submit compute jobs to bwUniCluster please visit:
* [[bwUniCluster Batch Jobs|bwUniCluster batch jobs]]

----

[[Category:bwHPC|Access bwUniCluster]]
[[Category:bwUniCluster|Access]]