Bug 1398719

Summary:	NeutronExternalNetworkBridge must be removed from documentation
Product:	Red Hat OpenStack	Reporter:	Ricardo Noriega <rnoriega>
Component:	documentation	Assignee:	Dan Macpherson <dmacpher>
Status:	CLOSED CURRENTRELEASE	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	10.0 (Newton)	CC:	dmacpher, dsneddon, srevivo
Target Milestone:	---	Keywords:	Documentation
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-17 06:26:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Ricardo Noriega 2016-11-25 16:43:19 UTC

Description of problem:

In documentation appears the following parameter is deprecated:

NeutronExternalNetworkBridge

As it was used before, if it's configured this way:

NeutronExternalNetworkBridge: "br-ex"

It will break floating IPs in case of VLAN based public networks getting the tag into the qrouter namespace.


Version-Release number of selected component (if applicable):

OSP10-beta


How reproducible:

Add this parameter in the network-environment.yaml template:

NeutronExternalNetworkBridge: "br-ex"

Commenting external_network_bridge =br-ex in /etc/neutron/l3_agent.ini and restarting the service, it will fix the issue.

Expected result:

Remove this parameter from Documentation.

Comment 1 Dan Macpherson 2016-12-09 05:41:57 UTC

@dsneddon: Can you confirm whether NeutronExternalNetworkBridge has been deprecated? If so, do you know which version of OSP it was deprecated?

Comment 2 Dan Sneddon 2016-12-09 22:45:31 UTC

(In reply to Dan Macpherson from comment #1)
> @dsneddon: Can you confirm whether NeutronExternalNetworkBridge has been
> deprecated? If so, do you know which version of OSP it was deprecated?

As far as I know, NeutronExternalNetworkBridge is still valid, but it should now always be set to "''" (single quotes inside double quotes). This causes Neutron to set up patches between br-int and any network bridges. The old (deprecated) behavior allowed setting "br-ex" to use br-ex directly without internal patches to br-ex. We used to recommend that operators could use "br-ex" if they had only one external bridge and used it on the native VLAN, on the theory that it might reduce CPU usage slightly. The truth is, OVS is efficient enough now that the difference is probably undetectable, and using internal patches is more flexible.

Anywhere we have "br-ex" in comments or examples, we should change it to "''".

Comment 3 Dan Macpherson 2016-12-10 15:04:19 UTC

Gotcha. Just remove references to:

NeutronExternalNetworkBridge: "br-ex"

But leave: 

NeutronExternalNetworkBridge: "''"

Comment 5 Dan Macpherson 2017-01-17 06:26:10 UTC

This hsould now be live for the OSP10 release. Closing this BZ.