Rucio

This are basic instructions on rucio.

Find the full info on: https://twiki.cern.ch/twiki/bin/view/CMSPublic/Rucio

- You need to be on sl7 for the commands to work

- initialise the env:

source /cvmfs/cms.cern.ch/cmsset_default.sh
source /cvmfs/cms.cern.ch/rucio/setup-py3.sh
voms-proxy-init -voms cms -rfc -valid 192:00
export RUCIO_ACCOUNT=`whoami`

- in rucio, a transfer is called a rule. In order to create a rule:

rucio add-rule cms:/CMS/DATA/SET/NAME 1 T2_MY_SITE  
rucio add-rule cms:/CMS/DATA/SET/NAME#BLOCK-NAME 1 T2_MY_SITE

- if there is a lot of data, add

--asynchronous

- users can also request rules, who are then to be approved by the admins. This is done with 2 extra modifiers:

--ask-approval

and

--lifetime (in seconds; for reference, 30 days is 2592000 seconds)

- check your rules:

rucio list-rules --account $RUCIO_ACCOUNT List all the rules you have and their state
rucio rule-info [RULE_HASH] monitor the progress of your rule and any transfers it may have initiated

More info here

- requests can also be done for users, but I have not tested this.

- users can also be given quota’s

- datasets can be grouped into containers. This can be handy if several datasets are needed for a specific analysis. All of then can then also be removed together if the analysis is finished. This is done via rucio containers. More info here.

At the moment of writing this document, these were the settings for our site:

rucio list-rse-attributes T2_BE_IIHE
T2_BE_IIHE:              True
cms_type:                real
country:                 BE
ddm_quota:               3355000000000000
fts:                     https://fts3-cms.cern.ch:8446
lfn2pfn_algorithm:       cmstfc
pnn:                     T2_BE_IIHE
quota_approvers:         odevroed,rougny,srugovac
reaper:                  True
region:                  C
rule_approvers:          odevroed,rougny,srugovac
source_for_total_space:  static
source_for_used_space:   rucio
tier:                    2