[ml2]/physical_network_mtus needs to be added in neutron-api charm

[Amad Ali]

Neutron has an option from Mitaka, to set different MTU for physnets.

[ml2]
physical_network_mtus =
#(List) A list of mappings of physical networks to MTU values. The format of the mapping is <physnet>:<mtu val>. This mapping allows specifying a physical network MTU value that differs from the default global_physnet_mtu value.

This however, is not a configurable parameter in the neutron-api charm today.

Can this be added?

[Amad Ali (amad)]

http://docs.openstack.org/mitaka/config-reference/networking/networking_options_reference.html

[Amad Ali (amad)]

Basic support for "global_physnet_mtu" and "path_mtu" options was recently added in [1]
However support for "physical_network_mtus" is still missing.

[1] https://bugs.launchpad.net/charms/+source/neutron-api/+bug/1650579

[Alvaro Uria (aluria)]

Are there plans to fix this bug in the next release? Thank you!

[Frode Nordahl (fnordahl)]

Review: https://review.openstack.org/#/c/539864/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/539864
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-api/commit/?id=08e806f09876f93e3453083124cc82afa7d7df58
Submitter: Zuul
Branch: master

commit 08e806f09876f93e3453083124cc82afa7d7df58
Author: Frode Nordahl <email address hidden>
Date: Thu Feb 1 09:47:47 2018 +0100

    Add support for configuring individual physical network MTUs

    This is needed if a subset of your flat or VLAN provider networks have a MTU
    that differ with what is set in global-physnet-mtu.

    Change-Id: Ifd348311b5c313fa95d6ed49c32d9b26b0f5e662
    Closes-Bug: #1663533