System

Mufasa is a Linux server located in a server room managed by the System Administrators.

Job Users and Job Administrators can only access Mufasa remotely.

Remote access to Mufasa is performed using the SSH protocol for the execution of commands and the SFTP protocol for the exchange of files. Once logged in, a user interacts with Mufasa via a terminal (text-based) interface.

Mufasa 2.0

At the beginning of November 2025 Mufasa has been subjected to a comprehensive hardware and software overhaul: the new system is sometimes called Mufasa 2.0; to distinguish it from the old system, the latter is sometimes called "Mufasa 1.0".

This wiki is currently (November 2025) being updated to reflect the changes. Elements that changed significantly from Mufasa 1.0 to Mufasa 2.0 are highlighted in yellow. When the title of a section is highlighted, it means either that it is a new section, or that the section's contents significantly changed.

Hardware

Mufasa is a server for massively parallel computation. It has been set up and configured by E4 Computer Engineering with the support of the Biomechanics Group, the CartCasLab laboratory and the NearLab laboratory.

Mufasa's main hardware components are:

• Supermicro A+ Server 4124GS-TNR
• 2 AMD Epyc 7542 32-core processors (64 CPU cores total)
• 1 TB RAM
• 7 TB of SSDs (fast temporary repository for datasets actively being used - see Storage spaces)
• 25 TB of HDDs (for user /home directories)
• 8 Nvidia A100 GPUs [based on the Ampere architecture]
• Ubuntu Linux 24.04 LTS server operating system

System resources are shared among different users and processes in order to optimise their usage and availability. This sharing is managed by SLURM.

CPUs and GPUs

Mufasa is fitted with two 32-core CPU, so the system has a total of 64 phyical CPUs. Of the 64 CPUs, most are reserved for the SLURM job scheduling system and can only be accessed via SLURM; the remaining few are used by the login server).

For what concerns GPUs, some of the physical A100 GPUs have been subdivided into “virtual” GPUs with different capabilities using Nvidia's MIG system. Precisely, 5 of the A100 GPUs have been subdivided into two GPUs, each possessing half the RAM of the original device (i.e., 20 GB). Since the A100 has 7 compute units onboard, one of the two virtual GPUs built out of a single A100 has 3 compute units, while the other has 4 compute units.

All in all, the GPU complement of Mufasa comprises the following devices:

5 GPUs with 20GB of RAM and 3 compute units

5 GPUs with 20GB of RAM and 4 compute units

3 GPUs with 40 GB of RAM

Thanks to MIG, users can use all the GPUs listed above as if they were all physical devices installed on Mufasa, without having to worry (or even know) which actually are and which instead are virtual GPUs. How these devices are made available to Mufasa users is explained in SLURM.

You can use command

nvidia-smi -L

to get in-depth information about the physical and virtual GPUs available to users in a system based on MIG. (On Mufasa, this command needs to be launched in a bash shell opened through SLURM in order to be able to access the GPUs.)

Accessing Mufasa

Login server

Differently from Mufasa 1.0, Mufasa 2.0 employs a login server to manage user connections. The login server is a Linux virtual machine with very limited resources (no GPUs, few CPUs, small RAM). Its task is only to provide users with a way to log into the system and launch User Jobs with SLURM. Jobs launched via SLURM run on Mufasa 2.0's physical hardware (not on the virtual hardware of the login server) and therefore can access to the hardware resources of Mufasa, such as the GPUs.

When you access Mufasa via SSH, the remote shell you are provided with is a shell to the login server, unable to perform computationally heavy tasks: for heavy tasks you have to launch a SLURM job. The only tasks you can execute directly from the login server shell are simple "housekeeping" tasks on your home directory, such as deleting files you do not need anymore.

Please note that if you try to run computationally heavy processes in the login server you can easily overwhelm its scarce resources, making it unavailable to all users and thus making Mufasa unreachable by anyone. The login server has safety mechanisms to prevent processes from hogging too much of its resources... by killing such processes. However, please avoid checking if these mechanisms work.

