Ussuri Series Release Notes¶
Trove now publishes images of some specific databases on http://tarballs.openstack.org/trove/images/ for testing purpose.
A new field named
service_status_updatedis added to the instance API response which e.g. could be used to validate if the instance ‘HEALTHY’ status is stale or not
A new database service status
HEALTHYis introduced to indicate that the service is responsive.
HEALTHYis the final status after
Admin user can delete datastore if there are no instances or backups associated.
Add XFS disk format for database data volume, cloud admin can config ‘ext3’, ‘ext4’ or ‘xfs’ in
Python 2.7 support has been dropped. Last release of Trove to support py2.7 is OpenStack Train. The minimum version of Python now supported by Trove is Python 3.6.
Trove is now using admin clients by default to communicate with Nova, Cinder, Neutron and Glance. Deployers want to stick to the old clients need to explicitly config the following options:
Any existing scripts that rely on the database instance
ACTIVEstatus should now rely on
The following config options are deprecated in favor of a separate configuration section
service_credentialsintroduced to define the Trove service user credentials for communication with other OpenStack services.
[DEFAULT] trove_auth_url os_region_name nova_proxy_admin_user nova_proxy_admin_pass nova_proxy_admin_tenant_id nova_proxy_admin_tenant_name nova_proxy_admin_user_domain_name nova_proxy_admin_project_domain_name
Fixed the issue that datastore version cannot be deleted because of dependency of deleted instances. Now, when instance or backup is deleted, the datastore version attribute is set to NULL in database. When datastore configuration parameter is deleted, the record is deleted from database rather than only set ‘deleted’ field to 1.