openstack/devstack
Code Issues Proposed changes

Document using Q_ML2_PLUGIN_PATH_MTU

Browse Source 
I tested it, and it works!

Change-Id: Ic345ededc37b2e0b7b5dbeb397aa55540d5c3bd8
Related-Bug: #1527675
This commit is contained in:
Mike Spreitzer
2016-01-26 14:06:17 -05:00
parent ffb96b85d3
commit 4baa4ce2b3
1 changed files with 13 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
doc/source/guides/neutron.rst
View File

@@ -23,7 +23,9 @@ Physical Network Setup
In most cases where DevStack is being deployed with a single In most cases where DevStack is being deployed with a single
interface, there is a hardware router that is being used for external interface, there is a hardware router that is being used for external
connectivity and DHCP. The developer machine is connected to this connectivity and DHCP. The developer machine is connected to this
network and is on a shared subnet with other machines. network and is on a shared subnet with other machines. The
`local.conf` exhibited here assumes that 1500 is a reasonable MTU to
use on that network.
.. nwdiag:: .. nwdiag::
@@ -434,6 +436,16 @@ bridge, to forward traffic sent by guest VMs.
Miscellaneous Tips Miscellaneous Tips
================== ==================
Non-Standard MTU on the Physical Network
----------------------------------------
DevStack defaults to assume that the MTU on the physical network
is 1500. A different MTU can be specified by adding the following to
the `localrc` part of `local.conf` on each machine.
::
Q_ML2_PLUGIN_PATH_MTU=1500
Disabling Next Generation Firewall Tools Disabling Next Generation Firewall Tools
---------------------------------------- ----------------------------------------