cinder backup improvements
There are currently a number of issues with the cinder backup service so I'm creating this blueprint to collate them since there is a some overlap and they could benefit from each other's context.
We currently have the following bugs/issues: (see Work Items section below)
Looking at these issues, there are a number of changes that need to be made to how the backup service works, notably:
1. We need AZ awareness when restoring to a new volume (need to ensure backup request goes to service running in correct AZ)
2. We need to include Glance metadata in backups (this should probabaly include encryption metadata i.e. store it all in backend store as opposed to the cinder db).
3. We need to support running multiple backup services on a single host running multiple backends.
4. We need a taskflow for backup operations
While some of these clearly involve changes that are not going to make H, it would be great to get some interim patches/
Blueprint information
- Status:
- Complete
- Approver:
- John Griffith
- Priority:
- Undefined
- Drafter:
- Edward Hope-Morley
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Started
- Milestone target:
- None
- Started by
- Edward Hope-Morley
- Completed by
- Sean McGinnis
Related branches
Related bugs
Sprints
Whiteboard
(smcginnis): Marking obsolete as this has been sitting out there for a long time. If this is still needed, please submit a new bp.
Remote attach does not and should not work cross-az - the request needs to go to a backup-manager in the right az --DuncanT
@DuncanT - oops I'll correct that.
