Set veth_mtu default to 9000
Unfortunately we may have to continue to support veth connections in the OVS agent for QoS use-cases. Related discussion: https://bugs.launchpad.net/bugs/1550501 For the particular veth connections that reference the 'veth_mtu' setting, they are constructed long before we know the MTUs of the networks that will be going over them. So this patch changes their default to be 9000 to try to ensure they won't be silently dropping frames in jumbo MTU deployments. Change-Id: I6859ebdde1f7e3a8163b49d705620e522ada606a Related-bug: #1542475
This commit is contained in:
parent
b9ef98b4f7
commit
2c9530c917
|
@ -110,7 +110,7 @@ agent_opts = [
|
|||
"(gre and/or vxlan).")),
|
||||
cfg.PortOpt('vxlan_udp_port', default=p_const.VXLAN_UDP_PORT,
|
||||
help=_("The UDP port to use for VXLAN tunnels.")),
|
||||
cfg.IntOpt('veth_mtu',
|
||||
cfg.IntOpt('veth_mtu', default=9000,
|
||||
help=_("MTU size of veth interfaces")),
|
||||
cfg.BoolOpt('l2_population', default=False,
|
||||
help=_("Use ML2 l2population mechanism driver to learn "
|
||||
|
|
Loading…
Reference in New Issue