openstack/neutron
Code Issues Proposed changes

Deprecate network_device_mtu

Browse Source 
All interface plugging MTUs should be calculated based on the
MTU of the network object that the port is being created on.

Partial-Bug: #1542108
Partial-Bug: #1542475

Change-Id: Idf6221fee2c7da86123b330ad3c235ecc6868242
This commit is contained in:
Kevin Benton 2016-02-22 16:56:02 -08:00
parent e3210bc880
commit 12ef585f91
2 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
neutron/agent/linux/interface.py
View File

@ -42,7 +42,11 @@ OPTS = [
'(e.g. RHEL 6.5) so long as ovs_use_veth is set to ' '(e.g. RHEL 6.5) so long as ovs_use_veth is set to '
'True.')), 'True.')),
cfg.IntOpt('network_device_mtu', cfg.IntOpt('network_device_mtu',
help=_('MTU setting for device.')), deprecated_for_removal=True,
help=_('MTU setting for device. This option will be removed in '
'Newton. Please use the system-wide segment_mtu setting '
'which the agents will take into account when wiring '
'VIFs.')),
] ]

6
releasenotes/notes/deprecate-network-device-mtu-59b78264c9974808.yaml Normal file
View File

@ -0,0 +1,6 @@
---
deprecations:
- The 'network_device_mtu' option is deprecated and will
be removed in the 'Newton' cycle. Please use the
system-wide segment_mtu setting which the agents will
take into account when wiring VIFs.