Building and using containers at HPC centres for the ATLAS experiment

¹ Duke University, Durham, NC, USA
² Argonne National Lab, Lemont, IL, USA
³ University of Illinois, Urbana-Champaign, Champaign, IL, USA
⁴ University of Texas, Arlington, Arlington, TX, USA
⁵ Brookhaven National Lab, Upton, NY, USA
⁶ Lawrence Berkeley National Lab, Berkeley, CA, USA
⁷ SLAC National Accelerator Lab, Menlo Park, CA, USA

^* e-mail: yangw@slac.stanford.edu

Published online: 17 September 2019

Abstract

The HPC environment presents several challenges to the ATLAS experiment in running their automated computational workflows smoothly and efficiently, in particular regarding issues such as software distribution and I/O load. A vital component of the LHC Computing Grid, CVMFS, is not always available in HPC environments. ATLAS computing has experimented with all-inclusive containers, and later developed an environment to produce such containers for both Shifter and Singularity. The all-inclusive containers include most of the recent ATLAS software releases, database releases, and other tools extracted from CVMFS. This helped ATLAS to distribute software automatically to HPC centres with an environment identical to those in CVMFS. It also significantly reduced the metadata I/O load to HPC shared file systems. The production operation at NERSC has proved that by using this type of containers, we can transparently fit into the previously developed ATLAS operation methods, and at the same time scale up to run many more jobs.