2024.2 Series Release Notes¶
22.0.0-4¶
Bug Fixes¶
fix a bug where the trove-manage script fails to upgrade the database when the DBDatastoreVersion table is not empty.
22.0.0¶
New Features¶
Users with the administrator role can configure the datastore registry external for each datastore version using a command, without editing configuration files.
Enable network_isolation by Default. This option has no impact on existing Trove instances. For more information, Please refer to the document network_isolation.
Support Alembic database migration tool.
Add support for setting owner, uid, gid for each datastore instance by configuring database_service_uname, database_service_uid and database_service_gid Story 2010827 <https://storyboard.openstack.org/#!/story/2010827>
Upgrade Notes¶
Trove has removed support for SQLAlchemy-Migrate. If users are upgrading from a version prior to “Wallaby,” they need to first upgrade to a version between “Wallaby” and “Bobocat” using SQLAlchemy-Migrate to complete the database schema migration, and then use Trove-manage to upgrade to the latest version.
Deprecation Notes¶
The
[DEFAULT] admin_rolesoption has been deprecated in favour of the newcontext_is_adminpolicy rule.
Bug Fixes¶
Rebuild of PostgreSQL database instances is now supported. Older PostgreSQL instances can be rebuilt as long as the target guest image is built from this release or later.
