yahoo-eng-team team mailing list archive

[Mark Doffman <mjdoffma@xxxxxxxxxx>]

https://blueprints.launchpad.net/neutron/+spec/mtu-selection-and-
advertisement

Blueprint for Neutron goes in to detail about how instances should get
the correct MTU value (Via DHCP or otherwise). If the MTU value is not
supplied for Neutron then the instance has no way of determining what
the correct MTU will be. The instance will use the default linux value,
which may or may not be correct. Setting to 1500 is not safe, and is no
better than using whatever the default linux value is.

Probably not a nova bug. MTU value should be broadcast by neutron if
having issues.

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

-- 
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/1496085

Title:
  network_data.json links can have None as MTU

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  If a Neutron network does not have an MTU set, the MTU for the links
  in network_data.json will be set to None. The spec seems to indicate
  all links will have an MTU. Either we should drop the key from the
  link if MTU isn't set, or set it to a safe default value like 1500.

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