Logging into the login server

User access to Mufasa is always remote and exploits the SSH (Secure SHell) protocol.

Access to Mufasa is not direct: instead, it is managed by a login server. Once the user has logged into the login server, they can issue commands to SLURM to run processing jobs.

To open a remote connection to the login server, open a local terminal on your computer and, in it, run command

ssh <username>@10.79.23.96

For example, user mrossi may access Mufasa with command

ssh mrossi@10.79.23.96

As soon as you launch the ssh command, you will be asked to type the password (i.e., the one of your user account on Mufasa). Once you provide the password, the local terminal on your computer becomes a remote terminal (a “remote shell”) through which you interact with the login server. The remote shell sports a command prompt such as

<username>@mufasa2-login:~$

(mufasa2-login is the Linux hostname of the login server). For instance, user mrossi will see a prompt similar to this:

mrossi@mufasa2-login:~$

Access via SSH works with Linux, MacOs and Windows 10 (and later) terminals. For other Windows users, a handy alternative tool (also including an X server, required to run on Mufasa Linux programs with a graphical user interface) is MobaXterm.

If you don't have a user account on Mufasa, you first have to ask your supervisor for one. See Users for more information.

In the remote shell to the login server opened via SSH, you can issue commands by typing them after the prompt, then pressing the enter key. Being Mufasa a Linux server, it will respond to all the standard Linux system commands such as pwd (which prints the path to the current directory) or cd <destination_dir> (which changes the current directory). On the internet you can find many tutorials about the Linux command line, such as this one.

To close the SSH session run

exit

from the command prompt of the remote shell.

Direct access to Mufasa (for users with running SLURM jobs)

While a user has SLURM jobs in execution, such user may also log into Mufasa directly, without passing through the login server. This allows the user to interact with the running jobs, e.g. to monitor their progress. Direct access to Mufasa is done via SSH with command

ssh <username>@10.79.23.97

For example, user mrossi may access Mufasa with command

ssh mrossi@10.79.23.97

As soon as you launch the ssh command, you will be asked to type the password (i.e., the one of your user account on Mufasa). Once you provide the password, the local terminal on your computer becomes a remote terminal (a “remote shell”) through which you interact with the Mufasa. The remote shell sports a command prompt such as

<username>@mufasa2:~$

(mufasa2 is the Linux hostname of Mufasa). For instance, user mrossi will see a prompt similar to this:

mrossi@mufasa2:~$

To a user logged into Mufasa this way, Mufasa appears to possess only the resources that SLURM has allocated to the running job(s) of that user. For instance, if the user has a running job that requested 4 CPUs and a GPU, to that user Mufasa will appear to have only 4 CPUs and a single GPU.

A special case of direct access to Mufasa occurs when a user, from the login server, asks SLURM to execute an interactive job. Such a job, when it goes into execution, opens a shell to Mufasa. To the user, this corresponds to the fact that the shell they were using to interact with the login server changes into a shell opened directly on Mufasa. This corresponds to the command prompt changing from

<username>@mufasa2-login:~$

to

<username>@mufasa2:~$

Another way to know if the current shell is the “base” shell or one run via SLURM is to execute command

echo $SLURM_JOB_ID

If no number gets printed, this means that the shell is the “base” one. If a number is printed, it is the SLURM job ID of the /bin/bash process.

To close the SSH session to Mufasa run

exit

from the command prompt of the remote shell.

VPN

To be able to connect to Mufasa, your computer must belong to Polimi's LAN. This happens either because the computer is physically located at Politecnico di Milano and connected via ethernet, or because you are using Polimi's VPN (Virtual Private Network) to connect to its LAN from somewhere else (such as your home). In particular, using the VPN is the only way to use Mufasa from outside Polimi. See this DEIB webpage for instructions about how to activate VPN access.

SSH timeout

SSH sessions to Mufasa may be subjected to an inactivity timeout: i.e., after a given inactivity period the ssh session gets automatically closed. Users who need to be able to reconnect to the very same shell where they launched a program (for instance because their program is interactive or because it provides progress update messages) should use the screen command.

