So, we successfully enabled functional testing utilizing GitLab's custom executor feature. The code responsible for creating template images and provisioning and tearing down the VM workers currently lives under my GitLab account [1] and I think it would be better if we hosted it under the libvirt umbrella, especially since the project should serve as a uniform way of setting up custom runners for anyone in the libvirt community. If you think this is not a good idea, then please speak up and raise your concerns. Note there's still quite some work to be done with the project in general, but I'd be happy for any feedback in terms of what needs to be done prior moving the project to the libvirt namespace.

On Thu, Mar 24, 2022 at 03:10:51PM +0000, Daniel P. Berrangé wrote: > On Thu, Mar 24, 2022 at 04:07:36PM +0100, Erik Skultety wrote: > > So, we successfully enabled functional testing utilizing GitLab's custom > > executor feature. The code responsible for creating template images and > > provisioning and tearing down the VM workers currently lives under my GitLab > > account [1] and I think it would be better if we hosted it under the libvirt > > umbrella, especially since the project should serve as a uniform way of setting > > up custom runners for anyone in the libvirt community. > > If you think this is not a good idea, then please speak up and raise your > > concerns. > > Note there's still quite some work to be done with the project in general, but > > I'd be happy for any feedback in terms of what needs to be done prior moving > > the project to the libvirt namespace. > > It is a core part of our new CI infrastructure. We don't want single > points of administrative failure, so it is definitely desirable to > have it under the libvirt umbrella. Even if you continue todo 99% of > the work on it, we're prepared should other people want/need to engage, > or eventually take over primary responsibility. What about the project's name, is libvirt-gitlab-executor okay to keep?