yahoo-eng-team team mailing list archive

[OpenStack Infra <1552089@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/302165
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=54fbf82ff38d76ba132c976d8502a134b521d393
Submitter: Jenkins
Branch:    master

commit 54fbf82ff38d76ba132c976d8502a134b521d393
Author: Ihar Hrachyshka <ihrachys@xxxxxxxxxx>
Date:   Wed Apr 6 12:34:16 2016 +0200

    networking-guide: document MTU configuration
    
    Also cleaned up obsolete suggestions to use Jumbo for optimal
    performance for tunnelled tenant networks, as well as dnsmasq specific
    hacks to advertise MTU to instances.
    
    Change-Id: I439806c506a5e0d80eeb4895038fca087e74edd4
    Closes-Bug: #1552089
    Closes-Bug: #1454328


** Changed in: openstack-manuals
       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/1552089

Title:
      Make agent interface plugging utilize network MTU

Status in neutron:
  Invalid
Status in openstack-manuals:
  Fix Released

Bug description:
  https://review.openstack.org/283790
  Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

  commit 4df8d9a7016ab20fce235833d792b89309ec98a7
  Author: Kevin Benton <kevin@xxxxxxxxxx>
  Date:   Mon Feb 22 16:41:45 2016 -0800

      Make agent interface plugging utilize network MTU
      
      This changes the 'plug' and 'plug_new' interfaces of the
      LinuxInterfaceDriver to accept an MTU argument. It then
      updates the dhcp agent and l3 agent to pass the MTU that
      is set on the network that the port belongs to. This allows
      it to take into account the overhead calculations that are
      done for encapsulation types.
      
      It's necessary for the L3 agent to have the MTU because it
      must recognize when fragmentation is needed so it can fragment
      or generate an ICMP error.
      
      It's necessary for the DHCP agent to have the MTU so it doesn't
      interfere when it plugs into a bridge with a larger than 1500
      MTU (the bridge would reduce its MTU to match the agent).
      
      If an operator sets 'network_device_mtu', the value of that
      will be used instead to preserve previous behavior.
      
      Closes-Bug: #1549470
      Closes-Bug: #1542108
      Closes-Bug: #1542475
      DocImpact: Neutron agents now support arbitrary MTU
                 configurations on each network (including
                 jumbo frames). This is accomplished by checking
                 the MTU value defined for each network on which
                 it is wiring VIFs.
      Co-Authored-By: Matt Kassawara <mkassawara@xxxxxxxxx>
      Change-Id: Ic091fa78dfd133179c71cbc847bf955a06cb248a

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