SSH and graphics

The standard form of the ssh command, i.e. the one described at the beginning of Accessing Mufasa, should always be preferred. However, it only allows text communication with Mufasa. In special cases it may be necessary to remotely run (on Mufasa) Linux programs that have a graphical user interface. These programs require interaction with the X server of the remote user's machine (which must use Linux as well). A special mode of operation of ssh is needed to enable this. This mode is engaged by running command ssh like this:

ssh -X <your username on Mufasa>@<Mufasa's IP address>

File transfer

Uploading files from local machine to Mufasa and downloading files from Mufasa onto local machines is done using the SFTP protocol (Secure File Transfer Protocol).

Linux and MacOS users can directly use the sftp package, as explained (for instance) by this guide. Windows users can interact with Mufasa via SFTP protocol using the MobaXterm software package. MacOS users can interact with Mufasa via SFTP also with the Cyberduck software package.

For Linux and MacOS user, file transfer to/from Mufasa occurs via an interactive sftp shell, i.e. a remote shell very similar to the one one described above. The first thing to do is to open a terminal and run the following command (note the similarity to SSH connections):

sftp <username>@<IP_address>

where username is the username on Mufasa of the user, and <IP_address> is the IP address of Mufasa.

You will be asked your password. Once you provide it, you access an interactive sftp shell, where the command prompt takes the form

sftp>

From this shell you can run the commands to exchange files. Most of these commands have two forms: one to act on the remote machine (in this case, Mufasa) and one to act on the local machine (i.e. your own computer). To differentiate, the “local” versions usually have names that start with the letter “l” (lowercase L).

cd <path>

to change directory to <path> on the remote machine.

lcd <path>

to change directory to <path> on the local machine.

get <filename>

to download (i.e. copy) <filename> from the current directory of the remote machine to the current directory of the local machine.

put <filename>

to upload (i.e. copy) <filename> from the current directory of the local machine to the current directory of the remote machine.

Naturally, a user can only upload files to directories where they have write permission (usually only their own /home directory and its subdirectories). Also, users can only download files from directories where they have read permission. (File permission on Mufasa follow the standard Linux rules.)

In addition to the terminal interface, users of Linux distributions based on Gnome (such as Ubuntu) can use a handy graphical tool to exchange files with Mufasa. In Gnome's Nautilus file manager, write

sftp://<username>@<IP_address>

in the address bar of Nautilus, where username is your username on Mufasa and <IP_address> is the IP address of Mufasa. Nautilus becomes a graphical interface to Mufasa's remote filesystem.

Using Mufasa

This section provide a brief guide to Mufasa users (especially those who are not experienced in the use of Linux and/or remote servers) about interacting with the system.

Storage spaces

User jobs require storage of programs and data files. On Mufasa, the space available to users for data storage is the /home/ directory. /home/ contains two types of directories:

Personal directories

Location and access

Personal directories are in /home/. They are dedicated to individual users of Mufasa.

The home directory of user UserName is /home/UserName/.

Usage

The home directory of a user is their own personal space on Mufasa. Space is limited (see Disk quotas), so you'll need to do some "housekeeping" to avoid filling it up.

The general rule is: keep in your home directory only the files that the work you are doing on Mufasa right now needs; remove a file as soon as it is not needed anymore for your current work.

Mufasa is not a storage space!

Shared directories

Location and access

Shared directories are in /home/shared/. They are dedicated to research groups, and each group decides internally how to manage the group's directory.

The shared directory of group GroupName is /home/shared/GroupName/. Users who belong to such group can read from and write to the directory.

Directory /home/shared/common/ is available to all research groups. Any user can read from and write to the directory.

Usage

Shared directories are used:

- To share data. If multiple users are using the same data, it makes sense to put the data in a shared directory instead of having multiple copies of them in each user's home directory.

- For faster read/write. Shared spaces are physically located on faster disks wrt the personal home directories (SSDs instead of mechanical HDDs). When a processing job requires reading or writing very large amounts of data, placing such data in a shared directory can significantly speed up the job.

