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. branch and pull request (alexis)
2. Re: Lease File Compression Requirements (Marcin Siodelski)
3. Re: branch and pull request (Marcin Siodelski)
4. Re: branch and pull request (alexis)
----------------------------------------------------------------------
Message: 1
Date: Thu, 18 Dec 2014 09:37:39 -0300
From: alexis <[email protected]>
To: [email protected]
Subject: [kea-dev] branch and pull request
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Hello guys, i?ve been working on trac 3636. i have a local trac3636 branch with
the changes (code and unit tests) that i would like to push for revision but im
receiving 403 for my user on github.
How is the correct procedure to push the change to be reviewed? so i can move
on and start on the database reconnect.
thanks in advance, regards
------------------------------
Message: 2
Date: Thu, 18 Dec 2014 16:22:31 +0100
From: Marcin Siodelski <[email protected]>
To: "Chaigneau, Nicolas" <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: [kea-dev] Lease File Compression Requirements
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Nicolas,
See my answers inline.
Marcin
On 12/18/14 11:25, Chaigneau, Nicolas wrote:
> 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.
>
I agree. I will update the requirements with the decision that the
server doesn't have to keep leases in one file. And, the design will
accommodate it.
> 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 ?
>
Perhaps the server should persist an information about the time when the
last LFC occurred and measure the period from there. And if the server
failed to write the last LFC time, e.g. because of the crash, the LFC
could start immediately or nearly immediately.
> 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.
>
Yes, I was thinking about it before. I think it is necessary for the
server to know whether the last cleanup completed successfully or not
when the server crashes in between. So, I agree.
> 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.
>
>
Agreed.
> 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.
>
------------------------------
Message: 3
Date: Thu, 18 Dec 2014 16:26:32 +0100
From: Marcin Siodelski <[email protected]>
To: alexis <[email protected]>
Cc: [email protected]
Subject: Re: [kea-dev] branch and pull request
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
What is the repository you're checking in to? Is it the main Kea
repository on github or you have cloned it and you have your private repo?
Marcin
On 12/18/14 13:37, alexis wrote:
> Hello guys, i?ve been working on trac 3636. i have a local trac3636
> branch with the changes (code and unit tests) that i would like to
> push for revision but im receiving 403 for my user on github.
>
> How is the correct procedure to push the change to be reviewed? so i
> can move on and start on the database reconnect.
>
> thanks in advance, regards
>
> _______________________________________________
> kea-dev mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/kea-dev
>
------------------------------
Message: 4
Date: Thu, 18 Dec 2014 12:29:34 -0300
From: alexis <[email protected]>
To: Marcin Siodelski <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [kea-dev] branch and pull request
Message-ID:
<CADN=mdq9hhavnh0yigx05pg4oyp4mvqj0vnoxo4hjtxoi8h...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
cloned master from
https://github.com/isc-projects/kea.git
with my github user which is afidalgo
On Thu, Dec 18, 2014 at 12:26 PM, Marcin Siodelski <[email protected]> wrote:
>
> What is the repository you're checking in to? Is it the main Kea
> repository on github or you have cloned it and you have your private repo?
>
> Marcin
>
>
> On 12/18/14 13:37, alexis wrote:
> > Hello guys, i?ve been working on trac 3636. i have a local trac3636
> > branch with the changes (code and unit tests) that i would like to
> > push for revision but im receiving 403 for my user on github.
> >
> > How is the correct procedure to push the change to be reviewed? so i
> > can move on and start on the database reconnect.
> >
> > thanks in advance, regards
> >
> > _______________________________________________
> > kea-dev mailing list
> > [email protected]
> > https://lists.isc.org/mailman/listinfo/kea-dev
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/kea-dev/attachments/20141218/ea724c51/attachment-0001.html>
------------------------------
_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev
End of kea-dev Digest, Vol 9, Issue 7
*************************************
