To answer a part of my own question: dnsmasq is running on the controller node because there is a libvirt service running. Which got installed as a dependency of the "Virtualization host" package group… so no one to blame but myself.
Am 12.06.2015 um 14:07 schrieb Uwe Sauter: > Gary, > > Thanks. > > That brings up the question why there are dnsmasq processes running on my > controller node (which has neutron-server running) and > not on the networking node (neutron-dhcp-agent neutron-l3-agent > neutron-metadata-agent neutron-openvswitch-agent). > > Any suggestions? > > > Regards, > > Uwe > > Am 12.06.2015 um 13:58 schrieb Gary Kotton: >> Hi, >> The DHCP agent runs the dnsmasq process. That is done on the network node. >> Thanks >> Gary >> >> On 6/12/15, 2:35 PM, "Uwe Sauter" <uwe.sauter...@gmail.com> wrote: >> >>> Hi, >>> >>> == TL;DR == >>> Which neutron service manages the DNSMASQ processes? Does this run on the >>> controller node or the networking node? >>> >>> >>> == Long story == >>> I have a five node Juno installation (1 controller, 1 storage, 1 network >>> and 2 compute nodes). >>> >>> I followed the Juno Red Hat installation guide [1] up to the point where >>> the dashboard was installed, making modifications where >>> necessary to account for the additional nodes. I'm using Neutron / ML2 as >>> networking component with GRE tenant networks. >>> >>> I am able to sucessfully start a Cirros VM but that instance won't get an >>> IP address. To resolve this I followed a link [2] that >>> told to add logging to dnsmasq. Here the relevant parts on the *network* >>> node: >>> >>> /etc/neutron/dhcp_agent.ini >>> [DEFAULT] >>> interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver >>> dhcp_driver = neutron.agent.linux.dhcp.Dnsmasq >>> use_namespaces = True >>> dhcp_delete_namespaces = True >>> verbose = True >>> dnsmasq_config_file = /etc/neutron/dnsmasq-neutron.conf >>> >>> >>> /etc/neutron/dnsmasq-neutron.conf >>> dhcp-option-force=26,1454 >>> log-facility = /var/log/neutron/dnsmasq.log >>> log-dhcp >>> >>> >>> Then I realized that there were no dnsmasq processes on the networking >>> node but only on the controller node. Is this correct? I >>> was under the impression that neutron-dhcp-agent (running on the >>> networking node) is the service that maintains DHCP on the tenant >>> networks. >>> >>> So the question is: >>> Which service manages dnsmasq and on which node should that run on? >>> >>> >>> Thanks, >>> >>> Uwe >>> >>> [1] http://docs.openstack.org/juno/install-guide/install/yum/content/ >>> [2] >>> https://ask.openstack.org/en/question/63110/unable-to-get-dhcp-lease-in-ju >>> no/ >>> >>> _______________________________________________ >>> Mailing list: >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>> Post to : openstack@lists.openstack.org >>> Unsubscribe : >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> > _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
