Go to file
justin-hopper 91943c7b3c Fix drift in deleted timestamp for Notification and Database
The deleted timestamp for the usage event and the database
    were being set at different intervals.  Now the time is
    captured once and shared between both usages.

    If the server deletion times out, a log message will be
    recorded but it will not throw an exception.  Ensures
    completion of clean up and record of deletion

Fixes: bug 1201685

Change-Id: I66f52f8b8a3954989844d3b5fa0794913e94ddfa
2013-07-19 14:14:10 -07:00
2013-06-24 14:11:15 -07:00
2013-06-24 14:11:15 -07:00
2013-06-24 14:11:15 -07:00
2013-06-24 14:11:15 -07:00
2013-06-14 18:25:42 -04:00
2013-06-24 14:11:15 -07:00
2013-04-29 18:01:12 -04:00
2013-06-25 10:41:57 +02:00
2013-06-25 11:30:18 +02:00
2013-06-24 14:11:15 -07:00
2013-06-24 14:11:15 -07:00
2013-06-25 11:30:18 +02:00
2013-07-11 15:02:23 -07:00
2013-06-25 11:28:47 +02:00

Trove

Trove is Database as a Service for Open Stack.

To run all tests and PEP8, run tox, like so: $ tox

To quickly run the tests for Python 2.7, run: $ tox -epy27

To generate a coverage report,run: $ tox -ecover (note: on some boxes, the results may not be accurate unless you run it twice)

If you'd like to start up a fake Trove API daemon for integration testing with your own tool, run: $ ./bin/start_server

Stop the server with: $ ./bin/stop_server

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