Browse code

Document using Q_ML2_PLUGIN_PATH_MTU

I tested it, and it works!

Change-Id: Ic345ededc37b2e0b7b5dbeb397aa55540d5c3bd8
Related-Bug: #1527675

Mike Spreitzer authored on 2016/01/27 04:06:17
Showing 1 changed files
... ...
@@ -23,7 +23,9 @@ Physical Network Setup
23 23
 In most cases where DevStack is being deployed with a single
24 24
 interface, there is a hardware router that is being used for external
25 25
 connectivity and DHCP. The developer machine is connected to this
26
-network and is on a shared subnet with other machines.
26
+network and is on a shared subnet with other machines.  The
27
+`local.conf` exhibited here assumes that 1500 is a reasonable MTU to
28
+use on that network.
27 29
 
28 30
 .. nwdiag::
29 31
 
... ...
@@ -434,6 +436,16 @@ bridge, to forward traffic sent by guest VMs.
434 434
 Miscellaneous Tips
435 435
 ==================
436 436
 
437
+Non-Standard MTU on the Physical Network
438
+----------------------------------------
439
+
440
+DevStack defaults to assume that the MTU on the physical network
441
+is 1500.  A different MTU can be specified by adding the following to
442
+the `localrc` part of `local.conf` on each machine.
443
+
444
+::
445
+    Q_ML2_PLUGIN_PATH_MTU=1500
446
+
437 447
 
438 448
 Disabling Next Generation Firewall Tools
439 449
 ----------------------------------------