Grid site testing for ATLAS with HammerCloud

J Elmsheuser,D Van Der Ster,F Hönig,F Legger,F G Sciacca,R Medrano Llamas,The Atlas Collaboration

doi:10.1088/1742-6596/513/3/032030

Abstract

With the exponential growth of LHC (Large Hadron Collider) data in 2012, distributed computing has become the established way to analyze collider data. The ATLAS grid infrastructure includes more than 130 sites worldwide, ranging from large national computing centers to smaller university clusters. HammerCloud was previously introduced with the goals of enabling virtual organisations (VO) and site-administrators to run validation tests of the site and software infrastructure in an automated or on-demand manner. The HammerCloud infrastructure has been constantly improved to support the addition of new test workflows. These new workflows comprise e.g. tests of the ATLAS nightly build system, ATLAS Monte Carlo production system, XRootD federation (FAX) and new site stress test workflows. We report on the development, optimization and results of the various components in the HammerCloud framework.

Highlights

The LHC at CERN is colliding protons or heavy ions at unprecedented center-of-mass energies and these collisions are recorded by several experiments including the ATLAS experiment [1]
The pilot code needs to adapt to the latest Grid middleware code updates and experiment workflow changes. This requires constant code validation which is done with a set of continuous HammerCloud functional tests that uses the latest pilot code version before it goes into large scale production;
Input data access modes are used at every site, each site needs an individual setup for Federated XRootD (FAX) testing

Summary

Introduction

The LHC at CERN is colliding protons or heavy ions at unprecedented center-of-mass energies and these collisions are recorded by several experiments including the ATLAS experiment [1]. Stress testing scheduled on demand: these tests are used to measure experiment applications under different site and application configurations and evaluate their performances; Site functional tests: a continuous flow of jobs is sent to the PanDA analysis and production system queues to validate their functionality. This requires constant code validation which is done with a set of continuous HammerCloud functional tests that uses the latest pilot code version before it goes into large scale production;

Results

Conclusion