Bug 1057832 - [RFE][cinder]: Refactor delete snapshot api using taskflow
Summary: [RFE][cinder]: Refactor delete snapshot api using taskflow
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/cind...
Whiteboard: upstream_milestone_none upstream_stat...
: 1016231 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-25 05:06 UTC by RHOS Integration
Modified: 2015-11-20 19:53 UTC (History)
4 users (show)

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


Attachments (Terms of Use)

Description RHOS Integration 2014-01-25 05:06:19 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/cinder/+spec/delete-snapshot-taskflow.

Description:

Refactor the delete_snapshot api/manager code to use Taskflow (https://wiki.openstack.org/wiki/TaskFlow).
Split delete_snapshot api/manager code into tasks that rollback/recover from failures during DB operations of delete_snapshot and during Quota operations of delete_snapshot.

Delete snapshot using taskflow pseudo code 

Cinder-api tasks:

class api_delete_snapshot:
def execute: 
check_volume_status
update db status
def revert:
revert updated DB

class api_rpc_request:
def execute:
rpc cast to delete_snapshot

Cinder-manger tasks:

class volume_delete_snapshot:
def execute:
driver.delete_snapshot
def revert:
update db in case of failure

class volume_update_metadata:
def execute:
update_volume_glance_metadata
def revert:
quota revert

class volume_update_quota:
def execute:
reserve_quota for delete_snapshot

class volume_commit_quota:
def execute:
commit quota for delete_snapshot

Specification URL (additional information):

None

Comment 1 Sean Cohen 2014-04-29 12:51:01 UTC
*** Bug 1016231 has been marked as a duplicate of this bug. ***


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