# Stork 0.3.0, January 10th, 2020, Release Notes

Welcome to the Stork 0.3.0 release. This is the third development release 
of the Stork project, which aims at providing a modern, responsive, and 
scalable dashboard solution with a well-defined REST API interface. The 
long-term goal of the project is to provide a monitoring and management 
solution for BIND 9, Kea DHCP, and more.

Features introduced in this version:

1. **BIND 9 discovery**. The BIND 9 applications are discovered on the 
machines monitored by Stork and their version and status are presented in 
the UI.

2. **Kea High Availability monitoring**. Basic High Availability (HA) 
status monitoring is available for the Kea DHCP servers running on the 
machines monitored by Stork that have the HA functionality enabled via the 
libdhcp_ha.so hooks library. The presented information includes the roles 
of the HA partners, their current state, and whether they currently serve 
DHCP clients, a.k.a. served scopes. The displayed status is periodically 
refreshed.

3. **User password**. A logged user can now change his or her own 
password. Also, two administrative groups have been defined: super-admin 
and admin. The former group has full control over the system; the latter 
has the same privileges except that the users belonging to this group are 
not allowed to manage other users' accounts.

4. **Basic dashboard**. The dashboard presented after signing in to the 
system includes the counts of applications currently monitored by the 
system and the counts of applications with any potential problems. For 
example, a Kea application for which only the DHCPv4 daemon is running 
when both DHCPv4 and DHCPv6 daemons are expected is flagged as having 
problems.

## Release Model

Stork has monthly development releases on the first Wednesday of each 
month (with some exceptions around holidays). The first major release, 
version 0.8, is planned for the spring of 2020.

We encourage users to test the development releases and report back their 
findings on the stork-dev mailing list, available at 
https://lists.isc.org/mailman/listinfo/stork-dev.

This text references issue numbers. For more details, visit the Stork 
GitLab page at https://gitlab.isc.org/isc-projects/stork/issues.

## License
This version of Stork is released under the Mozilla Public License, 
version 2.0.

   https://www.mozilla.org/en-US/MPL/2.0

## Download
The Stork source and PGP signature for this release may be downloaded from:

   https://ftp.isc.org/isc/stork

The signature was generated with the ISC code signing key which is 
available at:

   https://www.isc.org/pgpkey

ISC provides documentation in the Stork Administrator Reference Manual. It 
is currently available only in the source form in the docs/ directory. To 
build it, you need the Sphinx tool. This is expected to change in a future 
release. 

We ask users of this software to please let us know how it worked for you 
and what operating system you tested on. Feel free to share your feedback 
on the stork-dev mailing list 
(https://lists.isc.org/mailman/listinfo/stork-dev).  We would also like to 
hear whether the documentation is adequate and accurate. Please open 
tickets in the Stork GitLab project for bugs, documentation omissions and 
errors, and enhancement requests. We want to hear from you even if 
everything worked.

## Support
Professional support for Stork will become available once it reaches the 
1.0 milestone. Existing ISC customers that consider themselves *very* 
early adopters may get involved in the development process, including 
roadmap, features planning, and early testing, but the software maturity 
level does not constitute a typical professional service before the 1.0 
milestone.

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-dev List 
(https://lists.isc.org/mailman/listinfo/stork-dev). 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 upgrade notes since the 
Stork 0.2.0 release.

* 23 [func] godfryd

    Added presenting number of all and misbehaving applications
    on the dashboard page. If there are no applications added yet,
    the dashboard redirects to the list of connected machines.
    (Gitlab #120)

* 22 [doc] marcin
  
    Updated Stork ARM. Added documentation of the High Availability
    status monitoring with Kea. Added new sections describing applications
    management.
    (Gitlab #122)

* 21 [func] godfryd

    Added new Rake tasks to build and start two containers
    with Kea instances running as High Availability partners.
    (Gitlab #126)

* 20 [func] matthijs

    Add BIND 9 application to Stork.  Detects running BIND 9
    application by looking for named process.  Uses rndc to retrieve
    version information.
    (Gitlab #106)

* 19 [func] marcin

    Kea High Availability status is presented on the Kea application page.
    (Gitlab #110)

* 18 [func] marcin

    Logged user can now change his/her password. Also, users can be
    associated with one of the two default permission groups: super-admin
    and admin. The former can manage users' accounts. The latter is not
    allowed to manage other users' accounts.
    (Gitlab #97)

* 17 [func] marcin

    Implemented a mechanism by which it is possible to send a command
    from the Stork server to Kea via Stork Agent and Kea Control
    Agent.
    (Gitlab #109)

Thank you again to everyone who assisted us in making this release 
possible. 

We look forward to receiving your feedback.