Cargando…
Transitioning CMS to Rucio Data Managment
Following a thorough review in 2018, the CMS experiment at the CERN LHC decided to adopt Rucio as its new data management system. Rucio is emerging as a community software project and will replace an aging CMSonly system before the start-up of LHC Run 3 in 2021. Rucio was chosen after an evaluation...
Autor principal: | |
---|---|
Lenguaje: | eng |
Publicado: |
2020
|
Materias: | |
Acceso en línea: | https://dx.doi.org/10.1051/epjconf/202024504033 http://cds.cern.ch/record/2757339 |
_version_ | 1780969975762124800 |
---|---|
author | Vaandering, Eric |
author_facet | Vaandering, Eric |
author_sort | Vaandering, Eric |
collection | CERN |
description | Following a thorough review in 2018, the CMS experiment at the CERN LHC decided to adopt Rucio as its new data management system. Rucio is emerging as a community software project and will replace an aging CMSonly system before the start-up of LHC Run 3 in 2021. Rucio was chosen after an evaluation determined that Rucio could meet the technical and scale needs of CMS. The data management system for CMS needs to manage the current data sample of approximately 200 PB of data with 1 PB of transfers per day. The data management system must also have a development path suitable for LHC Run 4 (2026) data rates, which are expected to be 50 times larger.This contribution details the ongoing CMS adoption process as we replace our legacy system with Rucio, focusing on the challenges of integrating Rucio into an established set of experimental tools and procedures. This will include the migration of metadata, the construction of interfaces to the rest of the CMS computing tools, scale tests, operations, monitoring, and the plan to gradually turn over primary responsibility for the management of data to Rucio. A description of CMS user data management with Rucio will also be provided. |
id | oai-inspirehep.net-1831561 |
institution | Organización Europea para la Investigación Nuclear |
language | eng |
publishDate | 2020 |
record_format | invenio |
spelling | oai-inspirehep.net-18315612022-08-17T13:57:40Zdoi:10.1051/epjconf/202024504033http://cds.cern.ch/record/2757339engVaandering, EricTransitioning CMS to Rucio Data ManagmentComputing and ComputersFollowing a thorough review in 2018, the CMS experiment at the CERN LHC decided to adopt Rucio as its new data management system. Rucio is emerging as a community software project and will replace an aging CMSonly system before the start-up of LHC Run 3 in 2021. Rucio was chosen after an evaluation determined that Rucio could meet the technical and scale needs of CMS. The data management system for CMS needs to manage the current data sample of approximately 200 PB of data with 1 PB of transfers per day. The data management system must also have a development path suitable for LHC Run 4 (2026) data rates, which are expected to be 50 times larger.This contribution details the ongoing CMS adoption process as we replace our legacy system with Rucio, focusing on the challenges of integrating Rucio into an established set of experimental tools and procedures. This will include the migration of metadata, the construction of interfaces to the rest of the CMS computing tools, scale tests, operations, monitoring, and the plan to gradually turn over primary responsibility for the management of data to Rucio. A description of CMS user data management with Rucio will also be provided.FERMILAB-CONF-20-639-SCDoai:inspirehep.net:18315612020 |
spellingShingle | Computing and Computers Vaandering, Eric Transitioning CMS to Rucio Data Managment |
title | Transitioning CMS to Rucio Data Managment |
title_full | Transitioning CMS to Rucio Data Managment |
title_fullStr | Transitioning CMS to Rucio Data Managment |
title_full_unstemmed | Transitioning CMS to Rucio Data Managment |
title_short | Transitioning CMS to Rucio Data Managment |
title_sort | transitioning cms to rucio data managment |
topic | Computing and Computers |
url | https://dx.doi.org/10.1051/epjconf/202024504033 http://cds.cern.ch/record/2757339 |
work_keys_str_mv | AT vaanderingeric transitioningcmstoruciodatamanagment |