Add support to use dnsmasq with the OVS plug-in and GRE
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
puppet-neutron |
Fix Released
|
Low
|
Daniel Gollub |
Bug Description
http://
If you use the neutron DHCP agent, add these lines to the /etc/neutron/
Create /etc/neutron/
which could be implemented by adding support for dnsmasq_config_file in https:/
Should /etc/neutron/
Changed in puppet-neutron: | |
status: | New → Fix Committed |
importance: | Undecided → Low |
assignee: | nobody → Daniel Gollub (d-gollub) |
Changed in puppet-neutron: | |
milestone: | none → 3.0.0 |
Changed in puppet-neutron: | |
milestone: | 3.0.0 → none |
Changed in puppet-neutron: | |
milestone: | none → 4.0.0 |
no longer affects: | puppet-neutron/havana |
Changed in puppet-neutron: | |
status: | Fix Committed → Fix Released |
Maybe this change is a good base to start with: https:/ /review. openstack. org/#/c/ 63520/
Additionally you would have to do something like this in your manifests (untested):
---8<--- dhcp_agent_ dnsmasq_ mtu = 1454
$neutron_
file { '/etc/neutron/ dnsmasq. conf': 'yourpathto/ neutron/ dhcp-agent/ dnsmasq. conf.erb' ), 'neutron- dhcp-service' ],
ensure => file,
content => template(
owner => root,
group => root,
mode => 640,
notify => Service[
}
class { 'neutron: :agents: :dhcp': config_ file => '/etc/neutron/ dnsmasq. conf', etc/neutron/ dnsmasq. conf']
dnsmasq_
requires => File['/
}
---->8-----
dnsmasq.conf.erb: dhcp_agent_ dnsmasq_ mtu -%> dhcp_agent_ dnsmasq_ mtu %>
----8<---
<% if @neutron_
dhcp-option=26,<%= @neutron_
<% end -%>
---->8-----
dhcp-option-force or dhcp-option? Anyone has bad experience with using plain dhcp-option= instead of dhcp-option-force= with some DHCP client?
Not quite sure if it is in common interested to introduce a fine-grain configurable dnsmasq template directly - beside the dnsmasq_file options. If so I could provide additional changes for common dnsmasq options like the MTU size change.
Note: if you not only have to decrease the MTU due to GRE overhead (as you described in your blog post) but have to increase the MTU for jumbo frame usage with OVS and GRE Tunnel you will need to also change the MTU of the VIFs on the compute node by setting network_device_mtu. To make this nova option work for OVS drivers this change is required: https:/ /review. openstack. org/#/c/ 62221/ /review. openstack. org/#/c/ 63406/): network_device_mtu and Nova network_device_mtu (puppet-nova enhancement WIP).
network_device_mtu on the Neutron l3-agent might be also need to be adapted. So actually if you adapt the MTU for tenant networks you might need to adapt it to the same value at three different places: inside the guest by using Neutron DHCP Agent and the dhcp-option (this patch), Neutron L3-Agent (https:/