Fixed help messages for path_mtu and global_physnet_mtus options

Giving better recommendations for meaningful values.

Change-Id: Iea4a343465f06ba19fc8e504fc0ca329a718a8c5
Related-Bug: #1566706
This commit is contained in:
Andreas Scheuring 2016-06-15 09:08:30 +02:00
parent b3e6bc950b
commit f9d5064c22
2 changed files with 7 additions and 12 deletions

View File

@ -186,13 +186,10 @@ core_opts = [
'this value without modification. For overlay networks '
'such as VXLAN, neutron automatically subtracts the '
'overlay protocol overhead from this value. Defaults '
'to 1500, the standard value for Ethernet. Also '
'consider setting the path_mtu ml2 configuration value '
'to the global_physnet_mtu value when using the ml2 '
'plug-in. Otherwise the global_physnet_mtu '
'value might get overridden by a smaller path_mtu value '
'and hence have no effect on overlay/tunnel networks '
'but only flat and VLAN networks.'))
'to 1500, the standard value for Ethernet. If using the '
'ML2 plug-in with overlay/tunnel networks, also '
'configure the ml2 path_mtu option with the same value '
'as the global_physnet_mtu option.'))
]
core_cli_opts = [

View File

@ -43,11 +43,9 @@ ml2_opts = [
cfg.IntOpt('path_mtu', default=constants.DEFAULT_NETWORK_MTU,
help=_('Maximum size of an IP packet (MTU) that can traverse '
'the underlying physical network infrastructure without '
'fragmentation when using an overlay/tunnel protocol. '
'Either set this to the same value as the '
'global_physnet_mtu value or use it to explicitly '
'specify a physical network MTU value that differs from '
'the default global_physnet_mtu value.')),
'fragmentation for overlay/tunnel networks. In most '
'cases, use the same value as the global_physnet_mtu '
'option.')),
cfg.ListOpt('physical_network_mtus',
default=[],
help=_("A list of mappings of physical networks to MTU "