Wallaby Series Release Notes

15.0.0-19

Upgrade Notes

  • The default value of the Trove guest agent config option [postgresql] backup_docker_image is changed to openstacktrove/db-backup-postgresql:1.1.1. There is nothing to do if the option is not configured explicitly.

Security Issues

  • Changed the network mode of the database container to “bridge” and exposed the service ports. Cloud operator could adjust the iptables to restrict network access from the database container to the outside. An example:

    iptables -t filter -I DOCKER-USER 1 -d [restricted-network-range] -i docker0 ! -o docker0 -j REJECT

Bug Fixes

  • Fix guest-agent failed to start PostgreSQL container due to execution of the “CREATE DATABASE” statement within the context manager of psycopg library. See the following for details Stroy 2010761

  • Fixed backup creation failed issue when using custom container image registry.

  • Added a periodic task for the PostgreSQL datastore to clean up the archived WAL files. Added a check when creating incremental backups for PostgreSQL. A new container image openstacktrove/db-backup-postgresql:1.1.2 is uploaded to docker hub.

15.0.0

New Features

  • Added the ability to create the Cinder volume in the same AZ as the Nova instance. Set enable_volume_az to True (defaults to False)

  • Added the ability to quota on the total amount of RAM in MB used per project. Set quota.max_ram_per_tenant to enable. Default is -1 (unlimited) to be backwards compatible. Existing installations will need to manually backfill quote usage for this to work as expected.

  • Support image tags for the datastore version. When using image tags, Trove is able to get the image dynamically from Glance for creating instances. If both are specified, image ID takes precedence over image tags.

  • Added custom container registry configuration for Trove guest agent, it’s now possible to use images in the private registry rather than Docker hub.

  • Added MySQL 8 support, docker image openstacktrove/db-backup-mysql8.0 is created to support backup and restore.

  • In a multi-region deployment with geo-replicated Swift, the user can restore a backup in one region by manually specifying the original backup data location created in another region.

Upgrade Notes

  • The default value of [oslo_policy] policy_file config option has been changed from policy.json to policy.yaml. Operators who are utilizing customized or previously generated static policy JSON files (which are not needed by default), should generate new policy files or convert them into YAML format. Use the oslopolicy-convert-json-to-yaml tool to convert a JSON to YAML formatted policy file in a backward compatible way.

  • Any 3rd party clients that are talking with Trove API to wait for status should be notified to use operating_status instead.

Deprecation Notes

  • Use of JSON policy files was deprecated by the oslo.policy library during the Victoria development cycle. As a result, this deprecation is being noted in the Wallaby cycle with an anticipated future removal of support by oslo.policy. As such operators will need to convert to YAML policy files. Please see the upgrade notes for details on the migration of any custom policy files.

Bug Fixes

  • Fixed an issue that orphan volumes left after removing instances, especially for the case that instance creation failed because of timeout when waiting for the volume available.

  • Fixed a race condition that instance becomes ERROR when Trove is handling creating and deleting at the same time.