Enhancement: Unify Loadtest and CMS Rucio Client Images

[eachristgr]

Enhancement Description

Currently, the loadtest uses its own Rucio client image [1], which is released through a separate action [2], distinct from the one managing the CMS Rucio client release [3]. This separation creates a versioning issue: when the CMS Rucio client is updated, the loadtest action will not be triggered, causing the loadtest to use an outdated client version.

For example, the current CMS Rucio client version is 35.6.0, while the loadtest client remains at 1.31.7 due to this discrepancy.

[1] https://github.com/dmwm/rucio-flux/blob/c8dd870996d93f64a13bc4c7ad08714673263516/apps/production/prod-loadtest.yaml#L7-L10
[2] https://github.com/dmwm/CMSRucio/actions/workflows/loadtest-docker-image.yml
[3] https://github.com/dmwm/CMSRucio/actions/workflows/rucio-release-images.yml

Use Case

• Ensuring that loadtest always run with the latest CMS Rucio client version.
• Avoiding manual intervention to trigger loadtest image updates.
• Streamlining the release process by consolidating image builds.

Possible Solution

Instead of maintaining a separate image, modify the CMS Rucio client Dockerfile [1] to also include the required loadtest components. The current Loadtest Dockerfile [2] simply extends the CMS Rucio client image and copies the loadtest directory. This operation can be integrated directly into the CMS Rucio client Dockerfile. This change will allow both components to use a single image. Additional updates may be needed in Flux configuration files [3], [4] to automate deployment in line with other services.

[1] https://github.com/dmwm/CMSRucio/blob/master/docker/rucio_client/Dockerfile
[2] https://github.com/dmwm/CMSRucio/blob/master/docker/rucio_client/Dockerfile.loadtest
[3] https://github.com/dmwm/rucio-flux/blob/main/apps/options/loadtest/loadtest-helm.yaml
[4] https://github.com/dmwm/rucio-flux/blob/main/apps/production/prod-loadtest.yaml

Related Issues

No response