The easy way to scale it is to just launch more dhcp agents. The scaling issue arises when a single dhcp agent is managing thousands of dnsmasq instances and interfaces. On Wed, Mar 11, 2015 at 4:07 PM, Wanjing Xu <wanjing_xu at hotmail.com> wrote: > One of my peers mentioned that people talked about dnsmasq scale problems > at paris summit. So what was the scale problems? Currently, there is one > dnsmasq instance for each subnet. And pool management and allocation > seemed to be done at neutron. Thus dnsmasq is light-weighted. So if > dnsmasq does have scale issues, what is the suggested solution and what is > the common practice in using dhcp server? > > Regards! > > Wanjing Xu > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Kevin Benton -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150311/f9ab8c0e/attachment.html>