[kea-dev] Another hook suggestion: configurable periodic timers

Chaigneau, Nicolas nicolas.chaigneau at capgemini.com
Mon Dec 1 16:42:31 UTC 2014

Hello again,

I understand perfectly about priorities, no worries.
I'm just listing nice things that I could use if they happened at some point. :)

The hacky workaround will do, though.


> On 19.11.2014 17:50, Chaigneau, Nicolas wrote:
> > I think of the following:
> > 
> > Allow to define in configuration a list of timers, each of which would be composed of a period and identifier.
> > For instance, with a timer of 5 min and one of 1H:
> > 
> > 	"periodic-timers": [
> > 		{
> > 			"id": "timer-monitor"
> > 			"period": 300,
> > 		},
> > 		{
> > 			"id": "timer-1H"
> > 			"period": 3600,
> > 		}
> > 	]
> > 
> > Kea would trigger a new hook "periodic timer" each time the period of one of the timers is reached.
> > The hook library would receive both "id" and "period" arguments, which would allow to decide what to do (or do nothing).
> There are two aspects of this proposal. First, Kea does not support timers per se. At least not yet. This is something we will definitely implement in the near future. One specific reason for timers support is periodic lease clean up and expiration. We'll need a (configurable) timer that will trigger 2 things: expired lease processing and lease file rewrite. (or maybe there will be two separate timers for that, it isn't designed yet). There's no question about it and it will be implemented. I plan to file a ticket for that in the next couple days, along with other tickets required for lease expiration/clean up.
> The second aspect is whether to add custom (user definable) timers and a hook they would trigger. I see some value in such capability, but its implementation would take some time and honestly speaking there are more urgent missing features. So feel free to submit a ticket for this, but I'm afraid it is unlikely anyone would implement this anytime soon.
> Tomek

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 mailing list