... | ... | @@ -4,17 +4,17 @@ Welcome to the Stork 0.12.0 release. This is a development release of the Stork |
|
|
|
|
|
The changes introduced in this version are:
|
|
|
|
|
|
1. **BIND9 fix for multiple addresses**. Previous Stork agents had problems with parsing BIND9 configurations that had more than one addresses specified in their allow lists. This is now fixed #411.
|
|
|
1. **BIND 9 fix for multiple addresses**. Previous Stork agents had problems parsing BIND 9 configurations that had more than one address specified in their allow lists. This is now fixed. #411
|
|
|
|
|
|
1. **Events viewer**. Previous Stork agents were able to display the last 15 events in a small panel in the dashboard. This was useful, but very basic. The capability has been now significantly expanded. The event viewer widget on the dashboard now have paging mechanism, so earlier/later pages can be viewed and there's entirely new full page events viewer #357.
|
|
|
1. **Events viewer**. Previous Stork agents were able to display the last 15 events in a small panel in the dashboard. This was useful, but very basic. The capability has been now significantly expanded: the event viewer widget on the dashboard now has a paging mechanism, so earlier/later pages can be viewed, and there's an entirely new full page events viewer. #357
|
|
|
|
|
|
1. **Breadcrumbs navigation**. Some users have reported that navigating around the Stork UI is sometimes confusing. The newly added breadcrumbs navigation should make it more obvious and the navigation should be more intuitive #337.
|
|
|
1. **Breadcrumbs navigation**. Some users have reported that navigating around the Stork UI can be confusing. The newly added breadcrumbs navigation should make it more obvious and the navigation should be more intuitive. #337
|
|
|
|
|
|
1. **Verbose mode for DB migration**. Stork doesn't publish any DB schema and provides a `stork-db-migrate` tool that does the migration for you. This is more flexible, as over time there will be cases when the schema and data migration requires some processing and cannot be easily done in plain SQL. However, we got a report that on certain systems the schema migration failed and it was difficult to figure out what exactly the problem was. `stork-server` and `stork-db-migrate` now allow you to migrate up and down to specific schema versions and enable logging all queries. #366.
|
|
|
1. **Verbose mode for DB migration**. Stork does not publish any DB schema; it provides a `stork-db-migrate` tool that performs the migration. This is more flexible, as over time there will be cases when the schema and data migration require some processing and cannot be easily done in plain SQL. However, we received a report that on certain systems the schema migration failed and it was difficult to diagnose the problem. `stork-server` and `stork-db-migrate` now allow users to migrate up and down to specific schema versions and enable logging all queries. #366
|
|
|
|
|
|
We now have a solution for two issues reported: the ability to handle large configurations with thousands of subnets #398 and Stork being confused with the Kea IP address changing #409. Both have candidate solutions that are at various stages of reviews. Sadly, we were unable to complete their reviews and testing before the code freeze. However, they're expected to be part of the 0.13 release, expected next month.
|
|
|
We now have a solution for two issues reported: the ability to handle large configurations with thousands of subnets (#398) and no more confusion for Stork if the Kea IP address changed (#409). Both have candidate solutions that are at various stages of review, and they are expected to be part of the 0.13 release, expected next month.
|
|
|
|
|
|
Please see this link for known issues: https://gitlab.isc.org/isc-projects/stork/-/wikis/Known-issues
|
|
|
Please see this link for known issues: https://gitlab.isc.org/isc-projects/stork/-/wikis/Known-issues.
|
|
|
|
|
|
## Release Model
|
|
|
|
... | ... | @@ -53,7 +53,7 @@ Professional support for Stork will become available once it reaches the 1.0 mil |
|
|
Free best-effort support is provided by our user community via a mailing list. Information on all public email lists is available at https://www.isc.org/mailinglists/. If you have any comments or questions about working with Stork, please share them to the stork-users list (https://lists.isc.org/mailman/listinfo/stork-users). Bugs and feature requests may be submitted via GitLab at https://gitlab.isc.org/isc-projects/stork/issues.
|
|
|
|
|
|
## Changes
|
|
|
The following summarizes changes and important upgrades since the Stork 0.11.0 release.
|
|
|
The following summarizes changes and important upgrades since the Stork 0.10.0 release.
|
|
|
|
|
|
```
|
|
|
|
... | ... | |