yahoo-eng-team team mailing list archive

[OpenStack Infra <1549408@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/283847
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=69ec718b62db5766e43552cadfc7b659c7025ba4
Submitter: Jenkins
Branch:    master

commit 69ec718b62db5766e43552cadfc7b659c7025ba4
Author: Kevin Benton <kevin@xxxxxxxxxx>
Date:   Mon Feb 22 18:35:48 2016 -0800

    Use MTU value from Neutron in OVS/LB VIF wiring
    
    This patch adds the MTU attached to a Neutron network to
    the network model so the VIF plugging code can reference
    the MTU and set the correct value for the Neutron network
    it is attaching to.
    
    Closes-Bug: #1549408
    Change-Id: Ibd4de83e1af193eb2dcd997e6528d2fccaa2979a


** Changed in: nova
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1549408

Title:
  nova doesn't use Neutron MTUs when wiring up VIFs

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) liberty series:
  New

Bug description:
  Neutron Network objects can have an 'MTU' field that specifies the MTU
  that should be defined on all interfaces attached to that network.
  However, Nova currently doesn't do anything with that information when
  wiring up the Linux bridge and OVS ports. It only references the
  network_device_mtu config option which is deprecated and doesn't take
  into account the overhead of various encapsulation protocols.

  So if network_device_mtu is not specified or is smaller than the MTU
  of a Neutron network with jumbo frames, large packets from a VM will
  silently be dropped on the Linux bridge due to the mismatch of MTUs
  between the devices Nova has wired up and Neutron.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1549408/+subscriptions