1 of 5

ScienceBox + VRE brainstorming

Giovanni Guerrieri, Enrique García (CERN)

June 30th 2025 - ScienceBox + VRE meeting

2 of 5

2

  1. AAI: INDIGO IAM
  2. The Rucio Data Lake: Standalone Rucio instance running on CERN premises
  3. REANA: Standalone REANA instance running on CERN premises
  4. CVMFS: mounted on the VRE + ESCAPE-specific repo to host the collaboration’s SFT stack
  5. JupyterHub: Central aggregator for services and functionalities

The ESCAPE VRE

3 of 5

3

User’s interactions with the VRE

What makes the VRE, the VRE

4 of 5

4

Towards the VREx

The next generation of VREs

Two-fold scope

  • CERN / ESCAPE
    1. Consolidate the VRE concept and functionalities within ESCAPE (ET, ESO, CTAO, etc)
      • e.g. common Helm charts
    2. Help bridging existing services at CERN and build a modular / plug-n-play solution
    3. Expose an easy to access, fully integrated analysis environment for SME-like communities

  • EOSC
    • Streamline EOSC AAI integration within the VRE (ongoing summer project with REANA)
    • Deploy part of the VRE functionality (REANA and Rucio exts.) on the existing EOSC EU Node
    • Enrich the current VRE configuration to accommodate for more CERN services

5 of 5

5

ScienceBox

Initial inputs

From Kuba’s suggestions on the VREx proposal

  • Leverage successful ScienceBox deployments on commercial clouds to establish a baseline for connecting the VRE to off-premise resources.
  • Streamline charts between ScienceBox components (SWAN, EOS and CERNBox) and the base layer VRE charts
    • Optional add-on(s) for sites that want to deploy CERN storage technologies in addition to other CERN developed products.
    • Leverage federation capability of the Sync&Share storage deployed at the EOSC EU node.
  • Further synergies to be explored with the EOSC Data Commons project (IT-SD)