Change to set the container network MTU

Bug #1478110 reported by OpenStack Infra
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Invalid
Undecided
Unassigned
Kilo
Invalid
Undecided
RPC Documentation
Trunk
Invalid
Undecided
Unassigned

Bug Description

https://review.openstack.org/204796
commit 8cf1f44c9e9cd2304b8a1ad41282f2e993894632
Author: kevin <email address hidden>
Date: Wed Jul 22 19:06:57 2015 -0500

    Change to set the container network MTU

    This change adds the container network MTU option within the container
    network LXC config file. This will allow a deployer to set the MTU within
    a provider networks entry in openstack_user_config.yml.

    Example:

      ....
      provider_networks:
        - network:
            container_bridge: "br-storage"
            container_type: "veth"
            container_interface: "eth2"
            ip_from_q: "storage"
            type: "raw"
            container_mtu: "9000"
            group_binds:
              - glance_api
              - cinder_api
              - cinder_volume
              - nova_compute
              - swift_proxy

    This changes gives the deployer the ability to selectively set the mtu as
    needed.

    The dynamic_inventory.py script has been updated to allow for the MTU entry.

    Example file documentation has been added to show how to use this new setting.

    BackportPotential
    DocImpact
    Closes-Bug: #1477346

    Change-Id: If8c0ee042d2f1322f8322ea6c8ee33606070d880

Revision history for this message
Karin Levenstein (karin-levenstein) wrote :

This bug can be closed. The only documentation change required is to add an inline annotation to the example config file, and that was already done.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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