c457e33964
What we want is that when mongodb is do cluster-grow, by _group_shard_instances[1] to determine which instance is a replica set, this function in a replica sets can allow an instance without related_to opintion, which same as our originally planned is the same[2]. But now because of this check, result if have any instance without related_to will be error, this check was placed in the front of _group_shard_instances, resulting in we can not achieve the originally planned. My idea is to get rid of this check,with use _group_shard_instances to see whether related_to meet the requirements for grow. [1]:https://github.com/openstack/trove/blob/master/trove/common/strategies/cluster/experimental/mongodb/api.py#L496 [2]:https://specs.openstack.org/openstack/trove-specs/specs/liberty/cluster-scaling.html#add-replica-set Change-Id: I9e2f441d1434617077368e05efe95032fab01d4f
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
- Build guest image: http://docs.openstack.org/developer/trove/dev/building_guest_images.html