... | ... | @@ -88,7 +88,10 @@ CM must ensure that User1 edits the current Kea configuration. Thus, it first se |
|
|
|
|
|
Note that `config-get` command can put a heavy load on the Kea server to prepare the response, depending on the configuration size. Thus, we should consider an optimization that the `stork-agent` reads the Kea configuration file contents from the disk instead. It is only viable in cases when we are sure that the configuration has been created by Kea (i.e., as a result of the `config-write` command) because, in this case, it contains the entire runtime configuration. If an administrator has created the configuration file, it often omits some configuration parameters, relying on the default values.
|
|
|
|
|
|
After receiving the current configuration from Kea, CM should check if it has changed since the last fetch. It next creates a new revision in the Stork database if it has changed. It next returns the configuration to the user for edits. The user can safely edit the configuration because it is locked and available exclusively to this user. The user applies the edited configuration to the server (CM).
|
|
|
After receiving the current configuration from Kea, CM should check if it has changed since the last fetch. It next creates a new revision in the Stork database if it has changed. It next returns the configuration to the user for edits. The user can safely edit the configuration because it is locked and available exclusively to this user. The user applies the edited configuration to the server (CM). One of the ways the user can modify the configuration is by opening the online editor (PrimeNG has one):
|
|
|
|
|
|
![Zrzut_ekranu_2022-02-10_o_18.30.28](uploads/de8f4b068301f987c8e486583f320886/Zrzut_ekranu_2022-02-10_o_18.30.28.png)
|
|
|
|
|
|
|
|
|
CM begins the configuration dry run using the `config-test` command. The Kea server verifies its correctness without actually applying it. If the configuration is ok, the CM sends it again in the `config-set`. Then, it commits the configuration with the `config-write` command. CM saves the updated configuration as a next revision in the Stork database if there are no errors. It ends the update process, and the configuration is unlocked in the CM. Another user can now begin an update.
|
|
|
|
... | ... | |