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: Call for comments about Lease Expiration requirements in
Kea (Chaigneau, Nicolas)
----------------------------------------------------------------------
Message: 1
Date: Wed, 1 Jul 2015 09:14:40 +0000
From: "Chaigneau, Nicolas" <[email protected]>
To: Marcin Siodelski <[email protected]>, Kea Dev List
<[email protected]>
Subject: Re: [kea-dev] Call for comments about Lease Expiration
requirements in Kea
Message-ID:
<ab94b0b675bdf14189cd5a861db36c842bf27...@de-cm-mbx06.corp.capgemini.com>
Content-Type: text/plain; charset="iso-8859-1"
Hello,
Thanks for sharing these requirements and design. I have just a few comments:
1)
> C2. MUST provide a configuration switch to control the length of the period
> between two consecutive processing cycles
> C3. MUST provide a configuration switch to control the maximum number of
> leases to be processed in a single cycle
First, to be accurate, C2 and C3 are not "switches", but parameters.
About C3: I think a more relevant parameter would be the maximum amount of time
(allow at least up to the millisecond precision) spent processing expired
leases in a single cycle.
(You should still keep the limit on the number of processed leases so people
can choose to configure either or both.)
2)
Additionally, if (because of one of the limits) Kea is not able to handle all
of the expired leases (maybe if it happens in N consecutive cycles - this
should be also a configurable value), some kind of warning should be issued.
This would alert the administrator that his configuration is not adequate.
3)
> C4. SHOULD provide means to manually trigger lease reclaimation
It should also provide the means to bypass the limits (C3) so one can enforce
expiring all the leases in one command.
Regards,
Nicolas.
> -----Message d'origine-----
> De : [email protected] [mailto:[email protected]] De
> la part de Marcin Siodelski
> Envoy? : mercredi 24 juin 2015 14:27
> ? : Kea Dev List
> Objet : [kea-dev] Call for comments about Lease Expiration requirements in Kea
>
> All,
>
> As a part of the preparation for the Kea 1.0, I would like to ask the list
> participants to review and comment on a document presenting the requirements
> for the "Lease Expiration", which is available here:
>
> http://kea.isc.org/wiki/LeaseExpirationRequirements
>
> Note that this is an early version of the document. The goal of the early
> call for the review is to collect, discuss and incorporate all additional
> requirements before the design phase starts for real. This is to avoid
> unnecessary delays in designing the feature and making "last minute" changes
> affecting our productivity and then implementation process.
>
> Just for the record... we're planning to close the requirements and the
> design phase for "Lease Expiration" by the end of July, when we're planning
> to start the implementation work.
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 16, Issue 1
**************************************
