... | @@ -34,7 +34,10 @@ Many command-line tools offer options for remote management. For example: `psql` |
... | @@ -34,7 +34,10 @@ Many command-line tools offer options for remote management. For example: `psql` |
|
We should run the tool on the same machine as the managed application and control it over the `stork-agent`. The tools are often installed together with the managed applications. For example, the `mysql` client is often installed with the database server, `kea-admin` is installed with Kea. In that case, the Stork server does not need installing tools local to the server. It can simply use the tools available on the managed machines. Secondly, some tools may not provide remote management capabilities. Such tools must be controlled via the `stork-agent`. Having one philosophy in that regard simplifies Stork logic.
|
|
We should run the tool on the same machine as the managed application and control it over the `stork-agent`. The tools are often installed together with the managed applications. For example, the `mysql` client is often installed with the database server, `kea-admin` is installed with Kea. In that case, the Stork server does not need installing tools local to the server. It can simply use the tools available on the managed machines. Secondly, some tools may not provide remote management capabilities. Such tools must be controlled via the `stork-agent`. Having one philosophy in that regard simplifies Stork logic.
|
|
|
|
|
|
## Configuration Capabilities
|
|
## Configuration Capabilities
|
|
TBD
|
|
|
|
|
|
This term (short "caps") stands for Stork's ability to control various configuration aspects of an application. The presence or absence of the configuration capability (abbreviated "CC") depends on the specifics of an application. Typically, however, it is determined by the presence or absence of a command-line tool or REST API commands. In the Kea world, certain hook libraries' presence often determines the capabilities, but not always. Suppose a Kea DHCP server is connected to the Config Backend. Even if this server has the `subnet_cmds` hook library, the capability to send the commands over this hook library is disabled (absent) because the `subnet_cmds` hook library must not be used with the Config Backend. It is an example of a more complex algorithm to determine the configuration capability.
|
|
|
|
|
|
|
|
Stork should determine caps for each application when the app is first connected to Stork and every time Stork updates the application's state information (using the state puller). Next, it should make the caps available over the REST API to the client to enable and disable specific configuration controls and views in the UI.
|
|
|
|
|
|
## System Views
|
|
## System Views
|
|
TBD
|
|
TBD
|
... | | ... | |