[fedora-build-service] #12: Reduce the number of Celery queues used for job control
by fedora-badges
#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.
11 years, 6 months
Re: [fedora-build-service] #6: Enhance Command Line Client UI (was: Ehance Command Line Client UI)
by fedora-badges
#6: Enhance Command Line Client UI
-----------------------------+--------------------------------
Reporter: amitksaha | Owner: amitksaha
Type: enhancement | Status: new
Priority: major | Milestone: Initial Deployment
Component: Image Building | Version:
Resolution: | Keywords:
-----------------------------+--------------------------------
Changes (by tflink):
* component: General => Image Building
* milestone: => Initial Deployment
Comment:
Fixing typo and assigning to milestone. This will need more detail but
that will probably be after some discussion on a mailing list.
For now, I'm putting this as 'initial deployment' but it could probably be
put off until later.
--
Ticket URL: <https://fedorahosted.org/fedora-build-service/ticket/6#comment:1>
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.
11 years, 6 months
Re: [fedora-build-service] #8: Ability to Spawn/Provision on-demand VM's for building tasks
by fedora-badges
#8: Ability to Spawn/Provision on-demand VM's for building tasks
-----------------------------+-----------------------------
Reporter: amitksaha | Owner: somebody
Type: enhancement | Status: new
Priority: minor | Milestone: Glorious Future
Component: Job Management | Version:
Resolution: | Keywords:
-----------------------------+-----------------------------
Changes (by tflink):
* type: task => enhancement
* priority: major => minor
* milestone: => Glorious Future
* component: Image Building => Job Management
Comment:
I can think of a couple options for getting this done:
1. Use celery to control the bare metal hosts that we have available
1. Look into integrating with the new fedora infra cloud
I'm fine with either but I suspect that looking into using the private
cloud already set up by infra would be a better choice for us.
--
Ticket URL: <https://fedorahosted.org/fedora-build-service/ticket/8#comment:1>
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.
11 years, 6 months
[fedora-build-service] #10: image_builder doesn't clean up after itself
by fedora-badges
#10: image_builder doesn't clean up after itself
----------------------------+--------------------------------
Reporter: tflink | Owner: somebody
Type: defect | Status: new
Priority: major | Milestone: Initial Deployment
Component: Image Building | Version:
Keywords: |
----------------------------+--------------------------------
In a system where the builders are either disposable VMs or mock chroots
that are destroyed every time, not deleting work files after a build or
before a new build isn't a big deal.
However, the system currently re-uses build environments and there can be
problems with image building when the environment is re-used and not
cleaned. I've seen this most often when the first environment is using a
different kernel version from the current build.
If we end up using disposable virtual machines or switch to using mock,
this can be closed but for the short term, it would be wise to check for
empty work dirs before building and delete them if they aren't empty.
--
Ticket URL: <https://fedorahosted.org/fedora-build-service/ticket/10>
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.
11 years, 6 months