Implement Volume Backup Creation via TaskFlow
Implementing long-running operations via task flows is needed, so we can better control the operation process. Task flows will evetually allow us to pause/resume running backups, reverting in case of failure and tracking progress of running tasks.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Mikhail Khodos
- Direction:
- Needs approval
- Assignee:
- Mikhail Khodos
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- 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.
Motivation:
All long-running processes will eventually end up implemented as task flows.
Volume backups, for example, is such a potentially long-running process.
So creation of (and then restoration from) a volume backup should be implemented via
a task flow.
After the mechanism for task progress update is there (see https:/
Gerrit topic: https:/
Addressed by: https:/
Implements volume backups via task flow
Addressed by: https:/
Implements volume backups via task flow