Peter Stachowski 57e4602420 Disable wait for force-delete
In the scenario tests, sometimes the force-delete command doesn't end up
deleting the instance. This seems to be a timing issue in that it
doesn't occur during every run (and therefore might be hard to track
down). It's not terribly critical as you can run the command again and
it will probably work the second time, but until it's fixed the test
has been disabled.

Change-Id: Id5b041cb4d5276c5015921784526423e766d032c
Related-Bug: 1656422
2017-01-14 18:49:38 +00:00
2017-01-11 07:56:35 -05:00
2015-05-29 07:27:59 +00:00
2016-12-20 11:29:07 -05:00
2017-01-11 07:56:35 -05:00
2017-01-11 07:56:35 -05:00
2017-01-14 18:49:38 +00: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
2017-01-11 07:56:35 -05: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%