[Beaker-devel] [RFC V3 PATCH 0/5] beaker harness support for autotest

Dan Callaghan dcallagh at redhat.com
Mon Apr 15 07:39:18 UTC 2013


Excerpts from Don Zickus's message of 2013-04-13 05:09:48 +1000:
> Hi Folks,
> 
> Throwing this over the wall for a new round of reviewing.

Thanks for all your work on these patches, Don!

I had a look through them all this afternoon (I'm sorry it's taken me so 
long to get to it). I see there is a fair bit of code in there to 
support running existing Beaker/RHTS-style tasks inside autotest 
(emulating rhts-* commands, etc). I didn't realise that before.

Using autotest to run existing Beaker tasks is interesting and may be 
worth pursuing, but what's *more* interesting to us is the ability to 
run autotest tests as part of a Beaker recipe. We've had some interest 
from people who have existing autotest-based tests who would like to 
make use of Beaker's scheduling abilities.

Given my very limited understanding of autotest, this is what I was 
imagining we would need to do:

* Find a way to map native autotest control files to Beaker recipe XML. 
  The control files are real Python code, which makes them very 
  powerful, so I don't think it makes sense to try to abstract that away 
  in Beaker's XML. It might make more sense to allow the control file to 
  be embedded literally in the recipe XML. For example we could add 
  support for something like this:

    <recipe>
        ...
        <script><![CDATA[
job.run_test(...)
]]></script>
    </recipe>

  where <script/> replaces the series of <task/> elements that you would 
  normally see in a Beaker recipe.

* Write some code for autotest to fetch the Beaker recipe XML and 
  configure itself accordingly (that's the bootstrap stuff in these 
  patches).

* Wrote some code for autotest to collect test output and results and 
  report them to Beaker somehow (I don't see anything for this in these 
  patches, aside from the rhts-submit-log/rhts-report-result emulation?)

It would be great if we could get this working first, and then the 
support for running RHTS-style tasks could be an extra patch set on top 
of that.

Don, how does that sound to you?

-- 
Dan Callaghan <dcallagh at redhat.com>
Software Engineer, Infrastructure Engineering and Development
Red Hat, Inc.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <https://lists.fedorahosted.org/pipermail/beaker-devel/attachments/20130415/6a0bc398/attachment.sig>


More information about the Beaker-devel mailing list