bwHPC Wiki - User contributions [en]

Batch Jobs - bwUniCluster Features

2015-05-21T11:00:32Z

A Fuchs: /* msub -q queues */

This article contains information on features of the [[Batch_Jobs|batch job system]] only applicable on bwUniCluster.

= Job Submission =
== msub Command ==
The bwUniCluster supports the following additional msub option(s):
{| style="width:100%; vertical-align:top; background:#f5fffa;border:1px solid #000000;padding:1px"
! colspan="3" style="background-color:#999999;padding:3px"| bwUniCluster additional msub Options
|-
! style="width:15%;height=20px; text-align:left;padding:3px"|Command line
! style="width:20%;height=20px; text-align:left;padding:3px"|Script
! style="width:65%;height=20px; text-align:left;padding:3px"|Purpose
|- style="vertical-align:top;"
| style="height=20px; text-align:left;padding:3px" | -I
|
| style="height=20px; text-align:left;padding:3px" | Declares the job is to be run interactively.
|}
 
 

=== msub -l ''resource_list'' ===
No deviation or additional features to general [[Batch_Jobs|batch job]] setting.
=== msub -q ''queues'' ===

Compute resources such as walltime, nodes and memory are restricted and must fit into '''queues'''. Since requested compute resources are NOT always automatically mapped to the correct queue class, you must add to your msub command the correct queue class. Details are:

