Hi all, Currently when deleting a volume, it checks whether there are snapshots created from it. If yes deletion is prohibited. But it allows to extend the volume, no check whether there are snapshots from it.
The two behaviors in Cinder are not consistent from my viewpoint. In backend storage, their behaviors are same. For full snapshot, if still in copying progress, both extend and deletion are not allowed. If snapshot copying finishes, both extend and deletion are allowed. For incremental snapshot, both extend and deletion are not allowed. As a result, this raises two concerns here: 1. Let such operations behavior same in Cinder. 2. I prefer to let storage driver decide the dependencies, not in the general core codes. Meanwhile, if we let driver to decide the dependencies, the following changes need to do in Cinder: 1. When creating a snapshot from volume, it needs copy all metadata of volume to snapshot. Currently it doesn't. Any other potential issues please let me know. Any input will be appreciated. Best wishes Lisa __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
