From 273cef616db46abacc87be58692b1629ee744426 Mon Sep 17 00:00:00 2001 From: Ihar Hrachyshka Date: Fri, 29 Apr 2016 13:44:33 -0700 Subject: [PATCH] Stop configuring neutron to enforce DHCP MTU option Since Mitaka, Neutron does the right job to calculate and advertise correct MTU to instances, out of the box. Change-Id: I119cf3c2bf5fc7b6f7f049381b85a6b1c3aa8779 --- defaults/main.yml | 1 - releasenotes/notes/neutron-dhcp-mtu-8767de6f541b04c1.yaml | 8 ++++++++ 2 files changed, 8 insertions(+), 1 deletion(-) create mode 100644 releasenotes/notes/neutron-dhcp-mtu-8767de6f541b04c1.yaml diff --git a/defaults/main.yml b/defaults/main.yml index 2d33e84a..ee40aa36 100644 --- a/defaults/main.yml +++ b/defaults/main.yml @@ -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 diff --git a/releasenotes/notes/neutron-dhcp-mtu-8767de6f541b04c1.yaml b/releasenotes/notes/neutron-dhcp-mtu-8767de6f541b04c1.yaml new file mode 100644 index 00000000..c3f7b35a --- /dev/null +++ b/releasenotes/notes/neutron-dhcp-mtu-8767de6f541b04c1.yaml @@ -0,0 +1,8 @@ +--- +upgrade: + - As described in the `Mitaka release notes + `_ + 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``.