Rename appropriately workers and queues
Historic choices were made on some queue or worker names without thinking too much on the future implications. Those have now become inconsistent with their usage. This creates a bit of confusion when reading or actually operating. Now that we know a tad better what's what, it's time to concistently rename those.
Plan:
- swh/infra/ci-cd/swh-charts@866627bd Rename large_repository: prefix queues for large repository workers
- Dropping the use of oneshot* queues prefix (we'll spawn them back if we need some extra oneshot workers)
- Rename "addforgenow" workers (pods) to "add-forge-now"
- Rename "highpriority" workers (pods) to "save-code-now" ('-' in worker name is supported, e.g. 'large-repository' workers are fine since the start)
- Deprecate the use of highpriority image to the benefit of savecodenow image
Activity
mentioned in commit swh/infra/ci-cd/swh-charts@866627bd
assigned to @ardumont
added activity::MRO label
changed milestone to %MRO 2023
mentioned in commit swh/infra/ci-cd/swh-charts@8b2a5136
mentioned in commit swh/infra/ci-cd/swh-charts@d3f27076
mentioned in commit ardumont/swh-apps@e8e51b5b
mentioned in commit swh/infra/ci-cd/swh-charts@593a30be
mentioned in commit swh/infra/ci-cd/swh-charts@d748cedb
mentioned in commit ardumont/swh-apps@c405155c
Image built and referenced. Loaders deployed with proper names and images (first staging then production). Everything runs smoothly.
(Grafana tagged too).
[1] https://jenkins.softwareheritage.org/job/swh-apps/job/build-docker-image/88/console