#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.
#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.
#417: Prune old autotest results [waiting upstream]
-------------------------+---------------------------------------------
Reporter: kparal | Owner:
Type: task | Status: new
Priority: major | Milestone: Packaging, Review, & Deployment
Component: production | Keywords:
Blocked By: | Blocking:
-------------------------+---------------------------------------------
Since we execute a large number of jobs, the database fills pretty quickly
and the autotest interface gets slower and slower. Lucas implemented a new
script to prune the database, but we have to wait until it is released in
a new autotest-server version (probably 0.14).
https://github.com/autotest/autotest/issues/98
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/417>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
#251: Move autotest applications into /usr/*bin
-----------------------+----------------------------------------------------
Reporter: jlaska | Owner:
Type: task | Status: new
Priority: minor | Milestone: Packaging, Review, & Deployment
Component: packaging | Keywords:
-----------------------+----------------------------------------------------
The autotest package should supply binaries in /usr/bin/ ... so we can
rely on PATH and not have to call autotest with the full-path
(/usr/share/autotest/client/bin/autotest) when scheduling jobs in
'/usr/bin/autoqa'.
Alternatively, the autotest package could drop a script that updates PATH
appropriately into /etc/profile.d/autotest. But yuck.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/251>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
#419: Adjust code to Autotest API changes
-----------------------+--------------------------
Reporter: mkrizek | Owner: mkrizek
Type: task | Status: new
Priority: major | Milestone: Future tasks
Component: autotest | Keywords:
Blocked By: | Blocking:
-----------------------+--------------------------
With recent proposed changes to Autotest API [1], the job here is to make
appropriate adjustments to AutoQA code and make sure that everything works
after that.
[1] http://test.kernel.org/pipermail/autotest/2012-April/010235.html
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/419>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
I just filed a bug against yum that is causing problems with pungi
because pungi creates yum repos without configuration files.
Since depcheck does almost the same thing, we may want to keep an eye
on the resolution of this bug - if the root issue isn't fixed, we may
have to patch depcheck.
https://bugzilla.redhat.com/show_bug.cgi?id=852961
Tim