... | ... | @@ -36,7 +36,7 @@ Since you're logged in as super-admin, you can see the `Configuration` menu and |
|
|
|
|
|
## 4. Add new BIND9 machine to monitor
|
|
|
|
|
|
Go to `Services`->`Machines` and switch to `Unauthorized` machines view (top-right corner). Now click the action button in `agent-bind9` machine and then click `Authorize` in the menu.
|
|
|
Go to `Services`->`Machines` and switch to `Unauthorized` machines view (top-right corner). Now click the action button in `agent-bind9` machine and then click `Authorize` in the menu. And then switch back to `Authorized` machines.
|
|
|
|
|
|
In the demo, there are several docker containers simulating machines with Kea and BIND in various modes of operation. agent-bind9 is the name of one of such containers. Note that you didn't specify what kind of software is running on the `agent-bind9` machine. Stork server connected to the stork agent running there and the agent looked for Kea and BIND 9 and found only BIND 9. It should detect BIND 9 app running there.
|
|
|
|
... | ... | @@ -46,13 +46,13 @@ Click around. As of 0.9 the BIND capabilities are basic. Stork is able to check |
|
|
|
|
|
## 6. Add new Kea machine to monitor
|
|
|
|
|
|
Go to `Services`->`Machines` and click `Add New Machine`, type in `agent-kea`. The procedure is the same as before, but this time Stork detected Kea servers running. Notice that a problem is reported.
|
|
|
Go to `Services`->`Machines` and switch to `Unauthorized` machines view (top-right corner). Now click the action button in `agent-kea` machine and then click `Authorize` in the menu. And then switch back to `Authorized` machines. The procedure is the same as before, but this time Stork detected Kea servers running. Notice that a problem is reported.
|
|
|
|
|
|
Kea is being shipped with CA (Control Agent) preconfigured with control sockets for DHCPv4, DHCPv6 and DDNS. This simplifies deployment. In this particular Kea deployment only DHCPv4 daemon is installed. CA tries to connect to all of those daemons and continues with only those that respond. That makes it easy to deploy daemons selectively. However, Stork looks at the CA config and determines that there are 3 daemons expected, but only DHCPv4 is running. The other ones are greyed out and on their tab there is information that Stork agent cannot communicate with them. As this is initial situation Stork concludes that this is as expected and switches of monitoring of these daemons, only DHCPv4 is monitored and its status is green.
|
|
|
Kea is being shipped with CA (Control Agent) preconfigured with control sockets for DHCPv4, DHCPv6 and DDNS. This simplifies deployment. In this particular Kea deployment only DHCPv4 daemon is installed. CA tries to connect to all of those daemons and continues with only those that respond. That makes it easy to deploy daemons selectively. However, Stork looks at the CA config and determines that there are 3 daemons expected, but only DHCPv4 is running. The other ones are greyed out and on their tab there is information that Stork agent cannot communicate with them. As this is the initial situation Stork concludes that this is as expected and switches of monitoring of these daemons, only DHCPv4 is monitored and its status is green.
|
|
|
|
|
|
## 7. Inspect Kea details
|
|
|
|
|
|
You can either click on the Version on the Kea apps list or click of the machine and the link to details in the Kea app panel on the machine details page. Note the Kea version being returned and a list of currently loaded hooks. List of subnets is displayed as well.
|
|
|
You can either click on the Version on the Kea apps list or click on the machine and the link to details in the Kea app panel on the machine details page. Note the Kea version being returned and a list of currently loaded hooks. A list of subnets is displayed as well.
|
|
|
|
|
|
Note that the Kea app running on agent-kea does not have HA enabled, so HA status is not displayed.
|
|
|
|
... | ... | |