Difference between revisions of "BwForCluster User Access"

From bwHPC Wiki
Jump to: navigation, search
Line 51: Line 51:
 
|-
 
|-
 
!scope="column" {{Lightgray_small}}| Field of activity
 
!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" {{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" {{Lightgray_small}}| Parallel paradigm
Line 63: Line 63:
 
|-
 
|-
 
!scope="column" {{Lightgray_small}}| Software packages
 
!scope="column" {{Lightgray_small}}| Software packages
|scope="column" {{Tab element}} | State all software package you will or want to use for your compute project. Also include compiler, MPI and numerical packages (e.g. MKL, FFTW).
+
|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" {{Lightgray_small}}| Estimated requested computing resources
|scope="column" {{Tab element}} | Roughly estimate how many CPU hours are required to finish your compute project. To calculate "CPU hours" multiply "elapsed parallel computing time" with "number of CPU core" per job.
+
|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.''
 
''Example: Your code uses 4 CPU cores and has a wall time of 1h. This makes 4 CPU hours.''
 
|-
 
|-
Line 76: Line 76:
 
|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" {{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 this project
+
!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 compute project. Please give a value in GigaBytes.
+
|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 compute project has 4 more coworker and each of you produces until the end of your project 20 GigaByte of output, your maximum disk space is 100 GigaByte.''
+
''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" {{Lightgray_small}}| Estimated maximal temporary disk space per job
Line 91: Line 91:
 
<br><br>
 
<br><br>
 
<span style="font-weight:bold;font-size:115%;">Response</span>
 
<span style="font-weight:bold;font-size:115%;">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#Coworkers|coworkers]] can be added to your compute project.
+
# 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#Coworkers|coworkers]] can be added to your ''rechenvorhaben''.
 
# The cluster assignment team will be notified immediately about your submission.
 
# 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.
 
# 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.
Line 98: Line 98:
   
 
=== Coworkers ===
 
=== Coworkers ===
Important, each coworker must add herself/himself to compute projects, since only via personal authentication the correctness of personal credentials (provided by your home organization) can be guaranteed. To become coworker of a compute project, please login at
+
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
 
* https://www.bwhpc-c5.de/en/ZAS/bwforcluster_collaboration.php
 
and provide correct
 
and provide correct
 
* password
 
* password
 
* acronym
 
* acronym
of the compute project. Your project responsible will provide you with that information. The submitter will be assigned the role '''project member'''.
+
of the ''rechenvorhaben''. Your RV responsible will provide you with that information. The submitter will be assigned the role '''RV member'''.
 
<br><br>
 
<br><br>
 
<span style="font-weight:bold;font-size:115%;">Response</span>
 
<span style="font-weight:bold;font-size:115%;">Response</span>
# After submitting the request for participating a compute project, the coworker will receive an email from ZAS about the process. The membership status in the compute project is set active by default.
+
# 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 '''project responsible''' and '''project 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 project acronym the correctness of the process.
+
# 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 project responsible can set any '''project coworker''' to '''project manager''' and vice versa as well as deactivate/reactivate any '''project coworker''' or '''project manager'''.
+
# 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 project manager can deactivate/reactivate any '''project coworker'''.
+
# Any RV manager can deactivate/reactivate any '''RV coworker'''.
 
<br>
 
<br>
   
<!--=== Compute project extension ===
+
<!--=== RV extension ===
Any compute project is restricted to 1 year duration and the given compute resources during registration. Only the project responsible can apply for an extension of the compute project. The extension can be the duration by another year or the increase of computational resources. In any case, the project responsible must login at:
+
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>
 
<br><br>
 
<span style="font-weight:bold;font-size:115%;">Response</span>
 
<span style="font-weight:bold;font-size:115%;">Response</span>
# After submission the project responsible will receive an email from ZAS-->
+
# After submission the RV responsible will receive an email from ZAS-->
   
 
== Roles in a RV ==
 
== Roles in a RV ==
Line 125: Line 125:
 
|-
 
|-
 
!scope="column" {{Lightgray_small}}| RV responsible
 
!scope="column" {{Lightgray_small}}| RV responsible
|scope="column" {{Tab element}} | Registers compute projects. Can deactivate but also reactivate project managers and coworkers. Can promote coworkers to mangers and vice versa.
+
|scope="column" {{Tab element}} | Registers the RV (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" {{Lightgray_small}}| RV manager
|scope="column" {{Tab element}} | Defines a project coworker with rights to deactivate and reactivate project coworkers.
+
|scope="column" {{Tab element}} | Defines a RV coworker with rights to deactivate and reactivate RV coworkers.
 
|-
 
|-
 
!scope="column" {{Lightgray_small}}| RV coworker
 
!scope="column" {{Lightgray_small}}| RV coworker
|scope="column" {{Tab element}} | Registers her/his membership via compute project acronym and password.
+
|scope="column" {{Tab element}} | Registers her/his membership via RV acronym and password.
 
|-
 
|-
 
|}
 
