Add support for force-delete backups

Registered by ling-yun on 2014-06-04

Since there are volume force-delete function and snapshot force-delete function, backup also needs force-delete as well.
Use backup-create routine as an example to illustrate what benefit we can get from force-delete function.
Backup-create routine first backup volume and metadata, and then update the status of volume and backup. If database just went down after update the volume's status to 'available', leaving the backup's status to be 'creating' without having methods to deal with through API, because backup-delete api could only delete backup item in status of 'available' and 'error' .
If we have backup force-delete API, we could directly delete the backup item without manually change the backup's status in db to error and call backup-delete function, which is very useful for maintainers.

Blueprint information

Status:
Complete
Approver:
Mike Perez
Priority:
Medium
Drafter:
ling-yun
Direction:
Approved
Assignee:
wanghao
Definition:
Approved
Series goal:
Accepted for liberty
Implementation:
Implemented
Milestone target:
milestone icon 7.0.0
Started by
wanghao on 2015-05-06
Completed by
Mike Perez on 2015-07-24

Related branches

Sprints

Whiteboard

2015-02-09 <thingee>: Not sure on the status of this. We're pretty full as it is, so if there's not code posted now, doesn't have a good chance of getting in.

Gerrit topic: https://review.openstack.org/#q,topic:bp/for,n,z

Addressed by: https://review.openstack.org/98325
    Add blueprint for support-force-delete-backup

You should not set a milestone target unless the blueprint has been properly prioritized by the project drivers.

@Mike Perez: we will post the code asap in these few days.

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

Addressed by: https://review.openstack.org/166127
    Supprot for force-delete backups

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.