From Grid5000
Jump to: navigation, search
Note.png Note

This page is actively maintained by the Grid'5000 team. If you encounter problems, please report them (see the Support page). Additionally, as it is a wiki page, you are free to make minor corrections yourself if needed. If you would like to suggest a more fundamental change, please contact the Grid'5000 team.

Grid'5000 provides a set of software (mainly scientific-related) using Lmod, thanks to the module command line tool.

They are available from Grid5000 frontends or cluster's nodes (only on debianXX-big and debianXX-nfs environment if deployment is used).

The modules command

General usage

The module system is designed to load software and make it available by modifying environment (such as your PATH variable).

To get started, list available software using:

$ module available
---------------------------------------------- /grid5000/spack/v1/share/spack/modules/linux-debian11-x86_64_v2 ----------------------------------------------
  anaconda3/2022.05_gcc-10.4.0                         mpich/4.0.2_gcc-10.4.0
  apptainer/1.0.2_gcc-10.4.0                           mumps/5.4.1_gcc-10.4.0-intelmpi
  cmake/3.23.3_gcc-10.4.0                              mvapich2/2.3.7_gcc-10.4.0
  comgr/5.2.0_gcc-10.4.0                               netlib-lapack/3.10.1_gcc-10.4.0
  cuda/11.4.0_gcc-10.4.0                               netlib-scalapack/2.2.0_gcc-10.4.0-openmpi
  cuda/11.6.2_gcc-10.4.0                               opa-psm2/11.2.230_gcc-10.4.0
  cuda/11.7.1_gcc-10.4.0                        (D)    openblas/0.3.20_gcc-10.4.0
  cudnn/                       openjdk/1.8.0_265-b01_gcc-10.4.0
  cudnn/                (D)    openmpi/4.1.4_gcc-10.4.0
  gcc/10.4.0_gcc-10.4.0                                petsc/3.17.4_gcc-10.4.0-intelmpi
  gcc/12.2.0_gcc-10.4.0                         (D)    pmix/4.1.2_gcc-10.4.0
  glpk/4.65_gcc-10.4.0                                 py-numpy/1.23.3_gcc-10.4.0-intelmpi-python-3.9.13
  go/1.18_gcc-10.4.0                                   py-pyopencl/2020.2.2_gcc-10.4.0-intelmpi-python-3.9.13
  hip/5.2.0_gcc-10.4.0                                 python/3.9.13_gcc-10.4.0
  hipblas/5.2.0_gcc-10.4.0                             rdma-core/41.0_gcc-10.4.0
  hsa-rocr-dev/5.2.0_gcc-10.4.0                        rocblas/5.2.0_gcc-10.4.0
  hsakmt-roct/5.2.0_gcc-10.4.0                         rocm-cmake/5.2.0_gcc-10.4.0
  intel-oneapi-advisor/2022.1.0_gcc-10.4.0             rocm-opencl/5.2.0_gcc-10.4.0
  intel-oneapi-ccl/2021.6.0_gcc-10.4.0-intelmpi        rocm-openmp-extras/5.2.0_gcc-10.4.0
  intel-oneapi-compilers/2022.1.0_gcc-10.4.0           rocm-smi-lib/5.2.3_gcc-10.4.0
  intel-oneapi-dpl/2021.7.0_gcc-10.4.0                 rocminfo/5.2.0_gcc-10.4.0
  intel-oneapi-inspector/2022.1.0_gcc-10.4.0           rocprofiler-dev/5.2.0_gcc-10.4.0
  intel-oneapi-ipp/2021.6.0_gcc-10.4.0                 rocsolver/5.2.0_gcc-10.4.0
  intel-oneapi-mkl/2022.1.0_gcc-10.4.0-intelmpi        roctracer-dev-api/5.2.0_gcc-10.4.0
  intel-oneapi-mkl/2022.1.0_gcc-10.4.0-openmpi  (D)    scalasca/2.6_gcc-10.4.0-openmpi
  intel-oneapi-mpi/2021.6.0_gcc-10.4.0                 scotch/7.0.1_gcc-10.4.0-intelmpi
  intel-oneapi-vtune/2022.3.0_gcc-10.4.0               singularity/3.8.5_gcc-10.4.0
  julia/1.8.2_gcc-10.4.0                               starpu/1.3.9_gcc-10.4.0
  libfabric/1.15.1_gcc-10.4.0                          ucx/1.13.1_gcc-10.4.0
  llvm/13.0.1_gcc-10.4.0                               valgrind/3.19.0_gcc-10.4.0-intelmpi
  llvm-amdgpu/5.2.0_gcc-10.4.0                         valgrind/3.19.0_gcc-10.4.0-openmpi                     (D)
  metis/5.1.0_gcc-10.4.0                               vtk/9.0.3_gcc-10.4.0-intelmpi
  miniconda3/4.10.3_gcc-10.4.0                         vtk/9.0.3_gcc-10.4.0-openmpi                           (D)
  miniconda3/22.11.1_gcc-10.4.0                 (D)

  D:  Default Module

