開発中バージョンのリリースノート¶

25.0.0-10¶

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.

Backups (and therefore replica/clone bootstrap) used to fail with Cannot parse backup output whenever the API caller authenticated via an application credential. The trove-backup container was using keystoneauth1.identity.v3.Token with an explicit project_id when opening the Swift session, which forces Keystone to treat the request as a rescope. Keystone rejects rescope for tokens issued via application credentials with 401 Application credentials cannot request a scope and the backup process exited before producing any parseable output. The forwarded context.auth_token is already scoped to the Trove project, so the scope parameters were redundant and have been dropped; backups now work for password, application-credential and trust-issued tokens alike.