openstack/openstack-ansible-os_neutron
Code Issues Proposed changes

Stop configuring neutron to enforce DHCP MTU option

Browse Source 
Since Mitaka, Neutron does the right job to calculate and advertise
correct MTU to instances, out of the box.

Change-Id: I119cf3c2bf5fc7b6f7f049381b85a6b1c3aa8779
This commit is contained in:
Ihar Hrachyshka 2016-04-29 13:44:33 -07:00 committed by Jesse Pretorius
parent 4709ac7a1e
commit 273cef616d
2 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
defaults/main.yml
View File

@ -327,7 +327,6 @@ neutron_l3_ha_net_cidr: 169.254.192.0/18
# DHCP AGENT CONFIG
neutron_dhcp_config:
dhcp-option-force: "26,1450"
log-facility: "/var/log/neutron/neutron-dnsmasq.log"
# Types of networks supported by the ml2 plugin

8
releasenotes/notes/neutron-dhcp-mtu-8767de6f541b04c1.yaml Normal file
View File

@ -0,0 +1,8 @@
---
upgrade:
- As described in the `Mitaka release notes
<http://docs.openstack.org/releasenotes/neutron/mitaka.html>`_
Neutron now correctly calculates for and advertises the MTU to
instances. The default DHCP configuration to advertise an MTU
to instances has therefore been removed from the variable
``neutron_dhcp_config``.