Is your feature request related to a problem? Please describe.
As reasonably discussed in this GH issue:https://github.com/dmwm/WMCore/issues/12044
and 3 months ago when dm_weight was deployed in Rucio, we need to move away from the ddm_quota.
The dm_weight RSE attribute is a value normalized between 0 and 100, meant to reflect how usable an RSE is (e.g. storage available, etc).
Describe the solution you'd like
We need to update both:
WMCore codebase
and services_config service configuration repo (in all 3 branches)
to stop using the ddm_quota as a default value, likely switching it over to the dm_weight one.
TBD: we still have to discuss with the DM team whether we can simply use this attribute, or if we have to also verify the Rucio account storage space available before making input data placements (primary and pileup datasets).
Describe alternatives you've considered
Details of how to implement it for input data placement are yet to be discussed.
Impact of the new feature WM in general
Is your feature request related to a problem? Please describe. As reasonably discussed in this GH issue:https://github.com/dmwm/WMCore/issues/12044 and 3 months ago when
dm_weight
was deployed in Rucio, we need to move away from theddm_quota
.The
dm_weight
RSE attribute is a value normalized between 0 and 100, meant to reflect how usable an RSE is (e.g. storage available, etc).Describe the solution you'd like We need to update both:
ddm_quota
as a default value, likely switching it over to thedm_weight
one.NOTE that this documentation https://gitlab.cern.ch/dmwm/wmcore-docs/-/blob/master/docs/wmcore/Rucio-rules-created-by-WM.md?ref_type=heads needs to be updated accordingly.
TBD: we still have to discuss with the DM team whether we can simply use this attribute, or if we have to also verify the Rucio account storage space available before making input data placements (primary and pileup datasets).
Describe alternatives you've considered Details of how to implement it for input data placement are yet to be discussed.
Additional context None