On Thu, 2017-09-07 at 11:58 +0100, Daniel P. Berrange wrote: > > Fedora 26 has been released in the meantime, which means we can > > get rid of two builders instead of one! Someone will have to > > prepare the 'libvirt-fedora-26' builder, though, because it > > doesn't exist at the moment :) > > Until someone actually creates the new builders for F26 and > almost time for F27 now too, I don't think we should really > be turning off existing builders. I posted this in part to raise the issue of the Fedora 26 builder not being available yet, but I disagree on the fact that we can't get rid of Fedora 23 and 24 until that's in place. Building on two unsupported Fedora releases doesn't really buy us anything except for more load on the already tightly packed CI hosts. > We really badly need someone to write a kickstart file that > can 100% automate the provisioning of Fedora VMs suitable > for running our CI. Then we can quickly deploy builers when > new Fedora comes out and get to point where we're always > 100% aligned with testing on the 2 current supported releases > + rawhide. I've been working on Ansible playbooks for my development machines and I've intended from the very beginning to make them generic enough that I could use them for my own builders too with only minimal changes. Since I'm going to spend time on that regardless, I'm perfectly fine with coming up with something that can turn a freshly-installed Fedora guest into a builder suitable for the CentOS CI. As for the installation step, I've never used kickstart but I was thinking of taking advantage of the amazing work the virt-builder maintainers have been doing in quickly preparing templates after a new Fedora version has been released. How does that sound? -- Andrea Bolognani / Red Hat / Virtualization -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
