... | ... | @@ -4,17 +4,17 @@ Welcome to the Stork 0.13.0 release. This is a development release of the Stork |
|
|
|
|
|
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.
|
|
|
1. **Better handling for large Kea deployments**. Earlier Stork releases were unable to effectively monitor 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 addressing these limitations.
|
|
|
|
|
|
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.
|
|
|
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.
|
|
|
3. **Handling 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.
|
|
|
|
|
|
4. **Major testing efforts**. Stork has been in development for over a year. During that time, we have delivered many new features. To ensure that the project provides high quality software that is maintainable over the long term, we needed to step back and invest some effort in testing capabilities. Previously we had only backend unit-tests. With this release, we added two new significant capabilities. First, we added WebUI unit tests. As of this release, we have 49 such tests. Those tests are now part of our automated CI system #164. Second, we made substantial improvements to the system tests. We now have 7 system tests. Although the number is still small, each system test covers a wide spectrum of features, such as installing or upgrading packages on CentOS and Ubuntu, testing whether it is possible to use the UI to add new user with lower privileges and confirm that the new user is not allowed to create more users, testing Stork with a Kea configuration with many subnets and more #412. The Developer's Guide has been extended #427. Finally, we've improved our internal building and deployment scripts. This change is invisible to users, but it will improve our development process #402, #400.
|
|
|
4. **Major testing efforts**. Stork has been in development for over a year and during that time, we have delivered many new features. To ensure that the project provides high-quality software that is maintainable over the long term, we needed to step back and invest some effort in testing capabilities. Previously we had only backend unit-tests. With this release, we added two new significant capabilities. First, we added WebUI unit tests; as of this release, we have 49 such tests. Those tests are now part of our automated CI system (#164). Second, we made substantial improvements to the system tests, of which we now have seven. Although that number is still small, each system test covers a wide spectrum of features, such as installing or upgrading packages on CentOS and Ubuntu; testing whether it is possible to use the UI to add a new user with lower privileges and confirming that the new user is not allowed to create more users; testing Stork with a Kea configuration with many subnets; and more (#412). The Developer's Guide has been extended (#427). Finally, we've improved our internal building and deployment scripts. This change is invisible to users, but it improves our development process (#402, #400).
|
|
|
|
|
|
5. **UI improvements**. The "see more" link on the dashboard now leads to a subnets view and the subnets are filtered appropriately #389. The HA status information presented on the dashboard and Kea app view was corrected for the cases when the HA had not been configured or the HA state had not been fetched yet. #277
|
|
|
5. **UI improvements**. The "see more" link on the dashboard now leads to a subnets view and the subnets are filtered appropriately (#389). The HA status information presented on the dashboard and Kea app view was corrected for cases when the HA had not been configured or the HA state had not yet been fetched (#277).
|
|
|
|
|
|
6. **Debian 9 support**. A problem with building on Debian 9 has been spotted and fixed. #423
|
|
|
6. **Debian 9 support**. A problem with building on Debian 9 has been spotted and fixed (#423).
|
|
|
|
|
|
Please see this link for known issues: https://gitlab.isc.org/isc-projects/stork/-/wikis/Known-issues.
|
|
|
|
... | ... | @@ -67,7 +67,7 @@ The following summarizes changes and important upgrades since the Stork 0.12.0 r |
|
|
* 114 [bug] godfryd
|
|
|
|
|
|
The links on the dashboard to subnets and shared networks have been
|
|
|
adjuste so they take into account DHCP version. This way subnets and
|
|
|
adjusted so they take into account DHCP version. This way subnets and
|
|
|
shared network pages automatically set filtering by protocol version
|
|
|
based on parameters provided in URL.
|
|
|
(Gitlab #389)
|
... | ... | @@ -75,7 +75,7 @@ The following summarizes changes and important upgrades since the Stork 0.12.0 r |
|
|
* 113 [bug] godfryd
|
|
|
|
|
|
Fixed handling renamed statistics from Kea. In Kea 1.8 some
|
|
|
of the statistics have been renamed, eg. total-addreses
|
|
|
of the statistics have been renamed, e.g. total-addreses
|
|
|
to total-addresses. Now Stork supports both of the cases.
|
|
|
(Gitlab #413)
|
|
|
|
... | ... | @@ -126,7 +126,7 @@ The following summarizes changes and important upgrades since the Stork 0.12.0 r |
|
|
|
|
|
Added documentation for Stork system tests. The documentation
|
|
|
describes how to setup environment for running test tests,
|
|
|
how to run them and how to develope them.
|
|
|
how to run them and how to develop them.
|
|
|
(Gitlab #427)
|
|
|
```
|
|
|
|
... | ... | |