December 19, 2012
Working with Pingou on this I merged the playbooks into a single playbook. We were setting up jenkins and wanted a way of putting all the systems together quickly and easily. All it does is spin up a master instance, provision it, spin up 2 workers (one in el6 the other f17) provision them and end:
It could easily be done in ec2, euca, openstack or pretty much any system. I know there are more ways to skin this cat but I thought this was simple enough to follow along and others might find it interesting.
This is the playbook:
all of our ansible playbooks and inventory files are available here:
December 10, 2012
Bohuslav and I have been diligently working on the copr buildsystem code in the last month or so. We originally targetted the middle of november but that wasn’t to be. However, right now we have working rough-around-the-edges code. It has some completed successful builds so we know that part works.
A little background:
copr is intended to provide a safe place for packages to be built that are not packages that are not or cannot be built in fedora. Think of it as a place where you can scratch and chain build whatever you want (up to the obvious limits of legality :). It takes your packages, builds them against themselves and puts the repo up available for download.
Why not just do this in koji?
- koji is just for fedora builds
- koji does not allow external, arbitrary repositories for build deps
- koji’s builders are not destroyed and cleaned after each build
- koji just isn’t designed to do what copr does and grafting it on top of koji is a dangerous proposition to the safety and security of fedora builds.
How does copr do things?
You submit your build request (name of the copr, chroots to build against, repos to use to build and the list of src.rpms to build) into the frontend. The backend takes this request, creates a builder in our private cloud, builds the pkgs, pulls back the results onto a webserver, provides you with a link to the results and destroys the builder.
What’s the status right now?
The backend code works, but there are a lot of rough edges to sand down. The frontend code works, but there is a bunch of ui work needed there (right now Ryan Lerch is creating some mockups for how things should be). The code is available from the link at the top. Right now everything is in two branches a front end branch (bkabrda-workspace) and a backend branch (skvidal-backend). We’ll be merging them into master in short order.
We’ll be sending out a call for folks to help test in the not-so-distant future. The whole goal is to provide a place for people to build packages they would like to have available but maybe cannot have in fedora for one reason or another.
- alternative configuration/build options for an existing package
- not very easy to package in fedora (bundling, etc) but perfectly good software otherwise
- test builds
- your idea here
- builds based on other repos that are not included in fedora
Things which cannot be in a copr:
- software which are not legal to include in fedora
The fedora buildsys mailing list (email@example.com) is where we will discuss things going forward but I just wanted to let people know what we’ve been working on.