taskotron / libtaskotron

#216 Investigate "no-cloud" disposable clients
Closed: Fixed Opened by tflink.

Closed: Fixed
Reopen Issue

As described in [[planning/nocloud_disposable_clients | this wiki page]], one approach to having disposable clients is to create the virtual machines as part of the execution process instead of running buildslaves in virtual machines.

While it does present some advantages (local is almost identical to remote execution, don't need to deal with any cloud systems etc.), it also poses some potential issues with complexity.

Create a proof of concept for this method of disposable client creation so it can be farther evaluated.

This ticket is a duplicate of https://pagure.io/taskotron/issue/76

I went through and created a proof-of-concept around this idea of "no cloud" disposable clients. At the time of this writing, it is available in [[https://bitbucket.org/tflink/libtaskotron/src/eb5c8ac2ea09c442c79b255fd1ce88edbc28acca/?at=feature%2FT382-nocloud-disposable|my fork of libtaskotron]] - that fork/branch may be deleted in the future but still exists and mostly works for now.

After some discussion, I think that we're going to go forward with a slight variation on the original concept. I haven't gotten to writing up the details of that yet but will be doing so shortly in addition to getting started on tickets for implementation so we can get the ball rolling.

Either way, the investigation is pretty much complete, so I'm closing the ticket
Metadata
None
None
None
None
Low
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.