|
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. **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. 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.
|
|
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.
|
|
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 the cases when the HA had not been configured or the HA state had not been fetched yet. #277
|