[kea-dev] Adding MYSQL backend support
marcin at isc.org
Mon Jan 18 13:19:54 UTC 2016
Thanks for your interest in Kea and your initiative to create a MySQL
We heard from users that it is often desired to store configuration in
the database, rather than a file. For example: we're currently
implementing storing host reservations in an SQL database. We also
considered storing subnets configuration in the SQL database etc.
Implementing MySQL backend to hold full server configuration partly
overlaps with it. So, please allow a couple of days for us to discuss
this matter among the team members.
On 14.01.2016 04:43, Sallee, Jake wrote:
> I hope this is the correct place to be asking this question. If it is
> not or if there is another place I should be using as well please let
> me know.
> I am planning on adding MYSQL as a supported config backend for Kea;
> it seems to be a natural outcropping of my FOSDDI project.
> I wonder if anyone is already working on this. I am still in the
> planning stages and I would hate to do a fresh implementation if
> someone else is farther along than myself.
> If someone else is working on this I would be very willing to assist
> in anyway I can. I would also be very interested in hearing from them
> It is possible, of course, to simply write a wrapper script and parse
> the config info out of MYSQL into a JSON file and let Kea read that.
> But that feels klunky and I can see where errors can creep in.
> I think native built-in support for a ubiquitous service like MYSQL as
> a config backend is a huge plus for Kea. Given the fact that Kea
> already can use a DB store for its leases, extending that to the
> config file seems to be a logical situation.
> As always I welcome any ideas or feedback the community may have.
> Jake Sallee
> Godfather of Bandwidth
> System Engineer
> University of Mary Hardin-Baylor
> 900 College St.
> Belton, Texas
> Fone: 254-295-4658
> Phax: 254-295-4221
> kea-dev mailing list
> kea-dev at lists.isc.org
More information about the kea-dev