... | ... | @@ -4,15 +4,15 @@ 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 attaching to large Kea deployments. One specific failure report mentioned issues with attaching Kea installation with 4500 subnets for which 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, the one causing high CPU utilization during the Kea status update (see #421). We are working on removing these bottlenecks.
|
|
|
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. **WAITING FOR #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 has 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 this new address/port for further communication.
|
|
|
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.
|
|
|
|
|
|
4. **Major testing efforts**. Stork has been in development for over a year now. During that time, we delivered many new features at rapid pace. To ensure that the project provides high quality software that is maintainable in a long term, we needed to step back and invest some effort in the 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 42 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 UI to add new user with lower privileges and confirm that new user is not allowed to create more users, testing Stork with 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. 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 42 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.
|
|
|
|
|
|
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 has not been configured or the HA state has 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 the cases when the HA had not been configured or the HA state had not been fetched yet. #277
|
|
|
|
|
|
6. **Debian 9 support**. A problem with building on Debian 9 has been spotted and fixed. #423
|
|
|
|
... | ... | @@ -20,7 +20,7 @@ Please see this link for known issues: https://gitlab.isc.org/isc-projects/stork |
|
|
|
|
|
## Release Model
|
|
|
|
|
|
Stork has monthly development releases on the first Wednesday of each month (with some exceptions around holidays), although we sometimes delay it a bit for last-minute changes.
|
|
|
Stork has monthly development releases, with some exceptions.
|
|
|
|
|
|
We encourage users to test the development releases and report back their findings on the stork-users mailing list, available at https://lists.isc.org/mailman/listinfo/stork-users.
|
|
|
|
... | ... | |