From 4ad1834c50ad79fc978e7a6b0b62308246fa6258 Mon Sep 17 00:00:00 2001
From: Gabriele Cerami <gcerami@redhat.com>
Date: Fri, 4 Mar 2016 01:18:05 +0100
Subject: [PATCH] Documenting network_device_mtu in agents config files

In Mitaka, network_device_mtu is documented in the sample
config files because they are automatically generated
with oslo-config-generate. In past releases this option
is not exposed

Change-Id: Ia105863d34e0fe9f3eb618978308c2e42956be00
Closes-Bug: #1504527
---
 etc/dhcp_agent.ini | 3 +++
 etc/l3_agent.ini   | 3 +++
 2 files changed, 6 insertions(+)

diff --git a/etc/dhcp_agent.ini b/etc/dhcp_agent.ini
index 6996ed24fb4..8910a41cde7 100644
--- a/etc/dhcp_agent.ini
+++ b/etc/dhcp_agent.ini
@@ -26,6 +26,9 @@
 # Example of interface_driver option for LinuxBridge
 # interface_driver = neutron.agent.linux.interface.BridgeInterfaceDriver
 
+# MTU setting for device.
+# network_device_mtu =
+
 # The agent can use other DHCP drivers.  Dnsmasq is the simplest and requires
 # no additional setup of the DHCP server.
 # dhcp_driver = neutron.agent.linux.dhcp.Dnsmasq
diff --git a/etc/l3_agent.ini b/etc/l3_agent.ini
index b3ac40c3382..15941638d30 100644
--- a/etc/l3_agent.ini
+++ b/etc/l3_agent.ini
@@ -10,6 +10,9 @@
 # that supports L3 agent
 # interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver
 
+# MTU setting for device.
+# network_device_mtu =
+
 # Use veth for an OVS interface or not.
 # Support kernels with limited namespace support
 # (e.g. RHEL 6.5) so long as ovs_use_veth is set to True.