yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #62892
[Bug 1523614] Re: Deprecate vxlan_group option from lb_agent and retrieve configuration from type driver instead
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1523614
Title:
Deprecate vxlan_group option from lb_agent and retrieve configuration
from type driver instead
Status in neutron:
Expired
Bug description:
The vxlan group to be used with the linuxbridge agent can be configured via the linuxbridge agent configuration file [1].
[vxlan]
vxlan_group = 224.0.0.1
However there is a similar option in the vxlan type driver [2]
[ml2_type_vxlan]
vxlan_group = <None>
The linuxbridge agent configuration should be deprecated (be careful
about backwardscompatibility) and the type driver option to e used
instead. Therefore the linuxbridge agent should make an rpc call to
the plugin to retrieve this kind of information. This way the
configuration is stored once in the server, and not multiple times
distributed over all linuxbridge nodes (which is error prone). More
details see the discussion on patchset [3]
[1] http://docs.openstack.org/liberty/config-reference/content/networking-plugin-linuxbridge_agent.html
[2] http://docs.openstack.org/liberty/config-reference/content/networking-plugin-ml2_vxlan.html
[3] https://review.openstack.org/#/c/268153/
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1523614/+subscriptions
References