|}
Line 149: Line 149:
 
= Personal registration at bwForCluster =
 
= Personal registration at bwForCluster =
   
Once you have registered your compute project at ZAS by filling a short online form, the cluster assignment team will provide you with information about your designated bwForCluster - basically providing your with the correct website to finally register yourself for the designated cluster.
+
Once you have registered your RV or membership in a RV at ZAS by filling a short online form, the cluster assignment team will provide you with information about your designated bwForCluster - basically providing your with the correct website to finally register yourself for the designated cluster.
   
Please note, this step is different to your registration at ZAS since here you do not register your compute project but yourself as a person. Only based on your personal credentials a user account can be generated. However, defined resource requests (compare your compute project registration) will be cross-checked with the resources consumed by you and your coworkers of the compute project.
+
Please note, this step is different to your registration at ZAS since here you do not register your RV or your membership in a 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 ''rechenvorhaben''.
   
   
After step 1 and 2, i.e., approval of your compute project and issued bwForCluster entitlement, please visit:
+
After step 1 and 2, i.e., approval of your (membership in a) ''rechenvorhaben'' and issued bwForCluster entitlement, please visit:
 
* Cluster registration website (details given by CAT)
 
* Cluster registration website (details given by CAT)
 
*# Select your home organization from the list and click '''Proceed'''
 
*# Select your home organization from the list and click '''Proceed'''

Revision as of 14:59, 4 December 2014

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).

Bwforreg.svg


Granting user access to a bwForCluster requires 3 steps:

  1. Registration of your Rechenvorhaben at "Zentrale Antragsseite (ZAS)". A rechenvorhaben (RV) defines the planed compute activities of a group of researchers. As coworker of that group you only need to register your membership in a RV.
  2. Application for bwForCluster entitlement issued by your university,
  3. Personal registration at assigned cluster site based on approved RV Zas assignment icon.svg and issued bwForCluster entitlement Bwfor entitlement icon.svg.


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.


1 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
  • it covers a group of coworkers and
  • only the RV responsible must submit it.


1.1 How to register?

1.1.1 RV

Typically only the leader of a scientific work group or the senior scientist of research group/collaboration needs to login at

and to fill in all mandatory fields of the given web form. Please note that for your convenience you can also switch to the german version of the web form. The submitter of the RV will be assigned the role RV responsible.

The web formular consists of the following fields to be filled:

Field Explanation
Title Define a short title of your planned compute activities, maximum of 255 characters including spaces.
Description 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.
Scientific field 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.
Field of activity Define if your RV is primarily for research and/or teaching. If not applicable, use text box.
Parallel paradigm 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.
Programming language State the programming language(s) of your code or application.
Numerical methods State the numerical or "calculation" methods your code or application utilises. If you do not know, write "unknown".
Software packages State all software package you will or want to use for your RV. Also include compiler, MPI and numerical packages (e.g. MKL, FFTW).
Estimated requested computing resources 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.

Planned maximum number of parallel used CPU cores per job 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.

Estimated maximal memory requirements per CPU core Give an upper limit of how much RAM per CPU core your jobs require. Please give a value in GigaBytes.
Estimated requested persistent disk space for the rechenvorhaben 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.

Estimated maximal temporary disk space per job 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.

Institute 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

  1. 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, coworkers can be added to your rechenvorhaben.
  2. The cluster assignment team will be notified immediately about your submission.
  3. 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.
  4. ZAS notifies you in an email about your assigned bwForCluster and provides website details for step 3.


1.1.2 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

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

  1. 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.
  2. 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.
  3. 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.
  4. Any RV manager can deactivate/reactivate any RV coworker.



1.2 Roles in a RV

Role Explanation
RV responsible Registers the RV (planned compute activities). Can deactivate but also reactivate RV managers and coworkers. Can promote coworkers to mangers and vice versa.
RV manager Defines a RV coworker with rights to deactivate and reactivate RV coworkers.
RV coworker Registers her/his membership via RV acronym and password.



2 Issueing bwForCluster entitlement

Each university issues the bwForCluster entitlement only for their own members.

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

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


3 Personal registration at bwForCluster

Once you have registered your RV or membership in a RV at ZAS by filling a short online form, the cluster assignment team will provide you with information about your designated bwForCluster - basically providing your with the correct website to finally register yourself for the designated cluster.

Please note, this step is different to your registration at ZAS since here you do not register your RV or your membership in a 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 rechenvorhaben.


After step 1 and 2, i.e., approval of your (membership in a) rechenvorhaben and issued bwForCluster entitlement, please visit:

  • Cluster registration website (details given by CAT)
    1. Select your home organization from the list and click Proceed
    2. You will be directed to the Identity Provider of your home organisation
    3. Enter your home-organisational user ID / username and your home-organisational password and click Login button
    4. You will be redirected back to the cluster registration website
    5. Select bwForCluster Service Description (on the left hand side)
    6. Click Register
    7. Finally
      • optionally set a service password for authentication on bwForCluster