I've managed a start on integrating gabbi with Ceilometer. It's not anywhere close to done, but the steps are as follows:

• Download the patchset in this review.
• The tox.ini now has a gabbi target which will install gabbi from git so tox -egabbi will run the one test (so far) that is added by the patchset.

Under the hood what is happening is:

• The tox target establishes a temporary mongo db.
• ceilometer/gabbi/test_gabbi.py:
  • adjusts configuration for the mongo db
  • gets at the __class__ of the underlying WSGI application (not the paste pipeline, for now)
  • asks gabbi.driver to load YAML files out of ceilometer/gabbi/gabbits to create TestCases
• Those testcases are run by testtools.run.

The single test that is present in the lone YAML file requests / and confirms a string being present in the response, and the value of the Content-Type header. More would be present, but I'm tired.

Caveats:

• The test file itself is in a separate directory so the other tox targets will not find the test.
• testtools is being used instead of testr+subunit until I figure out how to get testr to use a different configuration (a specific group_regex is required to make concurrent runs behave appropriately).