{| border="1", style="width:100%; vertical-align:top; background:#f5fffa;border:1px solid #000000;padding:1px"
! colspan="6" style="background-color:#999999;padding:3px"| msub -q ''queue''
|- style="width:10%;height=20px; text-align:left;"
! style="width:10%;padding:3px"| ''queue''
! style="width:5%;padding:3px"| ''node''
! style="width:15%;padding:3px"| ''default resources''
! style="padding:3px"| ''minimum resources''
! style="padding:3px"| ''maximum resources''
! style="padding:3px"| ''node access policy''
|- style="vertical-align:top; height=20px; text-align:left"
| style="padding:3px"| develop
| style="padding:3px"| thin
| style="width:15%;padding:3px"| ''walltime''=00:10:00,''procs''=1, ''mem''=4000mb
| style="padding:3px"| ''nodes''=1
| style="padding:3px"| ''nodes''=1:''ppn''=16, ''walltime''=00:30:00
| style="padding:3px"| shared
|- style="vertical-align:top; height=20px; text-align:left"
| style="width:10%;padding:3px" | singlenode
| style="padding:3px"| thin
| style="padding:3px"| ''walltime''=00:30:01,''procs''=1, mem''=4000mb
| style="padding:3px"| ''nodes''=1, ''walltime''=00:30:01
| style="padding:3px"| ''nodes''=1:''ppn''=16, ''walltime''=3:00:00:00
| style="padding:3px"| shared
|- style="vertical-align:top; height=20px; text-align:left"
| style="width:10%;vertical-align:top;height=20px; text-align:left;padding:3px" | multinode
| style="padding:3px"| thin
| style="padding:3px"| ''walltime''=00:10:00,''procs''=1, ''mem''=4000mb
| style="padding:3px"| ''nodes''=2
| style="padding:3px"| ''nodes''=16:''ppn''=16, ''walltime''=2:00:00:00
| style="padding:3px"| singlejob
|- style="vertical-align:top; height=20px; text-align:left"
| style="width:10%;vertical-align:top;height=20px; text-align:left;padding:3px" | verylong
| style="padding:3px"| thin
| style="padding:3px"| ''walltime''=3:00:00:01,''procs''=1, ''mem''=4000mb
| style="padding:3px"| ''nodes''=1'', walltime''=3:00:00:01
| style="padding:3px"| ''nodes=1:''ppn''=16, ''walltime''=6:00:00:00
| style="padding:3px"| shared
|- style="vertical-align:top; height=20px; text-align:left"
| style="width:10%;padding:3px" | fat
| style="padding:3px"| fat
| style="padding:3px"| ''walltime''=00:10:00,''procs''=1, ''mem''=32000mb
| style="padding:3px"| ''nodes''=1
| style="padding:3px"| ''nodes''=1:''ppn''=32, ''walltime''=3:00:00:00
| style="padding:3px"| shared
|-
|}
Note that ''node access policy''=singlejob means that, irrespected of the requested number of cores, node access is exclusive.
Default resources of a queue class defines walltime, processes and memory if not explicitly given with msub command. Resource list acronyms ''walltime'', ''procs'', ''nodes'' and ''ppn'' are described [[Batch_Jobs#msub_-l_resource_list|here]].

==== Queue class examples ====

* To run your batch job longer than 3 days, please use$ msub -q verylong.

* To run your batch job on one of the [[BwUniCluster_File_System#Components_of_bwUniCluster|fat nodes]], please use$ msub -q fat.
 
 

= Environment Variables for Batch Jobs =
The bwUniCluster expands the [[Batch_Jobs#Environment Variables for Batch Jobs|common set of MOAB environment variables]] by the following variable(s):
{| style="width:100%; vertical-align:top; background:#f5fffa;border:1px solid #000000;padding:1px"
! colspan="3" style="background-color:#999999;padding:3px"| bwUniCluster specific MOAB variables
|- style="width:25%;height=20px; text-align:left;padding:3px"
! style="width:20%;height=20px; text-align:left;padding:3px"| Environment variables
! style="height=20px; text-align:left;padding:3px"| Description
|-
| style="width:20%;height=20px; text-align:left;padding:3px" | MOAB_SUBMITDIR
| style="height=20px; text-align:left;padding:3px"| Directory of job submission
|}
 
Since the work load manager MOAB on [[bwUniCluster]] uses the resource manager SLURM, the following environment variables of SLURM are added to your environment once your job has started:
{| style="width:100%; vertical-align:top; background:#f5fffa;border:1px solid #000000;padding:1px"
! colspan="3" style="background-color:#999999;padding:3px"| SLURM variables
|- style="width:25%;height=20px; text-align:left;padding:3px"
! style="width:20%;height=20px; text-align:left;padding:3px"| Environment variables
! style="height=20px; text-align:left;padding:3px"| Description
|-
| style="width:20%;height=20px; text-align:left;padding:3px" | SLURM_JOB_CPUS_PER_NODE
| style="height=20px; text-align:left;padding:3px"| Number of processes per node dedicated to the job
|-
| style="width:20%;height=20px; text-align:left;padding:3px" | SLURM_JOB_NODELIST
| style="height=20px; text-align:left;padding:3px"| List of nodes dedicated to the job
|-
| style="width:20%;height=20px; text-align:left;padding:3px" | SLURM_JOB_NUM_NODES
| style="height=20px; text-align:left;padding:3px"| Number of nodes dedicated to the job
|-
| style="width:20%;height=20px; text-align:left;padding:3px" | SLURM_MEM_PER_NODE
| style="height=20px; text-align:left;padding:3px"| Memory per node dedicated to the job
|-
| style="width:20%;height=20px; text-align:left;padding:3px" | SLURM_NPROCS
| style="height=20px; text-align:left;padding:3px"| Total number of processes dedicated to the job
|}
 
 
== Node Monitoring ==

By default nodes are not used exclusive anless they are requested with ''-l naccesspolicy=singlejob'' as described [[Batch_Jobs#msub_-l_resource_list|here]]. 
If a Job runs exclusive on one node you may do a ssh login to that node. To get the nodes of your job need to read the environment variable SLURM_JOB_NODELIST, e.g.

echo $SLURM_JOB_NODELIST > nodelist

= Interactive Jobs =
Interactive jobs on bwUniCluster [[BwUniCluster_User_Access#Allowed_activities_on_login_nodes|must '''NOT''' run on the logins nodes]], however resources for interactive jobs can be requested using msub. Considering a serial application with a graphical frontend that requires 5000 MByte of memory and limiting the interactive run to 2 hours execute the following:
<pre>
$ msub -I -V -l nodes=1:ppn=1 -l walltime=0:02:00:00
</pre>
The option -V defines that all environment variables are exported to the compute node of the interactive session.
After execution of this command '''DO NOT CLOSE''' your current terminal session but wait until the queueing system MOAB has granted you the requested resources on the compute system. Once granted you will be automatically logged on the dedicated resource. Now you have an interactive session with 1 core and 5000 MByte of memory on the compute system for 2 hours. Simply execute now your application:
<pre>
$ cd to_path
$ ./application
</pre>
Note that, once the walltime limit has been reached you will be automatically logged out of the compute system.
 
 

== Chain Jobs ==

The CPU time requirements of many applications exceed the limits of the job classes. In those situations it is recommended to solve the problem by a job chain. A job chain is a sequence of jobs where each job automatically starts its successor.

{{bwFrameA|
<source lang="bash">
#!/bin/bash
##################################################
## simple job run template for bwUniCluster ##
## to run chain jobs with MOAB ##
##################################################
##
## usage :
## msub -v myloop_counter=0 ./moab_chain_job.sh

#MSUB -l nodes=1:ppn=1
#MSUB -l walltime=00:00:05
#MSUB -l pmem=50mb
#MSUB -q develop
#MSUB -N chain

## Defaults
loop_max=10
cmd='sleep 2'

## Check if counter environment variable is set
if [ -z "${myloop_counter}" ] ; then
echo " ERROR: myloop_counter is undefined, stop chain job"
exit 1
fi

## only continue if below loop_max
if [ ${myloop_counter} -lt ${loop_max} ] ; then

## increase counter
let myloop_counter+=1

## print current Job number
echo " Chain job iteration = ${myloop_counter}"

## Define your command
cmd='sleep 2'
echo " -> executing ${cmd}"
${cmd}

if [ $? -eq 0 ] ; then
## continue only if last command was successful
msub -v myloop_counter=${myloop_counter} ./moab_chain_job.sh
else
## Terminate chain
echo " ERROR: ${cmd} of chain job no. ${myloop_counter} terminated unexpectedly"
exit 1
fi
fi
</source>
}}

----
[[Category:bwUniCluster|Batch Jobs - bwUniCluster features]]

BwForCluster User Access

2015-03-03T14:08:03Z

A Fuchs: /* 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 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|]].

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

 

= 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/organization/sos/puma/services/user-projects/user-access-and-user-management/bwunicluster/ 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="60%"
|-
!scope="row" {{Darkgray}} | Cluster topic and location
!scope="row" {{Darkgray}} | Registration server
|-
| bwForCluster Chemistry JUSTUS Ulm
| http://bwidm.rz.uni-ulm.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.

= 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="60%"
|-
!scope="row" {{Darkgray}} | Cluster topic and location
!scope="row" {{Darkgray}} | Login instructions
|-
| bwForCluster Chemistry JUSTUS Ulm
| [[BwForCluster_Chemistry_Login|bwForCluster Chemistry Login]]
|}

 

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

BwForCluster User Access

2015-03-02T16:02:43Z

A Fuchs: /* 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 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|]].

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

 

= 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_v3.pdf University of Karlsruhe - KIT]
* [[BwForCluster User Access Members Uni Konstanz|University of Konstanz]]
* [[BwForCluster User Access Members Uni Mannheim|University of Mannheim]]
* [https://www.hlrs.de/organization/sos/puma/services/user-projects/user-access-and-user-management/bwunicluster/ 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="60%"
|-
!scope="row" {{Darkgray}} | Cluster topic and location
!scope="row" {{Darkgray}} | Registration server
|-
| bwForCluster Chemistry JUSTUS Ulm
| http://bwidm.rz.uni-ulm.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.

= 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="60%"
|-
!scope="row" {{Darkgray}} | Cluster topic and location
!scope="row" {{Darkgray}} | Login instructions
|-
| bwForCluster Chemistry JUSTUS Ulm
| [[BwForCluster_Chemistry_Login|bwForCluster Chemistry Login]]
|}

 

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

File:Bwuni entitlement.svg

2015-02-17T10:33:08Z

A Fuchs:

File:Bwunireg.svg

2015-02-17T10:32:05Z

A Fuchs: Author: Annika Fuchs, Steinbuch Centre for Computing, KIT, 2014

Author: Annika Fuchs, Steinbuch Centre for Computing, KIT, 2014

BwForCluster User Access

2014-11-27T09:59:42Z

A Fuchs: /* Registration */

= Registration =

Granting access for a '''''bwForCluster''''' requires the registration at the [https://www.bwhpc-c5.de/ZAS/zas_uebersicht.php "Zentrale Antragsseite (ZAS)"].

ZAS

2014-11-27T09:34:07Z

A Fuchs: Redirected page to BwForCluster User Access

#REDIRECT [[BwForCluster_User_Access]]

BwForCluster User Access

2014-11-27T09:31:11Z

A Fuchs: Created page with "= Registration = Granting access and issuing a user account for '''''bwForCluster''''' requires the registration at the [https://www.bwhpc-c5.de/ZAS/zas_uebersicht.php "Zentr..."

= Registration =

Granting access and issuing a user account for '''''bwForCluster''''' requires the registration at the [https://www.bwhpc-c5.de/ZAS/zas_uebersicht.php "Zentrale Antragsseite (ZAS)"].

BwUniCluster 2.0 User Access

2014-03-20T08:59:14Z

A Fuchs: /* 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]
* [[‎BWUniCluster_User_Access_Members_Uni_Heidelberg|Ruprecht-Karls-Universität Heidelberg]]
* [[BWUniCluster_User_Access_Members_Uni_Ulm|Ulm University]]
* [http://www.kim.uni-hohenheim.de/bwhpc University of Hohenheim]
* [[BWUniCluster_User_Access_Members_Uni_Konstanz|University of Konstanz]]
* [[BWUniCluster_User_Access_Members_Uni_Mannheim|University of Mannheim]]
* [https://www.hlrs.de/organization/sos/puma/services/user-projects/user-access-and-user-management/bwunicluster/ 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]]

BwUniCluster 2.0 User Access

2014-01-29T14:25:45Z

A Fuchs:

{| 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]
* [[Media:unknown.pdf‎|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]]

Registration Support - bwUniCluster

2014-01-27T13:47:42Z

A Fuchs:

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

== Registration ==

If you have questions or problems concerning registration, please contact your local hotline.

{| style="width:100%; vertical-align:top; background:#f5fffa;border:2px solid #000000;"
! University !! Hotline
|-
| Albert Ludwig University of Freiburg || ''coming soon''
|-
| Eberhard Karls University, Tübingen || [mailto:hpcmaster@uni-tuebingen.de hpcmaster@uni-tuebingen.de]
|-
| Karlsruhe Institute of Technology (KIT) || [mailto:bwunicluster-hotline@lists.kit.edu bwunicluster-hotline@lists.kit.edu]
|-
| Ruprecht-Karls-Universität Heidelberg || [mailto:hpc-support@listserv.uni-heidelberg.de hpc-support@listserv.uni-heidelberg.de]
|-
| Ulm University || [mailto:helpdesk@uni-ulm.de helpdesk@uni-ulm.de]
|-
| University of Hohenheim || [mailto:kim-bw-projekt@uni-hohenheim.de kim-bw-projekt@uni-hohenheim.de]
|-
| University of Konstanz || [mailto:support@uni-konstanz.de support@uni-konstanz.de]
|-
| University of Mannheim || [mailto:hpc-support@mailman.uni-mannheim.de hpc-support@mailman.uni-mannheim.de]
|-
| University of Stuttgart || ''coming soon''
|}

BwUniCluster 2.0 User Access

2014-01-09T08:16:29Z

A Fuchs:

{| style="border-style: solid; border-width: 1px"
! Navigation: [[BwHPC_Best_Practice_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:
* Karlsruhe Institute of Technology (KIT)
* University of Mannheim
* University of Heidelberg
* University of Stuttgart
* University of Tübingen
* University of Ulm
* University of Freiburg
* University of Konstanz
* University of Hohenheim

To log on '''''bwUniCluster''''' an user account is required. All members of the shareholder
universities can apply for an account.

= Registration =

Granting access and issuing user accounts for '''''bwUniCluster''''' requires to fill in the
bwUniCluster application form and to sign the terms of usage (step A). Once approved please
register for an user account (step B).

== Step A: Application Form / Terms of Usage ==

Please fill in and sign the application form provided by your university:

* [[Media:KIT_Antrag_Benutzernummer_bwUniCluster_2013-12-13.pdf‎|Application form]] for members of KIT
* [[Media:unknown.pdf‎|Application form]] for members of the University of Mannheim
* [[Media:unknown.pdf‎|Application form]] for members of the University of Heidelberg
* [[Media:unknown.pdf‎|Application form]] for members of the University of Stuttgart
* [[Media:unknown.pdf‎|Application form]] for members of the University of Tübingen
* [[BWUniCluster_User_Access_Members_Uni_Ulm|Application form]] for members of the University of Ulm
* [[Media:unknown.pdf‎|Application form]] for members of the University of Freiburg
* [[Media:unknown.pdf‎|Application form]] for members of the University of Konstanz
* [[Media:unknown.pdf‎|Application form]] for members of the University of Hohenheim

== Step B: Web Registration ==

After step A and its approval 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/]
*# Select '''bwUniCluster Service Description''' (on the left hand side)
*# Click '''Register'''
*# Finally
*#* for KIT members '''optionally''' set a service password for authentication on bwUniCluster
*#* for all non-KIT members '''mandatorily''' set a service password for authentication on bwUniCluster


 

= 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:

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

== About 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 doing 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 '''Dienstpasswort setzen'''
# set new service, i.e. bwUniCluster, password, repeat it and click '''Save''' button.

= 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 jobs on bwUniCluster please visit:

* [[bwUniCluster Batch Jobs|bwUniCluster batch jobs]]

----

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