Important! Shared directories are used by several people, so it's important to quickly remove from them any file that is not actively in use.

Disk quotas

In Mufasa, Storage spaces are subjected to quotas: i.e., the files that are stored in them cannot occupy more than a given amount of disk space. Quotas apply both to personal directories (e.g., /home/userX/) and to shared directories (e.g., /home/shared/ResearchGroupY/).

The quotas assigned to user userX and the amount of it that you are currently using can be inspected with command

df -h /home/userX

When df is run from the is login server, its output is similar to the following:

gfontana@mufasa2-login:/home/shared$ df -h /home/gfontana/
Filesystem         Size  Used Avail Use% Mounted on
192.168.1.1:/home  150G   11G  139G   7% /home

Option -h provides human-readable values using measurement units such as K (KBytes), M (MBytes), G (GBytes)).

The data provided by df is the following:

Column "Filesystem"

the filesystem for which quota information is provided. This includes an (inconsequential) IP address because of the way the Virtual machine acting as login server is connected to the physical machine

Column "Size"

the disk quota assigned to the user

Column "Used"

the overall size of the files currently in the directory

Column "Avail"

how much space is still available in the directory before hitting the soft quota

Column "Use%"

percentage of the soft quota used up by the files currently in the directory

Column "Mounted on"

location of the directory in the filesystem of Mufasa

Quotas assigned by the quota system of Mufasa 2.0 are hard quotas. This means that the limit cannot be exceeded. When a user reaches their hard limit, they cannot use any more disk space: for them, the filesystem behaves as if the disks are out of space. Disk writes will fail, temporary files will fail to be created, and the user will start to see warnings and errors while performing common tasks. The only disk operation allowed is file deletion.

Finding out how much disk space is used by a directory

If your user has reading permission to directory /path/to/dir/ you can find out how much disk space is used by the directory with command du like this:

du -sh /path/to/dir/

The -sh flag is used to ask for options -s (which provides the overall size of the directory) and -h (which provides human-readable values using measurement units such as K (KBytes), M (MBytes), G (GBytes)).

In particular, you can find out how much disk space is used by your home directory with command

du -sh ~

In fact, in Linux the symbol ~ is shorthand for the path to the user's home directory.

If you want a detailed summary of how much disk space is used by each item (i.e., subdirectory or file) in a directory you own, use command

du -h /path/to/dir/

Hidden files and directories

In Linux, directories and files with a leading "." in their name are hidden. Usually these do not appear in listings, such as the output of the ls command, to avoid cluttering them up: however, they still occupy disk space.

The output of command du, however, also considers hidden elements and provides their size: therefore it can help you understand why the quota system says that you are using more disk space than reported by ls.

To get a list of all the files in a directory, including hidden ones, use command

ls -a

Changing file/directory ownership and permissions

Every file or directory in a Linux system is owned by both a user and a group. User and group ownerships are not connected, so a file can have as group owner a group that its user owner does not belong to.

Being able to manipulate who owns a file and what permissions any user has on that file is often important in a multi-user system such as Mufasa. This is a recapitulation of the main Linux commands to manipulate file permissions. Key commands are

chown to change user ownership

chgrp to change group ownership

chmod to change access permissions

Of course, they can only be employed by a user who has writing permission on the file or directory to be modified.

All three commands above accept option -R (uppercase) for recursive operation, so -if needed- you can change ownership and/or permissions of all contents of a directory and its subdirectories with a single command.

The syntax of chown commands is

chown <new_user_owner> <path/to/file>

where <new_user_owner> is the user part of the new file ownership.

The syntax of chgrp commands is

chgrp <new_group_owner> <path/to/file>

where <new_group_owner> is the group part of the new file ownership.

User and group ownership for a file can also be both changed at the same time with

chown <new_user_owner>:<new_group_owner> <path/to/file>

For what concerns chmod, the easiest way to use it makes use of symbolic descriptions of the permissions. The format for this is

