Compact guide to Initial Project Letters (PRACE)
Scope
The content of this page is of interest for any principal investigators (PI) and persons of contact (PC) of SuperMUC-NG projects. Here you find explanatory/additional information to both the initial project information letter which you received from LRZ via ticket after approval of your project.
Mentoring Information Letter
Assignment of a Mentor to your Project
Initial Project Information Letter (via Ticket from LRZ)
General information / useful links
General | |
---|---|
SuperMUC-NG | SuperMUC-NG documentation |
https://servicedesk.lrz.de/ | Please, contact LRZ Servicedesk to report incidents, other technical problems and service requests. |
Large-scale projects only | |
Contact your mentor | Do you have any question, which does not fit into a service request or incident ticket? Please contact your mentor! |
Project Activation Process
The project activation includes the registration of user IDs on SuperMUC-NG in the following groups, which are indexed by the according suffix:
- permission to use compute ressources: PROJECT_ID-c,
- creation of directories on LRZ file system: PROJECT_ID-d.
Every day at 8 o’clock the databases are updated by carrying out the provisioning process.
Please consider: The user IDs of your project do not appear in your project view of the LRZ IDM Portal. All user IDs are listed within the general SuperMUC-NG project "hpcusers". You are not project manager of "hpcusers". The user IDs can be found in the new IDM portal for project groups https://idmportal2.sim.lrz.de/ .
User Account Activation Process
Role | Action | |
---|---|---|
Step 1 | I am
| Please contact your master user or the principal investigator (PI) or person of contact (PC) of your project. |
Step 2 | master user (PI/PC) | Please open a service request ticket to add/activate new members within your project. You will receive the user ID and the activation notification for this ID in the relevant project via this ticket. Please provide this information to the user. The user ID of existing users will not change. |
Step 3 | master user (PI/PC) | Important: Both the access to SuperMUC-NG and the data transfer to/from SuperMUC-NG via Globus Online require a static and public IP address of the computer which directly accesses the login nodes of the supercomputer (user's workstation, gateway etc.)! Please open another service request ticket to activate this IP address. You will receive a notification about the activation via this ticket. |
Step 4 | user | Steps to access the supercomputer:
|
Local Project ID
You will need the local project ID for both communication with LRZ and for administrative actions within your project by utilizing the service-request templates at LRZ:
For details please visit Access and Login to SuperMUC-NG.
Password Reset and Export Control Regulations
In case of doing a password reset, the user has to comply with the export control regulations. Additionally, the master user (PI and/or PC) will be asked to comply with those regulations, too. Please visit the section "Richtlinien im HPC-Bereich" at https://www.lrz.de/wir/regelwerk/ to get explanatory information on that topic and usage conditions with respect to the supercomputer at LRZ.
Did you encounter problems with password reset or do you have other technical problems? Please open a ticket via LRZ Servicedesk.
Two-Factor-Authentication (2FA)
In order to improve the security of SuperMUC-NG, LRZ has changed the authentication procedure on all login nodes to two-factor authentication (2FA).
Associated Project Partners
Does your project application list associated project partners, who will also work on the supercomputer in terms of consuming compute time?
If so, then we kindly ask you to send a service request in order to apply for according user IDs.
LRZ distinguishes between project partners and project members.