Bug 1041253 - [RFE][nova]: Defer all instance deletion for a configurable interval
Summary: [RFE][nova]: Defer all instance deletion for a configurable interval
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/nova...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 14:05 UTC by RHOS Integration
Modified: 2015-03-19 17:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:04:58 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 14:05:42 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/deferred-instance-deletes.

Description:

Defer instance deletion for a period of time rather than immediately purging them from disk

There are three types of "erroneous deletion" that we've seen in production:

1.  User error, e.g., People clicking on "Terminate" by mistake

2.  Software bugs, e.g., Live migrations get confused and claim success, when the instance on the remote side is nowhere near usable

3.  Confusing API behavior, e.g., Calling "stop" and then "start" is destructive to the instance as a side-effect, which catches people by surprise

Currently, the "soft delete" functionality only protects against Condition #1.  We propose adding an additional "deferred delete" functionality that protects against them all by using whatever data protection features the storage drivers see fit to postpone purging the bits off of disk for a user-specified length of time.  There would also be a periodic job on the compute node that would periodically run the corresponding purges on the appropriate storage drivers as needed.

We are willing to implement the framework for the feature, as well as the functionality for the libvirt driver.

Specification URL (additional information):

None


Note You need to log in before you can comment on or make changes to this bug.