[Kea-users] "filename" vs "option bootfile-name"

[Marcin Siodelski]

On 03.09.2016 12:18, Patrik Lundin wrote:
> On Sun, Jul 10, 2016 at 08:26:16PM +0200, Patrik Lundin wrote:
> >
> > Anyway, like I said I will accept the fact that kea considers "file"
> > deprecated in favor of the boot-file-name option. It just means the
> > autoinstall feature of OpenBSD needs to know about it as well.
> >
>
> To follow up on this, the development branch of OpenBSD now has an
> installer that is capable of picking up the filename from options
> rather than the "file" field:
> http://marc.info/?l=openbsd-cvs&m=147144203513174&w=2
>
> However, upon reading the kea 1.1.0-beta release notes
> (https://kb.isc.org/article/AA-01417) yesterday I noticed something:
> ===
> - Significantly extends the existing host reservation capabilities to
>    include reservations of specific DHCP options, reservations of siaddr,
>    sname, and file fields within DHCPv4 messages, and reservations of
>    multiple IPv6 addresses/prefixes.
> ===
>
> Does this mean you changed your minds and it is now possible to configure
> "file" without having to write a custom hook lib for it? How come? Is
> it also
> possible to configure "file" on a global level or only for a specific
> host reservation?
>

We consulted that matter with various Kea users and it turned out that
there is still a large base of them which have a strong desire to use
those fields. Therefore, we decided to add generic support for it.

Currently, the siaddr, sname and file can be all defined for a host or
for a class. The siaddr can also be specified on a subnet level. We may
also need to add support for sname and file being specified on a subnet
level. Not sure if global entries for those values are that useful. though.

Marcin Siodelski
ISC