[Bug 1674307] Re: Neutron v9 jumbo frames support

2017-06-09 Thread Launchpad Bug Tracker
[Expired for neutron (Ubuntu) because there has been no activity for 60 days.] ** Changed in: neutron (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1674307] Re: Neutron v9 jumbo frames support

2017-04-10 Thread James Page
FTR out br-tun MTU is also 1500 so I don't think that actually matters. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674307 Title: Neutron v9 jumbo frames support To manage notifications about

[Bug 1674307] Re: Neutron v9 jumbo frames support

2017-04-10 Thread James Page
I've just redeployed a cloud onto Xenial/Ocata in a similar configuration; the instances running on the cloud all get the higher MTU as configured by neutron, irrespective of the MTU on the tunnel bridge. I've confirmed this using iperf to assess performance between units including mismatched MTU

[Bug 1674307] Re: Neutron v9 jumbo frames support

2017-04-10 Thread James Page
For reference: http://paste.ubuntu.com/24354849/ The only diff I can see is that br-int's MTU is 1450 in the original bug report - that looks wrong compared to our install: 24: br-int: mtu 8958 qdisc noop state DOWN mode DEFAULT group default qlen 1 ** Changed in: neutron