6672fe868a
Trove backups are stored in Swift as Dynamic Large Objects. This is not ideal, and could cause restore to fail as DLOs may not return all of their parts. Static Large Objects should be used instead. SLOs perform checksum and object size validation and can reduce object download times significantly. Changes are needed to the Swift storage strategy and taskmanager's backup delete model to perform actions on SLOs. The corresponding unittests and fakes are also updated. A special case occurs when the backup object fits in a single Swift object segment, in which case it will not be made a SLO. Change-Id: Ide30a1e7f909a3b7fecb16268367b56468306d42 Closes-bug: 1489997
Trove
Trove is Database as a Service for OpenStack.
Usage for integration testing
If you'd like to start up a fake Trove API daemon for integration testing with your own tool, run:
$ ./tools/start-fake-mode.shStop the server with:
$ ./tools/stop-fake-mode.shTests
To run all tests and PEP8, run tox, like so:
$ toxTo run just the tests for Python 2.7, run:
$ tox -epy27To run just PEP8, run:
$ tox -epep8To generate a coverage report,run:
$ tox -ecover(note: on some boxes, the results may not be accurate unless you run it twice)
If you want to run only the tests in one file you can use testtools e.g.
$ python -m testtools.run trove.tests.unittests.python.module.path