Peter Stachowski 606c59737f Have scenario tests retrive guest log on error
As an aid to debug guest failures, a Metaclass was added
to the TestRunner class that allows failed tests to
pull back and echo the guest log from 'registered'
instances.

This uses the guest-log feature that is available for
all datastores.

IDs for instances created in the tests were registered
to report on failures.

Two guest-log tests were also commented out, as they
seem to not work properly: see
https://bugs.launchpad.net/trove/+bug/1653614
This was discovered while testing the new retrieval
code.  Other tests were also modified so that
'SkipTest' exceptions would be raised properly.

Change-Id: I448bd2f0181351ef1536e20c41f9d45f95478587
Partial-Bug: 1652964
2017-01-05 14:50:04 -08:00
2015-05-29 07:27:59 +00:00
2016-12-20 11:29:07 -05:00
2016-12-18 08:18:47 -05:00
2016-10-24 04:12:55 +00:00
2013-06-14 18:25:42 -04:00
2013-06-24 14:11:15 -07:00
2014-03-19 15:06:23 +01:00
2016-10-26 05:27:09 +00:00
2015-05-29 07:27:59 +00:00
2013-04-29 18:01:12 -04:00
2016-09-14 13:56:24 -04:00
2016-12-01 22:07:32 +00:00
2015-11-19 10:25:01 +00:00
2016-08-12 05:29:41 -07:00
2015-09-23 14:14:17 +00:00

Trove

image

Trove is Database as a Service for OpenStack.

Getting Started

If you'd like to run from the master branch, you can clone the git repo:

git clone https://github.com/openstack/trove

You can raise bugs here: https://bugs.launchpad.net/trove

Python client

https://git.openstack.org/cgit/openstack/python-troveclient

References

Description
OpenStack Database As A Service (Trove)
Readme 114 MiB
Languages
Python 95%
Shell 4.9%