Bug 1250041

Summary:	[RFE] Backport MTU advertisement to OSP 6
Product:	Red Hat OpenStack	Reporter:	Eduard Barrera <ebarrera>
Component:	openstack-neutron	Assignee:	lpeer <lpeer>
Status:	CLOSED WONTFIX	QA Contact:	Ofer Blaut <oblaut>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5.0 (RHEL 7)	CC:	amuller, chrisw, dcadzow, nyechiel, tfreger, yeylon
Target Milestone:	---	Keywords:	FeatureBackport, FutureFeature
Target Release:	8.0 (Liberty)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-09-24 10:44:44 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Eduard Barrera 2015-08-04 12:07:39 UTC

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.

http://specs.openstack.org/openstack/neutron-specs/specs/kilo/mtu-selection-and-advertisement.html


Can we have it backported from Kilo to OSP 6?

Comment 5 Assaf Muller 2015-08-05 12:39:28 UTC

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.

Comment 6 Nir Yechiel 2015-09-24 10:44:44 UTC

Closing this request based on feedback from engineering as described in comment #5 above.