core_plugin is defaulted to a non existed plugin
Bug #1093989 reported by
yong sheng gong
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Undecided
|
Gary Kotton |
Bug Description
cfg.
I propose let it point to:
quantum.
Changed in quantum: | |
milestone: | none → grizzly-2 |
status: | Fix Committed → Fix Released |
Changed in quantum: | |
milestone: | grizzly-2 → 2013.1 |
To post a comment you must log in.
To me, setting a default plugin is something that should be done by a distro. This already happens in practice, with Canonical setting it to OVS, and devstack defaulting to q-plugin as OVS. I think some versions of fedora default to OVS, while perhaps older versions of Red Hat default to linux-bridge, since OVS is not available.
I agree that having a non-existant plugin there makes no sense. I think having the field empty probably by default makes the most sense, but if we're going to pick one, the OVS plugin probably makes sense.