yahoo-eng-team team mailing list archive

[yatin <1542503@xxxxxxxxxxxxxxxxxx>]

ML2/OVN properly consider overlay header and set network mtu, so closing
as not a bug, If you see some case is missed and see it in master or any
stable release feel free to reopen.

** Changed in: neutron
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1542503

Title:
  [OVN] Lacking mechanism to provide proper MTU to instances

Status in neutron:
  Invalid

Bug description:
  Virtual networks using an overlay protocol such as GENEVE include
  overhead that reduces the effective MTU for an instance. By default,
  network interfaces in an instance use a 1500 MTU. If the physical
  network also uses a 1500 MTU, an instance cannot send a packet using a
  1500 MTU due to overlay protocol overhead. Neutron offers a net-mtu
  extension that provides a field indicating MTU for a particular
  network. In the ML2 plug-in, this value accounts for the amount of
  overhead via type driver. The DHCP agent can provide this value to
  instances. The OVN plug-in needs a mechanism for indicating a proper
  MTU value that accounts for any overlay protocol overhead. Similar to
  ML2, the conventional DHCP agent can provide this value, but OVN also
  needs to consider the implications with a native DHCP agent.

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