yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #32418
[Bug 1449263] [NEW] The native OVSDB Connection class should allow users to pass in their own Idl instance
Public bug reported:
The OVS library now allows registering a notification hook by
subclassing the Idl class and defining a notify() function. To be able
to use this in Neutron (and networking-ovn), it must be possible for the
Connection object to use a subclassed Idl. It currently is hardcoded to
instantiate its own idl from ovs.db.idl.Idl.
networking-ovn needs to pass in a subclassed Idl to be able to notify
neutron when a port is successfully wired. Neutron could use this to
avoid having to spawn ovsdb-client monitor when using the native OVSDB
driver.
** Affects: neutron
Importance: Undecided
Assignee: Terry Wilson (otherwiseguy)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1449263
Title:
The native OVSDB Connection class should allow users to pass in their
own Idl instance
Status in OpenStack Neutron (virtual network service):
In Progress
Bug description:
The OVS library now allows registering a notification hook by
subclassing the Idl class and defining a notify() function. To be able
to use this in Neutron (and networking-ovn), it must be possible for
the Connection object to use a subclassed Idl. It currently is
hardcoded to instantiate its own idl from ovs.db.idl.Idl.
networking-ovn needs to pass in a subclassed Idl to be able to notify
neutron when a port is successfully wired. Neutron could use this to
avoid having to spawn ovsdb-client monitor when using the native OVSDB
driver.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1449263/+subscriptions
Follow ups
References