Current Series Release Notes

16.0.0.0b1-10

Upgrade Notes

  • Dell EMC PS Series storage driver is not supported and removed starting from the Ussuri release. It was marked as deprecated in the Train release.

Bug Fixes

  • The volume-transfers list calls (GET /v3/{project_id}/volume-transfers, GET /v3/{project_id}/volume-transfers/detail) were not recognizing name as a filterable attribute. That has been fixed in the current release.

16.0.0.0b1

New Features

  • Huawei Cinder Driver Support Dorado V6 Storage.(iSCSI, FC)

  • Added the image_conversion_cpu_limit and image_conversion_address_space_limit as configurable parameters. This adds configurability to the image conversion process to prevent the process from timing out when converting larger images.

  • The LINSTOR Driver for Cinder now supports LINSTOR 0.9.12.

  • Fujitsu Driver: Added multiple pools support.

  • Dell EMC PowerMax driver now supports Unisphere storage group and array tagging to allow the user to specify a user defined tag to facilitate easy access and classification.

  • This release includes support for Glance multiple stores. An operator may now specify which Glance store will be used when a volume is uploaded to Glance as an image. Some details about this feature:

    • This feature is not directly user-facing. To enable it, an operator must add the field image_service:store_id in the volume-type extra-specs. The value of the field is a valid store identifier (id) configured in Glance, which may be discovered by making a GET /v2/info/stores call to the Image Service API.

    • If image_service:store_id is not set in the extra-specs for a volume-type, then any volume of that type uploaded as an image will be uploaded to the default store in Glance.

    • The image_service:store_id can only be set in the extra-specs for a volume-type when multiple glance stores are configured.

    • Cinder validates proposed Glance store identifiers by contacting Glance at the time the image_service:store_id is added to a volume-type’s extra-specs. Thus the Image Service API must be available when a volume-type is updated.

Upgrade Notes

  • The LINSTOR driver for Cinder supports LINSTOR 0.9.12. The driver supports LINSTOR backend using REST API.

    The new driver adds ‘linstor_autoplace_count’ configuration option that specifies the number of volume replicas.

  • Python 2.7 support has been dropped. The last release of Cinder to support py2.7 is OpenStack Train. The minimum version of Python now supported by Cinder is Python 3.6.

  • The Huawei FusionStorage driver was marked unsupported in the Train release and has now been removed. All data on FusionStorage backends should be migrated to a supported storage backend before upgrading your Cinder installation.

  • IBM DS8k drivers had been previously marked unsupported. Testing requirements have been addressed and they are now fully supported again. IBM DS8k drivers allow cinder to manage volumes in FC environment.

  • IBM Storwize drivers had been previously marked unsupported. Testing requirements have been addressed and they are now fully supported again. IBM Storwize drivers allow cinder to manage volumes both in iSCSI and FC environment.

  • The MacroSAN Storage driver has been marked as unsupported and is now deprecated. enabled_unsupported_driver will need to be set to True in the driver’s section in cinder.conf to continue to use the driver.

  • The Brocade Fibre Channel Zone Manager driver has been marked as unsupported and is now deprecated. It is subject to removal during the “V” development cycle, following the standard OpenStack deprecation policy. The config option enable_unsupported_driver will need to be set to True in the driver’s section in cinder.conf to continue to use it in this release.

  • SolidFire supports Synchronous, Asynchronous and SnapshotsOnly replication modes. This adds the config option solidfire:replication_mode to specify the mode to be used by Cinder. Its value can be Sync, Async or SnapshotsOnly.

  • The Nimble Storage driver was marked unsupported in the Train release and has now been removed. All data on Nimble Storage backends should be migrated to a supported storage backend before upgrading your Cinder installation.

  • The ProphetStor Flexvisor driver was marked unsupported in the Train release and has now been removed. All data on ProphetStor Flexvisor backends should be migrated to a supported storage backend before upgrading your Cinder installation.

  • If you have backup_driver_status_check_interval option in your cinder.conf we recommend you to use backup_driver_stats_polling_interval to avoid deprecation warnings in logs.

  • SPDK target and volume drivers have been updated with new SPDK specific RPC calls due to deprecation of some old RPC calls. Starting from Ussuri release SPDK release v19.10 or higher is required.

  • The Sheepdog driver was marked unsupported in the Train release and has now been removed. All data on Sheepdog backends should be migrated to a supported backend before upgrading your Cinder installation.

  • The Veritas Access driver was marked unsupported in the Train release and has now been removed. All data on Veritas Access backends should be migrated to a supported storage backend before upgrading your Cinder installation.

  • The Veritas Clustered NFS driver has been marked as unsupported and is now deprecated. enabled_unsupported_driver will need to be set to True in the driver’s section in cinder.conf to continue to use the driver.

  • The Virtuozzo Storage driver was marked unsupported in the Train release and has now been removed. All data on Virtuozzo Storage backends should be migrated to a supported storage backend before upgrading your Cinder installation.

  • The Virtuozzo driver has been marked as unsupported and is now deprecated. enable_unsupported_driver will need to be set to True in the driver’s section in cinder.conf to continue to use it.

