Hello,
unfortunately, the DB backend is not supposed to be edited manually. Instead,
you'd need to load either the MySQL or PostgreSQL Configuration Backend hook
library. This exposes a convenient API to interact with the DB.
>From this section of the manual:
>https://kea.readthedocs.io/en/kea-2.4.0/arm/hooks.html#available-hook-libraries
> you'll find that both hook libs are open source. However, they have an
>inevitable dependency on this other hook:
>https://kea.readthedocs.io/en/kea-2.4.0/arm/hooks.html#std-ischooklib-libdhcp_cb_cmds.so
> which is only available after paying a recurring subscription.
The structure of the DB is rather intuitive, but manually inserting rows into
it has been made rather difficult on purpose and I don't suggest trying to
bypass all the obstacles, otherwise the integrity of the DB may not be fully
guaranteed.
Best,
Nicolò.
January 15, 2024 at 12:10 PM, "mtint hpc" <hpcmt...@gmail.com> wrote:
>
> Hello everyone,
>
> We are in the process of transitioning from our previous DDI solution to
> phpIPAM, KEA DHCP with a database backend, and PowerDNS. Currently, KEA is
> operational without a database backend for DHCP reservations. In our setup,
> there won't be any DHCP pools, and IP addresses will be allocated via the
> DHCP reservation. We have a total of 10 subnets. Can anyone provide guidance
> on how to proceed with this migration and which tables in the Kea schema
> should be edited?
>
> Thank you,
>
> Michael
>
--
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@lists.isc.org
https://lists.isc.org/mailman/listinfo/kea-users
