Grid5000:Home
 Grid'5000 is a precursor infrastructure of SLICES-RI, Scientific Large Scale Infrastructure for Computing/Communication Experimental Studies.
|
|
Grid'5000 is a large-scale and flexible testbed for experiment-driven research in all areas of computer science, with a focus on parallel and distributed computing, including Cloud, HPC, Big Data and AI. Key features:
Older documents:
|
Random pick of publications
Five random publications that benefited from Grid'5000 (at least 3007 overall):
- Enzo Isnard, Sébastien Héron, Mahmoud Elsawy, Stéphane Lanteri. Optimization of imaging systems containing metasurfaces using a ray-wave model. Metamaterials 2025 -19th International Congress on Artificial Materials for Novel Wave Phenomena, METAMORPHOSE VI AISBL; University of Amsterdam; AMOLF, Sep 2025, Amsterdam, Netherlands. hal-05250474 view on HAL pdf
- Honore Cesaire Mounah, Djob Mvondo, Julia Lawall, Yérom-David Bromberg. The Impact of Kernel Asynchronous APIs on the Performance of a Kernel VPN. SYSTOR 2025 - 18th ACM International System and Storage Conference, Sep 2025, Virtual conference, Israel. pp.167-173, 10.1145/3757347.3759133. hal-05211974 view on HAL pdf
- Ndeye-Emilie Mbengue, Pierre Monnin, Miguel Couceiro, Fabien Gandon. Which Are the Low-Resource Languages of the Semantic Web?. ESWC 2026 - 23rd European Semantic Web Conference, May 2026, Dubrovnik, Croatia. hal-05607932 view on HAL pdf
- Angelo Rodio, Giovanni Neglia, Zheng Chen, Erik G Larsson. A Unified Convergence Analysis for Semi-Decentralized Learning: Sampled-to-Sampled vs. Sampled-to-All Communication. AAAI-26 - 40th Annual AAAI Conference on Artificial Intelligence, Jan 2026, Singapore, Singapore. hal-05423080 view on HAL pdf
- Jérémie Rodez, Patricia Stolf, Thierry Monteil. Placement of Distributed Machine Learning Services for AI- and Smart Grid-Enabled IoT Platforms. 2026. hal-05279358 view on HAL pdf
Latest news
Debian 13 "Trixie" std environment is now the default environment on (almost) all nodes
Dear users,
We are pleased to announce that Debian 13 (Trixie) std environment is
now the default environment on most nodes. See `kaenv3 -l debian%13%` for a list of available variants.
There is some significant evolutions, particularly regarding the
environment modules. Indeed, some components that were included in the environment images are now provided by modules loading, including CUDA, ROCm and OpenMPI.
Node network interface now have both IPv4 and (public) IPv6 addresses
by default, which should have no impact on most uses.
For more informations, see the Release Notes, available at
https://www.grid5000.fr/w/Debian_13_Trixie_environments_release_notes
As previous default environment move, frontend of every sites have been reinstalled in Debian 13 too.
If you have any questions or problems, please contact <support-staff@lists.grid5000.fr>
Best regards,
Nicolas Perrin, for Abaca and Grid’5000/SLICES-FR
Inria, DSI Service Production
-- Grid'5000 Team 14:54, 26 Aug 2026 (CEST)
Some clusters under Debian 13 "Trixie" environment by default and migration maintenance
Dear users,
The default standard environment has changed to Debian 13 for some
selected clusters over the past few weeks.
Here they are:
This is a key step towards the widespread deployment of Debian13. Most
clusters will be switched to a Debian 13 default environment Wednesday 26 August 2026.
If you need to, all the variants images (min, nfs, big) are available
for deployment, see `kaenv3 -l debian%13%` on frontends to list them.
Remember that there is a significant change concerning the modules. See
the preview announce : https://www.grid5000.fr/w/News#Upcoming_changes_to_modules
Best regards,
For Abaca and Grid'5000/SLICES-FR,
Nicolas Perrin
-- Grid'5000 Team 16:00, 02 Jul 2026 (CEST)
Hello everyone,
Let's start with a quick TLDR, details on the rationale and implementation are available below: new modules will be available with the new standard environment, and are already live for testing (but not activated by default).
If you want to test them you need to run the following commands:
unset MODULEPATH
module use /grid5000/guix-modules/x86_64/latest /grid5000/spack/module-others
Now for more details: for the past months we have been working on updating the standard environment and the way we provide modules.
The current way uses Spack under the hood, and is tightly bound to the underlying operating system.
It's been proven to be quite a burden for the team, and therefore we are changing the way we manage modules to:
- use a solution oblivious to the Linux flavor; - have means to update software versions automatically, and a clear release cycle; - actually have something reproducible; - be able to automatically test our most sensitive modules when they change (on both OAR and SLURM clusters).
Under the hood we switched to Guix to manage them²; it will be totally transparent for you.
The upcoming modules are located in `/grid5000/guix-modules/x86_64`, and you can try them today!
In order to use them you need to perform the following commands¹:
unset MODULEPATH
module use /grid5000/guix-modules/x86_64/latest
The list of modules for the `latest` release is available here:
https://api.grid5000.fr/explorer/software.
We know it's missing a few software compared to the current modules, we've tracked them here.
These should b...
Changes to VS Code and AI Extensions Usage on Frontend
Recently, we have observed a critical increase in resource consumption (CPU and memory) on these nodes. This is primarily caused by VS Code Server (or similar) instances and associated AI-assisted coding extensions (such as Copilot, Tabnine, or local LLM agents) running directly on the frontend.
As a reminder, frontends are strictly dedicated to lightweight tasks: code editing, file management, and job submission. Running heavy background processes or AI agents on these shared machines degrades performance for the entire community and risks crashing the machines. Frontend are not sized for heavy code/system compilation/build either. Heavy tasks must be run on reserved nodes.
What is changing:
- ban on frontend: running VS Code Server (or similar), AI extensions, or any background development agents directly on the frontend will shortly be prohibited. - automated cleanup: we will actively monitor these nodes. Any unauthorized, resource-intensive processes or persistent VS Code servers found running on the login nodes will be terminated without prior warning.
How to continue using VS Code and AI tools?:
We fully understand that these tools could be essential for your work. Therefore, this usage is completely permitted and supported on the compute nodes.
To use VS Code and your AI agents properly, you must schedule an interactive session via the batch scheduler (OAR). You can do this by:
- Requesting an interactive allocation using oarsub -I.
- Tunneling your VS Code Remote-SSH connection directly to the allocated compute node instead of the frontend
This ensures you have dedicated resources for your AI tools without impacting other users.
-- Grid'5000 Team 16:00, 15 Jun 2026 (CEST)
Grid'5000 sites
Current funding
INRIA
|
CNRS
|
UniversitiesIMT Atlantique |
Regional councilsAquitaine |
