Open Stack

Hi all,

    I have submit a blueprint about deferred deletion for volumes in cinder: https://review.openstack.org/#/c/97034/

    The implements of deferred deletion for volumes will introduce some complexity, to this point, there are different options in stackers. So we would like to get some feedback from anyone, particularly cloud operators.

	Here, I introduce the importance of deferred deletion for volumes again.  
    Currently in cinder, calling the API of deleting volume means the volume will be deleted immediately. If the user specify a wrong volume by mistake, the data in the volume may be lost forever. To avoid this, I hope to add a deferred deletion mechanism for volumes. So for a certain amount of time, volumes can be restored after the user find a misuse of deleting volume. 
    Moreover, there are deferred deletion implements for instance in nova and image in glance, I think it is very common feature to protected important resource.
    So I think deferred deletion for volumes is valuable,  it seems to me that should be sufficient.

    Welcome your feedback and suggestions!

Thanks.

Zhou Yu