expose the ability to set the mtu for container networks

Bug #1477346 reported by Kevin Carter
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
Wishlist
Kevin Carter
Kilo
Fix Released
Wishlist
Kevin Carter
Trunk
Fix Released
Wishlist
Kevin Carter

Bug Description

Container networks should have the ability to allow the MTU to be set. This can be exposed within the https://github.com/stackforge/os-ansible-deployment/blob/master/playbooks/roles/lxc_container_create/templates/container-interface.ini.j2 template if the `item.value.mtu` value is set.

Example syntax add:

{% if item.value.mtu is defined %}
lxc.network.mtu = {{ item.value.mtu }}
{% endif %}

This will give a deployer the ability to select and set the MTU for a given interface type which would be useful in L3 and storage network scenarios.

Tags: in-kilo
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-ansible-deployment (master)

Fix proposed to branch: master
Review: https://review.openstack.org/204796

Changed in openstack-ansible:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-ansible-deployment (kilo)

Fix proposed to branch: kilo
Review: https://review.openstack.org/205618

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-ansible-deployment (master)

Reviewed: https://review.openstack.org/204796
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=8cf1f44c9e9cd2304b8a1ad41282f2e993894632
Submitter: Jenkins
Branch: master

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

Changed in openstack-ansible:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-ansible-deployment (kilo)

Reviewed: https://review.openstack.org/205618
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=0f888d12ed5d878ee4893bca4d4bd94c292cbcb2
Submitter: Jenkins
Branch: kilo

commit 0f888d12ed5d878ee4893bca4d4bd94c292cbcb2
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
    (cherry picked from commit 8cf1f44c9e9cd2304b8a1ad41282f2e993894632)

tags: added: in-kilo
Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.11

This issue was fixed in the openstack/openstack-ansible 11.2.11 release.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/openstack-ansible 11.2.12

This issue was fixed in the openstack/openstack-ansible 11.2.12 release.

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.14

This issue was fixed in the openstack/openstack-ansible 11.2.14 release.

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.