Send kea-dev mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/kea-dev
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of kea-dev digest..."
Today's Topics:
1. Hooks libraries and configuration information (Vadim Fedorenko)
2. Re: Client classification design (Thomas Markwalder)
----------------------------------------------------------------------
Message: 1
Date: Fri, 16 Oct 2015 18:48:47 +0300
From: Vadim Fedorenko <[email protected]>
To: [email protected]
Subject: [kea-dev] Hooks libraries and configuration information
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
It's good point to have an access to full configuration values inside the hook
library. For example, I want to know the lease database connection parameters
to make my hooks library access the same database for some reasons. And it's
not a good thing to make duplicates in library's own parameter list.
--
Best regards,
Vadim
------------------------------
Message: 2
Date: Fri, 16 Oct 2015 13:46:46 -0400
From: Thomas Markwalder <[email protected]>
To: [email protected]
Subject: Re: [kea-dev] Client classification design
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
On 10/16/15 7:43 AM, Thomas Markwalder wrote:
> On another note, it would be good to look at the tasks Tomek has
> identified and see if we can identify concurrent work paths. In other
> words, what parts can be done in parallel?
>
> Thomas
> _______________________________________________
> kea-dev mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/kea-dev
Just to clarify my suggestion:
{
"Dhcp4": {
:
# Globally v4 class definitions using format in proposal 2
"client-classes": [
{ class A },
{ class B },
:
{ class X },
],
# Subnets use format in proposal 3 for option-data
"subnet4": [
{ subnet 0 },
{ subnet 1 },
:
{ subnet n },
],
"lease-database": {
:
},
:
}
}
------------------------------
_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev
End of kea-dev Digest, Vol 19, Issue 7
**************************************
