neutron-api charm has outdated MTU settings

Bug #1650579 reported by Tytus Kurek
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
OpenStack Neutron API Charm
Fix Released
High
Unassigned
neutron-api (Juju Charms Collection)
Invalid
High
Unassigned

Bug Description

It looks like neutron-api charm has outdated MTU settings. Currently MTU can be adjusted using the "network-device-mtu" option which configures the following settings:

- "network_device_mtu", however this options is deprecated in Mitaka and does not exist in Newton at all [1-2]
- "veth_mtu", however this option is now set to 9000 by default in Mitaka and Newton [1-2]

It also looks like MTU adjustment has changed significantly in Mitaka [3]. The neutron-api charm is missing options to configure "global_physnet_mtu", "path_mtu" and "physical_network_mtus" settings.

I've just performed the following tests:

TEST 1:

- I deployed OpenStack Mitaka on Trusty with "network-device-mtu" option set to 9000 and "instance-mtu" option of neutron-gateway charm set to 8900
- I launched two instances on different compute nodes
- I observed fragmentation of traffic flowing between instances

TEST 2:

- I deployed OpenStack Mitaka on Trusty without "network-device-mtu" option set and "instance-mtu" option of neutron-gateway charm set to 8900
- I patched neutron-api charm with "global_physnet_mtu" and "path_mtu" options set to 9000
- I launched two instances on different compute nodes
- I observed no fragmentation of traffic flowing between instances

References:

[1] http://docs.openstack.org/mitaka/config-reference/networking/networking_options_reference.html
[2] http://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html
[3] http://docs.openstack.org/mitaka/networking-guide/config-mtu.html

Revision history for this message
Tytus Kurek (tkurek) wrote :
Revision history for this message
Corey Bryant (corey.bryant) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-neutron-api (master)

Reviewed: https://review.openstack.org/411913
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-api/commit/?id=491e501b062a35722ac8eaa0cc9ef317fd556583
Submitter: Jenkins
Branch: master

commit 491e501b062a35722ac8eaa0cc9ef317fd556583
Author: Tytus Kurek <email address hidden>
Date: Fri Dec 16 17:45:11 2016 +0100

    Add basic support for "global_physnet_mtu" and "path_mtu" options.

    I've added basic support for "global_physnet_mtu" and "path_mtu"
    options by allowing to configure them via charm parameters.

    Change-Id: Ia95533418ccd4b7d1b96270633193ea34b1edecb
    Partial-Bug: 1650579

James Page (james-page)
Changed in neutron-api (Juju Charms Collection):
status: New → Triaged
importance: Undecided → High
milestone: none → 16.10
status: Triaged → Fix Committed
milestone: 16.10 → 17.01
James Page (james-page)
Changed in charm-neutron-api:
importance: Undecided → High
status: New → Fix Committed
Changed in neutron-api (Juju Charms Collection):
status: Fix Committed → Invalid
James Page (james-page)
Changed in charm-neutron-api:
milestone: none → 17.02
James Page (james-page)
Changed in charm-neutron-api:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.