Move task status from volume_status to a dedicated field
Currently the single status field of a volume holds the basic states, such as ‘available’ or ‘in-use’, but is also used by different tasks that run for the volume (‘backing-up’) - see https:/
Reducing the volume status field to hold only a reduced set of states and moving tasks and their status to a dedicated field would allow for two state machines: One for the state of the volume itself and another coordinating the tasks.
One use case can be the mentioned live-migration of a server with an attached volume. While the volume is in the potentially longer lasting state of 'backing-up', the server cannot also be migrated to a different host (see https:/
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Niklas Schwarz
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by