... | ... | @@ -18,7 +18,7 @@ It is ideal that the northbound interfaces support both a graphical display (via |
|
|
|
|
|
| # | Feature | Details | Feasibility | Milestone |
|
|
|
| ------ | ------ | ------ | ------ | ------ |
|
|
|
| 1.1 | IPs | server interface IPs. configured by stork admin. (Bind, kea instances addresses) | | 1 |
|
|
|
| 1.1 | IPs | As an admin I can add Kea and BIND instances (their addresses and some metadata). I also can browse them and search them by particular fields. | | 1 |
|
|
|
| 1.2 | Application(s) installed | User would like to see what applications are installed on each server. (dhcpv4, dhcpv6, ddns, Kea hooks, MySQL/Postgres/Cassandra backend, bind 9 (presumably there can be more than one application per server - certainly there can be multiple Kea hooks installed and configured. Includes *service IP*.| | 1 |
|
|
|
| 1.3 | Application role | User would like to be able to quickly see what is the server's role in the network (Kea:failover primary, failover secondary, failover lb, lease backend, host backend, config backend, BIND zone master, secondary, hidden master, ... configured by stork admin. | | 1 |
|
|
|
| 1.4 | Software versions | OS version running, application version, build#. discovered. Many users will have their own build systems, or use multiple OSes, so the 'version' field may need to include OS, build#, etc & we need to allow for version #s that do not match ISC version numbers in case of OS packages with different numbering systems. Config flags the image was built with. Hooks loaded (Kea hooks, BIND hooks, BIND RPZ plug-in)| | DB backend versions out of scope for 1.0 |
|
... | ... | |