After pool is introduced, cinder should support the new and old version of the driver compatible
Bug #1574503 reported by
YaoZheng_ZTE
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
New
|
Low
|
Unassigned |
Bug Description
After pool is introduced in the BP https:/
if the driver has not supported it, In the process, the backend name is specified as the pool name.
But if the driver later Implemented it, pool name is the back-end driver reported. so , if we have legacy volume,
the volume 's host like is: 'HostA@
Changed in cinder: | |
assignee: | nobody → YaoZheng_ZTE (zheng-yao1) |
Changed in cinder: | |
importance: | Undecided → Medium |
Changed in cinder: | |
importance: | Medium → Low |
Changed in cinder: | |
status: | In Progress → New |
To post a comment you must log in.
We should deal with this compatibility issue, The scheme: when start volume service, we can get all volumes by the host, then backend_ name, we call get_pool query the pool_name from driver, then modify the volume's host information.
extract pool information from volume's host. If the pool is None or volume_