Bug 1041249 - [RFE][nova]: Support user custom reclaim interval when soft deleting
Summary: [RFE][nova]: Support user custom reclaim interval when soft deleting
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:04 UTC by RHOS Integration
Modified: 2015-03-19 17:32 UTC (History)
2 users (show)

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


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 14:04:59 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/custom-expire-in-soft-delete.

Description:

Now when reclaim_instance_interval is great than 0, the delete action will become soft_delete.
Whilst currently implemented the reclaim_instance_interval is system level config. User can't control the expires time of instance. 
This blueprint support user to specify the reclaim_instance_interval.
For example, I can keep a important instance for 1 weeks, and keep some not so important about 1 hour. 
-gtt

In detail, the API will looks like below ( suggested by Brian Lamar):
DELETE /v2/1234/servers/e14b69ce-eb17-4998-a8cb-114640db328b?delay_until=<utc_date>

If "delay_until" is set too far in the future, this DELETE call could return 400 Bad Request with details about the operator's maximum allowed reclaim interval.

reclaim_instance_interval_max: If = 0 then "soft" deletes are effectively disabled. Users can never request a "soft" delete farther in the future than this value allows.


Specification URL (additional information):

None


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