Hello,<div><br></div><div>RedHat-hosted Koji servers offer an invaluable service by allowing all of us, package maintainers, to build all of "our" Fedora packages. I guess that that infrastructure is not cost-less for RedHat and and the quality of service is great (for instance, the wait in the queues, before Koji actually builds the packages submitted via the command-line client, is not so long).</div>
<div><br></div><div>As Fedora is pretty advanced in the cloud/virtualisation arena, we could imagine a "Koji Cloud", hosted on VMs offered by volunteers. For instance, I could contribute a few VMs in Europe (hosted on <a href="http://www.ovh.co.uk/">http://www.ovh.co.uk/</a>). Our Cloud SIG (<a href="https://fedoraproject.org/wiki/Cloud_SIG">https://fedoraproject.org/wiki/Cloud_SIG</a>) and/or Virt ML (<a href="https://admin.fedoraproject.org/mailman/listinfo/virt">https://admin.fedoraproject.org/mailman/listinfo/virt</a> and <a href="https://fedoraproject.org/wiki/Getting_started_with_virtualization">https://fedoraproject.org/wiki/Getting_started_with_virtualization</a>)/RedHat ET (<a href="http://et.redhat.com/">http://et.redhat.com/</a>) colleagues could help designing and implementing the following infrastructure:</div>
<div> * VM template/images, ready to be started on the volunteer's servers everywhere in the world, 24x7.</div><div> - SSH public keys of Koji administrators would be part of the images, so that they can have an easy access to them, just in case.</div>
<div> - Those VMs would update themselves automatically.</div><div> - The containers could be standardised as well. For instance, ProxMox/OpenVZ or Fedora/CentOS with libvirt.</div><div> * A directory (LDAP, or something less centralised, like the address book of Skype, for instance), keeping track of all those VMs:</div>
<div> - with the corresponding last known status;</div><div> - with the VM configurations (Fedora/CentOS release, CPU, memory, disk usage, etc);</div><div> - with some rating corresponding to their quality of service (build duration, reliability of the VM, MTBF, etc).</div>
<div> * A dispatcher system:</div><div> - which would route the Koji build requests to available VMs;</div><div> - collect the outcome of the builds (logs, RPM packages, statistics, QoS, etc) and store them in the current ("centralised") Koji infrastructure.</div>
<div><div><br></div><div>As I am not a specialist of all those technologies, I may have forgotten a lot of things, but you get the idea.</div><div>Doesn't it sound great? Does it sound realisable? Am I crazy to dream to such an infrastructure?</div>
</div><div><br></div><div>Cheers</div><div><br></div><div>Denis</div><div><br></div>