For about 6 years various people have been maintaining a "virt-preview" repository. This is a selection of virtualization packages for Fedora N+1, built against Fedora N, the idea being that Fedora users who are interested in new virt features coming up can try them using their current Fedora. It is, as far as we know, quite popular, or at least, we get a lot of email when it breaks.
https://fedoraproject.org/wiki/Virtualization_Preview_Repository http://fedorapeople.org/groups/virt/virt-preview/
The problems:
What would solve all of those problems is having virt-preview-f<X> targets (tags?) added to Koji.
It's my understanding that any packager would then be able to submit a virt-preview build (solving issue #1), to be built in Koji on all architectures (#2), and having Koji make a repo automatically under http://kojipkgs.fedoraproject.org/repos/ (#3).
I believe also (perhaps I'm wrong about it) that this would be minimal effort for engineering to implement, while providing Fedora virt developers with a lot of value.
Please note that Copr [1] will be available very soon. And by "soon", I mean days rather than weeks. Copr is meant especially for such cases as yours.
[1] https://fedorahosted.org/copr/
I don't know enough to evaluate whether the previous comment is correct or not because all the Copr documentation is "TBD" or just missing. I even tried looking at the source but it's hardly any better. Could you point me to some documentation which explains what Copr is and how it works, and especially precisely how we would use it for the virt-preview workflow?
Edit: Does it even allow shared repos? We are already running a Ubuntu PPA-alike which only Cole is able to contribute to. The problem is that we want lots of people to be able to contribute during the ordinary fedpkg workflow.
ACTION: mmaslano will ask about arm in copr (mmaslano, 18:50:36)
ACTION: mmaslano will ask about automatically produce repo config files by copr (mmaslano, 18:54:35)
I forgot to mention in meeting minutes, we agreed with rjones on:
Create a new FAS account "virt-preview", set a password on it, give this account COPR access.
ad arm - no one looked on it. it would need some arm virtual guest in Fedora Cloud (will ask about this on todays fedora infra meeting) and some change in code (because arm builds will need to spawn different ami. ad repo config - new code already do that, I just need to deploy it in production (after I resolve some problems).
According the dgilmore the arm are not in Fedora Cloud. Getting emulated guests is probably possible. But not easily.
The issues with arm are somewhat complex:
Until very recently the firmware had no way to route just some SOC's to some uplinks. So, we couldn't seperate out some SOC's on a chassis without having them all reachable to each other. This is now hopefully in reach with a new update, we need to investigate it and see if it will work.
Arm SOC's are not reachable network wise from the fedora cloud hosts. This is possibly fixable via some firewall changes.
Copr is very set on interacting with cloud instances. Re-installing and bringing up a new arm SOC instance to build on might be possible, but will be a bunch of different code.
Doing a virtual arm builder in the cloud might work, but not we don't do emulated builds anywhere else, so it could not be ideal for some cases. Also, we would need to work out config, etc.
This appears to have stalled - marking as a meeting item.
Removing from agenda per request of submitter. (meeting time conflict)
Closing since it looks like we'll use copr.
Login to comment on this ticket.