Train Series Release Notes

1.0.1

Known Issues

  • At the moment use of reserved stores is only limited to filesystem store driver. Also default filesystem_store_datadir path for these stores is set to /var/lib/glance/<store_name>, so with if you are using devstack for the deployment, you need to make sure you have appropriate permissions to create these reserved stores directories.

Other Notes

  • In this version, refactor was made how registering of filesystem configuration options for reserved stores works. Consumer just need to pass the key:value pair where key represents the name of the reserved store and value represents the actual store driver, to the glance_store.

1.0.0

Prelude

The Glance Project Team is excited to announce the version 1.0.0 release of the glance_store library. This release marks the finalization of changes introduced on an experimental basis in previous releases beginning with 0.25.0 to support the Glance Multi-store backend support feature.

New Features

  • Multiple backend stores may be configured using the glance_store.multi_backend module. See the documentation of the create_multi_stores function in the glance_store Reference Guide for details.

Known Issues

  • The responses from some functions in the glance_store.multi_backend module, which was EXPERIMENTAL until this release, have changed. In particular, the glance_store.driver.Store.add function which returns a tuple whose last element is a dictionary of storage system specific information, no longer contains a ‘backend’ key. Instead, this key is named ‘store’. This change extends to any convenience functions that wrap Store.add.

    Consumers relying upon the EXPERIMENTAL behavior should not upgrade past version 0.29.1. Now that the multi_backend module is fully supported in release 1.0.0, it will not undergo any more backward-incompatible changes.

Upgrade Notes

  • Consuming services should begin the transition away from the glance_store.backend module and instead use the glance_store.multi_backend module. The backend module is expected to be removed during the ‘U’ development cycle.

Deprecation Notes

  • The ‘stores’ and ‘default_store’ configuration options have been deprecated for removal since the OpenStack Rocky release. They are subject to removal early in the ‘U’ development cycle. When these options are removed, the glance_store.backend module, that depends on them, will be removed as well.

0.29.1

Critical Issues

  • glance_store 0.29.0 was released with backwards incompatible changes. There was no corresponding releasenote to mention this. 0.29.1 has reverted said change which will be included to 1.0.0 release later on the cycle.

Bug Fixes

  • Following bugs were fixed and included after 0.28.0 release: * Bug 1824533: Do not include ETag when puting manifest in chunked uploads * Bug 1818915: Python3: Fix return type on CooperativeReader.read * Bug 1805332: Prevent unicode object error from zero-byte read

0.29.0

New Features

  • Added keyword argument to register_store_opts and create_multi_stores calls to configure reserved stores by the consuming service. This feature will allow a mix of operator-configured stores via enabled_backends configuration option set in the [glance_store] section of the consuming service’s configuration file, and stores that are reserved for use by the consuming service.

Upgrade Notes

  • The store_capabilities_update_min_interval configuration option, deprecated since the Rocky release, has been removed. The option configured a capability that was not implemented by any glance_store drivers. Thus its removal will have no impact on any deployments.