Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Three butlers with Repos are setup at the three main Rubin processing sites.


SiteRepoCollection prefix
USDF/repo/mainHSC/runs/PDR2/VVDS/w_2024_02_DM-40654
FRDFhsc_pdr2_multisiteHSC/runs/PDR2/PDR2-VVDS-FR/w_2024_02_DM-40654
UKDFhsc_pdr2_multisiteHSC/runs/PDR2/PDR2-UK-VVDS/w_2024_02_DM-40654

To connect to Rucio, one needs to have the rucio-clients package installed.

...

  1. setup a current stack (for instance w_2024_12)
  2. pip install rucio-clients.  (you may need to update your version of pip)
  3. rucio ping. (this will report an error as you don't have a rucio.cfg file).
  4.  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
    
    


  5. Change the account = yanny line to match 
  6. export RUCIO_CONFIG=rucio.cfg 
  7. 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.
  8. export X509_USER_PROXY=x509up_u2768 (or whatever)
  9. try rucio ping again
  10. 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
  11. 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.
  12. 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