... | ... | @@ -2,21 +2,21 @@ |
|
|
|
|
|
Welcome to Stork 1.3.0, another development release. The changes introduced in this version are:
|
|
|
|
|
|
**Kea Configuration Management: host reservations**. The long term goal is provide the ability in Stork to manage most aspects of Kea configuration. It is now possible to create subnet-level or global host reservations in one or multiple Kea servers. This can be done using a button on the host reservations page [#717, #720, #729].
|
|
|
**Kea Configuration Management: host reservations**. The long-term goal is for Stork to be able to manage most aspects of Kea configuration. It is now possible to create subnet-level or global host reservations in one or more Kea servers, via a button on the host reservations page [#717, #720, #729].
|
|
|
|
|
|
**Build improvements**. A substantial effort has been put into the Rake-based build system. The rake tasks were reorganized in into several namespaces. As a result, the Stork images are built faster, with a smaller footprint and the task names are much more uniformly named [#709]. This substantial change also addressed several other problems. A problem with building with premium hooks has been fixed [#684]. The deploy mechanism (currently used internally by ISC) has been fixed [#719]. The rake tasks related to testing are now consistent [#436]. There is now a way (`rake check`) to check if dependencies for building Stork are available [#21, #437]. The tasks have better comments [#489]. The installation using rake (`rake install:server`, `rake install:agent`) has been redone and it now installs the necessary files in the default locations [#653]. The rake task for running an agent can now optionally use a custom port (`rake run:agent PORT=4242`) [#660].
|
|
|
**Build improvements**. A substantial effort has been put into the Rake-based build system. The Rake tasks were reorganized into several namespaces; as a result, the Stork images are built faster, with a smaller footprint, and the task names are much more uniform [#709]. This substantial change also addressed several other problems. A problem with building with premium hooks has been fixed [#684]. The deploy mechanism (currently used internally by ISC) has been fixed [#719]. The Rake tasks related to testing are now consistent [#436]. There is now a way (`rake check`) to verify whether dependencies for building Stork are available [#21, #437]. The tasks have better comments [#489]. The installation using Rake (`rake install:server`, `rake install:agent`) has been redone and now installs the necessary files in the default locations [#653]. The Rake task for running an agent can now optionally use a custom port (`rake run:agent PORT=4242`) [#660].
|
|
|
|
|
|
**Restart Stork service on failure**. The systemd services are now automatically restarted on failure [#721]. Thank you to Kevin Fleming for the patch!
|
|
|
|
|
|
**Documentation**. The Stork ARM and the log messages have been edited for clarity and consistency [#718].
|
|
|
**Documentation**. The Stork ARM and log messages have been edited for clarity and consistency [#718].
|
|
|
|
|
|
**Improved machine dump readability**. Special characters are no longer escaped in machine dumps, for better readability [#665].
|
|
|
**Improved machine-dump readability**. Special characters are no longer escaped in machine dumps, for better readability [#665].
|
|
|
|
|
|
Please see this link for known issues: https://gitlab.isc.org/isc-projects/stork/-/wikis/Known-issues.
|
|
|
|
|
|
## Incompatible Changes
|
|
|
|
|
|
**Different Rakefile tasks** The name of the rake tasks used in development automation have changed as a result of the refactorization. Run `rake --tasks` to get the new set of tasks.
|
|
|
**Different Rakefile tasks** The names of the Rake tasks used in development automation have changed as a result of the refactorization. Run `rake --tasks` to get the new set of tasks.
|
|
|
|
|
|
## Release Model
|
|
|
|
... | ... | |