On Thu, Dec 04, 2014 at 05:00:31PM -0700, Tim Flink wrote: > What if we turned that on it's head a bit and put VM spawning into the > task itself - spawn a vm local to the buildslave that is then > responsible for the actual work in the task instead of doing all the > work inside the buildslave process? This would allow for image and vm > requirements to be described in the task without weird multiple > parsings and could avoid most if not all of the problems/complexity that > we've started seeing in getting buildbot to work with latent > buildslaves.
This seems both sane and useful to me, but we _will_ want to run at least some tests in the actual cloud environments. Should that stuff go _back_ to fedimg? (Also random other note: if you're using cloud-init to expand image root, ssh keys can be part of that too, right?) -- Matthew Miller <[email protected]> Fedora Project Leader _______________________________________________ qa-devel mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/qa-devel
