Victoria Series Release Notes

21.1.0

Bug Fixes

  • Bug1913625: Glance will leak staging data

  • Bug1914826: web download with invalid url does not report error

  • Bug1916052: Unable to Create trust errors in glance-api

  • Bug1930597: Doc for “Configuring SSL Support” outdated in glance

21.0.0

Prelude

The Victoria release includes some important milestones in Glancedevelopment priorities.

  • Added support to calculate virtual size of image based on disk format

  • Added support for sparse image upload for filesystem and rbd driver ofglance_store

  • Improved performance of rbd store chunk upload

  • Fixed some important bugs around copy-image import method and importingimage to multiple stores

  • Added support to configure multiple cinder stores

New Features

  • Added support for cinder multiple stores.

  • Added policy support to allow copying image to multiple stores,even if those images are not owned by the current user’s project.

  • Added support to calculate virtual size of image based on disk format

  • Added support for sparse image upload for filesystem and rbd driver

  • Improved performance of rbd store chunk upload

  • Added support to configure multiple cinder stores

Upgrade Notes

  • Theglance-replicator optionsmastertoken andslavetoken weredeprecated in the Pike release cycle. These options have now been removed.The optionssourcetoken andtargettoken should be used instead.

  • During upgrade from single cinder store to multiple cinder stores, legacyimages location url will be updated to the new format with respect to thevolume type configured in the stores.Legacy location url: cinder://<volume-id>New location url: cinder://<store-id>/<volume-id>

  • After upgrading, deployments using the cinder backend shouldupdate their config to specify a volume type. Existing images onthose backends will be updated at runtime (lazily, when they arefirst read) to a location URL that includes the store and volumetype information.

Deprecation Notes

  • This release removes endpoints and config options relatedto glance-registry. Including but not limited to configoption ‘data-api’ which has no production supportedoptions left. SimpleDB has not been supported sincemoving DB migrations to alembic and registry is removed.All registry specific options and config files have beenremoved. ‘glance-registry’ command has been removed.

  • The deprecated ‘enable_v2_api’ config option has beenremoved.

  • The Imagechecksum property contains an MD5 hash of the image dataassociated with an image. MD5 has not been considered secure for sometime, and in order to comply with various security standards (forexample, FIPS), an implementation of the MD5 algorithm may not beavailable on glance nodes.

    The secure “multihash” image properties,os_hash_algo andos_hash_value have been available on images since glanceversion 17.0.0 (Rocky). Until this point, the MD5checksumproperty has been populated solely for backward compatability. Itis not, however, necessary for validating downloaded image data.

    Thus, we are announcing the DEPRECATION in this release of theimagechecksum property. It will remain as an image property,but beginning with the Victoria release, thechecksum willnotbe populated on new images.

    Users should instead rely on the secure “multihash” to validate imagedownloads. The python-glanceclient, for example, has been using multihashvalidation (with an optional MD5 fallback) since version 2.13.0 (Rocky).

Bug Fixes

  • Bug1881958: read-only http store should not be used if –all-stores specified for import/copy image workflow

  • Bug1889640: Image import might result ‘active’ image with no data.

  • Bug1889676: “stores” can be set as property breaking multistore indication of stores where the images are present

  • Bug1887994: Mixed message in admin docs to deploy under httpd

  • Bug1884596: A change was added to the import API which providestime-based locking of an image to exclude other import operationsfrom starting until the lock-holding task completes. The lock isbased on the task that we start to do the work, and the UUID ofthat task is stored in theos_glance_import_task image property,which indicates who owns the lock. If the task holding the lock failsto make progress for 60 minutes, another import operation will beallowed to steal the lock and start another import operation.

  • Bug1885725: ‘copy-image’ import job should not run additional plugins

  • Bug1888349: glance-cache-manage utility is broken

  • Bug1886374: Improve lazy loading mechanism for multiple stores

  • Bug1885003: Interrupted copy-image may break a subsequent operation

  • Bug1884587: image import copy-image API should reflect proper authorization

  • Bug1876419: Failed to parse json file /etc/glance/metadefs/compute-vmware.json

  • Bug1856581: metadefs: OS::Glance::CommonImageProperties out of date

  • Bug1843576: Glance metadefs is missing Image property hw_vif_multiqueue_enabled

  • Bug1856578: docs: image schema customization restrictions

  • Bug1808814: admin docs: interoperable image import revision for stein

  • Bug1870336: Update ‘common image properties’ doc

  • Bug1888713: Async tasks, image import not supported in pure-WSGI mode

  • Bug1891190: test_reload() functional test causes hang and jobs TIMED_OUT

  • Bug1891352: Failed import of one store will remain in progress forever if all_stores_must_succeed=True

  • Bug1887099: Invalid metadefs for watchdog

  • Bug1795950: Fix cleaning of web-download image import in node_staging_uri

  • Bug1895663: Image import “web-download” doesn’t check on download size