[openstack-dev] [db][all] (Proposal) Restorable & Delayed deletion of OS Resources

Allamaraju, Subbu subbu at subbu.org
Mon Mar 17 05:23:53 UTC 2014

Hope this is not too late to ask this question, but isn't this extra code just fat finger mistakes?

IME, most provisioning on cloud happens via automated tools, and it seems counter-productive to design a feature for manual operations.


On Mar 13, 2014, at 12:42 PM, Boris Pavlovic <bpavlovic at mirantis.com> wrote:

> Hi stackers, 
> As a result of discussion:
> [openstack-dev] [all][db][performance] Proposal: Get rid of soft deletion (step by step) 
> http://osdir.com/ml/openstack-dev/2014-03/msg00947.html
> I understood that there should be another proposal. About how we should implement Restorable & Delayed Deletion of OpenStack Resource in common way & without these hacks with soft deletion in DB.  It is actually very simple, take a look at this document: 
> https://docs.google.com/document/d/1WGrIgMtWJqPDyT6PkPeZhNpej2Q9Mwimula8S8lYGV4/edit?usp=sharing
> Best regards,
> Boris Pavlovic 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

More information about the OpenStack-dev mailing list