chmod [users]<+|-><permissions> <path/to/file>

where

<path/to/file> is the file or directory that the change is applied to

[users] is ugo or a subset of it; the three letters correspond respectively:

to the user who owns <path/to/file>

to the group that owns <path/to/file>

to everyone else (others)

If [users] is not specified, it is assumed to be u

+ or - correspond to adding or removing permissions

<permissions> is rwx or a subset, corresponding to read, write and execute permissions

Note that r, w and x permission have a different meaning for files and for directories.

For files

permission r allows to read the contents of the file

permission w allows to change the contents of the file

permission x allows to execute the file (provided that it is a program: e.g., a shell script)

For directories

permission r allows to list the files within the directory

permission w allows to create, rename, or delete files within the directory

permission x allows to enter the directory (i.e., cd into it) and access its files

For instance, if the owner of file myfile.txt runs

chmod g+rwx myfile.txt

they are granting permission to read, write and execute myfile.txt to all the Linux users belonging to the same group of the user.

If the owner of directory mydir runs

chmod go-x mydir

they are taking away permission to enter directory mydir from everyone except the user who owns the directory.

If you want additional information about file and directory permissions in a Linux system work, this is a good online guide.

Containers

As a general rule, all computation performed on Mufasa must occur within containers. Below is the definition of a container according to Docker (the most diffuse container platform):

“A container is a sandboxed process on your machine that is isolated from all other processes on the host machine. When running a container, it uses an isolated filesystem. [containing] everything needed to run an application - all dependencies, configuration, scripts, binaries, etc. The image also contains other configuration for the container, such as environment variables, a default command to run, and other metadata.”

The container management system used by Mufasa 2.0 is Singularity.

Singularity provides a comprehensive user guide, but for basic usage of Mufasa this wiki -particularly User Jobs and Singularity- should contain all the necessary information.

Using containers allows each user of Mufasa to build the software environment that their job(s) require. In particular, using containers enables users to configure their own (containerized) system and install any required libraries on their own, without need to ask administrators to modify the configuration of Mufasa. As a consequence, users can freely experiment with their (containerized) system without risk to the work of other users and to the stability and reliability of Mufasa. In particular, containers allow users to run jobs that require multiple and/or obsolete versions of the same library. Finally, within their own containers any user can be root, i.e. have full administrator powers over the (container's) system. This is necessary to perform some operations that it would be impossible to perform on Mufasa, where users do not have root privileges.

How to run containers on Mufasa is explained in User Jobs. There is also a page of this wiki dedicated to Singularity.

The SLURM job scheduling system

Mufasa uses SLURM (Slurm Workload Manager, formerly known as Simple Linux Utility for Resource Management) to manage shared access to its resources. From SLURM's documentation:

“Slurm is an open source, fault-tolerant, and highly scalable cluster management and job scheduling system for large and small Linux clusters. Slurm has three key functions. First, it allocates exclusive and/or non-exclusive access to resources (compute nodes) to users for some duration of time so they can perform work. Second, it provides a framework for starting, executing, and monitoring work (normally a parallel job) on the set of allocated nodes. Finally, it arbitrates contention for resources by managing a queue of pending work.”

This wiki includes a section dedicated to SLURM. It explains how SLURM works, focusing on how it is configured on Mufasa.

Users of Mufasa must use SLURM to run any resource-heavy process. A resource-heavy process is any computing job that requires any of the following:

• GPUs
• multiple CPUs
• a significant amount of RAM.

Jobs run via SLURM have access to all the resources of Mufasa. Jobs run outside SLURM are executed by the login server virtual machine, which has minimal resources and no GPUs. Using SLURM is therefore the only way to execute resource-heavy jobs on Mufasa (this is a key difference between Mufasa 1.0 and Mufasa 2.0).

SLURM is capable of managing complex computing systems composed of multiple clusters (i.e. sets) of servers, each comprising one node (i.e. machine) or more. The case of Mufasa is the simplest of all: Mufasa is in fact the one node of a SLURM computing cluster composed of a single machine.