yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #24873
[Bug 1396489] [NEW] OVSInterfaceDriver should use ovs_lib not call ovs-vsctl directly
Public bug reported:
ovs_lib module is responsible for the interaction with OVS but OVSInterfaceDriver._ovs_add_port() method calls directly
ovs-vsctl which implies inconsistencies: ovs_lib calls ovs-vsctl with a timeout but not OVSInterfaceDriver._ovs_add_port().
** Affects: neutron
Importance: Undecided
Assignee: Cedric Brandily (cbrandily)
Status: In Progress
** Tags: ovs
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1396489
Title:
OVSInterfaceDriver should use ovs_lib not call ovs-vsctl directly
Status in OpenStack Neutron (virtual network service):
In Progress
Bug description:
ovs_lib module is responsible for the interaction with OVS but OVSInterfaceDriver._ovs_add_port() method calls directly
ovs-vsctl which implies inconsistencies: ovs_lib calls ovs-vsctl with a timeout but not OVSInterfaceDriver._ovs_add_port().
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1396489/+subscriptions
Follow ups
References