bwHPC Wiki - User contributions [en]

Registration/2FA/FAQ

2023-11-22T10:53:27Z

B Wiebelt:

= Second Factor (2FA) FAQ =

== How does 2FA work? ==

2FA uses two out of multiple factors for authentication. Factors are:

* Something you know (password or PIN)
* Something you own (mobile phone or security device)
* Something you are (biometric features)

The principle idea is that even if an attacking party manages to get hold of one factor, it still has to acquire a second factor for a completely successful attack. Such a completely successful attack results in a theft of your identify, possibly leading to malicious acts committed on your behalf and to your disadvantage.

== Why is 2FA necessary? ==

2FA is the current state-of-the-art method to prevent or mitigate cyber attacks. It is far superior to using a single shared secret (i.e. "password"), even if very strong passwords are used. 2FA mitigates fishing attempts, person-in-the-middle attacks and even cases where local computers (i.e. notebooks or workstations) have been stolen or compromised.

2FA is constantly replacing password-only authentication schemes in a networked world to improve cyber security and prevent identity theft.

== Why is 2FA so resilient? ==

When computers become comprised, passwords and private keys can easily be recorded, copied and used for future attacks at any time from any place. Without a second factor, an attacking party cannot proceed autonomously without further involvement of the victim. As soon as a second factor is required, i.e. something you own or something you are, an attacking party lacks an element which it cannot provide or simulate. Furthermore, these second factors are securely contained in uncompromisable areas on the respective devices (e.g. phones or hardware security keys). For authentication, a challenge is issued that only the owner of the device can answer. The secret never leaves the secure area during this challenge.

== I am using a password manager in conjunction with passwords that are individual per service, long and complex and thus impossible to guess. Isn't this good enough? ==

This is very good practice and in fact recommended for all systems that do not support 2FA yet. However, consider this: Your passwords need to be interpreted by the remote systems and are therefore available to the remote systems in clear text. If a remote system has been compromised, your password and thus your identity are compromised as well. And if an attacker has compromised your host, they can read or intercept the password, but not the second factor.

== I am using SSH private keys and secure them with a passphrase. Isn't this good enough? ==

This is very good and in fact recommended for all systems reachable via SSH that do not support 2FA yet. However, consider this: Computers are vulnerable by remote attacks (a thoughtless wrong click can be sufficient) and local attacks (somebody manipulates your machine when left unattended).

In case you become the victim of a successful attack, your machine will be compromised and every action will be recorded and monitored without you knowing, possibly for a very long time.

2FA offers at least some mitigation in this case.

== What happens if my local computer is compromised? ==

2FA does not prevent this from happening, but it offers mitigation. The services you use that are protected with 2FA are only partially compromised:

* An attacking party cannot use the compromised secret ("password") that it acquired from monitoring your local computer to gain remote access to the 2FA secured service. To initiate a remote session from the attacking parties' computers to the 2FA secured service, the second factor is required, which the attacking party does not have and cannot simulate, since it requires physical ownership of the respective security device.
* An attacking party cannot initiate a session from your compromised local computer to the remote computer without your active participation. The attacking party would have to present a second factor which requires a non-automatic action originating from the respective physical security device.
* ATTENTION: An attacking party can still monitor and possibly hijack connections from your compromised local computer to remote systems at the time these connections are actively initiated by you. However, exploitation is much more difficult than copying a simple shared password and needs to be adapted to the service which is attacked. For the attacking party, this bears at least a heightened risk of being discovered.
* Your passwords, passphrases and secret SSH keys are likely to have been compromised and therefore have to be exchanged after the attack becomes known to you. Your other factors have never left the external devices you keep them on and don't need to be changed. You have only answered cryptographic challenges with them, and these challenges and their corresponding answers cannot be predetermined by an attacker.

== What happens if I loose my security hardware token? ==

An attacking party would need to combine a found or stolen second factor (e.g. phone or security key) with a software attack, i.e. infecting your local computer, to get hold of the secret you know (i.e. PIN or password) to access services secured by 2FA. Nevertheless, you should remove old or lost second factors and replace them with new ones.

== What happens if I loose my phone? ==

