[openstack-dev] [Neutron] MTU configuration pain
Sean M. Collins
sean at coreitpro.com
Fri Jan 15 17:41:45 UTC 2016
MTU has been an ongoing issue in Neutron for _years_.
It's such a hassle, that most people just throw up their hands and set
their physical infrastructure to jumbo frames. We even document it.
> Ideally, you can prevent these problems by enabling jumbo frames on
> the physical network that contains your tenant virtual networks. Jumbo
> frames support MTUs up to approximately 9000 bytes which negates the
> impact of GRE overhead on virtual networks.
We've pushed this onto operators and deployers. There's a lot of
code in provisioning projects to handle MTUs.
We have mentions to it in our architecture design guide
I want to get Neutron to the point where it starts discovering this
information and automatically configuring, in the optimistic cases. I
understand that it can be complex and have corner cases, but the issue
we have today is that it is broken in some multinode jobs, even Neutron
developers are configuring it correctly.
I also had this discussion on the DevStack side in https://review.openstack.org/#/c/112523/
where basically, sure we can fix it in DevStack and at the gate, but it
doesn't fix the problem for anyone who isn't using DevStack to deploy
Today we have a ton of MTU configuration options sprinkled throghout the
L3 agent, dhcp agent, l2 agents, and at least one API extension to the
REST API for handling MTUs.
So yeah, a lot of knobs and not a lot of documentation on how to make
this thing work correctly. I'd like to try and simplify.
Sean M. Collins
More information about the OpenStack-dev