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. Re: Lease File Compression Requirements (Chaigneau, Nicolas)
----------------------------------------------------------------------
Message: 1
Date: Thu, 18 Dec 2014 10:25:04 +0000
From: "Chaigneau, Nicolas" <[email protected]>
To: Marcin Siodelski <[email protected]>, "[email protected]"
<[email protected]>
Subject: Re: [kea-dev] Lease File Compression Requirements
Message-ID:
<ab94b0b675bdf14189cd5a861db36c84194b7...@de-cm-mbx06.corp.capgemini.com>
Content-Type: text/plain; charset="utf-8"
Hello,
I've read the latest version (3) of the requirements page (and the related
messages posted on the list).
This seems good to me.
A few points I'd like to discuss:
1)
On the two vs one lease file debate:
For me, having two lease files instead of one really is not an issue.
Administration will adapt.
Performances, however, are crucial. So if there's a noticeable gain to expect
from the multiple files option, I'd prefer to go that way.
2)
On requirement 2.b:
"The LFC must be triggered periodically and the interval must be configurable."
One additional thing that could be handy is to have LFC occur at predictable
times (independently of when the server was started).
For example, the ability to trigger LFC once an hour at the beginning of each
hour.
Maybe something similar to cron scheduling ?
3)
Following point 2) above, it could be useful for an external process to know
when LFC is currently happening.
(so it would know, for instance, that it is not advisable to read the lease
file until LFC processing is finished)
This could be achieved for example through a "lease lock file", created and
deleted by Kea, respectively at LFC start and completion.
4)
On lease file synchronization across servers (in active/standby mode):
This can be taken care of outside of Kea.
For instance, this can be achieved through a HA cluster architecture with DRBD.
Regards,
Nicolas.
On 16/12/14 12:02, Marcin Siodelski wrote:
>
> As a first step towards the implementation of this feature in Kea, I
> created a page with requirements:
>
> http://kea.isc.org/wiki/LeaseFileCompressionRequirements
>
> All input to this document is welcome.
>
> I am planning on creating an accompanying design document using the
> requirements presented here.
>
> Again, please share your thoughts.
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not authorized
to read, print, retain, copy, disseminate, distribute, or use this message or
any part thereof. If you receive this message in error, please notify the
sender immediately and delete all copies of this message.
------------------------------
_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev
End of kea-dev Digest, Vol 9, Issue 6
*************************************
