Use stack_task for stack delete

Registered by Steve Baker on 2013-07-10

Stack delete should use stack_task so it can be run in parallel, like suspend and resume.

This would also mean:
- rewriting volume and instance delete to implement check_delete_complete instead of directly using TaskRunner
- implement some simple check_delete_complete 404 checking for resource that are demonstrating races on delete (most involving neutron)

Blueprint information

Status:
Complete
Approver:
Steve Baker
Priority:
Medium
Drafter:
Steve Baker
Direction:
Approved
Assignee:
Vijendar Komalla
Definition:
Approved
Series goal:
Accepted for havana
Implementation:
Implemented
Milestone target:
milestone icon 2013.2
Started by
Steven Hardy on 2013-07-31
Completed by
Steven Hardy on 2013-09-05

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/parallel-delete,n,z

Addressed by: https://review.openstack.org/37764
    Resources state explicitly their allowed delete policies.

Addressed by: https://review.openstack.org/39307
    Use stack_task for stack delete

Addressed by: https://review.openstack.org/44336
    Implement parallel delete

Addressed by: https://review.openstack.org/44337
    parallelize volume deletion

Addressed by: https://review.openstack.org/44338
    parallelize instance delete

Addressed by: https://review.openstack.org/44339
    parallelize StackResource delete

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.