MonARCH on Rocky Linux 2024¶
What is the plan?¶
As part of the security uplift, we are migrating MonARCH login, data transfer and compute nodes into Rocky Linux. This migration is done progressively by first deploying a pair of new front-facing nodes for you to access; and then the compute nodes are scheduled to be rebuilt to Rocky Linux.
The most noticeable aspect of this change is that the existing software modules on the previous OS (CentOS) are potentially unusable on Rocky Linux. You may need to update your job scripts so that a compatible module (if applicable) is loaded instead of the older one. Please see below for the table of which software modules are compatible on Rocky Linux, and if they are not compatible, we have installed a newer Rocky Linux version, or alternatively, have installed one on the OS itself.
Important
Existing CentOS nodes will be converted into Rocky Linux soon. Please take the necessary steps to future-proof your job scripts.
What has not changed¶
Your username and password is as on the existing MonARCH
Your current $HOME folder and existing project / scratch folders are accessible
The SLURM job scheduler is shared on both CentOS and Rocky Linux nodes
How to access the Rocky Linux front-facing nodes?¶
A pair of new front-facing nodes are ready for you to use the Rocky Linux:
monarch-login4.erc.monash.edu
monarch-dtn2.erc.monash.edu
We are still applying some finishing touches on the ``dtn2`` so some functions are possibly missing.
How do I submit jobs to Rocky nodes?¶
The easiest way is to submit Rocky Linux jobs is to sbatch
them from within
the monarch-login4
login node. Jobs submitted from this login node will
automatically be directed to run on the Rocky Linux nodes.
If you are submitting jobs to the existing CentOS nodes, there is no need to change
your job scripts, simply submit them from the either monarch-login1
or monarch-login2
.
Rocky Linux capacity will increase as we convert existing nodes.
From these existing login nodes, you can also submit jobs to the Rocky Linux nodes by
adding a --constraints
line into your job scripts as follows:
#SBATCH --constraints=r9
Alternatively, during the sbatch
command, you can include a flag -C
as follows:
sbatch -C r9 jobscript.sh
What modules are available?¶
When running the module avail
command, you will see three sections of installed
software modules. The first section:
------------------------ /apps/modulefiles -------------------------
anaconda/2024.02-1 lammps/20230802
ansys/24r1 leveldb/1.23
canu/v2.2 libjpeg-turbo/3.0.2
ctffind/4.1.8 molden/6.9
fftw/3.3.10 motioncor2/1.6.4
The second section shows additional modules installed using Spack.
--------------------- /apps/spack/modulefiles ----------------------
hpl/2.3-gcc-11.3.1-npardb4 hpl/2.3-npardb4
Lastly, the existing CentOS software modules are shown. These modules are considered legacy and they are possibly incompatible on Rocky Linux. The table below shows what works (Compatible). Those software that are not compatible are either built fresh specifically for the Rocky Linux or they have been installed on at the operating system.
Software Module Compatibility Table¶
Software |
Current module on CentOS |
Compatibility / New version |
---|---|---|
adf |
|
Compatible – load |
anaconda |
|
|
ansys |
|
|
bison |
|
OS built-in – no module load needed |
blas |
|
OS built-in – no module load needed |
boost |
|
OS built-in – no module load needed |
canu |
|
|
cblas |
|
OS built-in – no module load needed |
cmake |
|
OS built-in – no module load needed |
comsol |
|
Compatible – load |
cplex |
|
Compatible – load |
cuda |
|
Compatible – load |
eigen |
|
OS built-in – no module load needed |
ffmpeg |
|
OS built-in – no module load needed |
fftw |
|
OS built-in – no module load needed |
gaussian |
|
Compatible – load |
gcc |
|
OS built-in – no module load needed |
gdal |
|
|
geos |
|
|
gflags |
|
|
glog |
|
|
gmp |
|
|
gromacs |
|
|
gsl |
|
|
gurobi |
|
Compatible – load |
hdf5 |
|
OS built-in – no module load needed |
intel |
|
|
java |
|
OS built-in – no module load needed |
julia |
|
``julia/1.10.2 `` |
lammps |
|
|
lapack |
|
OS built-in – no module load needed |
leveldb |
|
|
libjpeg-turbo |
|
OS built-in – no module load needed |
lmdb |
|
OS built-in – no module load needed |
make |
|
OS built-in – no module load needed |
mathematica |
|
Compatible – load |
matlab |
|
Compatible – load |
mesa |
|
OS built-in – no module load needed |
mkl |
|
|
molden |
|
|
mpfr |
|
|
ncurses |
|
OS built-in – no module load needed |
netcdf |
|
OS built-in – no module load needed |
openblas |
|
OS built-in – no module load needed |
opencv |
|
OS built-in – no module load needed |
openfoam |
|
|
openmpi |
|
|
openssl |
|
OS built-in – no module load needed |
proj |
|
|
protobuf |
|
|
python |
|
OS built-in – no module load needed |
qt |
|
OS built-in – no module load needed |
raven |
|
|
samtools |
|
|
scalapack |
|
OS built-in – no module load needed |
snappy |
|
|
sqlite3 |
|
OS built-in – no module load needed |
virtualgl |
|
Compatible – load |
zlib |
|
OS built-in – no module load needed |
How do I request software to be installed on Rocky Linux?¶
Please submit a request for a software installation via the google form below: https://docs.google.com/forms/d/e/1FAIpQLScSuz80Bof2QyGUNo-6aWsUgjTcQ5ZN6H91g5R1QEkyxULhZA/viewform