
SolidFire driver introduced a clone image feature in Kilo release[1] where we would create a cache volume with volume ID same as of image ID to create volume from image efficiently by cloning from that cached volume. This feature worked same as the image cache feature we have in cinder so it was deprecated in queens[2] and removed in train[3] in favor of image cache feature provided by cinder. However, we still kept compatibility code if users had solidfire cached volumes to still take advantage of those to create efficient volume from images. In the current master (Yoga), we can safely assume that people have moved to using the image cache feature of cinder since the solidfire options to enable efficient cloning doesn't exist since train release. This patch removes the remaining code around this feature as it doesn't provide any additional benefit and we also log an ERROR message unnecessarily confusing the operators for every create volume from image request (details are in the linked launchpad bug). Closes-Bug: #1959178 [1] https://review.opendev.org/c/openstack/cinder/+/142859 [2] https://review.opendev.org/c/openstack/cinder/+/511623 [3] https://review.opendev.org/c/openstack/cinder/+/664739 Change-Id: I8fe00b06ebb439f83f8cad0f592064c540c54b77
OpenStack Cinder
OpenStack Cinder is a storage service for an open cloud computing service.
You can learn more about Cinder at:
Getting Started
If you'd like to run from the master branch, you can clone the git repo:
git clone https://opendev.org/openstack/cinder
If you'd like to contribute, please see the information in CONTRIBUTING.rst
You can raise bugs on Launchpad
Python client
Description
Languages
Python
99.7%
Smarty
0.3%