Current Series Release Notes¶

25.0.0-39¶

Introduced a new configuration option [DEFAULT]/cinder_client_version with default value set as 3. This allows operators to supply the intended version of Cinder API to interact with.

Simplifies the DevStack installation process for Trove.

The setup procedure is updated to produce a working environment out of the box, and the documentation now provides clearer step-by-step installation instructions.

From now on it is possible to have the same backup image for series of datastore versions. Trove guest-agent will iterate over tagged versions for backup images from more to less specific ones attempting to find an image rather then fail if exact image is not present in the registry. For instance, in case you defined [mariadb]/backup_docker_image: registry/db-backup-mariadb and have only 10.4 in the registry, such image will cover whole 10.4 series, including 10.4.1, 10.4.2, 10.4.3, etc.

Improves instance list method by using Nova tags feature. Tags was introduced in Nova API version 2.26 in 2017. Querying Nova servers by tags allow to check relevant servers only instead of retrieving all of them, preventing possible 504 errors in large clouds.

Service credentials removal from trove-guestagent.conf. Trove guestagent no longer requires Keystone service credentials. Operators should remove this section from trove-guestagent.conf. Storing credentials on guest instances represents a security risk.

Even after upgrading to this version, the existing guest-agent images will function normally alongside the existing backup images. However, to ensure compatibility with newly built guest images as well as the legacy ones, you must rebuild the backup images.

Logic for fetching Cinder API version has been fixed, and it no longer relies on the [DEFAULT]/cinder_service_type value. This allows to have a cinder_service_type defined as block-storage, or any other name which is not versioned.

Fixes MariaDB when datastore use official MariaDB dockerhub images. MariaDB starting from version 10.7 use different default path to configuration file.

Use pre-auth Swift client and remove Keystone re-auth. Stop using Keystone sessions and token re-scoping in backup and restore flows.

Backup container’s swift client now respects swift_api_insecure config option in trove-guestagent.conf, instead of relying on hardcoded insecure=True.