Kea for IPv4

[ciroiriarte]

Would completely migrating IPv4 assingment to Kea make sense?, is there any blocker?. Is that something that would be accepted as a PR?

My understanding is ISC DHCP is EOL, and Kea is the recommended replacement.

[olebowle]

Hi, thanks for reaching out! I agree that ISC should be replaced by Kea for all use cases. We would like to use the database for most of Keas state, since this will allow us later to easily enable high availability with multiple Kea instances. Be aware, that ISC is quite entangled into our codebase (getting / parsing leases, DDNS, releasing IP addresses, static IPs, IP pools of the NetGws, checking how many IPs are used NetGw etc). If you'd like to tackle it anyway, please feel free. I'm happy to look at your changes. I may have to cherry-pick your commits later on, since what you see here is a downstream repo of our own internal one. Of course we will mention you / your github handle in the commit message.

[ciroiriarte]

I would like to move away from file and database access as much as possible.

API interactions would be my preference when available.

I have several things in mind:

Replacing Icinga2/Cacti with LibreNMS
Replacing ISC DHCP with Kea
Replacing Bind with PowerDNS

Will try to eat the elefant piece by piece.

Any recommendations for testing for regressions?

[olebowle]

We have a lab for testing the DHCP server and to provision the modems. We can deploy your code there and test it. Please make LibreNMS available as an alternative, since we have customers relying on Cacti.

From what you have in mind, replacing ISC DHCP with Kea will be most welcomed by us.

[ciroiriarte]

For DHCP, a rip and replace would be acceptable?, or having both Kea and ISC as options is required in this case?

[olebowle]

Rip and replace is fine and preferred I'd say. Of course we need a migration from the old state of ISC to the same state in Kea (lease files etc.). This can be achieved with a laravel system migration.