neutron.conf mtu parameter needed

Patch under review:
https://review.openstack.org/#/c/99928/

Change abandoned by Mark T. Voelker (<email address hidden>) on branch: master
Review: https://review.openstack.org/99928
Reason: Already present in the neutron::agents::l3 class.

This actually already available via the neutron::agents::l3 class in Icehouse and master:

https://github.com/stackforge/puppet-neutron/blob/master/manifests/agents/l3.pp#L70-L72

https://github.com/stackforge/puppet-neutron/blob/stable/icehouse/manifests/agents/l3.pp#L70-L72

Hmm. This is interesting for sure. But it’s not an L3 feature. It does certainly get applied to the l3_agent.ini config file, but it’s if nothing else more appropriate for L2. I have a use case where no L3_agent will be created, so even here this parameter will not be applied.

Robert

On Jun 13, 2014, at 7:19 AM, Mark T. Voelker <email address hidden> wrote:

> This actually already available via the neutron::agents::l3 class in
> Icehouse and master:
>
> https://github.com/stackforge/puppet-
> neutron/blob/master/manifests/agents/l3.pp#L70-L72
>
> https://github.com/stackforge/puppet-
> neutron/blob/stable/icehouse/manifests/agents/l3.pp#L70-L72
>
> ** Changed in: puppet-neutron
> Status: In Progress => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1329643
>
> Title:
> neutron.conf mtu parameter needed
>
> Status in Puppet module for Neutron:
> Invalid
>
> Bug description:
> http://lists.openstack.org/pipermail/openstack-
> dev/2013-October/017033.html
>
> https://bugs.launchpad.net/openstack-manuals/+bug/1242534
>
> Specifically allow the passing of a parameter to network_device_mtu.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/puppet-neutron/+bug/1329643/+subscriptions

The question would be which of the L3 agent and the plugin agent read it. It's possible it's both, in which case it may need to appear in both places. It's highly unlikely to be the L3 agent alone, because the bridge or switch created, and I believe also the tap interfaces to VMs, need to have it applied.

Change posted: https://review.openstack.org/#/c/100041/

Reviewed: https://review.openstack.org/100041
Committed: https://git.openstack.org/cgit/stackforge/puppet-neutron/commit/?id=2da560c8835938f0b7ce2aa68460f6ba1c008f2b
Submitter: Jenkins
Branch: master

commit 2da560c8835938f0b7ce2aa68460f6ba1c008f2b
Author: Robert Starmer <email address hidden>
Date: Fri Jun 13 18:24:36 2014 -0700

    Add network_device_mtu to neutron.conf

    Already a parameter for L3_agent, but that isn't
    exactly the right configuration, due to the fact
    that this parameter is specifically a L2 feature.

    Added in neutron.conf to set the default MTU for all
    created networks. Discussion available here:

    http://lists.openstack.org/pipermail/openstack-dev/2013-October/017033.html
    https://bugs.launchpad.net/openstack-manuals/+bug/1242534

    Added test to validate parameter
    Fixed mis-spelled parameter in test
    Added deprecation warninigs to agents/l3.pp

    Closes-Bug: #1329643
    Change-Id: Id8544799855c500f0c871681695db502ab4dc87c