Reviewed: https://review.openstack.org/540077 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2a44b3fa3dd0e7f133c3503d08e1b5fecf6cbc6f Submitter: Zuul Branch: master
commit 2a44b3fa3dd0e7f133c3503d08e1b5fecf6cbc6f Author: Hongbin Lu <[email protected]> Date: Thu Feb 1 18:13:03 2018 +0000 Set mtu for VXLAN interface in linuxbridge Change-Id: I169613ecf936b4484447d1ca0ed81e4cb5369ce2 Closes-Bug: #1744101 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1744101 Title: linuxbridge: vxlan interfaces doesn't get MTU Status in neutron: Fix Released Bug description: When vxlans are created, f.ex. via ensure_vxlan in neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py - no mtu is assigned. This explains why we get vxlan interfaces with 1500 byte mtu even- though neutron has been instructed to use 9000 bytes mtu. The function called: def add_vxlan(self, name, vni, group=None, dev=None, ttl=None, tos=None, local=None, srcport=None, dstport=None, proxy=False): cmd = ['add', name, 'type', 'vxlan', 'id', vni] ... Creates the interface, and from what I understand mtu should be between 'add' and 'type'. I have been unable to find any other place where the mtu would be propagated to the vxlan interface and our tests indicate that it never happens. The problem is that this causes the bridge to set it self to the lower mtu and... noone is happy =) This is on: git describe 11.0.2-8-g7fd30cb (stable/pike) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1744101/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