Use "module spider" to find all possible modules.
Use "module keyword key1 key2 ..." to search for all possible modules matching any of the "keys".

Note.png Note

If you need additional software to be installed, feel free to contact Grid5000 support team and we can look into it.

To load something into your environment use the load command:

$ module load gcc
$ gcc --version
gcc (Spack GCC) 12.2.0

By default, module loads the latest version available of a software (sorted by lexicographical order). You can also specify the version you need:

$ module load gcc/10.4.0_gcc-10.4.0
$ gcc --version
gcc (Spack GCC) 10.4.0

You can also find out more information about the package using whatis or show commands:

$ module whatis gcc
$ module show gcc

If you want to unload one or all the currently loaded modules, you can use:

$ module unload gcc
$ module purge

The full documentation of module command is available at:

Using modules in jobs

The module command is not a real executable, but a shell function.

If it is not available from your shell (it might be the case if you use zsh), ensure that /etc/profile.d/ is sourced.

In addition, module must be executed in an actual shell to work: a simple oarsub "module load gcc" will fail, you must use either:

Terminal.png fnancy:
oarsub 'bash -l -c "module load gcc; gcc --version"'

or alternatively:

Terminal.png fnancy:
oarsub ". /etc/profile; module load gcc; gcc --version"

Modules that require connection to license server

Some modules are licensed and require a connection to a license server.

We currently propose two license protected modules, Matlab and DDT/Map.

At the time of this writing (beg. May, 2023), in order to use both of them, it is required for the user to:

  • have an access to a license server from her laptop/workstation (either being connected to the user laboratory network, or connected via an institutional VPN)
  • and at the same time, connect to the reserved node with a special SSH ports redirection, as explained below.

We plan to simplify this process for Inria users by providing an automatic access to some Institutional license servers (based on the user belonging to a Granting Group Access - GGA).

Matlab example

In the following example, we are using the Université de Lorraine license server to run matlab.

  • Connect from your workstation to your previously reserved node with a ssh port redirection.

typically, for port 27000 only:

 (workstation):~$ ssh -R 27000:<token.licenceserver.tld>:27000 <node>.<site>.g5k
 (workstation):~$ ssh -R -R <node>.<site>.g5k
  • Set up the link to your Matlab License server through your ssh connection, typically:
 (node):~$ export LM_LICENSE_FILE=27000@
  • Load the Matlab module named matlab (with version accordingly to your provided licence), for example:
 (node):~$ module load matlab/R2022a
  • Start Matlab without graphical environment:
 (node):~$ matlab -nodisplay -nodesktop -nosplash

Note: No Matlab License server is needed to use Matlab Runtime on nodes.

DDT/Map example

In the following example, we are using the Inria license server to run ddt because, currently, the DDT/Map module is supported only for Inria members.

  • Connect from your workstation to your previously reserved node with a ssh port redirection.
 (workstation) % ssh -YC -R <node>.<site>.g5k
  • Load the Matlab module named ddt (with version accordingly to your provided licence), for example:
 (node):~$ module load ddt
  • Start DDT using the GUI:
 (node):~$ ddt

Sharing modules between users

Modules can be shared between users by using a group storage.

Note.png Note

This documentation assume that you already know what is a group storage, and that you already have one for storing your modules. If it's not the case, check the Group Storage Documentation.

Put the modules in a dedicated folder of the group storage, so that the modules are reachable by any user belonging to the group storage.

Terminal.png access:
rsync modules-dir/ /srv/my-storage@storage_fqdn/modules-dir

After adding the directory to the MODULEPATH environment variable, the modules inside this directory will be loadable by other users of the group. This can be done by using one of the two following commands.

Terminal.png node:
module use /srv/my-storage@storage_fqdn/modules-dir


Terminal.png node:
export MODULEPATH=/srv/my-storage@storage_fqdn/modules-dir:$MODULEPATH

Finally, the modules can be loaded.

Terminal.png node:
module load my-personal-module

If you are not familiar with modules, you will find here a sample setup to build and share a set of modules of your own.