Refactor the backup service to have a common interface
This blueprint aims to have a common interface between the volume driver and the backup service.
In the current situation the there is only one volume driver (lvm) that supports backups and only one backup service (swift). In order to support more volume drivers and more backup targets there has to be some rework done in the existing interface.
Blueprint information
- Status:
- Complete
- Approver:
- Marc Koderer
- Priority:
- Low
- Drafter:
- Marc Koderer
- Direction:
- Approved
- Assignee:
- Marc Koderer
- Definition:
- Approved
- Series goal:
- Accepted for havana
- Implementation:
- Implemented
- Milestone target:
- 2013.2
- Started by
- Marc Koderer
- Completed by
- John Griffith
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Adding interface class for backup services
This seems rather lacking in detail... there is a common interface now. Please add detail to what you feel is missing and what benefits any changes bring. -- DuncanT
The interface should follow the common OpenStack semantics. Therfore "backup service" will be renamed to "backup driver". An inteface class will ease up the creation of new backup drivers. -- mkoderer
Work Items
Work items:
Add common interface class: DONE
Rename backup service to backup driver: DONE
Add old2new mapping to support old configuration: DONE
Add documenation how backup drivers can be added: TODO