While there are a lot of things which folks want to use Taskotron for,
most of those things are predicated on our support for disposable
clients and that's still the next big thing that I'd like to get
working. I'm ignoring the other things that we'd do with disposable
clients for the scope of this thread because there's a lot of work here
already.
Assuming that we go forward with my proposal for no-cloud disposable
clients, there are several things which still need to be done:
- define a VM spec for the recipes
- figure out how to manage images and image metadata so that we can
find and retrieve images on the buildslaves.
* Mike was talking about looking into using Glance from OpenStack for
this.
* Another option would be to integrate it into trigger/ExecDb
- Write any required code for the image management and retrieval system
- deploy the system for image management and retrieval
- re-deploy the buildslaves so that they work better with the new
image-based approach. ie - run them on bare metal so that we're not
slowing stuff down with virt-in-virt
- get the code working
* we can start by specifying local paths to VM images instead of any
tags or metadata
* stealing bits from Mike's testCloud may be a good option
https://github.com/Rorosha/testCloud
* not sure if we want to use much from Beaker here, I don't like the
idea of using expect scripts unless there are no other options
- Get a basic ExecDB working
* Josef has started on this, still waiting for a demo instance to
start working out the details and kinks
- Write tasks to generate updated images to use for tasks
* This could be manual at first but I'd like to see it happen on a
regularly scheduled basis.