...
Three butlers with Repos are setup at the three main Rubin processing sites.
Site | Repo | Collection prefix |
---|---|---|
USDF | /repo/main | HSC/runs/PDR2/VVDS/w_2024_02_DM-40654 |
FRDF | hsc_pdr2_multisite | HSC/runs/PDR2/PDR2-VVDS-FR/w_2024_02_DM-40654 |
UKDF | hsc_pdr2_multisite | HSC/runs/PDR2/PDR2-UK-VVDS/w_2024_02_DM-40654 |
To connect to Rucio, one needs to have the rucio-clients package installed.
...
- setup a current stack (for instance w_2024_12)
- pip install rucio-clients. (you may need to update your version of pip)
- rucio ping. (this will report an error as you don't have a rucio.cfg file).
- Make a rucio config rucio.cfg file which looks like this:
Code Block [client] # Rubin Hosts rucio_host = https://rubin-rucio.slac.stanford.edu:8443 auth_host = https://rubin-rucio.slac.stanford.edu:8443 #rucio_host = https://rubin-rucio-dev.slac.stanford.edu:8443 #auth_host = https://rubin-rucio-dev.slac.stanford.edu:8443 account = yanny ca_cert = /etc/grid-security/certificates auth_type = x509_proxy request_retries = 3
- Change the account = yanny line to match
- export RUCIO_CONFIG=rucio.cfg
- get a kx509 token. There are several ways to do this. One way is to do 'kx509' on a machine which has kx509 installed, this will make a x509 cert in /tmp/<something>. copy /tmp/<something> to the same place you have the rucio.cfg file.
- export X509_USER_PROXY=x509up_u2768 (or whatever)
- try rucio ping again
- you will also need to download a certificate package, unwind it and install it and point to it with export X509_CERT_DIR=etc/grid-security/certificates
- then rucio ping again ... if you have permission denied, do a voms-proxy-info command on the same place you did your 'kx509' to get your cert and email or message the DN Distinguished name string (DC=/Name=/....) to Brandon or Yuyi to add you to the list of authorized Rubin Rucio users.
- Then when that is ok, try rucio ping again. It should return the version of the rucio server (something like 34.0 or higher)
Once you have a working version of rucio-clients installed and a valid X509 PROXY and access to Rubin Rucio, you can try out various rucio commands to see what's in Rubin Rucio.
Some common ones are:
rucio -h (help)
rucio list-scopes
rucio list-dids <scope>:* (list all datasets)
rucio list-dids <scope>:* --filter 'type=all'. (list all datasets and all files in each dataset)
rucio list-rses (list all rucio storage endpoints)
rucio list-file-replicas <scope>:<name> (show which replicas in which rse a did with <scope>:<name> is located in)
rucio get-metadata <scope>:<name>. (list metadata for a scope:name)
To register objects that are in a butler into a RUCIO rse, one uses the dm_rucio_register command available from github