Deprecate vxlan_group option from lb_agent and retrieve configuration from type driver instead

[Matt Kassawara]

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/

[Sean M. Collins (scollins)]

Not sure what you mean by unused:

http://paste.openstack.org/show/481060/

[Matt Kassawara (ionosphere80)]

The Linux bridge agent uses [vxlan] vxlan_group in the linuxbridge_agent.ini file.

[Sean M. Collins (scollins)]

So I guess, what is the actual difference between vxlan_group in the ml2 mech driver, versus the vxlan_group option in the LB agent. Are they meant to be the same thing? For instance, is vxlan_group supposed to be stored on the neutron-server and the agents pick it up from the server, and the LB agent is not pulling it correctly and is instead pulling it from a local config option?

[Matt Kassawara (ionosphere80)]

I'm not sure how many mechanisms can use VXLAN in multicast mode, but if it's more than Linux bridge, perhaps those agents should use the ML2 option rather than a local option.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Kevin Benton (<email address hidden>) on branch: master
Review: https://review.openstack.org/254318
Reason: abandoning for now under the assumption that this option will be used to eventually deprecate the agent-side one

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/268153

[OpenStack Infra (hudson-openstack)]

Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/268153
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

[Armando Migliaccio (armando-migliaccio)]

If you are still working on this please resume, or allow someone else to pick this up.

[Armando Migliaccio (armando-migliaccio)]

This bug is > 180 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

[Launchpad Janitor (janitor)]

[Expired for neutron because there has been no activity for 60 days.]