Cinder Scalable Backup Service
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:
- newton-1
- Started by
- Mike Perez
- Completed by
- Sean McGinnis
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Blueprint Spec for scalable backup service
Addressed by: https:/
POC for blueprint spec
Gerrit topic: https:/
Addressed by: https:/
POC for scalable backup
Addressed by: https:/
Scaling backup service blueprint spec
Addressed by: https:/
Scaling backup service blueprint spec
Gerrit topic: https:/
Addressed by: https:/
Add restore_volume_id in backup
Gerrit topic: https:/
Addressed by: https:/
Scaling backup service
Addressed by: https:/
Scaling backup service -- rolling upgrade