ddafb0e40d
Trove implies strict network requirements. All Trove instances must be launched in a network that is connected to the management network so that Guest Agents residing in the data plane could communicate with control plane services, e.g. RabbitMQ and Trove Conductor. Trove Devstack plugin creates a management network bound to management physnet (trove-mgmt), as well as tenant network (alt-private) connected to it via a router. Consequently, Trove instances deployed in the tenant network can easily access the management services mentioned above. However, these networks are visible only from the perspective of the tenant that created the networks. Since Tempest does not provide an easy way to create a similar management network, and as such does not enable creating tenant network for Trove instances automatically, this change adds --share flag to networks created by Devstack so that Tempest could reuse them. Change-Id: I8c642ab6150858478c48291a51675ef9d15dafaa Signed-off-by: Bartosz Zurkowski <b.zurkowski@samsung.com>
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:
For information on how to contribute to trove, please see CONTRIBUTING.rst and HACKING.rst
You can raise bugs here: Bug Tracker
The plan for trove can be found at Trove Specs
- Release notes for the project can be found at:
Python client
Python-troveclient is a client for Trove.
Dashboard plugin
Trove-dashboard is OpenStack dashbaord plugin for Trove.