CALCULATIONS ON THE LOGIN NODE ARE NOT ALLOWED!
The login node of PALMA is not a place to start any serious calculations nor is it a playground for testing purposes or compiling programs! Any user processes violating this rule will be terminated immediately without any warning!
This page gives you an overview of the most important aspects of the PALMA-II cluster, how to connect to it and what a typical workflow could look like. Specifics can be found in the subsections for each topic separately.
PALMA-II consist of several hundred compute nodes running CentOS 7 as operating system. Every node consists of 2 Intel Xeon Gold 6140 CPUs containing 18 CPU cores each. Users will first have to connect to so-called login nodes to gain access to the compute nodes themselves. Applications or compute jobs can then be started via an interactive session or via job/batch scripts using the slurm workload manager.
To access the PALMA-II cluster you have to connect to one of the login nodes via an SSH connection using a terminal emulator. If you are on Linux or Mac OS, you can use the terminal applications that come pre-installed with your OS. If you are on Windows you can use PuTTY or (since Windows 10) the command prompt if you enabled Windows 10 OpenSSH feature.
- SSH address: email@example.com
You will need an ssh-key to access PALMA. Please find further instructions here.
If you need a short introduction on how to use a shell (terminal), we highly recommend this video tutorial series: https://hpc-wiki.info/hpc/Introduction_to_Linux_in_HPC
For verification, the current SSH host keys of the login node have the following fingerprints:
When you log in to the cluster for the first time, a directory /home/[a-z]/<your-username> is created for you. Please use this folder only to store your applications. Do not store your numerical results in here. Storage in /home is limited. For (numerical) results of your computations use the folder /scratch/tmp/<your-username>. The environment variable $WORK automatically points to the scratch folder.
|/home/[a-z]/<username>||Personal applications, binaries, libraries etc.|
|/scratch/tmp/<username>||Working directory, storage for numerical output |
(start your applications from here!)
|/mnt/beeond||Temporary working filesystem, provided on a per-job basis|
There is NO BACKUP of the home and working directory on PALMAII as these are not intended as an archive. We kindly ask you to remove your data there as soon as it is no longer needed.
Further information can be found at: Data & Storage
An example using scp is given below:
|Copy a local file to your home folder on PALMA-II|
|Copy a local folder to your working directory on PALMA-II|
|Copy a file on PALMA-II to your local computer|
Loading available software
Common applications are provided through a module system and have to be loaded into you environment before usage. You can load and unload them depending on your needs and preferences. The most important commands are:
|List currently available modules (software)|
|Search for a module with a specific NAME|
|Load a module into your environment|
|Un-load a module from your environment|
|List all currently loaded modules|
|Unload all module in your environment|
Details and specifics can be found in the module system section.
Jobs can be started in three different ways using the the slurm workload manager:
- Interactive (giving you direct access to the compute nodes)
- Non-interactive (using slurm to directly queue a job)
- Batch system (submitting a job script)
|Interactive||salloc <config options>|
|Non-interactive||srun <config options> <my-applications-to-run>|
All methods will reserve a certain amount of CPU cores or nodes for a given amount of time depending on your settings. Further information about the submission of jobs, configuration options, example job scripts can be found in the Submitting Jobs section.
An example of a typical workflow on PALMA-II is given below:
1. Connect to the login node of palma
|2. Navigate to your working directory|
|3. Load the needed software into your environment|
|4. Start your simulation / computation|