conf file sync between master/peer

[Kyle Johnson]

Hello Greg,

You're right, breaking down the dhcpd.conf file into smaller parts and
using include statements helps.  Most people probably manually sync. the
files between the servers and restart the dhcpd process as needed, or write
a small script to do the work for them.
Personally, I am making my changes in configuration management (in this
case, chef).  The dhcp servers check into the chef master every 30 minutes,
or I force a sync., to pull down the appropriate files (in this case,
dhcpd.conf), and then restart any services which depend on those files (in
this case, dhcpd).

Hope this helps,
Kyle


On Mon, May 13, 2013 at 7:41 PM, Gregory Sloop <gregs at sloop.net> wrote:

> I have another question about keeping a master and peer in "sync" as
> one changes one config file on one server, without having to manually
> edit/sync both.
>
> It looks like breaking down the dhcp.conf files into component pieces and
> syncing the "common" pieces for both master-peer with something like
> rsync +restart seems like a reasonable approach.
>
> I'm assuming there are others who have done something like this - but
> I haven't seen a lot of examples out there.
>
> Any tips - what works, what doesn't? What to watch for, or success
> stories?
>
> TIA
> -Greg
>
>
> --
> Gregory Sloop, Principal: Sloop Network & Computer Consulting
> 503.251.0452 x121 Voice | 503.251.0452 Fax
> www.sloop.net
> mailto:gregs at sloop.net
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20130514/fe45f0c8/attachment.html>