fedora-infrastructure

#9021 Move the loopabull tasks to openshift
Closed: Fixed by pingou. Opened by pingou.

Closed: Fixed
Reopen Issue

Describe what you would like us to do:

We currently have 3 or 4 tasks/jobs running in loopabull for which using ansible is a little bit of an overkill. I'd like to see if we can design a fedora-messaging consumer supporting plugins and allowing to move these jobs out of loopabull.

We should be able to scale up this consumer (which would be easy in openshift and rabbitmq since they would use the same queue).

We should be able to easily add more plugins in the future if desired.

It should preferably all be in one project in openshift (whether we do one pod/consumer or severl pods of one consumer + plugins) so it's easy from an administration point of view to go and find what is misbehaving if something is.

When do you need this to be done by? (YYYY/MM/DD)

Before the colo-move is over as this would spare us from re-deploying loopabull there.

This has been implemented in https://pagure.io/fedora-infra/toddlers

Metadata Update from @smooge:
- Issue assigned to pingou
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: groomed, low-trouble, medium-gain

Toddlers is now running in openshift and loopabull has been stopped.

I'm going to open another ticket to clean up the loopabull host and ansible if toddler keeps up with its work.

Metadata Update from @pingou:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata

low-trouble medium-gain

None
None
Normal
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.