... | ... | @@ -20,6 +20,8 @@ UC6: **Reverting changes** - The sysadmin implemented a change and users started |
|
|
|
|
|
UC7: **Audit** - In a larger deployment, there is a group of admins. There should be an audit trail of who implemented given change. There should be some history of the configuration elements being changed.
|
|
|
|
|
|
UC8: **Planning changes** - In more complex environments, larger and strategic changes are planned in advance. It should be possible to prepare new configuration, but not apply it immediately and define a point in time where it should be deployed. Examples: renumber to new ISP, retire old printer/router/etc.
|
|
|
|
|
|
## Configuration aspects
|
|
|
|
|
|
Kea configuration is incredibly complicated. It is unlikely that every knob would get a graphical representation in Stork. However, there are some configuration elements that are more important than others. The primary determining factor is frequency of changes. For example, adding or changing new host reservation is typically a frequent event, often happening many times per day. On the other hand, network interface is something that's typically set up once and then never changed. The following list is a recommended implementation order for the management capabilities:
|
... | ... | |