[Kea-users] migrating an existing LDAP configuration

Darren Ankney darren.ankney at gmail.com
Fri Apr 12 14:52:11 UTC 2024


I clicked "send" too soon.  I meant to share this knowledge base
article that is slightly relevant.  The focus is on using Kea with
pgpool-ii but it does show an example of storing the configuration in
the database and working with it via the API at the end:
https://kb.isc.org/docs/experimenting-with-postgresql-high-availability

Thank you,
Darren Ankney

On Fri, Apr 12, 2024 at 10:50 AM Darren Ankney <darren.ankney at gmail.com> wrote:
>
> Hi Udo,
>
> That is correct.  To store the configuration in the database, you
> would need the Configuration Backend Commands hook:
> https://kea.readthedocs.io/en/kea-2.4.1/arm/hooks.html#libdhcp-cb-cmds-so-configuration-backend-commands
> which does require a support subscription.
>
> Thank you,
> Darren Ankney
>
> On Fri, Apr 12, 2024 at 8:10 AM Udo Rader <udo.rader at bestsolution.at> wrote:
> >
> > Hi,
> >
> > even after searching the list archives and the docs, I am not really sure what the migration path for our existing ISC DHCP server could look like.
> >
> > Currently we are using ISC DHCP in three different places (data centers). They all consume their configuration (subnets, static host entries, DHCP options, ...) from an OpenLDAP server, which is replicated to the different data centers.
> >
> > Every data center has its own base DN in LDAP, eg
> >
> > dhcpd.conf in data center1:
> > [...]
> > ldap-base-dn "ou=DC1,ou=DHCP,dc=example,dc=com";
> > [...]
> >
> > dhcpd.conf in data center 2:
> > [...]
> > ldap-base-dn "ou=DC2,ou=DHCP,dc=example,dc=com";
> > [...]
> >
> > dhcpd.conf in data center 3:
> > [...]
> > ldap-base-dn "ou=DC3,ou=DHCP,dc=example,dc=com";
> > [...]
> >
> > Leases are stored locally and they are irrelevant for migration.
> >
> > I understand that KEA does not support LDAP as a backend and so I would be willing to migrate the existing configuration to something else, but even after reading the docs, I fail to fully understand what my options are.
> >
> > My best guess so far is that I could replace LDAP by either MySQL or Postgres, configure database replication and have the various local KEA instances connect to the replicated local database instances. Is that correct?
> >
> > And if so, am I right to assume that for this to work, I need the "Kea Configuration Backend" (which requires a support subscription)?
> >
> > Thanks for any insights.
> >
> > Udo
> > ________________________________
> >
> > Udo Rader, MSc, MBA, Head Unicorn Wrangler
> > BestSolution.at EDV Systemhaus GmbH
> > Salurner Straße 15, 6020 Innsbruck, Austria
> > https://www.BestSolution.at
> > Reg. Nr. FN 222302s am Firmenbuchgericht Innsbruck
> > [BestSolution]
> > --
> > ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
> >
> > To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
> >
> > Kea-users mailing list
> > Kea-users at lists.isc.org
> > https://lists.isc.org/mailman/listinfo/kea-users


More information about the Kea-users mailing list