OpenStack Database As A Service (Trove)
86a870cc50
We had two different workflows here using the same variable but expecting it to have a totally different format. The taskmanager dns code was populating that variable with nova api output; the database list code populated it manually with a custom-format structure. This seems to have survived a long time because these are both edge cases: the dns workflow was only traversed with dns integration is switched on (unusual) and the database list only relied on IP addresses when hostnames weren't present. This patch picks a winner (the custom structure used by the database listing code) and modifies the dns workflow to live with that same format. This is spackle over a whole lot of bitrot, but should get both use cases working properly. Story: #2010077 Task: #45568 Change-Id: I5832733dd312db24d2d8047658fdd1af9f4e700a |
||
|---|---|---|
| api-ref/source | ||
| backup | ||
| contrib | ||
| devstack | ||
| doc | ||
| etc | ||
| integration | ||
| playbooks | ||
| releasenotes | ||
| roles/trove-devstack | ||
| tools | ||
| trove | ||
| zuul.d | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| bindep.txt | ||
| CONTRIBUTING.rst | ||
| generate_examples.py | ||
| HACKING.rst | ||
| LICENSE | ||
| pylintrc | ||
| README.rst | ||
| requirements.txt | ||
| run_tests.py | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
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://opendev.org/openstack/trove
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.