[kea-dev] Lease File Compression Requirements
nicolas.chaigneau at capgemini.com
Thu Dec 18 10:25:04 UTC 2014
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:
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.
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 ?
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.
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.
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:
> 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.
More information about the kea-dev