319518285a
For our production Openstack DBaaS the lifecycle for a datastore version is: - create datastore, e.g. postgresql 16.10; datastore is enabled, users may create instances for it - datastore is disabled due to the next minor version is available, e.g. postgresql 16.11 was released - legacy stage: old instances on disabled postgresql 16.10 still works; version update for old datastore instances is advised but not a mandatory - cleanup stage: all user instances was upgraded to upper versions, datastore 16.10 may be gracefully removed So the problem here is that users are not able to create configuration group for disabled datastore versions and fully control their running database instances. This leads to a bad user experience forcing them to upgrade their instance to the latest version, for which they may not be ready yet. In our opinion, there should be a possibility to modify configuration for the running instances even on disabled datastores. Instance creation for a disabled datastore should not be available though. Change-Id: I65edce7f6304860d0e38b26d7abb8b9d40653026 Signed-off-by: Erkin Mussurmankulov <mangust404@gmail.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:
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 dashboard plugin for Trove.