incremental backup improvements for L

Registered by wanghao on 2015-06-03

At Kilo release we supported incremental backup, but there are still some points need to be improved.
1. From the API perspective, there is no place to show the backup is incremental or not. It's useful to 3rd part billing system, they could have different fee for full and incremental backup.
2. User also don't the know if the incremental backup can be deleted or not, it's important because cinder don't allow to delete this backup since 'Incremental backups exist for this backup'. At now, they must have a try to know it. So if there is a flag
to indicate the backup can't be deleted or not, it will bring more convenient to user and
reduce API call.
3.Enriching the notification system via reporting to Ceilometer, add parent_id to report.

Blueprint information

Status:
Complete
Approver:
Mike Perez
Priority:
Medium
Drafter:
wanghao
Direction:
Approved
Assignee:
wanghao
Definition:
Approved
Series goal:
Accepted for liberty
Implementation:
Implemented
Milestone target:
milestone icon 7.0.0
Started by
Mike Perez on 2015-07-17
Completed by
John Griffith on 2015-08-31

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/cinder-incremental-backup-improvements-for-l,n,z

Addressed by: https://review.openstack.org/187926
    Incremental backup improvements for L

Addressed by: https://review.openstack.org/188328
    Incremental backup improvements for L

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.