Whenever we need to include a new daemon, we need to explicitly set its count to 0 in tier0-reaper [1] and loadtest [2] configuration which seem to be inheriting the general prod rucio config [3]. Often times, this is overlooked and requires extra attention to fix.
Enhancement Description
Whenever we need to include a new daemon, we need to explicitly set its count to 0 in tier0-reaper [1] and loadtest [2] configuration which seem to be inheriting the general prod rucio config [3]. Often times, this is overlooked and requires extra attention to fix.
[1] https://github.com/dmwm/rucio-flux/blob/main/apps/production/tier0-reaper-rucio-daemons.yaml [2] https://github.com/dmwm/rucio-flux/blob/main/apps/production/loadtest-rucio-daemons.yaml [3] https://github.com/dmwm/rucio-flux/blob/main/apps/production/prod-rucio-daemons.yaml
Use Case
Defining new daemons
Possible Solution
I haven't investigated, yet
Related Issues
https://github.com/dmwm/rucio-flux/pull/332 https://github.com/dmwm/rucio-flux/pull/335