Note about quantum database and plug-ins is inaccurate.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Fix Released
|
Medium
|
Tom Fifield |
Bug Description
In the openstack-network book section on install Quantum and plug-ins [1][2] we find a note that says:
"Different plugins can use different database schemas, so when switching a plugin, you must always drop the quantum database and start fresh."
It's been brought to my attention [3] that this is somewhat inaccurate in as much as the plug-ins actually create separate databases such as:
cisco => quantum_l2network
linuxbridge => quantum_
metaplugin => quantum_metaplugin
nec => ovs_quantum
nicira => nvp_quantum
openvswitch => ovs_quantum
ryu => ryu_quantum
Obviously there is an exception here (there's always one...) in that the nec and openvswitch plug-ins actually use the same database. That said, the issues with the existing note are:
- It makes it sound like there is a single "quantum" database involved here that the plug-ins 'fight' for.
- It states that you must always drop the plug-in database when switching - but it appears this isn't actually necessary (maybe advisable but that's different to must always)?
I think the note needs to be updated to reflect these factors or removed and this information reflected elsewhere (I am still considering how best to present this information).
[1] http://
[2] http://
[3] https:/
Changed in openstack-manuals: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
status: | Confirmed → Triaged |
milestone: | none → grizzly |
tags: | added: quantum |
Changed in openstack-manuals: | |
assignee: | nobody → Tom Fifield (fifieldt) |
status: | Triaged → In Progress |
Fix proposed to branch: master /review. openstack. org/24006
Review: https:/