... | @@ -14,7 +14,7 @@ Kea team sometimes meet to pursue certain goals. Usually we meet around other co |
... | @@ -14,7 +14,7 @@ Kea team sometimes meet to pursue certain goals. Usually we meet around other co |
|
* 12 Oct - Hackathon day 2, starting at 10am
|
|
* 12 Oct - Hackathon day 2, starting at 10am
|
|
*
|
|
*
|
|
|
|
|
|
The venue place is tbd, but it's likely to be ETI faculty building of the [Gdańsk University of Technology](https://en.wikipedia.org/wiki/Gda%C5%84sk_University_of_Technology).
|
|
The venue place is tbd, but there are talks in progress with ETI faculty of the [Gdańsk University of Technology](https://en.wikipedia.org/wiki/Gda%C5%84sk_University_of_Technology).
|
|
|
|
|
|
## Technical goals
|
|
## Technical goals
|
|
We would like to focus on two emerging technologies that hopefully will make it into upcoming Kea 1.5 release. The first one is **configuration backend**. Current (1.4.0) Kea code is able to store its configuration in JSON configuration files or be able to receive it over REST interface. The goal of this feature is to be able to store large chunks of the configuration in a database. The ultimate goal is to be able to start kea with only database credentials and it would retrieve whole remaining configuration from a database.
|
|
We would like to focus on two emerging technologies that hopefully will make it into upcoming Kea 1.5 release. The first one is **configuration backend**. Current (1.4.0) Kea code is able to store its configuration in JSON configuration files or be able to receive it over REST interface. The goal of this feature is to be able to store large chunks of the configuration in a database. The ultimate goal is to be able to start kea with only database credentials and it would retrieve whole remaining configuration from a database.
|
... | | ... | |