Deprecation Notes

  • The configuration option rbd_keyring_conf for the Ceph cinder driver presents a security risk and the option is hereby deprecated and scheduled to be removed early in the ‘V’ development cycle, following the standard OpenStack deprecation policy. For more information, see OSSN-0085: Cinder configuration option can leak secret key from Ceph backend.

  • The MacroSAN Storage driver has been marked as unsupported and is now deprecated. enable_unsupported_driver will need to be set to True in the driver’s section in cinder.conf to continue to use the driver. It its support status does not change the driver will be removed in the ‘V’ development cycle.

  • The Brocade Fibre Channel Zone Manager driver has been marked as unsupported and is now deprecated. It is subject to removal during the “V” development cycle, following the standard OpenStack deprecation policy. The config option enable_unsupported_driver will need to be set to True in the driver’s section in cinder.conf to continue to use it in this release.

  • backup_driver_status_check_interval config option is renamed to backup_driver_stats_polling_interval to be similar with volume drivers configuration. Old option name support will be dropped in U release.

  • The Veritas Clustered NFS driver has been marked as unsupported and is now deprecated. enable_unsupported_driver will need to be set to True in the driver’s section in cinder.conf to continue to use the driver. It its support status does not change the driver will be removed in the ‘V’ development cycle.

  • The Virtuozzo driver has been marked as unsupported and is now deprecated. enable_unsupported_driver will need to be set to True in the driver’s section in cinder.conf to continue to use it. If its support status does not change, it will be removed in the ‘U’ development cycle.

Security Issues

  • Due to OSSN-0085: Cinder configuration option can leak secret key from Ceph backend, deployers using the rbd_keyring_conf option are advised to stop using it immediately. The option has been deprecated for removal early in the ‘V’ development cycle.

Bug Fixes

  • An incorrect lock in the remotefs code, which is used for the NFS driver, and other similar drivers, resulted in concurrent clone volume operations failing. create_cloned_volume now locks on the source volume id, meaning multiple clone operations from the same source volume are serialized.

    A lock in the volume manager flow generally prevents this on normal clone volume operations, but this clone method in the driver is called for operations such as cloning from the cinder image-volume cache or cloning from a cinder backend used as a glance store.

  • The SolidFire replication was fixed. Several bugs were addressed (creating replicated volumes from snapshots, from volumes, retype a volume to a replicated type, managing a volume to a replicated type, correctly updating portal info on failover/failback and some minor other fixes). Closes bugs #1834013, #1751932.

  • This change fixes bug 1845483 - 3PAR: For Peer Persistence, add policy options in RCG. Following options are added after Remote Copy Group (RCG) is created: autoFailover, pathManagement, autoRecover

  • PowerMax driver - fix to eliminate ‘cannot use the device for the function because it is in a Copy Session’ when attempting to delete a volume group that previously had a group snapshot created on and deleted from it.

  • Catch argument exceptions when configuring multiattach for rbd volumes. This allows multiattach images with flags already set to continue instead of raising an exception and failing.

Other Notes

  • PowerMax driver - the minimum version of Unisphere for PowerMax for the current release is 9.1.0.5. It is however recommended to install the Security Releases(SR) of Unisphere for PowerMax if they become available.