... | ... | @@ -17,7 +17,7 @@ Related requirements: https://gitlab.isc.org/isc-projects/stork/-/issues/158 |
|
|
|
|
|
## 2. Display Kea config (JSON)
|
|
|
|
|
|
[Stork](https://gitlab.isc.org/isc-projects/stork) is a UI/dashboard tool for monitoring [Kea](https://gitlab.isc.org/isc-projects/kea) DHCP server. Kea uses extended JSON (JSON with javascript comments) to store its configuration. An assortment of examples can be found in `doc/examples/kea4` and doc/examples/kea6` in the Kea sources. The Stork server already has the capability to retrieve that information using the existing API (it instructs stork-agent to call `config-get` command on Kea). The retrieved information is then stored on the stork-server in a PostgreSQL database.
|
|
|
[Stork](https://gitlab.isc.org/isc-projects/stork) is a UI/dashboard tool for monitoring [Kea](https://gitlab.isc.org/isc-projects/kea) DHCP server. Kea uses extended JSON (JSON with javascript comments) to store its configuration. An assortment of examples can be found in `doc/examples/kea4` and `doc/examples/kea6` in the Kea sources. The Stork server already has the capability to retrieve that information using the existing API (it instructs stork-agent to call `config-get` command on Kea). The retrieved information is then stored on the stork-server in a PostgreSQL database.
|
|
|
|
|
|
As of March 2021, Stork can show specific elements (networks, subnets, reservations), but lacks the ability to show the whole Kea configuration. We would like to get the ability to display the whole configuration assigned to the specific Kea daemon (DHCP server, Control Agent etc). This feature can be implemented incrementally, starting from the easiest to more sophisticated.
|
|
|
|
... | ... | |