Update the volume's available_zone after changed its backend's available_zone
Registered by
Brin Zhang
In the scenario of many of our cloud customers, they are always need to add (or change) a volume backend for the OpenStack cluster, with this scenario, we should change the volume's available_zone if it's backend's available_zone changed.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Brin Zhang
- Direction:
- Needs approval
- Assignee:
- xuanyandong
- Definition:
- Drafting
- Series goal:
- Proposed for xena
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)
