yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #77337
[Bug 1818693] [NEW] Make "phys_brs" parameter variable in OVSAgentExtensionAPI
Public bug reported:
In [1], a new init parameter was introduced in the class
OVSAgentExtensionAPI. This change in the extension API can break
backwards compatibility with other projects (networking_sfc and bagpipe
are affected).
Because this parameter is needed only in qos_driver extension when
calling OVSAgentExtensionAPI.request_phy_brs() (to retrieve the physical
bridges), we can make this new parameter optional not to break other
stadium projects. When the OVS it's initialized (in-tree agent), the
extension is called with the three needed parameters.
[1]
https://review.openstack.org/#/c/406841/22/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_agent_extension_api.py@43
** Affects: neutron
Importance: Undecided
Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez)
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/1818693
Title:
Make "phys_brs" parameter variable in OVSAgentExtensionAPI
Status in neutron:
In Progress
Bug description:
In [1], a new init parameter was introduced in the class
OVSAgentExtensionAPI. This change in the extension API can break
backwards compatibility with other projects (networking_sfc and
bagpipe are affected).
Because this parameter is needed only in qos_driver extension when
calling OVSAgentExtensionAPI.request_phy_brs() (to retrieve the
physical bridges), we can make this new parameter optional not to
break other stadium projects. When the OVS it's initialized (in-tree
agent), the extension is called with the three needed parameters.
[1]
https://review.openstack.org/#/c/406841/22/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_agent_extension_api.py@43
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1818693/+subscriptions
Follow ups