#12: Reduce the number of Celery queues used for job control
----------------------------+------------------------------------
Reporter: tflink | Owner: somebody
Type: enhancement | Status: new
Priority: major | Milestone: Semi-Public Deployment
Component: Job Management | Version:
Keywords: |
----------------------------+------------------------------------
At the moment, the build service requires one Celery queue per (version,
arch) tuple supported in the builders. This doesn't scale well and makes
rabbitmq admin a bit messier than it needs to be.
Celery does support adding attributes to tasks on a queue and the last
time I looked, celeryd can be configured to only take tasks with certain
attributes.
Change the queue setup such that there are fewer queues needed to support
distributed building (down to one queue, if possible and it makes sense)
--
Ticket URL: <https://fedorahosted.org/fedora-build-service/ticket/12>
fedora-build-service <https://fedorahosted.org/fedora-build-service>
A service to build fedora images with a somewhat arbitrary package set from the
standard fedora repos or builds from koji.
_______________________________________________
autoqa-devel mailing list
[email protected]
https://lists.fedorahosted.org/mailman/listinfo/autoqa-devel
