Volume drivers should support check is volume already exists
After some fail or cinder-volume restart we want try create/
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Ivan Kolodyazhny
- Direction:
- Needs approval
- Assignee:
- Yuriy Nesenenko
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Sean McGinnis
Related branches
Related bugs
Sprints
Whiteboard
Sean: Abandoning this as it appears to have stalled in reviews. If still desired we can reopen.
Avishay: I would change the semantics of the call to be "what is the status of volume X"? The return value would be one of: OK, not found, error (I think these are states everyone can agree on). Now you can have checks to make sure the Cinder DB is consistent with the storage. This will reduce cases where the volume exists in one but not the other, but also give some indication of the volume's health. Even better, make a batch call to the driver with a list of volume ID - "what is the status of these 100 volumes?"
Gerrit topic: https:/
Addressed by: https:/
Checking the existence of volume
Addressed by: https:/
Implement blueprint: check-volume-exists