One of the most promising things that we've looked at this far for disposable clients is the existing ephemeral client support that is already in buildbot.
Experiment with that support to answer the following questions: can this be used with the existing fedora infra cloud? what are the limitations of using this support - images and/or snapshots * what happens in buildbot when problems occcur in cloud image deployment?
The main output of this ticket will be an analysis of how well the integration works and whether it appears to be a) feature-ful and b) stable enough to start using soon in production.
This ticket is a duplicate of https://pagure.io/taskotron/libtaskotron/issue/186
After spending quite a bit of time with this, I think that we're going to go forward with something closer to the no-cloud approach for disposable clients.
Between adding complexity directly into the buildmaster config and needing to figure out how to make all spawned VMs connect with the right dev/stg/prod buildmaster using the correct credentials and having to deal with openstack, it's just more complexity than we want to require.
Additionally, this method makes it more difficult for us to say "just install libtaskotron and it's pretty much the same as production" with a straight face.
Metadata Update from @tflink: - Issue tagged with: infrastructure
Log in to comment on this ticket.