This release is a pre-release and may not be stable for production use.
rucio_register
Command and API to add Butler specific information to Rucio metadata.
This is a guide to using the rucio_register command for registering Butler files with Rucio.
Butler files are expected to be located in a Rucio directory structure, below a directory named for a Rucio scope. For example, if the root of the Rucio directory is "/rucio/disks/xrd1/rucio" and the Rucio scope is "test", the files should be located below "/rucio/disks/xrd1/rucio/test".
Example
The command "rucio-register" registers files with Rucio. This command requires a YAML configuration file which specifies the Rucio rse and scope, as well as the root of the directory where files are deposited, and the external reference to the Rucio RSE. This configuration file can be specified on the command line, or in the environment variable RUCIO_REGISTER_CONFIG.
The command can register data-products or raws:
for data products:
rucio-register data-products -r /rucio/disks/xrd1/rucio/test -c HSC/runs/RC2/w_2023_32/DM-40356/20230814T170253Z -t visitSummary -d rubin_dataset -C register_config.yaml
for raws:
rucio-register raws -r /rucio/disks/xrd1/rucio/test -d rubin_dataset --collections LATISS/raw/all -C register_config.yaml
Note that for raws, this is similar to how one uses the butler command
This command looks for files registered in the butler repo "/repo/main" using the "dataset-type" and "collections" arguments to query the butler. Note that the repo name's suffix is the Rucio "scope". In this example, that scope is "main".
The resulting datasets' files are registered with Rucio, as specified in the "config.yaml" file. Additionally, those files are registered with the Rucio dataset specified by the "rucio-dataset" argument.
config.yaml
The config.yaml file includes information which specifies the Rucio RSE to use, the Rucio scope, the local root of the RSE, and the URL prefix of the location where Rucio stores the files.
rucio_rse: "XRD1"
scope: "main"
rse_root: "/rucio/disks/xrd1/rucio"
dtn_url: "root://xrd1:1094//rucio"
Metadata
Release files for lsst-rucio-register 29.2.2rc1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| lsst_rucio_register-29.2.2rc1.tar.gz | 25.5 kB | Without provenance | Details for lsst_rucio_register-29.2.2rc1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lsst_rucio_register-29.2.2rc1-py3-none-any.whl | Python 3 | none | any | Details for lsst_rucio_register-29.2.2rc1-py3-none-any.whl |
Total release size: 53.6 kB
Release files / lsst_rucio_register-29.2.2rc1.tar.gz
| Download URL | lsst_rucio_register-29.2.2rc1.tar.gz |
|---|---|
| Size | 25.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aba97875838dbefe31485c3759a684235675f638f6ab5193e29bd946a6662f0c
|
|
BLAKE2b-256 checksum How to use checksums |
c4af8678392f303136dfc4bec8c178bb2ee10650e2256e3c2c9fce9b0dffd419
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / lsst_rucio_register-29.2.2rc1-py3-none-any.whl
| Download URL | lsst_rucio_register-29.2.2rc1-py3-none-any.whl |
|---|---|
| Size | 28.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
66e6260fad24b8c6cc036a1022d29a729e220433198c9d9f14a375d36f5ede1f
|
|
BLAKE2b-256 checksum How to use checksums |
b04e72e2ffb60f232ddf9cbc4fe3365219c7f84ff742bb07201d6443934ca0aa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for lsst-rucio-register 29.2.2rc1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.