... | ... | @@ -41,7 +41,9 @@ Since you're logged in as super-admin, you can see the `Configuration` menu and |
|
|
|
|
|
### 4. Add new Kea machine to monitor
|
|
|
|
|
|
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.
|
|
|
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.
|
|
|
|
|
|
In the demo, there are several docker containers simulating machines with Kea and BIND in various modes of operation. `agent-kea` is the name of one of such containers. Note that you didn't specify what kind of software is running on the `agent-kea` machine. Stork server connected to the stork agent running there and the agent looked for Kea and BIND 9 and found only DHCPv4 deamon and Control Agent (CA) of Kea.
|
|
|
|
|
|
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 off monitoring of these daemons, only DHCPv4 is monitored and its status is green.
|
|
|
|
... | ... | @@ -49,13 +51,18 @@ Kea is being shipped with CA (Control Agent) preconfigured with control sockets |
|
|
|
|
|
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.
|
|
|
|
|
|
Note that the Kea app running on agent-kea does not have HA enabled, so HA status is not displayed.
|
|
|
The sample Kea configuration has couple reservations, subnets, and shared networks that you can inspect here. You can also review full Kea configuration by clicking "Raw configuration".
|
|
|
|
|
|
The `Data Storage` section comprises information about various files used by the particular Kea instance and its database backends. The DHCPv4 server on `agent-kea` uses MySQL lease and config backend. The DHCPv6 server on `agent-kea6` uses PostgreSQL lease backend. Authorize these machines and navigate the respective Kea apps to see how the backends are presented.
|
|
|
|
|
|
Note that the Kea app running on agent-kea does not have HA enabled, so HA status is not displayed. We will get to this in later parts of the demo.
|
|
|
|
|
|
The sample Kea configuration has couple subnets that you can inspect here.
|
|
|
If the demo is started with the `CS_REPO_ACCESS_TOKEN`, the `agent-kea-premium` machine with paid Kea hooks libraries will be created for experiments with hooks. Authorize it and navigate to the Kea view for that machine. Its `Data Storage` section includes a location of the forensic logging files generated by the Kea server.
|
|
|
|
|
|
The `Data Storage` section comprises information about various files used by the particular Kea instance and its database backends. The DHCPv4 server on agent-kea uses MySQL lease and config backend. The DHCPv6 server on agent-kea6 uses PostgreSQL lease backend. Authorize these machines and navigate the respective Kea apps to see how the backends are presented.
|
|
|
You can inspect configured logs. If those logs write to local files, Stork agent can retrieve and display them for you.
|
|
|
|
|
|
Stork can also do configuration review. For the `agent-kea` machine, everything looks good, but there are other machines that have their configuration suboptimal.
|
|
|
|
|
|
If the demo is started with the `cs_repo_access_token`, the agent-kea-premium machine with paid Kea hooks libraries can be monitored. Authorize it and navigate to the Kea view for that machine. Its `Data Storage` section includes a location of the forensic logging files generated by the Kea server.
|
|
|
|
|
|
### 6. Add two Kea servers that work as HA pair
|
|
|
|
... | ... | @@ -65,7 +72,7 @@ You can now inspect the HA status of those servers. Note the difference between |
|
|
|
|
|
Optionally, you may want to connect to simulate one of the Kea servers crashing and observe how the surviving Kea server detects the problem and how Stork provides extra insight into what's happening.
|
|
|
|
|
|
As of 0.12, the Stork Environment Simulator listening on <http://localhost:5000/> (this available in demo only) allows you to conveniently stop and start services to simulate all sorts of failures. Go ahead and kill one of the kea-dhcp4 daemons. Alternatively, you can do it yourself. Open a new console. Make sure you are in the Stork directory where the demo is being run, then connect to the docker machine and use kill command to abruptly stop kea.
|
|
|
As of now, the Stork Environment Simulator listening on <http://localhost:5000/> (this is available in demo only) allows you to conveniently stop and start services to simulate all sorts of failures. Go ahead and kill one of the kea-dhcp4 daemons. Alternatively, you can do it yourself. Open a new console. Make sure you are in the Stork directory where the demo is being run, then connect to the docker machine and use kill command to abruptly stop kea.
|
|
|
|
|
|
```plaintext
|
|
|
# Make sure this is the directory where you run `rake docker_up` from.
|
... | ... | @@ -96,6 +103,8 @@ To restart Kea, use the following command: |
|
|
|
|
|
You can now logout from the docker image using `exit` or by pressing ctrl-d.
|
|
|
|
|
|
The
|
|
|
|
|
|
### 7. DHCPv6 support
|
|
|
|
|
|
Stork fully supports IPv6 from the day one. Add another machine called `agent-kea6`. Notice the IPv6 subnet and several pools.
|
... | ... | |