CMS Rucio
Welcome to the CMS Rucio documentation TWiki! This page contains details on CMS-specific aspects of the Rucio data management system. The Rucio core documentation is maintained in a separate page, and is often referenced within these pages. Rucio logo
During the initial phase of CMS Rucio adoption, all interaction with the rucio system will be through a command-line interface, which can be accessed by sourcing the setup script and telling Rucio who you are:
source /cvmfs/
voms-proxy-init -voms cms -rfc -valid 192:00
source /cvmfs/
export RUCIO_ACCOUNT=`whoami` # Or your CERN username if it differs
You can then issue the command rucio --help to understand all your options.

Rosetta stone

Some terminology differs between the Rucio system and the historical terms developed by CMS. In many cases, there is a one-to-one mapping between terms, and in a few cases there is a name conflict that means something different in Rucio than in the PhEDEX/Dynamo data management system. We try to identify legacy terms throughout this documentation, giving precedence to the Rucio definition when ambiguous.
CMS term Rucio term Description
various DID A Data Identifier (DID) is a file, dataset, or container
Block Dataset DID A rucio dataset is a collection of files. Like in PhEDEx, this is the smallest unit of data that can be individually addressed by a replication rule.
CMS Dataset Container DID A rucio container is a collection of other rucio dataset or container DIDs (arbitrarily nested). Each CMS dataset corresponds to one rucio container that is a collection of all the rucio datasets (CMS blocks) belonging to that CMS dataset
N/A Scope A Rucio DID consists of a scope and a name. The name is the file/block/dataset/container name. The scope is a new concept for CMS. All official data will be in the 'cms' scope; user data will be in many scopes named like user.johndoe
PhEDEx Subscription Rule (partial) A policy that, when created, initiates a set of transfers. Unlike in PhEDEx, where only a single subscription can pin a block to a PhEDEx group and site, multiple rules may map onto the same physical DID replicas.
N/A Quota Users and user groups in Rucio can be assigned a quota at a site, which removes the need for site administrators to manually approve rule requests.

Edit | Attach | Watch | Print version | History: r29 < r28 < r27 < r26 < r25 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r29 - 2020-10-15 - NicholasCharlesSmith1
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CMSPublic All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback