You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dear ALL,
There are some Rucio API that can be useful for some workflows.
At Belle II we use:
(format: DIRACAPI->RucioAPI )
adRepRule -> add_rule : Create rules on datasets (LPN). A rule after created triggers replication and registeration automatically in rucio. This also sets lifetime (if wanted) on any manual replication rule created.
Rather than doing replicate and registerReplica in DIRAC, this APi from rucio is asyncronous and automatic.
getRepStatus-> list_did_rules : To check the state of replicas (rule) . This provides more info like who owns the rule and lifetime of rule.
categoriesLPNs -> get_metadata_bulk (check did type of LPN and its child) : It is helpful to know if a LPN is one of the following:
a. container of container
b. container of dataset
c. dataset
d. file
(More info about the terminology at: https://rucio.cern.ch/documentation/file_dataset_container/)
userQuota -> get_local_account_usage and get_global_account_usage : these gives the info about user's storage usages, limit and quota left.
We expose these API in: DMS/Client/RucioClient.py. We can make a pull-request to show the current implementation we have at Belle II.
These will be helpful to other comunnity using rucio via DIRAC.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Dear ALL,
There are some Rucio API that can be useful for some workflows.
At Belle II we use:
(format: DIRACAPI->RucioAPI )
adRepRule -> add_rule : Create rules on datasets (LPN). A rule after created triggers replication and registeration automatically in rucio. This also sets lifetime (if wanted) on any manual replication rule created.
Rather than doing replicate and registerReplica in DIRAC, this APi from rucio is asyncronous and automatic.
getRepStatus-> list_did_rules : To check the state of replicas (rule) . This provides more info like who owns the rule and lifetime of rule.
categoriesLPNs -> get_metadata_bulk (check did type of LPN and its child) : It is helpful to know if a LPN is one of the following:
a. container of container
b. container of dataset
c. dataset
d. file
(More info about the terminology at: https://rucio.cern.ch/documentation/file_dataset_container/)
userQuota -> get_local_account_usage and get_global_account_usage : these gives the info about user's storage usages, limit and quota left.
We expose these API in: DMS/Client/RucioClient.py. We can make a pull-request to show the current implementation we have at Belle II.
These will be helpful to other comunnity using rucio via DIRAC.
Beta Was this translation helpful? Give feedback.
All reactions