798d9354f6
It turns out that the way the python34 tests are run in parallel is to spin up several processes (not threads). This means that putting locks around creating the database in a single 'run' would need an inter-process lock not a thread lock. While the feasibility of this is investigated, change the behaviour of the tests to run in series to increase stability. On a 4 cpu test machine this only increased the run time by 70s. Partially implements: blueprint trove-python3 Change-Id: I530fcf22b697148a3d0a286015c5a79481528d8e
Trove
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
- Wiki: https://wiki.openstack.org/wiki/Trove
- Developer Docs: http://docs.openstack.org/developer/trove
You can raise bugs here: https://bugs.launchpad.net/trove
Python client
https://git.openstack.org/cgit/openstack/python-troveclient
References
- Installation docs: http://docs.openstack.org/developer/trove/dev/install.html
- Manual installation docs: http://docs.openstack.org/developer/trove/dev/manual_install.html
- Trove integration: https://github.com/openstack/trove-integration
- Build guest image: http://docs.openstack.org/developer/trove/dev/building_guest_images.html