Hi Ionut, I am working on a similar effort: Adding driver for neutron-dhcp-agent [1] & [2]. Is it similar to what you are trying to do? My approach doesn't need any extra database. There are two ways to achieve HA in my case:
1. Run multiple neutron-dhcp-agents and set agents_per_network >1 so more than one dhcp servers will have the config needed to serve the dhcp request 2. ISC-DHCPD itself has some HA where you can setup peers. But I haven't tried that yet. I have this driver fully implemented and working here at Yahoo!. Working on making it more generic and upstreaming it. Please let me know if this effort is similar so that we can consider working together on a single effort. [1] https://review.openstack.org/#/c/212836/ [2] https://bugs.launchpad.net/neutron/+bug/1464793 On Thu, Sep 24, 2015 at 9:40 AM, Dmitry Tantsur <divius.ins...@gmail.com> wrote: > 2015-09-24 17:38 GMT+02:00 Ionut Balutoiu < > ibalut...@cloudbasesolutions.com>: > >> Hello, guys! >> >> I'm starting a new implementation for a dhcp provider, >> mainly to be used for Ironic standalone. I'm planning to >> push it upstream. I'm using isc-dhcp-server service from >> Linux. So, when an Ironic node is started, the ironic-conductor >> writes in the config file the MAC-IP reservation for that node and >> reloads dhcp service. I'm using a SQL database as a backend to store >> the dhcp reservations (I think is cleaner and it should allow us >> to have more than one DHCP server). What do you think about my >> implementation ? >> > > What you describe slightly resembles how ironic-inspector works. It needs > to serve DHCP to nodes that are NOT know to Ironic, so it manages iptables > rules giving (or not giving access) to the dnsmasq instance. I wonder if we > may find some common code between these 2, but I definitely don't want to > reinvent Neutron :) I'll think about it after seeing your spec and/or code, > I'm already looking forward to them! > > >> Also, I'm not sure how can I scale this out to provide HA/failover. >> Do you guys have any idea ? >> >> Regards, >> Ionut Balutoiu >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > > -- > -- > -- Dmitry Tantsur > -- > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
