... | ... | @@ -32,7 +32,7 @@ Kea has a RESTful API for various management activities and monitoring, like sta |
|
|
|
|
|
**Complexity:** medium (assuming you know C++ and know a thing or two about REST API) to insane (if you never heard about DHCP and think laptops and phones connect to networks by pure magic)
|
|
|
|
|
|
### 2. Statistics enhancements
|
|
|
### 2. Statistics enhancements (1 candidate)
|
|
|
|
|
|
Kea is currently able to report dozens of statistics. However, for each statistic there is only one specific value being reported. For certain types of activities it is highly desirable to have multiple observations over time. Having many data points gives an insight into processes that are changing over time, e.g. daily patterns in user activities, DOS detection and mitigation etc.
|
|
|
|
... | ... | @@ -46,7 +46,7 @@ Kea is currently able to report dozens of statistics. However, for each statisti |
|
|
|
|
|
**Difficulty**: easy, unless a bit of math scares you off
|
|
|
|
|
|
### 3. HTTP GET Support
|
|
|
### 3. HTTP GET Support (1 candidate)
|
|
|
Kea supports many commands that are exposed via REST interface. Some of them are read-only in nature, like retrieving configuration (whole or parts of it, like whole configuration, specific subnet, specific host, specific address lease etc.) or statistics. Unfortunately, Kea uses POST mechanism to retrieve all of them. Some commands could be limited to GET mechanism. Many deployments that do not want to change Kea configuration on the fly could limit access to GET only rather than allowing POST access. This would have security benefits.
|
|
|
|
|
|
**Why**: Nice small security improvement in REST interface that will be applauded by users. Great way to learn internals of HTTP protocol.
|
... | ... | @@ -127,7 +127,7 @@ The mechanism defined in RFC4388 and RFC5007 provide a mechanism to query the se |
|
|
|
|
|
**Difficulty**: easy
|
|
|
|
|
|
### 9. ISC DHCP => Kea Migration Assistant
|
|
|
### 9. ISC DHCP => Kea Migration Assistant (1 candidate)
|
|
|
This is a web site, or web page anyway, that will enable a user to upload an ISC DHCP configuration file. The file will then be fed through a modified version of ISC DHCP which will save the configuration file in a format that Kea can import. The process will also generate a log file, which will flag any errors or configuration statements in the original file that could not be translated to a Kea configuration. We have the modified version of ISC DHCP already more or less done, what we need is the infrastructure and UI to upload, process, and respond back to the user.
|
|
|
|
|
|
**Why**: To help a current user of ISC DHCP migrate to Kea, by generating an equivalent configuration for Kea from an existing ISC DHCP configuration.
|
... | ... | |