... | ... | @@ -8,7 +8,7 @@ This release adds new features, improves existing features, clarifies documentat |
|
|
|
|
|
**Setting lease time for client classes.** Earlier Kea versions allowed to set different lease lifetimes depending on where the device was located in your network (using the global, network, or subnet levels). However, it was impossible to change the lifetime based on device type. This missing capability is now implemented for IPv4, with IPv6 support coming up soon #1635.
|
|
|
|
|
|
**TLS support work in progress.** The Kea team continues its work on TLS implementation in Kea. The ultimate goal is for CA to be able to accept https connections. While the TLS solution is now usable yet, the work is definitely picking up the pace with several important milestones being completed. There are now several new parameters available in Control Agent (CA) configuration: `trust-anchor`, `cert-file`, `key-file` and `cert-required`. The parameters can be configured, but they are not used yet. A new config example `doc/examples/agent/https.json` has been added with some commentary #1662. Another under the hook change updated the asiolink library to be able to handle the new TLS socket type. This is not a user-visible change #1644.
|
|
|
**TLS support work in progress.** The Kea team continues its work on TLS implementation in Kea. The ultimate goal is for CA to be able to accept https connections. While the TLS solution is not usable yet, the work is definitely picking up the pace with several important milestones being completed. There are now several new parameters available in Control Agent (CA) configuration: `trust-anchor`, `cert-file`, `key-file` and `cert-required`. The parameters can be configured, but they are not used yet. A new config example `doc/examples/agent/https.json` has been added with some commentary #1662. Another under the hook change updated the asiolink library to be able to handle the new TLS socket type. This is not a user-visible change #1644.
|
|
|
|
|
|
**DB cluster improvements.** Kea never officially supported any DB clustering solutions. Nevertheless, people used clusters with varying results. ISC team began experiments with several clustering solutions: Galera, Percona, NDB, and group replication. While we don't officially any of them yet, we are gaining experience and testing many scenarios right now. Those experiments reached a stage where we are able to set up clusters and run unit and system tests. The first two improvements are related to our MySQL libraries to better run on the Percona cluster. One ticket updated the MySQL schema with the primary key for forensic logging (#1709), while another fixed several problems in unit tests that manifested themselves only on Percona (#1708). Finally, we are getting ready to run performance tests of multiple Kea instances connected to the DB cluster. To do that reliably, we need to export the list of leases assigned by each instance and then correlate them to check for any duplicates. With that in mind, we extended `perfdhcp` tool with the ability to export the list of assigned leases. We hope to make good use of that capability in future tests #1703.
|
|
|
|
... | ... | |