lfoss/2025b now available in the EESSI RISC-V stackThe EESSI RISC-V software stack available through the dev.eessi.io/riscv repository
now includes the lfoss/2025b toolchain.
This is an important milestone for the RISC-V enablement work in EESSI, since it brings a modern LLVM-based software toolchain to the growing collection of software available for RISC-V systems through EESSI.
Building on our initial HPE/Cray Slingshot‑11 results, we further refined MPI tuning and validated the setup using EESSI 2025.06.
The outcome is a significant performance improvement, bringing MPI support in EESSI much closer to vendor tuned Cray MPI environments.
MUSICA (Multi-Site Computer Austria) is the latest addition to Austria's national supercomputing infrastructure. The system's compute resources are distributed across three locations in Austria: Vienna, Innsbruck, and Linz. We describe the process that led to the adoption of EESSI as a base for the software stack on the MUSICA system at the Austrian Scientific Computing (ASC) research center.
Since our blog post in Feb'25 announcing that EESSI will be integrated in the EuroHPC Federation Platform (EFP), we have been working hard on making this a reality.
The Federated Software Catalog (FSC) component of EFP will use EESSI as a base. As a result, EESSI will soon be available on all EuroHPC supercomputers.
In fact, EESSI is already available on the majority of them today!
The HPC software landscape offers powerful tools for managing scientific software, such as EasyBuild and Spack.
EESSI provides a ready-to-use software stack with thousands of optimized software installations that were built with EasyBuild.
Imagine you are working on an HPC system with EESSI already available. You have access to a wealth of optimized installations for scientific software packages, libraries, tools, as well as compilers. But you need to install a new tool or a specific version of a package that's not in EESSI yet.
You can already extend EESSI with new software through the EESSI-extend module. This utility provides you with a pre-configured EasyBuild installation that you can use to build packages from easyconfig files.
Like EasyBuild, Spack is a flexible build tool that also offers a vast repository of build recipes maintained by a large and active community, making it a familiar tool for many HPC users. By enabling Spack to leverage software installations already available in EESSI as dependencies, we can offer users the best of both worlds: the convenience of a pre-built, optimized software stack combined with the flexibility to quickly build new packages using tools they already know.
This year's FOSDEM exceeded all expectations a first-time attendee like me could have. Filled with interesting talks, wide range of diverse people and impactful projects, I bring back home a bag full of stickers, lovely memories and some Belgian chocolates.
Bringing EESSI and EMBL's computational community closer together during EMBL's CoDash hackathon. Simultaneously working towards bringing a large repository of scientific software in-use at EMBL's HPC cluster to EESSI.
EESSI provides a rich set of software installations, which were built and installed using EasyBuild.
Can we convince Spack to reuse software installed in EESSI, and by doing so make EESSI more attractive to those of you who prefer using Spack over EasyBuild?
Several people have expressed interest in exposing the software installations provided by EESSI to Spack, so they can be used as dependencies when building and installing software with Spack.
Recently, we have explored how this could be achieved through a proof-of-concept with QuantumESPRESSO.
The goal here is to build and install only QuantumESPRESSO with Spack, and leveraging software installations from EESSI for all required dependencies, including the compiler and libraries for MPI, BLAS/LAPACK, FFTW, etc.
Kubernetes, also known as K8s, is an open-source container orchestration platform widely used for automating the deployment, scaling, and management of containerized applications. Normally, deploying a specific application on Kubernetes requires preparing a container image including the target software and all its dependencies. Furthermore, the software should be optimized depending on the target hardware architecture to achieve the best performance, which could prove particularly challenging especially on heterogeneous systems. Implementing an integration of EESSI with Kubernetes will allow the many sites and enterprises that already use K8s to more easily get access to a wide variety of optimized software installations.
In this blog post, we present a proof of concept (PoC) for deploying EESSI on a Kubernetes cluster.
In a previous blog post, “An example CI workflow that leverages EESSI CI tools”, Pedro Santos Neves explained how to set up a GitLab CI workflow. This post will focus on GitHub CI workflows and show how to access the development repository of EESSI.