[Pacemaker] Building an active/passive dhcp server

[Helmut Weymann]

Am Freitag, 19. März 2010 schrieb Emmanuel Lesouef:
> Hello,
>
> I'm trying to make a active/passive dhcp server.
>
> Currently, it works with the following setup :
>
> * 2 debian servers with pacemaker :
> node1 with physical ip1 and virtual ip vip1 (managed with pacemaker)
> node2 with physical ip2.
>
> * 1 lsb dhcp3-server resource that is on node1 and migrates ok on node2,
>
> * a rsync cron gets the dhcp lease file from node1 to node2 in order
>   not to start an empty dhcp lease file,
>
> * the server should be delivering dhcp lease with vip1 because it
>   is on a vlan and core router use cisco ip helper to send dhcp
>   requests.
>
> The problem is that when node1 come online again, there's a difference
> in the dhcp lease file.
>
> I think that using rsync to synchronize the lease file is not the best
> solution and that a clustered file system is the best solution.
>
> What are your opinions about such a setup ? Are there some "best
> practices" ?
>
> Thanks for your help and informations about this.
You may want to use the builtin failover feature if ISC DHCP server.
see http://www.daemon-systems.org/man/dhcpd.conf.5.html
Regards,

helmut

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100322/66f6cf87/attachment-0002.html>