os-vif does not current respect the neutron provided mtu, it just uses
the configuration inside os-vif. This is a big regression from mitaka
and liberty.
Long term, this is something os-vif will be able to do by correctly
parsing and acting on the network info. For now we just set the mtu for
a second time once os-vif has done what it wants to do.
Reviewed: https:/ /review. openstack. org/370681 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=77f546623bb 6c0b2a4441940f1 740abd45bd3352
Committed: https:/
Submitter: Jenkins
Branch: master
commit 77f546623bb6c0b 2a4441940f1740a bd45bd3352
Author: John Garbutt <email address hidden>
Date: Thu Sep 15 11:29:45 2016 +0100
Override MTU for os_vif attachments
os-vif does not current respect the neutron provided mtu, it just uses
the configuration inside os-vif. This is a big regression from mitaka
and liberty.
Long term, this is something os-vif will be able to do by correctly
parsing and acting on the network info. For now we just set the mtu for
a second time once os-vif has done what it wants to do.
Closes-Bug: #1623876
Change-Id: Id4ca38fa1bb84f 8cdb5edcd9ccb7a cd8c8e9b60c