openstack
/
neutron
Code Issues Proposed changes

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
This commit is contained in:
Gabriele Cerami 2016-03-04 01:18:05 +01:00
parent 7a03db00f7
commit 4ad1834c50
2 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
etc/dhcp_agent.ini
View File

@ -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

3
etc/l3_agent.ini
View File

@ -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.