> - We need a migration path for all the current consumers of isc-dhcp
> (Server & CLIENT!)
Replacing the client is already being worked on by foundations (for
early boot) and the cloud-init team (for cloud-init).
> and maybe also dnsmasq (to consolidate all around Kea):
While it is a valiant effort to consider dnsmasq users, there is a
reason they didn't use isc-dhcp to begin with.
We might have a look, but I'd not consider dnsmasq users a blocker.
I think walinuxagent is the one that I have not heard of yet in regard
to this efforts, someone needs to look into this indeed.
And I mean independent to kea, just for the sake of dchp-client being
no more fully maintained.
> $ reverse-depends src:dnsmasq -c main
As I said above, I welcome any effort but would consider this optional.
Great Analysis, thanks Lukas.
> - We need a migration path for all the current consumers of isc-dhcp
> (Server & CLIENT!)
Replacing the client is already being worked on by foundations (for
early boot) and the cloud-init team (for cloud-init).
> and maybe also dnsmasq (to consolidate all around Kea):
While it is a valiant effort to consider dnsmasq users, there is a
reason they didn't use isc-dhcp to begin with.
We might have a look, but I'd not consider dnsmasq users a blocker.
> $ reverse-depends src:isc-dhcp -c main
...
> * walinuxagent [amd64 arm64] (for isc-dhcp-client)
I think walinuxagent is the one that I have not heard of yet in regard
to this efforts, someone needs to look into this indeed.
And I mean independent to kea, just for the sake of dchp-client being
no more fully maintained.
> $ reverse-depends src:dnsmasq -c main
As I said above, I welcome any effort but would consider this optional.
> Required TODOs:
I'm sure Athos will soon start to tackle those.