[Kea-users] Using Host Reservations in Kea

[Marcin Siodelski]

Hi Bryan,

I can't promise that we'll implement support for shared subnets in Kea
1.1.0 host reservations. The current scope for 1.1.0 release is already
defined and we're trying to avoid adding new work to not endlessly defer
the release. Though, we realize that shared subnets are the common use
case and that we need to get round to this sooner rather than later. I
also keep in mind your use case. From last discussion I remember that
you were able to get it to work a with a hook library? Is the approach
with the library still sufficient for you?

Marcin


On 23.06.2016 02:24, Bryan Perry wrote:
> Any word on whether the shared network quirk has been worked out yet?
> ie. Can 1.1.0 find and use a reservation from subnet 169 if the giaddr
> corresponds to subnet 170 but they are both part of a shared network?
> 
> Thanks,
> Bryan
> 
> On 6/22/2016 6:18 PM, Klaus Steden wrote:
>>
>> Fantastic. The documentation looks great, too. Is there an official
>> expected date for release available yet? I'm liking the software so far,
>> getting the reservation features working in MySQL will make it even
>> better.
>>
>> cheers,
>> Klaus
>>
>> On Wed, Jun 22, 2016 at 8:39 AM, Marcin Siodelski <marcin at isc.org
>> <mailto:marcin at isc.org>> wrote:
>>
>>     On 22.06.2016 17 <tel:22.06.2016%2017>:31, Thomas Andersen wrote:
>>     >
>>     > On 22/06/16 17:24, "kea-users-bounces at lists.isc.org
>>     <mailto:kea-users-bounces at lists.isc.org> on behalf of Templin, Fred
>>     L" <kea-users-bounces at lists.isc.org
>>     <mailto:kea-users-bounces at lists.isc.org> on behalf of
>>     Fred.L.Templin at boeing.com <mailto:Fred.L.Templin at boeing.com>> wrote:
>>     >
>>     > > This is the case we are interested in - many kea servers
>> connected to the
>>     > > single database. We want that each server will then have
>> consistent host
>>     > > reservation information for the clients that may come to them
>> for service.
>>     > >
>>     > > This means that the site administrators will only need to add
>> and remove
>>     > > host reservations in a single database rather than having to
>> push the same
>>     > > information into multiple places, which I think would ease
>> administrative
>>     > > overhead and be less prone to errors. Sounds like this should
>> work with
>>     > > the new features kea 1.1.0 will be providing?
>>     >
>>     >
>>     > This is what we do today in our installation with 1.0.0
>>     >
>>     >
>>     > /Thomas
>>     >
>>     >
>>     One thing to say about Kea 1.0.0 is that it doesn't allow you to
>>     specify DHCP options per host. It also doesn't work with IPv6
>>     reservations in the database. Kea 1.1.0 will also use database more
>>     efficiently, by reducing the number of queries made to the database
>>     to retrieve host information.
>>
>>     Marcin
>>     _______________________________________________
>>     Kea-users mailing list
>>     Kea-users at lists.isc.org <mailto:Kea-users at lists.isc.org>
>>     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
>>
> _______________________________________________
> Kea-users mailing list
> Kea-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/kea-users