Deprecate advertise_mtu option

[Ihar Hrachyshka]

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.

[Doug Wiegley (dougwig)]

How do we handle deprecation requests? I'm going to pretend it's an RFE.

[Armando Migliaccio (armando-migliaccio)]

We should provide a patch that must contain a release note and have all the bells and whistles that describe what steps are needed to take (if any) when the variable is removed (in this case).

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/310448
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=4955746bbff317d5976a1130d695b928561afc00
Submitter: Jenkins
Branch: master

commit 4955746bbff317d5976a1130d695b928561afc00
Author: Ihar Hrachyshka <email address hidden>
Date: Wed Apr 27 07:43:56 2016 -0500

    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

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/neutron 9.0.0.0b1 development milestone.