As I look at what all would be required to get Tunir running in Taskotron in time for f25, I'm liking it less and less. It requires so many dirty hacks that will have to be un-done later that I'd rather not do it if there's another option.

Another potential option is to run the Tunir jobs in Beaker, letting Beaker handle the setup and teardown of the bare metal boxen with vagrant instead of forcing Taskotron to treat them separately.

I assume that as long as the testing is started in response to certain fedmsgs and the results end up in resultsdb, the requirement would be satisfied. With that in mind, I propose investigating the following:

• write beaker jobs for running the Tunir tasks on properly configured bare metal boxen
• run the Tunir tasks in such a way that they can be sent to resultsdb
• either wrap execution in libtaskotron and use --local mode or write a wrapper layer that submits Tunir output to resultsdb
• write up a quick fedmsg listener which can kick off beaker jobs in response to what autocloud is listening for

If this works, I think we'd be in almost the same functionality place with fewer ugly hacks and more progress towards integrating Beaker jobs into Taskotron (which is on our roadmap anyways).

Look into what would be required to run Tunir jobs in Beaker and if it seems reasonable.