... | ... | @@ -4,7 +4,7 @@ Welcome to the Stork 0.14.0 release. This is a development release of the Stork |
|
|
|
|
|
The changes introduced in this version are:
|
|
|
|
|
|
* **Large configuration handling**: Stork 0.14 is now much better suited for handling large configurations, e.g. with several thousand subnets. The process of adding new subnets has been greatly streamlined and now takes much less time. Subnets are now indexed (#421). Another problem solved was that the Stork server triggered the periodic configuration pull too early. If the initial update took a long time, the first periodic renewal was kicked off early and was intervening. This race condition is fixed (#446). Furthermore, Stork's periodic configuration pull is now smarter. It calculates a hash and is able to detect a configuration change, bypassing unnecessary processing in the very likely case of the configuration not changing (#460).
|
|
|
* **Large configuration handling**: Stork 0.14 is now much better suited for handling large configurations, e.g. with several thousand subnets. The process of adding new subnets has been greatly streamlined and now takes much less time. Subnets are now indexed (#421). Another problem solved was that the Stork server triggered the periodic configuration pull too early. If the initial update took a long time, the first periodic renewal kicked off before the initial update was complete. This race condition is fixed (#446). Furthermore, Stork's periodic configuration pull is now smarter. It calculates a hash and is able to detect a configuration change, bypassing unnecessary processing in the very likely case of the configuration not changing (#460).
|
|
|
|
|
|
* **Reconfigure events**: Stork now records the reconfiguration events detected in Kea. The information about the user who authorized the change is not logged. This information may be added in a future Stork release (#353, #460).
|
|
|
|
... | ... | |