Abstract
DIRAC and Rucio are two standard pieces of software widely used in the HEP domain. DIRAC provides Workload and Data Management functionalities, among other things, while Rucio is a dedicated, advanced Distributed Data Management system. Many communities that already use DIRAC have expressed their interest in using DIRAC for Workload Management in combination with Rucio for Data Management. In this paper, we describe the integration of the Rucio File Catalog into DIRAC that was initially developed for the Belle II collaboration.
Highlights
DIRAC (Distributed Infrastructure with Remote Agent Control) [1] is a piece of software initially developed for the LHCb collaboration [2]
Each file in the catalog has a Logical File Name (LFN) and each LFN can have a list of associated Physical File Names (PFN) that correspond to the physical copies of the files at different sites
Before the implementation of the Rucio File Catalog (RFC) plugin, two file catalogs were supported by DIRAC:
Summary
DIRAC (Distributed Infrastructure with Remote Agent Control) [1] is a piece of software initially developed for the LHCb collaboration [2]. It is designed as "interware" as it provides a complete solution for managing distributed resources. Developed by the ATLAS collaboration [4], Rucio has quickly gained popularity outside ATLAS due to its advanced features.
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
