dhcp_agent only allows one dnsmasq_dns_server

[Jesse Pretorius]

As quantum.agent.linux.dhcp.Dnsmasq makes use of the --server command line when starting dnsmasq there can only be one server configured for the dnsmasq_dns_server option in dhcp_agent.ini

This is not ideal.

Ideally if a network is not created with its own dns server options, the options provided in dnsmasq_dns_server should be used and put into the opts file just as the network-configured options would be.

This would enable dns to work without dns options configured on the network using defaults provided by the deployer.

[Mark McClain (markmcclain)]

If the tenant does not define a name server for the network, the update DNS is the dnsmasq. dnsmasq will default to the servers for the network host. Are you proposing that this option be converted to a list?

[Jesse Pretorius (jesse-pretorius)]

For us using the hosts's DNS servers is not ideal as they are internal DNS servers which expose records which we'd rather not have exposed to instances. We want them to use public DNS servers instead. This is why we'd like to set the dnsmasq_dns_server option with multiple DNS servers.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/62002

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/62002
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a269541c603f8923b35b7e722f1b8c0ebd42c95a
Submitter: Jenkins
Branch: master

commit a269541c603f8923b35b7e722f1b8c0ebd42c95a
Author: Sylvain Afchain <email address hidden>
Date: Fri Dec 13 00:12:29 2013 +0100

    Allow multiple DNS forwarders for dnsmasq

    This patch change the dnsmasq_server configuration option to a ListOpt
    in order to enable user to specify multiple DNS forwarders for each
    dnsmasq instance.

    DocImpact

    Change-Id: I21963b4a6c99e4edb11040d77a6aeaa35ff44641
    Closes-bug: #1240027