BwForCluster User Access: Difference between revisions
Jump to navigation
Jump to search
m (Changed redirect target from Registration/bwForCluster to Registration) Tag: Redirect target changed |
|||
(116 intermediate revisions by 10 users not shown) | |||
Line 1: | Line 1: | ||
#REDIRECT [[Registration]] |
|||
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 [[#Issueing 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|]]. |
|||
<br> |
|||
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''. |
|||
<br> |
|||
== 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. |
|||
<span style="font-weight:bold;font-size:110%;">Response</span> |
|||
# After submitting you will get an email from ''ZAS'' confirming your submission. With this email you are given an unique<br>* acronym<br>* password<br>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 ]]. |
|||
<br> |
|||
=== 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. |
|||
<span style="font-weight:bold;font-size:110%;">Response</span> |
|||
# 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. |
|||
<!--=== RV extension === |
|||
Any RV is restricted to 1 year duration and the given compute resources during registration. Only the RV responsible can apply for an extension of the RV. The extension can be the duration by another year or the increase of computational resources. In any case, the RV responsible must login at: |
|||
<br><br> |
|||
<span style="font-weight:bold;font-size:115%;">Response</span> |
|||
# After submission the RV responsible will receive an email from ZAS--> |
|||
== 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. |
|||
|- |
|||
|} |
|||
<br> |
|||
= Issueing 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]] |
|||
* [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 |
|||
| http://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). |
|||
*# Optionally but strongly recommended: Click on '''Set Service Password''' and set a password for the cluster. |
|||
*# '''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]] |
|||
|} |
|||
<br> |
|||
---- |
|||
[[Category:Access|bwForCluster]][[Category:bwForCluster_Chemistry]][[Category:bwForCluster_MLS&WISO_Production]][[Category:bwForCluster_MLS&WISO_Development]] |
Latest revision as of 17:59, 17 February 2022
Redirect to: