openstack/openstack-ansible-os_neutron
Code Issues Proposed changes

Provide support for "force_metadata" in dnsmasq

Browse Source 
Metadata server is important in some deployments and VMs need a way to
reach it. Normally, neutron routers include a static route to the
metadata server and things work, however, when using external L3 plugins
(e.g. ODL) that static route might not be there by default and thus VMs
don't have a way to contact the metadata server. For these cases, there
is an alternative in which the DHCP server pushes the route to the
instances through the 121 message defined in the DHCP standard. To use
this alternative in dnsmasq, we need force_metadata = True in its config

Change-Id: I2def87c8e7ed4b9ac87b66f825f2766a67a9a802
Signed-off-by: Manuel Buil <mbuil@suse.com>
This commit is contained in:
Manuel Buil 2018-10-03 17:04:44 +02:00
parent 6ac95259d2
commit 012329cb35
2 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
defaults/main.yml
View File

@ -402,6 +402,9 @@ neutron_dnsmasq_dns_servers: ""
# Limit number of leases to prevent a denial-of-service.
neutron_dnsmasq_lease_max: 16777216
# Specify if dnsmasq should send a route to metadata server through DHCP 121 message to VM
neutron_dnsmasq_force_metadata: False
###
### Metadata Agent Plugin Configuration
###

1
templates/dhcp_agent.ini.j2
View File

@ -17,3 +17,4 @@ dnsmasq_lease_max = {{ neutron_dnsmasq_lease_max }}
# Metadata
enable_isolated_metadata = True
force_metadata = {{ neutron_dnsmasq_force_metadata }}