Cinder Scalable Backup Service

Registered by Tom Barron

Currently cinder backup service is tightly coupled to, and must run on the same node as, cinder volume service. We propose to break this tight coupling, so that the backup service can run on other nodes, enabling potential horizontal scale-out of the backup service as backup workloads require.

Blueprint information

Status:
Complete
Approver:
Mike Perez
Priority:
Low
Drafter:
Tom Barron
Direction:
Approved
Assignee:
Tom Barron
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
milestone icon newton-1
Started by
Mike Perez
Completed by
Sean McGinnis

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#/q/topic:bp/scalable-backup-service,n,z

Addressed by: https://review.openstack.org/#/c/203215/
     Blueprint Spec for scalable backup service

Addressed by: https://review.openstack.org/#/c/203291/
     POC for blueprint spec

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

Addressed by: https://review.openstack.org/203291
    POC for scalable backup

Addressed by: https://review.openstack.org/203215
    Scaling backup service blueprint spec

Addressed by: https://review.openstack.org/240978
    Scaling backup service blueprint spec

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

Addressed by: https://review.openstack.org/260903
    Add restore_volume_id in backup

Gerrit topic: https://review.openstack.org/#q,topic:bp/scalable-backup-service,n,z

Addressed by: https://review.openstack.org/262395
    Scaling backup service

Addressed by: https://review.openstack.org/269412
    Scaling backup service -- rolling upgrade

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.