CVMFS at JLab


CVMFS (CernVM-File System) at JLab

What is it?

The CernVM-File System (CernVM-FS) provides a scalable, reliable, low-maintenance software distribution platform. It was originally developed for High Energy Physics (HEP) collaborations to distribute software across globally distributed computing resources.

Key characteristics:


JLab Specifics

At Jefferson Lab, CVMFS is preconfigured on ifarm and farm nodes.

Local repository access is optimized through the squid cache:

CVMFS_HTTP_PROXY="http://sci-squid.jlab.org:3128"

Software is published using OASIS (OSG Application Software Installation Service).


Example Usage on ifarm

CVMFS repositories function like locally installed software. For example:

% ls /cvmfs/oasis.opensciencegrid.org/
accre  auger    csiu  fermilab  glow   ilc   ligo  nanohub  osg           sbgrid
atlas  cmssoft  enmr  geant4    gluex  jlab  mis   nova     osg-software  snoplussnolabca

For Scicomp-provided software environments, see: Environment Modules.


Getting Data Into OASIS

Data placed in specific source directories is synchronized and published to CVMFS.

New top-level project directories require an update to the cronjob configuration. Users must submit a ServiceNow incident to request additions.

Changes (adds/removes) to the source directory are published at the next scheduled sync. After rsync completes, OSG processes the updated content and republishes it.


Log Files

Each project has a dedicated log file, which is rotated and purged periodically. Logs provide a reliable source for diagnosing:


Rsync Excludes

Each project directory includes an oasis_exclude.txt file. This file is passed to rsync’s --exclude-from option.

Important notes:


Restrictions (Effective January 20, 2026)

Beginning January 20, 2026, CVMFS access will be limited to a defined set of approved repositories. This change improves performance, reduces unnecessary mounts, and matches expected access patterns.


Impact

Only the following repositories will remain enabled:

All other repositories will be disabled and will no longer auto-mount on login or compute nodes.

If software, data, or workflows depend on a repository outside the approved list, users must notify Scientific Computing Operations.


Requesting Additional Repositories

To request the re-enabling of a repository, provide:

  1. Repository FQDN
  2. Usage description (software, data, workflow)
  3. User group or project needing access

Requests are reviewed on a case-by-case basis.


Need Additional Help?

Submit a ServiceNow incident for:


References