Red Hat Bugzilla – Bug 1250041
[RFE] Backport MTU advertisement to OSP 6
Last modified: 2016-04-26 13:18:41 EDT
Description of problem:
MTU advertisement functionality
This new feature allow specification of the desired MTU for a network, and advertisement of the MTU to guest operating systems when it is set. This new capability will avoid MTU mismatches in networks that lead to undesirable results such as connectivity issues, packet drops and degraded network performance.
Can we have it backported from Kilo to OSP 6?
I looked in to this: The patches include API, DB and configuration file changes, all criteria that block backports. It's not possible to backport this feature according to our policy.
Aside from that, keep in mind that only phases 1 and 2 of the spec were merged: The MTU of a network is discovered from the agent configurations, exposed via the API and advertised via DHCP to the guest. The user/admin cannot select a network's API, and the different Neutron devices MTUs are still not configured automatically.
Closing this request based on feedback from engineering as described in comment #5 above.