... | ... | @@ -65,7 +65,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.
|
|
|
|
|
|
You may 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 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 youself. 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.
|
|
|
|
|
|
```
|
|
|
# Make sure this is the directory where you run `rake docker_up` from.
|
... | ... | @@ -143,13 +143,24 @@ Grouping subnets into shared networks is a very popular feature in Kea and other |
|
|
|
|
|
16. **DHCP Dashboard**.
|
|
|
|
|
|
One of easily missed features of Stork is its dashboard. Make sure you click on the Stork logo (or the Stork name next to it). This is a high level overview of all the things being currently monitored. If you followed the demo, you should see something similar to this:
|
|
|
One of easily missed features of Stork is its dashboard. Make sure you click on the Stork logo (or the Stork name next to it). Since 0.10, there is also an explicit link in the DHCP menu. This is a high level overview of all the things being currently monitored. If you followed the demo, you should see something similar to this:
|
|
|
|
|
|
![dashboard-0.9-2](uploads/fe59d09250b42dcc550f8b0cfe0d7cd7/dashboard-0.9-2.png)
|
|
|
![dashboard](uploads/2edf278e2c20f5558c230551e0764c2c/dashboard.png)
|
|
|
|
|
|
The list of subnets shows top 5 subnets with highest pool utilization. There's a list of events on the right hand side. If you configured Grafana, you will see links to Grafana to inspect historic values for subnets and how they changed over time.
|
|
|
|
|
|
17. **Grafana**
|
|
|
17. **Events**
|
|
|
|
|
|
Stork records various events in the system. There are several places where you can observe events;
|
|
|
|
|
|
1. The dashboard - here you can see the latest 15 events in the whole networks being monitored.
|
|
|
1. The Machine view - here you can the events related to this specific machine
|
|
|
1. Events viewer - this is a full page event viewer, which lets you filter events by severity, machine, app type, daemon and for the events that were results of user's actions - also by user.
|
|
|
|
|
|
![events-viewer](uploads/11439438bb815b1f4e6a93d76177d082/events-viewer.png)
|
|
|
|
|
|
|
|
|
18. **Grafana**
|
|
|
|
|
|
An early Grafana integration was introduced in 0.5. In 0.9, you can go to `Configuration` and `Settings` and set up the link to your Grafana. In case of demo, type in `http://localhost:3000` (if running the demo locally) or `http://stork.lab.isc.org:3000` (if using on stork.lab). Go to http://localhost:3000 or http://stork.lab.isc.org:3000 and log in using admin/admin credentials. Please don't change the password, so the next person viewing the demo can take a look, too.
|
|
|
|
... | ... | @@ -165,32 +176,25 @@ We're currently using third party exporter together with a Stork embedded export |
|
|
|
|
|
Click on Home and then Stork Bind DNS dashboard. There are some generic statistics, as well as the Cache Hit Ratio/Hit/Miss statistics provided by Stork. More are coming in future Stork releases.
|
|
|
|
|
|
18. **You can change your own password**.
|
|
|
|
|
|
Go to `Profile` -> `Settings`.
|
|
|
|
|
|
19. **Change other users password**.
|
|
|
|
|
|
If you're a super-admin, you can change others passwords. Log in as super-admin (e.g. admin user), click on `Configuration` -> `Users` and then on the user you want to modify. Click `Edit`.
|
|
|
|
|
|
20. **You can delete machines**.
|
|
|
|
|
|
Go to `Services` -> `Machines` and pick a machine you want to have deleted. Click on the hamburger button (three horizontal lines) on the right hand and choose `Delete` from the menu. Note anything running on the machine will disappear from Stork. The actual services running won't be affected, Stork simply stopped monitoring them. You can re-add them to see that they're doing fine.
|
|
|
19. **Other tasks**.
|
|
|
|
|
|
21. **Check Stork version**.
|
|
|
Here's a list of smaller things you can do.
|
|
|
|
|
|
You can hover your mouse over the Stork logo. It will display some information about Stork itself (version, compilation time).
|
|
|
1. **change your password** by going to `Profile` -> `Settings`.
|
|
|
2. **change others password*. If you're a super-admin, you can change others passwords. Log in as super-admin (e.g. admin user), click on `Configuration` -> `Users` and then on the user you want to modify. Click `Edit`.
|
|
|
3. **delete machines**. Go to `Services` -> `Machines` and pick a machine you want to have deleted. Click on the hamburger button (three horizontal lines) on the right hand and choose `Delete` from the menu. Note anything running on the machine will disappear from Stork. The actual services running won't be affected, Stork simply stopped monitoring them. You can re-add them to see that they're doing fine.
|
|
|
4. **Check Stork version**. You can hover your mouse over the Stork logo. It will display some information about Stork itself (version, compilation time).
|
|
|
|
|
|
## Wrapping up
|
|
|
|
|
|
Once you're done, please clean up, so the the next person starts from scratch:
|
|
|
Once you're using the stork.lab service, please clean up, so the the next person starts from scratch:
|
|
|
|
|
|
- stop any traffic generator
|
|
|
- delete all machines
|
|
|
|
|
|
# Feedback
|
|
|
|
|
|
Stork in very early stages and is being developed rapidly. Your feedback is essential. Please go to Stork project page and report new issues or add your comments to existing ones. In particular, we're interested in:
|
|
|
Stork in early stages and is being developed rapidly. Your feedback is essential. Please go to Stork project page and report new issues or add your comments to existing ones. In particular, we're interested in:
|
|
|
|
|
|
- things that are non-intuitive, broken, confusing
|
|
|
- missing functionalities you'd like to see (we're aware of many, please search the existing issues and +1 or comment on existing ones)
|
... | ... | |