... | ... | @@ -31,8 +31,8 @@ Configuration tracking may sound a bit complicated, but Stork already stores the |
|
|
|
|
|
Here's a high level sketch of tasks required to complete phase 1:
|
|
|
|
|
|
- Evaluate if stork-server code (written in go) provides an API to make the configuration available. The Kea config information is there and there are API calls (such as `/hosts`, `/overview`, `/shared-networks` and `/subnets`) that return specific fragments of the configuration, but most likely there will be a need to implement new API call that return it as a whole JSON structure.
|
|
|
- Extend the Angular interface to visualize the Kea configuration. The visualization can be simple for now, but it should be extensible, so the more complicated tasks would be possible in the future. See Phase 2 and 3 above. The current Stork interface is implemented using AngularJS 9 (migration to 10 is planned) with extensive used of PrimeNG library.
|
|
|
- Evaluate if stork-server code (written in go) provides an API to make the configuration available. The Kea config information is there and there are API calls (such as `/hosts`, `/overview`, `/shared-networks` and `/subnets`) that return specific fragments of the configuration, but most likely there will be a need to implement new API call that returns it as a whole JSON structure.
|
|
|
- Extend the Angular interface to visualize the Kea configuration. The visualization can be simple for now, but it should be extensible, so the more complicated tasks would be possible in the future. See Phase 2 and 3 above. The current Stork interface is implemented using AngularJS 9 (migration to 10 is planned) with extensive use of the [PrimeNG](https://www.primefaces.org/primeng/) library. Use of existing libraries with compatible licenses is encouraged.
|
|
|
- The solution should have unit tests (see [Stork ARM Sections 5.6 and 5.7](https://kea.readthedocs.io/projects/Stork/en/v0.15.0/devel.html) )
|
|
|
- The solution should have adequate code comments
|
|
|
- The patch will go through a normal review that applies to all existing Stork developers. The process is [described here](https://gitlab.isc.org/isc-projects/stork/-/wikis/Processes/gitlab-howto).
|
... | ... | |