[kea-dev] kea apache cassandra/datastax cassandra

[Tomek Mrugalski]

On 25.05.2016 02:11, Tomek Mrugalski wrote:
> 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.
Just a status update for this week. The short version is: has some minor
issues here and there, but it was nothing serious. And it works!

The slightly longer is that I installed and set up Cassandra. So far I
used a single cassandra node (running on my dev machine), so kept the
replication factor to 1. As I understand it, this doesn't give me any
redundancy, but makes it easier to test.

I had some problems initializing the database. kea-init didn't work
without doing make install first (that's a minor thing). After doing
make install, the code didn't work either and complained about keatest
having 6 tables:

  ERROR/kea-admin: Expected empty database keatest, but there are 6
  tables:

  keatest  system_schema  system_auth  system  system_distributed
  system_traces. Aborting.

I'm still learning the basics, but I think this is a small bug in the
kea-admin that uses DESCRIBE keyspaces; command, while it should say
DESCRIBE tables; instead. I may be wrong about this one. Anyway, I have
commented it out for now.

The database has been initialized. They were some warnings, but they're
not relevant for now (kept them in my notes, though).

kea-admin lease-version dscsql

properly reports schema version as 1.0.

I have created an example Kea config and reported:
DHCPSRV_DSCSQL_DB opening DataStax Cassandra lease database:
contact_points=127.0.0.1 keyspace=keatest type=dscsql universe=4

After that, a single client got IPv4 address. I then checked using
csqlsh that the lease is in the database:

> select * from keatest.lease4;

For some reason it showed 192.0.2.1 address as -1073741311, but I
presume it an issue with signed/usigned display. All other fields,
including hwaddr are set properly.

Ok, that's it for today. Will continue my tests and code review on Monday.

Tomek