Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement: Revisit tier0-reaper and loadtest flux configs #846

Open
haozturk opened this issue Sep 23, 2024 · 0 comments
Open

Enhancement: Revisit tier0-reaper and loadtest flux configs #846

haozturk opened this issue Sep 23, 2024 · 0 comments

Comments

@haozturk
Copy link
Contributor

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

dmwm/rucio-flux#332
dmwm/rucio-flux#335

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant