Ed Cranford 384576675f Conductor proxies host db access for guests
Previously, instances updated their status by
updating the database on the host directly.
Necessarily, each instance would need access to the
database to stay updated.

Trove's new conductor service eliminates that need by
working as a proxy for those instances. By sending a heartbeat
to conductor via RPC, conductor updates the database
on the host on behalf of the instance.

As backups also made use of the host database, the backup
code has been refactored to take richer inputs to remove
the need to query the host database, and now conductor is
also used to submit updates to backup states.

Implements: blueprint trove-conductor

Change-Id: I4cb34baedd0e3a50051f9e66de95c9028c66e4b5
2013-11-26 11:52:00 -06: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-11-19 13:28:59 +02:00
2013-06-24 14:11:15 -07:00
2013-09-30 11:43:42 -04: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 quickly run PEP8, run: $ tox -epep8

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 114 MiB
Languages
Python 95%
Shell 4.9%