Allow dnsmasq_dns_servers to be configured for DHCP Agent
authorFeng Pan <fpan@redhat.com>
Thu, 19 Jan 2017 22:02:58 +0000 (17:02 -0500)
committerFeng Pan <fpan@redhat.com>
Thu, 19 Jan 2017 22:31:16 +0000 (17:31 -0500)
Closes-Bug: 1657901
Change-Id: I1491fed0ec79f9cdc5bb04555fdefcf1d29f29c9
Signed-off-by: Feng Pan <fpan@redhat.com>
puppet/services/neutron-dhcp.yaml

index 5e7de18..bb4742c 100644 (file)
@@ -39,6 +39,10 @@ parameters:
     default:
       tag: openstack.neutron.agent.dhcp
       path: /var/log/neutron/dhcp-agent.log
+  NeutronDhcpAgentDnsmasqDnsServers:
+    default: []
+    description: List of servers to use as dnsmasq forwarders
+    type: comma_delimited_list
 
 resources:
 
@@ -64,6 +68,7 @@ outputs:
           - neutron::agents::dhcp::enable_isolated_metadata: {get_param: NeutronEnableIsolatedMetadata}
             neutron::agents::dhcp::enable_force_metadata: {get_param: NeutronEnableForceMetadata}
             neutron::agents::dhcp::enable_metadata_network: {get_param: NeutronEnableMetadataNetwork}
+            neutron::agents::dhcp::dnsmasq_dns_servers: {get_param: NeutronDhcpAgentDnsmasqDnsServers}
             tripleo.neutron_dhcp.firewall_rules:
               '115 neutron dhcp input':
                 proto: 'udp'