Rucio: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 12: | Line 12: | ||
* [mailto:rucio-users@googlegroups.com public user group rucio-users@googlegroups.com], [mailto:rucio-dev@cern.ch developers rucio-dev@cern.ch] | * [mailto:rucio-users@googlegroups.com public user group rucio-users@googlegroups.com], [mailto:rucio-dev@cern.ch developers rucio-dev@cern.ch] | ||
* [https://indico.cern.ch/event/813752/contributions/4051564/attachments/2122693/3573056/DUNE_Rucio_GDB_2020_Oct_Wenlong.pdf DUNE status] | * [https://indico.cern.ch/event/813752/contributions/4051564/attachments/2122693/3573056/DUNE_Rucio_GDB_2020_Oct_Wenlong.pdf DUNE status] | ||
* Metacat [https://cdcvs.fnal.gov/redmine/projects/metacat redmine] [https://github.com/ivmfnal/metadata.git github] [https://metadatadb.readthedocs.io/en/latest/ docs] | |||
Revision as of 19:43, 12 August 2021
Introduction
Rucio is a CERN software system for storing file metadata and organizing the delivery of that data to users. Its primary features are scalability, flexibility, adaptive file replication, and built-in monitoring. It can use various backends for databases, various platforms for its servers and daemons, various transfer and storage method plug-ins, and a command line and python interface for users. If Mu2e were to adopt it, it would likely replace SAM metadata and ifdh. It likely has a prestage function, but is not clear if it has a SAM project functionality.