... | ... | @@ -22,16 +22,21 @@ Thanks to the generous invite from [Department of Computer Communications](https |
|
|
|
|
|
Prof. Józef Woźniak and doc. Krzysztof Nowicki will open up the hackathon.
|
|
|
|
|
|
## Kea overview
|
|
|
|
|
|
Kea is a modern DHCP environment that provides a variety of services (DHCPv4, DHCPv6, DDNS, DHCPv4-over-DHCPv6) and is able to interact with many environments, such as MySQL, PostgreSQL, Cassandra (a NoSQL database), RADIUS and many more. It's a successor of the ISC DHCP software that has been providing DHCP services for over two decades. Kea is currently deployed in many small and large networks. All Facebook datacentres are serviced by Kea. There are confirmed production deployments on four continents. The larges ones count their users in millions.
|
|
|
|
|
|
## 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.
|
|
|
|
|
|
The second one is **YANG/NETCONF**. This is a realitively young technology that becomes more and more popular. The concept here is that any device, appliance, server or service can store its configuration as YANG data. To be able to do that, YANG schema (or YANG model) has to be defined. There is also NETCONF protocol that defines how to uniformly manage (set, query, change, delete etc.) YANG configurations. We have early YANG models for Kea and would like to improve them and make some progress regarding Kea support for them.
|
|
|
|
|
|
[NETCONF overview](designs/netconf-overview), [NETCONF requirements for Kea](designs/netconf-design), [NETCONF design](designs/netconf-design). Also, RFC4741, RFC6020.
|
|
|
Background materials: [NETCONF overview](designs/netconf-overview), [NETCONF requirements for Kea](designs/netconf-design), [NETCONF design](designs/netconf-design). Also, RFC4741, RFC6020.
|
|
|
|
|
|
## Participants
|
|
|
|
|
|
Please join us regardless if you're already a Kea user, want to known the Kea team personally, or perhaps convince us that the feature you really want is absolutely necessary. Even if you never used Kea before, but are interested in learning how a modern, C++11-based, REST project is being developed, now is your chance!
|
|
|
Please join us regardless if you're already a Kea user, want to known the Kea team personally, or perhaps convince us that the feature you really want is absolutely necessary. Even if you never used Kea before, but are interested in learning how a modern, C++11-based, REST API capable project is being developed, now is your chance!
|
|
|
|
|
|
While physical presence is strongly preferred, it will be possible to participate remotely.
|
|
|
|
... | ... | |