Default plugin in the plugins.ini
Bug #817813 reported by
Sumit Naiksatam
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Unassigned | ||
quantum (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
The plugin configuration used to earlier point to the FakePlugin. However, now it points to OVSQuantumPlugin. Is OVSQuantumPlugin being packaged as the default plugin?
If so, probably the README file should be changed to reflect that.
If not, this might be the consequence of the file getting merged from an OVS-specific branch, in which case we should revert back to the FakePlugin configuration.
Related branches
lp:~danwent/neutron/bug817813
- Salvatore Orlando: Approve
- Sumit Naiksatam: Approve
-
Diff: 9 lines (+1/-2)1 file modifiedquantum/plugins.ini (+1/-2)
summary: |
- Default plugin in the plug.ini + Default plugin in the plugins.ini |
Changed in quantum: | |
importance: | Undecided → High |
Changed in quantum: | |
status: | New → Fix Committed |
milestone: | none → diablo-3 |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
Changed in quantum (Ubuntu): | |
status: | New → Fix Released |
To post a comment you must log in.
mmm... good catch, don't think that was intentional. I suspect that slipped
in by accident during an un-related check-in. bzr makes it really easy to
accidentally commit your own config files.... can't wait until we are on
github :)
I'll fix.
dan
On Thu, Jul 28, 2011 at 5:34 PM, Sumit Naiksatam
<email address hidden>wrote:
> Public bug reported: /bugs.launchpad .net/bugs/ 817813 /bugs.launchpad .net/quantum/ +bug/817813/ +subscriptions
>
> The plugin configuration used to earlier point to the FakePlugin.
> However, now it points to OVSQuantumPlugin. Is OVSQuantumPlugin being
> packaged as the default plugin?
>
> If so, probably the README file should be changed to reflect that.
>
> If not, this might be the consequence of the file getting merged from an
> OVS-specific branch, in which case we should revert back to the
> FakePlugin configuration.
>
> ** Affects: quantum
> Importance: Undecided
> Status: New
>
> ** Summary changed:
>
> - Default plugin in the plug.ini
> + Default plugin in the plugins.ini
>
> --
> You received this bug notification because you are a member of Netstack-
> admins, which is the registrant for quantum.
> https:/
>
> Title:
> Default plugin in the plugins.ini
>
> Status in Quantum L2 as a service:
> New
>
> Bug description:
> The plugin configuration used to earlier point to the FakePlugin.
> However, now it points to OVSQuantumPlugin. Is OVSQuantumPlugin being
> packaged as the default plugin?
>
> If so, probably the README file should be changed to reflect that.
>
> If not, this might be the consequence of the file getting merged from
> an OVS-specific branch, in which case we should revert back to the
> FakePlugin configuration.
>
> To manage notifications about this bug go to:
> https:/
>
-- ~~~~~~~ ~~~~~~~ ~~~~~~ ~~~~~~~ ~~~~~~~ ~~~~~~
~~~~~~~
Dan Wendlandt
Nicira Networks, Inc.
www.nicira.com | www.openvswitch.org
Sr. Product Manager
cell: 650-906-2650
~~~~~~~