neutron: don't set external_network_bridge option by default
authorIhar Hrachyshka <ihrachys@redhat.com>
Tue, 6 Dec 2016 22:24:30 +0000 (22:24 +0000)
committerEmilien Macchi <emilien@redhat.com>
Thu, 23 Feb 2017 14:46:39 +0000 (14:46 +0000)
commitfd3ac00879b4456564711c6599f5542602641b33
tree40bd1b5250109d3ab492e824389f4b1447504047
parentdfa98bc2e8e71d80d54abc92a91a980bc1ffd5cf
neutron: don't set external_network_bridge option by default

It's deprecated, to be removed in Ocata, and it's discouraged to set it
to anything but the default value ('') that means that routers are not
plugged directly into br-ex, but allows l2 agent to do the wiring.

There are known issues with setting it to br-ex (like wrong port
statuses): If533cf7c4c379be78f5a15073accaff7f65973ab

The only caveat to setting it to the default ('') value is that in that
case l2 agent should be configured with bridge mapping for physical
networks. Since we already configure bridge_mappings for the agent, we
should be safe to unset the option.

Now that it's the default, there is no reason to override it in example
environments.

This patch also changes the description for the parameter to make it
more clear that users are not expected to set it unless they know what
they are doing. Also, moved the parameter into deprecated section to
make it even more clear it's not something to touch in new deployments.

Change-Id: Iade7fbaf92c8c601227f4456a15ea3f13a907ee2
Related-Bug: #1563070
(cherry picked from commit 21d2afd4bf9f57fd0fb3709d87acb452f13912df)
environments/net-bond-with-vlans-no-external.yaml
environments/net-bond-with-vlans-v6.yaml
environments/net-bond-with-vlans.yaml
environments/net-single-nic-linux-bridge-with-vlans.yaml
environments/net-single-nic-with-vlans-no-external.yaml
environments/net-single-nic-with-vlans-v6.yaml
environments/net-single-nic-with-vlans.yaml
environments/network-environment.yaml
puppet/services/neutron-l3-compute-dvr.yaml
puppet/services/neutron-l3.yaml