Hello Andrew, Searching further, I find "neutron-ovs-cleanup" mentioned in the admin guide:
http://docs.openstack.org/admin-guide-cloud/content/install_neutron-l3.html which says: "If you reboot a node that runs the L3 agent, you must run the neutron-ovs-cleanup command before the neutron-l3-agent service starts." So I believe this service should start during server bootup of network node (where neutron-l3-agent service runs). Maybe they failed to include this in the official admin guide. On Mon, Jun 30, 2014 at 1:31 AM, Andrew Mann <and...@divvycloud.com> wrote: > Neutron itself starts the dnsmasq processes for tenant networks > (neutron-dhcp-agent is the service for this I believe), so you should not > enable dnsmasq in the system startup unless you are using another instance > of dnsmasq for a non-neutron purpose (such as providing dns and dhcp > services on your physical network to bare metal systems). > > I don't know much about neutron-ovs-cleanup, so I can't help with that > part of the question. > > > On Sun, Jun 29, 2014 at 1:56 PM, Vimal Kumar <vimal7...@gmail.com> wrote: > >> Hello, >> >> I followed the exact steps mentioned at: >> >> http://docs.openstack.org/trunk/install-guide/install/yum/content/ >> >> .. to create a 3 node Openstack IceHouse environment (controller, network >> & compute). >> >> I see that "neutron-ovs-cleanup" service is present on network & compute >> node, but it is turned off on both. Should this be set to on (in >> chkconfig)? If yes, then on which node should this service supposed to run >> (I recon network node, but still wanna confirm with the community). >> >> Also, I have the same concern about "dnsmasq" service. I see that this >> service is installed on network node, but is turned off in chkconfig. >> >> However I can find a dnsmasq process currently running: >> >> nobody 10602 0.0 0.0 12884 772 ? S 14:09 0:00 dnsmasq >> --no-hosts --no-resolv --strict-order --bind-interfaces >> --interface=tap47c93394-55 --except-interface=lo >> --pid-file=/var/lib/neutron/dhcp/18018aab-920b-42d4-99c3-c036155e60bf/pid >> --dhcp-hostsfile=/var/lib/neutron/dhcp/18018aab-920b-42d4-99c3-c036155e60bf/host >> --addn-hosts=/var/lib/neutron/dhcp/18018aab-920b-42d4-99c3-c036155e60bf/addn_hosts >> --dhcp-optsfile=/var/lib/neutron/dhcp/18018aab-920b-42d4-99c3-c036155e60bf/opts >> --leasefile-ro --dhcp-range=tag0,192.168.1.0,static,86400s >> --dhcp-lease-max=256 --conf-file= --domain=openstacklocal >> >> The Openstack official guide for RHEL flavors does not mention whether >> these services should be turned on during server reboot (using chkconfig). >> >> My concern is whether to start them automatically in case of a server >> reboot. Please assist. >> >> Regards, >> Vimal >> >> _______________________________________________ >> 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 >> >> > > > -- > Andrew Mann > DivvyCloud Inc. > www.divvycloud.com >
_______________________________________________ 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