SolidFire driver's name isn't consistent with other drivers
Bug #1136081 reported by
Mathieu Gagné
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cinder |
Fix Released
|
Low
|
Mathieu Gagné | ||
Bug Description
The SolidFire driver's name is "SolidFire", not "SolidFireDriver" as you would "expect" by looking at the other drivers.
This is mostly a consistency issue trigged by my OCD.
| Changed in cinder: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| assignee: | nobody → John Griffith (john-griffith) |
| tags: | added: drivers |
Revision history for this message
| Duncan Thomas (duncan-thomas) wrote | #1 |
| tags: | added: solidfire |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to cinder (master) | #2 |
| Changed in cinder: | |
| assignee: | John Griffith (john-griffith) → Mathieu Gagné (mgagne) |
| status: | Triaged → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to cinder (master) | #3 |
| Changed in cinder: | |
| status: | In Progress → Fix Committed |
| Changed in cinder: | |
| milestone: | none → havana-3 |
| status: | Fix Committed → Fix Released |
| Changed in cinder: | |
| milestone: | havana-3 → 2013.2 |
To post a comment you must log in.
I think changing this would cause old config files to become broken during upgrade unless the driver name mapping stuff we have can be co-opted into helping?
If not, I'd rather not see this changed.