infrastructure on Gaia Lab · Blog

Serving models and looking after the cluster: the infrastructure behind the other lines

Tue, 22 Sep 2026 14:15:00 +0200

Ninth and final instalment of Cluster X-ray. Here we group what does not fit into a research line but shows up in almost everyone’s scripts.

Serving models so that others can work #

Several lines in the series need a large model up and running: a judge to score responses, a synthetic data generator, a coding assistant. On a cluster with one GPU per node, the natural way to serve it is a Slurm job that brings up vLLM, waits for it to respond, registers with a shared proxy and stays there until its time runs out. On finishing, it deregisters: the model appears in and disappears from the catalogue along with the job.

What really runs on our cluster, read from the scripts themselves

Tue, 22 Sep 2026 10:00:00 +0200

A cluster’s job history is usually a wall of six-digit identifiers and cryptic names —mcpfw_cc, eval_dynamic_pid, boltz2— that say everything to whoever launched them and nothing to anyone else. But if you keep the scripts, the wall turns into a document: people write down why they do things, especially when a batch costs money and a night of waiting.

What it connects to: the 5G and B5G experimentation infrastructure of the Espinardo Campus

Thu, 10 Sep 2026 10:00:00 +0200

When we present the experimental vehicle we usually dwell on what it carries on board. In this post we turn the question around and explain what it connects to: the vehicle is the mobile edge of the 5G and B5G experimentation infrastructure that we at Gaia Lab, within the ANTS group at the University of Murcia, have deployed on the Espinardo Campus. We describe its five building blocks and how the vehicle closes the loop.