Current Series Release Notes¶
27.0.0-51¶
Upgrade Notes¶
The WSGI script
cinder-wsgihas been removed. Deployment tooling should instead reference the Python module path for this service,cinder.wsgi.api, if their chosen WSGI server supports this (gunicorn, uWSGI) or implement a.wsgiscript themselves if not (mod_wsgi).
Bug Fixes¶
Hitachi driver: Enable support for VSP One B20. VSP One B20 supports ADR functionality that offers up to 4:1 data saving, and Thin Image Advanced that supports superior ROW functionality. In addition, the B20 supports vClone technology that allows for instantaneous cloning and shared data between clones.
Bug #2106680: Configuration of the
volume_clear_ioniceoption now behaves consistently with the othervolume_clear_*options. Keep in mind that thevolume_clear_*options apply only to the LVM driver and only when thick volumes are being used. See the data leakage section of the Security page of the Cinder Administration Guide for more information.
The NetApp driver supports SMAS replication which on ONTAP is supported only from ONTAP 9.15.1. Additional validations are added to the driver to ensure ONTAP version checks and initialization of SnapMirror as part of creation of SMAS relationship.
- Bug #2119123:
Fix for NetApp Cinder Driver - Active Sync issues
Bug #2121812: Default node model to empty string in netapp driver.
NetApp driver bug #2125054: Fixed default_filter_fucntion for NetApp driver to maintain the consistency across different platforms like ONTAP9 and ASAr2.
Admin can add a custom filter to impose the total_volumes limit for ONTAP backends like below. filter_function=capabilities.total_volumes < <max_volumes_admin_wants>
Note: The admin needs to configure the scheduler_default_filters to include the DriverFilter as well under [DEFAULT] stanza as part of cinder.conf, please refer [1] for the default filter list.
[1] https://docs.openstack.org/cinder/latest/configuration/block-storage/samples/cinder.conf.html
Bug #2121361: Fixed issue when performing optimized image-volume clone using a backend with
clone_across_poolscapability enabled.
Bug #2056081: When cloning a volume from a source volume, we used the user ID of source volume user and not of the current user. Now we use the user ID as provided in the user context that initiated the operation.
Bug #2104334: Fixed optimized migration path for LVM volumes during retype.
HPE Nimble driver. Report thin provisioning capability correctly according to backend configuration.