187725fafb
In order to allow replication sets to be all on the same hypervisor (affinity) or all on different hypervisors (anti-affinity) a new argument (locality) needed to be added to the Trove create API. This changeset addresses the Trove server part of this feature. 'locality' can now be added to the ReST payload for a create command and it is passed along as a scheduler hint to Nova. The replication scenario tests were enhanced to test that 'affinity' works and 'anti-affinity' fails (since devstack sets up a single hypervisor by default). A check for the existance (and lack of) server-groups was added. This is to ensure that not only is the server-group created properly, but also that it has been deleted after all the related instances are gone. DocImpact: New functionality Partially implements: blueprint replication-cluster-locality Depends-On: I18f242983775526a7f1e2644302ebdc0dac025cf Change-Id: I7d924c25d832f9ff4386e9497bfd214f1b2b3503
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