Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/

Bug 1227298

Summary: Packstack should support MTU settings
Product: [Community] RDO Reporter: Itzik Brown <itbrown>
Component: openstack-packstackAssignee: Martin Magr <mmagr>
Status: CLOSED WONTFIX QA Contact: Shai Revivo <srevivo>
Severity: medium Docs Contact:
Priority: medium    
Version: JunoCC: aortega, derekh, ichavero, kbasil, srevivo
Target Milestone: ---Keywords: Triaged
Target Release: Liberty   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-10 14:17:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Itzik Brown 2015-06-02 11:13:16 UTC 
Description of problem:

MTU selection and advertisement had been introduced in Kilo.
During installation Packstack put 'dhcp-option-force=26,1400' in /etc/neutron/dnsmasq-neutron.conf.
When dnsmasq process is spawned /etc/neutron/dnsmasq-neutron.conf is the last configuration file so the MTU for the instances is set to 1400.

It's desirable to use the configuration options introduced by the specification of 'MTU selection and advertisement' instead of the current behaviour.  

Version-Release number of selected component (if applicable):
openstack-packstack-puppet-2015.1-0.2.dev1537.gba5183c.el7ost.noarch
openstack-packstack-2015.1-0.2.dev1537.gba5183c.el7ost.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: