... | ... | @@ -6,7 +6,7 @@ The changes introduced in this version are: |
|
|
|
|
|
1. **Better handling for large Kea deployments**. Earlier Stork releases had problems with monitoring large Kea deployments. One specific failure report mentioned issues with monitoring a Kea installation with 4500 subnets. Processing a response to the ``config-get`` command was very slow, effectively causing the system to hang. This particular problem has been addressed and Stork can now be connected to significantly larger Kea deployments. We are aware of other bottlenecks. In particular, there is one causing high CPU utilization during Kea status updates (see #421). We are working on removing these bottlenecks.
|
|
|
|
|
|
2. **Receiving statistics from Kea 1.8.0**. Some of the DHCPv4 lease statistics were renamed in Kea 1.8.0 and earlier Stork versions did not recognize them. Stork can now recognize both the statistics returned by Kea 1.8.0 and the earlier Kea versions.
|
|
|
2. **Receiving statistics from Kea 1.8.0**. Some of the DHCPv4 lease statistics were renamed in Kea 1.8.0 and earlier Stork versions did not recognize them. Stork can now recognize both the statistics returned by Kea 1.8.0 and the earlier Kea versions #413.
|
|
|
|
|
|
3. **Stork is able to handle IP address changes**. Earlier Stork releases did not properly handle a situation when an address or port of the Kea Control Agent changed. As a workaround, it was possible to remove and add a specific machine again. This is no longer necessary (see #409). Stork now detects Kea Control Agent's IP address/port change and uses the new address/port for further communication.
|
|
|
|
... | ... | |