yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #82133
[Bug 1864548] Re: There's no reason the ovn l3 plugin should create its own ovsdb connections
Reviewed: https://review.opendev.org/708985
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d92e71c297d84f767dfb9b2485e64853decce873
Submitter: Zuul
Branch: master
commit d92e71c297d84f767dfb9b2485e64853decce873
Author: Terry Wilson <twilson@xxxxxxxxxx>
Date: Thu Feb 20 22:26:44 2020 +0000
Use OVN mech driver OVSDB connections for l3 plugin
It is possible to re-use the mech driver ovsdb connections in the
ovn l3 plugin, saving the overhead of two db connections/in-memory
copies of the db per process.
Closes-Bug: #1864548
Change-Id: I022dea485f42cf76c4cec67ee43eed9a3770ec9c
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1864548
Title:
There's no reason the ovn l3 plugin should create its own ovsdb
connections
Status in neutron:
Fix Released
Bug description:
The l3 ovn plugin creates it's own NB/SB OVSDB connections when it
could just use the ones already created by the mech driver. No reason
to maintain two in-memory copies of each DB for each process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1864548/+subscriptions
References