Modern phones are protected by biometric measures. The biometric secrets are kept in a secure enclave on the device and cannot be extracted once registered. Neither an attacking party nor you nor the manufacturer can extract the secret data after the initial transfer. It is only ever used inside the secure area on the device to answer cryptographic challenges. In case you don't trust the manufacturers to keep your biometric data safe, you can use a PIN as an alternative. However, you still have to accept a certain level of trust towards the phone manufacturer. This is unavoidable unless you have the means to provide the complete chain of security yourself.

To avoid losing your access, some apps allow secure backups of your secondary factors, but to be safe you should register more than one second factor including backup TANs.

== Whats happens if I loose all secondary factors? ==

There are recovery procedures which vary by service. A common method are recovery codes (backup TANs), which you can print out and deposit in a safe location. Recovery codes work like master keys, so they must never be kept on the same device which is used to access the 2FA protected service.
If all else fails, most services will grant you access again after a thorough identity verification.

MATLAB

2021-04-14T09:31:38Z

B Wiebelt:

{| width=600px class="wikitable"
|-
! Description !! Content
|-
| module load
| math/matlab
|-
| License
| [https://de.mathworks.com/pricing-licensing/index.html?intendeduse=edu&prodcode=ML Academic License/Commercial]
|-
| Citing
| n/a
|-
| Links
| [https://de.mathworks.com/products/matlab/ MATLAB Homepage] | [https://de.mathworks.com/index.html?s_tid=gn_logo MathWorks Homepage] | [https://de.mathworks.com/support/?s_tid=gn_supp Support and more]
|-
| Graphical Interface
| No
|}

= Description =

'''MATLAB''' (MATrix LABoratory) is a high-level programming language and interactive computing environment for numerical calculation and data visualization.

= Availability =

MATLAB is available on selected bwHPC-Clusters along with a collection of toolboxes. A complete list of versions currently installed on the bwHPC-Clusters can be obtained from the [https://www.bwhpc.de/software.html Cluster Information System (CIS)].

= Adding MATLAB to Your Environment =

In order to check which versions of MATLAB are installed on the compute cluster, run the following command:
<pre>$ module avail math/matlab</pre>

In general, several MATLAB versions should be returned.
The default version can be accessed by loading the appropriate module:
<pre>$ module load math/matlab</pre>

Other MATLAB versions (if available) can be loaded according to:
<pre>$ module load math/matlab/<version></pre>
with <version> specifying the desired version.

An interactive MATLAB session with graphical user interface (GUI) can be started with the command (requires X11 forwarding enabled for your ssh login):
<pre>$ matlab</pre>

Since graphics rendering can be very slow on remote connections, the preferable way is to run the MATLAB command line interface without GUI:
<pre>$ matlab -nodisplay</pre>

Note: It is not advisable to invoke an interactive MATLAB session on a login node of the cluster.
The recommended way to run a long-duration interactive MATLAB session is to submit an interactive job and start MATLAB from within the dedicated compute node assigned to you by the queueing system (consult the specific cluster users guide on how to submit interactive jobs).

The following command will execute a MATLAB script or function named "example" on a single thread:
<pre>$ matlab -nodisplay -singleCompThread -r example > result.out 2>&1</pre>

The output of this session will be redirected to the file result.out. The option -r executes the MATLAB statement non-interactively. The option -singleCompThread limits MATLAB to single computational thread. Most of the time, running MATLAB in single-threaded mode will meet your needs. But if you have mathematically intense computations that benefit from the built-in multithreading provided by MATLAB's BLAS and FFT implementation, then you can experiment with running in multi-threaded mode by omitting this option (see section 4.1 - Implicit Threading).

As with all processes that require more than a few minutes to run, non-trivial MATLAB jobs must be submitted to the cluster queuing system. Example batch scripts are available in the directory pointed to by the environment variable $MATLAB_EXA_DIR.

The help page of the MATLAB module provides more version specific information:
<pre>$ module help math/matlab</pre>

= Parallel Computing Using MATLAB =

Parallelization of MATLAB jobs is realized via the built-in multithreading provided by MATLAB's BLAS and FFT implementation and the parallel computing functionality of MATLAB's Parallel Computing Toolbox (PCT). The MATLAB Parallel/Distributed Computing Server is not available on the bwHPC-Clusters.

== Implicit Threading ==

A large number of built-in MATLAB functions may utilize multiple cores automatically without any code modifications required. This is referred to as implicit multithreading and must be strictly distinguished from explicit parallelism provided by the Parallel Computing Toolbox (PCT) which requires specific commands in your code in order to create threads.

Implicit threading particularly takes place for linear algebra operations (such as the solution to a linear system A\b or matrix products A*B) and FFT operations. Many other high-level MATLAB functions do also benefit from multithreading capabilities of their underlying routines. However, the user can still enforce single-threaded mode by adding the command line option -singleCompThread.

Whenever implicit threading takes place, MATLAB will detect the total number of cores that exist on a machine and by default makes use of all of them. This has very important implications for MATLAB jobs in HPC environments with shared-node job scheduling policy (i.e. with multiple users sharing one compute node). Due to this behaviour, a MATLAB job may take over more compute resources than assigned by the queueing system of the cluster (and thereby taking away these resources from all other users with running jobs on the same node - including your own jobs).

Therefore, when running in multi-threaded mode, MATLAB always requires the user's intervention to not allocate all cores of the machine (unless requested so from the queueing system). The number of threads must be controlled from within the code by means of the maxNumCompThreads(N) function (which is supposed to be deprecated) or, alternatively, with the feature('numThreads', N) function (which is currently undocumented).

== Using the Parallel Computing Toolbox (PCT) ==

By using the PCT one can make explicit use of several cores on multicore processors to parallelize MATLAB applications without MPI programming. Under MATLAB version 8.4 and earlier, this toolbox provides 12 workers (MATLAB computational engines) to execute applications locally on a single multicore node. Under MATLAB version 8.5 and later, the number of workers available is equal to the number of cores on a single node (up to a maximum of 512).

If multiple PCT jobs are running at the same time, they all write temporary MATLAB job information to the same location. This race condition can cause one or more of the parallel MATLAB jobs fail to use the parallel functionality of the toolbox.

To solve this issue, each MATLAB job should explicitly set a unique location where these files are created. This can be accomplished by the following snippet of code added to your MATLAB script.

{{bwFrameA|
<source lang="Matlab">

% create a local cluster object
pc = parcluster('local')

% get the number of dedicated cores from environment
num_workers = str2num(getenv('SLURM_NPROCS'))

% explicitly set the JobStorageLocation to the tmp directory that is unique to each cluster job (and is on local, fast scratch)
parpool_tmpdir = [getenv('TMP'),'/.matlab/local_cluster_jobs/slurm_jobID_',getenv('SLURM_JOB_ID')]
mkdir(parpool_tmpdir)
pc.JobStorageLocation = parpool_tmpdir

% start the parallel pool
parpool(pc,num_workers)

</source>
}}

Note: The code snippet also sets the correct number of parallel workers in MATLAB according to the total number of processes dedicated to the job given by the environment variable $SLURM_NPROCS in the job submission file.

= General Performance Tips for MATLAB =

MATLAB data structures (arrays or matrices) are dynamic in size, i.e. MATLAB will automatically resize the structure on demand. Although this seems to be convenient, MATLAB continually needs to allocate a new chunk of memory and copy over the data to the new block of memory as the array or matrix grows in a loop. This may take a significant amount of extra time during execution of the program.

Code performance can often be drastically improved by preallocating memory for the final expected size of the array or matrix before actually starting the processing loop. In order to preallocate an array of strings, you can use MATLAB's build-in cell function. In order to preallocate an array or matrix of numbers, you can use MATLAB's build-in zeros function.

The performance benefit of preallocation is illustrated with the following example code.

{{bwFrameA|
<source lang="Matlab">

% prealloc.m

clear all;

num=10000000;

disp('Without preallocation:')
tic
for i=1:num
a(i)=i;
end
toc

disp('With preallocation:')
tic
b=zeros(1,num);
for i=1:num
b(i)=i;
end
toc

</source>
}}

On a compute node, the result may look like this:

<pre>
Without preallocation:
Elapsed time is 2.879446 seconds.
With preallocation:
Elapsed time is 0.097557 seconds.
</pre>

Please recognize that the code runs almost 30 times faster with preallocation.

----
[[Category:Mathematics software]]
[[Category:BwUniCluster]]
[[Category:BwUniCluster_2.0]]
[[Category:BwForCluster_BinAC]]
[[Category:BwForCluster_MLS&WISO_Production]]
[[Category:BwForCluster_Chemistry]]
[[Category:BwForCluster_JUSTUS_2]]

BwUniCluster2.0/Support

2021-02-16T10:40:13Z

B Wiebelt:

== Registration ==
If you have questions or problems concerning '''registration''', please open a ticket via

* '''[https://bw-support.scc.kit.edu/ bwSupport Portal]'''

or contact your local university hotline:

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

== Problems with Login/2-Factor-Authentication ==

'''Q: How do I register/deactivate a token?'''

A: Please refer to the [[bwUniCluster 2.0 User Access/2FA Tokens|2FA documentation wiki page]].

 

'''Q: I have lost my 2FA device or can no longer generate One-Time Passwords using my software token.'''

A: KIT users can contact the [https://www.scc.kit.edu/en/services/servicedesk.php KIT ServiceDesk], users from all other institutions should open a support ticket via the [https://bw-support.scc.kit.edu/ bwSupport Portal].

== Deregistration ==

If you are no longer using the bwUniCluster 2.0 and want to deregister yourself, please follow the [[BwUniCluster_2.0_User_Access#Deregistration|Deregistration instructions]]. This will also automatically remove your e-mail address from the user mailing list and you will no longer receive user announcements for this system.

----
[[Category:Support]][[Category:bwUniCluster_2.0]]

User:M Janczyk/Support

2019-08-28T16:39:47Z

B Wiebelt:

==General Support==

For assistance regarding access to and usage of the bwForCluster NEMO, please send an e-mail to [mailto:enm-support@hpc.uni-freiburg.de enm-support@hpc.uni-freiburg.de].

==Mailing List==

If you would like to receive updates on the status of the bwForCluster NEMO as well as event and course announcements, you can subscribe our HPC newsletter by sending an e-mail to [mailto:hpc-news-subscribe@hpc.uni-freiburg.de hpc-news-subscribe@hpc.uni-freiburg.de].

If you would like to unsubscribe, please send an e-mail to [mailto:hpc-news-unsubscribe@hpc.uni-freiburg.de hpc-news-unsubscribe@hpc.uni-freiburg.de].

For old news visit our local [https://www.hpc.uni-freiburg.de/news HPC page].

[[Category:BwForCluster NEMO]]
[[Category:BwForCluster NEMO|Support]]
[[Category:Support|bwForCluster NEMO Support]]

User:M Janczyk/Acknowledgement

2018-07-31T14:18:47Z

B Wiebelt:

When preparing a publication describing work that involved the usage of a bwForCluster, e.g. the bwForCluster NEMO, please ensure that you reference the bwHPC initiative, the bwHPC-C5 project and – if appropriate – also the bwHPC facility itself. The following sample text is suggested as a starting point.

Acknowledgement:
The authors acknowledge support by the state of Baden-Württemberg through bwHPC
and the German Research Foundation (DFG) through grant no INST 39/963-1 FUGG (bwForCluster NEMO).

In addition, we kindly ask you to notify us of any reports, conference papers, journal articles, theses, posters, talks which contain results obtained on any bwHPC resource by sending an email to
[mailto:publications@bwhpc-c5.de publications@bwhpc-c5.de] stating:
* cluster facility (e.g. bwForCluster NEMO)
* RV acronym (e.g. bw16A000)
* author(s)
* title ''or'' booktitle
* journal, volume, pages ''or'' editors, address, publisher
* year.

Such recognition is important for acquiring funding for the next generation hardware, support services, data storage and infrastructure.

The publications will be referenced on the [https://www.bwhpc.de/en/user_publications.php bwHPC website].

[[Category:BwForCluster NEMO]]
[[Category:Acknowledgement]]
[[Category:BwForCluster NEMO|Acknowledgement]]
[[Category:Acknowledgement|bwForCluster NEMO]]
[[Category:Acknowledgment|bwForCluster NEMO]]

BwForCluster User Access

2016-11-11T14:01:47Z

B Wiebelt: /* Personal registration at bwForCluster */

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/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]]

|}

 

----
[[Category:Access|bwForCluster]][[Category:bwForCluster_Chemistry]][[Category:bwForCluster_MLS&WISO_Production]][[Category:bwForCluster_MLS&WISO_Development]]

User:M Janczyk/Support

2016-11-10T14:10:39Z

B Wiebelt:

==General Support==

For assistance regarding access to and usage of the bwForCluster NEMO, please send an e-mail to [mailto:enm-support@bwhpc-c5.de enm-support@bwhpc-c5.de].

==Mailing List==

If you would like to receive updates on the status of the bwForCluster NEMO as well as event and course announcements, you can subscribe our HPC newsletter by sending an e-mail to [mailto:hpc-news-subscribe@hpc.uni-freiburg.de hpc-news-subscribe@hpc.uni-freiburg.de].

If you would like to unsubscribe, please send an e-mail to [mailto:hpc-news-unsubscribe@hpc.uni-freiburg.de hpc-news-unsubscribe@hpc.uni-freiburg.de].

For old news visit our local [https://www.hpc.uni-freiburg.de/news HPC page].

[[Category:BwForCluster NEMO]]
[[Category:BwForCluster NEMO|Support]]
[[Category:Support|bwForCluster NEMO Support]]

User:M Janczyk/Acknowledgement

2016-08-30T12:48:16Z

B Wiebelt:

When preparing a publication describing work that involved the usage of a bwForCluster, e.g. the bwForCluster NEMO, please ensure that you reference the bwHPC initiative, the bwHPC-C5 project and – if appropriate – also the bwHPC facility itself. The following sample text is suggested as a starting point.

Acknowledgement:
The authors acknowledge support by the state of Baden-Württemberg through bwHPC
and the German Research Foundation (DFG) through grant no INST 39/963-1 FUGG.

In addition, we kindly ask you to notify us of any reports, conference papers, journal articles, theses, posters, talks which contain results obtained on any bwHPC resource by sending an email to
[mailto:publications@bwhpc-c5.de publications@bwhpc-c5.de] stating:
* cluster facility (e.g. bwForCluster NEMO)
* RV acronym (e.g. bw16A000)
* author(s)
* title ''or'' booktitle
* journal, volume, pages ''or'' editors, address, publisher
* year.

Such recognition is important for acquiring funding for the next generation hardware, support services, data storage and infrastructure.

The publications will be referenced on the [http://www.bwhpc.de/en/user_publications.php bwHPC website].

[[Category:BwForCluster NEMO]]
[[Category:Acknowledgement]]
[[Category:BwForCluster NEMO|Acknowledgement]]
[[Category:Acknowledgement|bwForCluster NEMO]]
[[Category:Acknowledgment|bwForCluster NEMO]]

BwUniCluster2.0/Acknowledgement

2016-04-07T20:10:36Z

B Wiebelt:

The HPC resource bwUniCluster is funded by the Ministry of Science, Research and the Arts Baden-Württemberg and the Universities of the State of Baden-Württemberg:
* 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.

Therefore, any work performed on bwUniCluster should be appropriately cited:

'''"The authors acknowledge support by the state of Baden-Württemberg through bwHPC."'''

Furthermore, please report any publication that cites bwUniCluster to [mailto:publications@bwhpc-c5.de publications@bwhpc-c5.de] stating:
* DOI (if available)
* author(s)
* title ''or'' booktitle
* journal, volume, pages ''or'' editors, address, publisher
* year.
This information will be used for the evaluation of bwUniCluster.

----
[[Category:bwUniCluster|Acknowledgement]]
[[Category:Acknowledgement|bwUniCluster]]

File:BwCluster.remote.r2014b.tar

2015-09-02T15:44:01Z

B Wiebelt:

File:BwCluster.remote.r2014b.zip

2015-09-02T15:43:51Z

B Wiebelt:

File:BwCluster.remote.r2015a.tar

2015-09-02T15:43:37Z

B Wiebelt:

File:BwCluster.remote.r2015a.zip

2015-09-02T15:43:13Z

B Wiebelt: