Deprecate advertise_mtu option
Now that we advertise MTU via DHCP and RA by default, there is no reason to keep the option available for configuration. Other agents/plugins are also encouraged to advertise MTU values to instances by their own means. DocImpact: mark the advertise_mtu option as deprecated as of Newton. Closes-Bug: 1576000 Change-Id: Ibf7d60dfc57bec090f16d909c050c09e7cfd9352
This commit is contained in:
parent
b047e3c28a
commit
4955746bbf
@ -154,6 +154,7 @@ core_opts = [
|
||||
help=_('Number of seconds between sending events to nova if '
|
||||
'there are any events to send.')),
|
||||
cfg.BoolOpt('advertise_mtu', default=True,
|
||||
deprecated_for_removal=True,
|
||||
help=_('If True, advertise network MTU values if core plugin '
|
||||
'calculates them. MTU is advertised to running '
|
||||
'instances via DHCP and RA MTU options.')),
|
||||
|
@ -0,0 +1,10 @@
|
||||
---
|
||||
deprecations:
|
||||
- The 'advertise_mtu' option is deprecated and will be removed in Ocata.
|
||||
There should be no use case to disable the feature, hence the option is
|
||||
considered redundant. DHCP and L3 agents will continue advertising MTU
|
||||
values to instances. Other plugins not using those agents are also
|
||||
encouraged to advertise MTU to instances. The actual implementation of MTU
|
||||
advertisement depends on the plugin in use, but it's assumed that at least
|
||||
DHCP option for IPv4 clients and Router Advertisements for IPv6 clients is
|
||||
supported.
|
Loading…
Reference in New Issue
Block a user