As I recall, network_device_mtu sets up the MTU on a bunch of structures independently of whatever the correct value is. It was a bit of a workaround back in the day and is still a bit of a workaround now. I'd sooner we actually fix up the new mechanism (which is kind of hard to do when the closest I have to information is 'it probably doesn't work').
On 26 January 2016 at 09:59, Sean M. Collins <s...@coreitpro.com> wrote: > On Mon, Jan 25, 2016 at 08:16:03PM EST, Fox, Kevin M wrote: > > Another place to look... > > I've had to use network_device_mtu=9000 in nova's config as well to get > mtu's working smoothly. > > > > I'll have to read the code on the Nova side and familiarize myself, but > this sounds like a case of DRY that needs to be done. We should just set > it once *somewhere* and then communicate it to related OpenStack > components. > -- > Sean M. Collins > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
