[fedora-build-service] #9: default templates use /tmp
by fedora-badges
#9: default templates use /tmp
----------------------------+--------------------------------
Reporter: tflink | Owner: somebody
Type: defect | Status: new
Priority: major | Milestone: Initial Deployment
Component: Image Building | Version:
Keywords: |
----------------------------+--------------------------------
The templates currently in git specify /tmp as working directories for
lorax and pungi. This is fine for F17 and earlier, but with tmpfs in F18,
this can cause problems because /tmp isn't a real filesystem.
This is a simple fix - just substitute /var/tmp for /tmp in the templates.
It might be worth a warning if someone tries to use /tmp as a work
directory but I really don't think that's necessary at this time.
--
Ticket URL: <https://fedorahosted.org/fedora-build-service/ticket/9>
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, 2 months
[fedora-build-service] #14: Remove requirement for repo mirror in configuration files
by fedora-badges
#14: Remove requirement for repo mirror in configuration files
----------------------------+--------------------------------
Reporter: tflink | Owner: somebody
Type: defect | Status: new
Priority: major | Milestone: Initial Deployment
Component: Image Building | Version:
Keywords: |
----------------------------+--------------------------------
While the support for repo mirrors can be nice, it can also be a
hinderance if users are building images in an environment where a specific
repository is desired (this will be the situation inside the fedora
infrastructure).
Allow for configuration files to not require repomirror specifications
--
Ticket URL: <https://fedorahosted.org/fedora-build-service/ticket/14>
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, 5 months
[fedora-build-service] #16: Support Sourcing kickstarts directly from spin-kickstarts git
by fedora-badges
#16: Support Sourcing kickstarts directly from spin-kickstarts git
----------------------------+-------------------------------
Reporter: tflink | Owner: somebody
Type: enhancement | Status: new
Priority: minor | Milestone: Public Deployment
Component: Image Building | Version:
Keywords: |
----------------------------+-------------------------------
This one occurred to me today when I was updating the kickstart I use for
building smoke DVDs - it would be nice to be able to source kickstarts
directly from spin-kickstarts git instead of using them from the package.
The spin-kickstarts package isn't updated very often for pre-releases and
releng pulls straight from git for the TCs and Rcs
--
Ticket URL: <https://fedorahosted.org/fedora-build-service/ticket/16>
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, 5 months
[fedora-build-service] #11: Support Triggers from fedbus
by fedora-badges
#11: Support Triggers from fedbus
----------------------------+-----------------------------
Reporter: tflink | Owner: somebody
Type: enhancement | Status: new
Priority: minor | Milestone: Glorious Future
Component: Job Management | Version:
Keywords: |
----------------------------+-----------------------------
Fedbus current emits messages for builds and updates. Support the
monitoring of fedbus, looking for specific package builds. If there are
new builds of the desired package, wait X minutes and kick off an ISO
build job
--
Ticket URL: <https://fedorahosted.org/fedora-build-service/ticket/11>
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, 5 months
Fedora Build Service: Configuration files and Options to support
by Amit Saha
Hi all,
In its current state, the CLI tools require the user to strictly follow
the supported templates and specify *all* the options and sections --
even if they are blank. Even for the Web UI, the config file is
generated such that it follows this template strictly. That is not very
exciting. [1a,1b]
As a first step towards changing this to allow the config file to have
only the bare minimum required for building images, I have created a
list of the three tools used to create boot, DVD and live images with
their mandatory, optional with no sensible defaults, optional with
sensible defaults and switches. The list can be found at [2]. Please
correct if there is anything I may have got wrong.
Is it fair to assume that only the mandatory options as required by the
original tools should also be the only ones supported by the build
service as well?
Once this list is decided, the CLI and the WebUI can assume the original
sensible defaults or change them to a pre-decided default values for the
others, in case they are not specified.
[1a] https://fedorahosted.org/fedora-build-service/
[1b]
https://fedorahosted.org/releases/f/e/fedora-build-service/devel/doc/HOWT...
[2] https://gist.github.com/4076586
[2] I have plans for a config file generator script.
Thanks for any inputs.
Best,
Amit.
--
Amit Saha <http://echorand.me>
Infrastructure Engineering and Development
Red Hat, Inc.
11 years, 5 months
Current State of Image Building Project
by Tim Flink
I figure that one good place to start is to describe the current state
of the project - what it can do and what the gotchas are. Amit, if I'm
missing anything, please correct me or add what I'm missing.
The local part of image building works fine - there are some quirks to
the process and a configuration file format to learn but the added
builds are downloaded and included in images. I haven't done much
testing with building live images but I believe that is also working.
In order to use any of the building code, you need to have the
following installed:
koji lorax livecd-tools pungi pykickstart spin-kickstarts
Virtualenv doesn't work unless you create it as root because the CLIs
need to be run as root for pungi/lorax and that changes paths to the
point that not all the code works. I'm sure there are ways to work
around it other than creating the virtualenv as root but I haven't
tried very hard to find one.
The remote parts work once set up - I had it set up at one point
without the web front end and was able to build images. It needs a bit
of polish but the needed stuff is mostly there, I just found the setup
process to be a little touchy and fragile. The current method of
configuration is rather pre-defined and not incredibly flexible but the
basic method is sound.
The web interface wasn't a priority during GSoC and thus, it is pretty
rough around the edges. I was never able to get the full stack working
but it's certainly capable of working. The UX needs more designing and
a re-skin but this stuff can be done at a later date.
I think that sums it up relatively well. The docs should fill in any
more details that I've not written enough to start using the code. If
not, feel free to ask questions here or in #fedora-qa.
Tim
11 years, 5 months
Image Building Project
by Tim Flink
We've been talking a little bit on an internal list (the
conversation spawned out of something unrelated) about getting the image
build service project from GSoC 2012 to the point where it can be
deployed and used. Since the project doesn't have a mailing list of its
own and it isn't all that unrelated to autoqa, we're moving the
conversation here.
I spent a little bit of time putting git and trac into a somewhat
usable shape and filed a few tickets for some of the work that needs to
be done. I'm going to continue doing so and would welcome any help in
this department
If anyone wants to be involved with the discussion and/or development,
please let one of us know. We don't have a list set up but I'd love to
get help on this - both Amit and I have admin access to the project and
are able to add people.
The trac instance is at:
https://fedorahosted.org/fedora-build-service/
Git is at:
http://git.fedorahosted.org/cgit/fedora-build-service.git/
I've pushed the current docs to:
https://fedorahosted.org/releases/f/e/fedora-build-service/devel/doc/
Tim
11 years, 5 months