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: kea apache cassandra/datastax cassandra (Razvan Becheriu)
2. Initial proposal for Kea Control API (Tomek Mrugalski)
3. Re: kea apache cassandra/datastax cassandra (Tomek Mrugalski)
----------------------------------------------------------------------
Message: 1
Date: Tue, 24 May 2016 15:39:14 +0300
From: Razvan Becheriu <[email protected]>
To: Tomek Mrugalski <[email protected]>
Cc: [email protected]
Subject: Re: [kea-dev] kea apache cassandra/datastax cassandra
Message-ID:
<CAPj=nfsvs9wsmqex413wiwi-az3h7f1bpndb7-dzvxmwzhw...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi,
Have you been able to look over the pull request? Do you have access to the
files/changes?
I just want to make sure I did all the steps necessary for the pull-request.
Thanks,
Razvan
On Thu, May 19, 2016 at 5:42 PM, Razvan Becheriu <
[email protected]> wrote:
> Hi,
>
> I've updated the kea-admin script with the commands needed to initialize
> the database and added necessary scripts to call the cqlsh (cassandra
> database client).
>
> I've attached to this file the necessary documentation needed to build the
> datastax cpp driver and to build KEA with cassandra backend.
>
>
>
> On Thu, May 19, 2016 at 2:06 PM, Tomek Mrugalski <[email protected]> wrote:
>
>> On 19.05.2016 10:58, Razvan Becheriu wrote:
>> > I work for Qualitance in collaboration with Deutsche Telekom.
>> > I have been working on improving the KEA server by adding support for
>> > apache cassandra/datastax cassandra.
>> I've been hearing about this Cassandra work for a while. It's exciting
>> to finally see the code.
>> > From my understanding, the new source files will be commited with
>> > "Apache License".
>> Yes. Please make sure you put the appropriate license note at the top of
>> each new file you added. I presume most of the new code comes in new
>> files. Also, make sure you update COPYING file. Adding a new section
>> there explaining that the Cassandra backend is distributed under Apache
>> license should do the trick. Another file to modify is AUTHORS. ISC
>> tries to keep track of all contributions that we received, but we're
>> flexible with it. We can put that whatever the contributor wants to -
>> name and company, just the name, only company, even anonymous is ok.
>>
>> >
>> > I am ready to commit the changes to a separate branch (for code
>> > review). The source files have been updated to latest (main branch)
>> > version.
>> Great! Can you submit a pull request on github? I'm sure you know how to
>> do it, but in case you haven't used it before, here's
>> https://help.github.com/articles/using-pull-requests/. This seems to be
>> the best way forward, as we would be able to tweak the code during the
>> review.
>>
>> Once I get the pull request, I'll start reviewing it.
>>
>> I was told that this change also has some documentation. It would be
>> great if you could include it. I must admit I have never set up
>> Cassandra before, but I presume there will be some installation required
>> and then some form of database initalization, similar to SQL schema.
>> Will this be a part of the patch? If not, can you explain how to set up
>> a test environment?
>>
>> > One thing to mention is that not all unit tests have been written for
>> > the cassandra backend.
>> That's unfortunate, but we can live with it. We always try to ask for
>> unit tests, but I still haven't seen a patch with full unit tests suite
>> :) Luckily the unit tests framework for the lease manager are structured
>> in a way that it's easy to extend to additional backends.
>> Once I see the code and understand it a bit, I'll write missing tests
>> for it.
>>
>> Thanks a lot,
>> Tomek
>>
>>
>> _______________________________________________
>> kea-dev mailing list
>> [email protected]
>> https://lists.isc.org/mailman/listinfo/kea-dev
>>
>
>
>
> --
> *Razvan Becheriu* | senior software engineer | QUALITANCE?
> *RO:* +00 (000) 000 000 | *office:* +40 (372) 944 741
> Opera Center bldg. 2, fl. 7-8, 2 Dr. Nicolae D. Staicovici, Bucharest
> 050556
> <https://www.google.ro/maps/place/QUALITANCE/@44.433653,26.079464,17z/data=!4m6!1m3!3m2!1s0x40b1ff173c5bc0b9:0x7226343f810c7ede!2sQUALITANCE!3m1!1s0x40b1ff173c5bc0b9:0x7226343f810c7ede?hl=ro>
> [email protected] | www.qualitance.com
> --
> The information contained in this email is confidential. It is intended
> only for the stated addressee and access to it by any other person is
> unauthorised. If you are not an addressee, you must not disclose, copy,
> circulate or in another way use or reply to the information contained in
> this email. Such unauthorised use may be unlawful. If you have received
> this email in error, please notify the sender immediately and delete all
> copies from your computer and network.
>
--
*Razvan Becheriu* | senior software engineer | QUALITANCE?
*RO:* +00 (000) 000 000 | *office:* +40 (372) 944 741
Opera Center bldg. 2, fl. 7-8, 2 Dr. Nicolae D. Staicovici, Bucharest 050556
<https://www.google.ro/maps/place/QUALITANCE/@44.433653,26.079464,17z/data=!4m6!1m3!3m2!1s0x40b1ff173c5bc0b9:0x7226343f810c7ede!2sQUALITANCE!3m1!1s0x40b1ff173c5bc0b9:0x7226343f810c7ede?hl=ro>
[email protected] | www.qualitance.com
--
The information contained in this email is confidential. It is intended
only for the stated addressee and access to it by any other person is
unauthorised. If you are not an addressee, you must not disclose, copy,
circulate or in another way use or reply to the information contained in
this email. Such unauthorised use may be unlawful. If you have received
this email in error, please notify the sender immediately and delete all
copies from your computer and network.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/kea-dev/attachments/20160524/ba64099b/attachment-0001.html>
------------------------------
Message: 2
Date: Wed, 25 May 2016 01:27:00 +0200
From: Tomek Mrugalski <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [kea-dev] Initial proposal for Kea Control API
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Hi,
I have just finished an initial proposal for Control API for Kea. The
proposal is available here:
http://kea.isc.org/wiki/ControlAPIRequirements
I'm very eager to hear your opinions on this. If you're an existing or
prospective user, can you also share your perceived priorities of those
proposed calls? Sharing your opinion on kea-dev is the best way to
respond, but sending your comments privately off the list is ok, too.
The complete API is huge and there is no way ISC could implement all of
it, at least not in one release. Therefore it's very useful to
prioritize which calls should be implemented first.
Note that ISC does not plan to make actual implementation of the API in
Kea 1.1. We had preliminary discussions whether it would be a good
leading topic for Kea 1.2, but we did not make any specific decisions yet.
Tomek
------------------------------
Message: 3
Date: Wed, 25 May 2016 02:11:54 +0200
From: Tomek Mrugalski <[email protected]>
To: Razvan Becheriu <[email protected]>
Cc: [email protected]
Subject: Re: [kea-dev] kea apache cassandra/datastax cassandra
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
On 24.05.2016 14:39, Razvan Becheriu wrote:
> Have you been able to look over the pull request? Do you have access to
> the files/changes?
> I just want to make sure I did all the steps necessary for the pull-request.
Yes. Thanks a lot. I have not investigated it immediately, as I was busy
with another task. Now the initial text of control API requirements is
done, I can focus on Cassandra.
I was able to download your code, build cpp-driver, tweak the script to
point to the right place and then build Kea with Cassandra backend
enabled. I'm now learning how to set up Cassandra instance. Your
documentation was very helpful so far and I see it also covers
installation and setup, so I'm hopeful I'll be able to run some tests soon.
I'll keep you posted.
Tomek
------------------------------
_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev
End of kea-dev Digest, Vol 26, Issue 4
**************************************
