... | @@ -5,7 +5,7 @@ This page describes a self-demo that you can run on Stork. To run it you need on |
... | @@ -5,7 +5,7 @@ This page describes a self-demo that you can run on Stork. To run it you need on |
|
- access to http://stork.lab.isc.org:8080 (ISC employees only)
|
|
- access to http://stork.lab.isc.org:8080 (ISC employees only)
|
|
- an Ubuntu box (download stork, type ``rake docker_up``, connect to http://locahost:8080)
|
|
- an Ubuntu box (download stork, type ``rake docker_up``, connect to http://locahost:8080)
|
|
|
|
|
|
Once Stork becomes a bit more mature, we're planning to have a public demo site.
|
|
Once Stork becomes a bit more mature, we're planning to have a public demo site. Stork documentation is available at https://stork.readthedocs.io. It may be useful during this self-guided tour.
|
|
|
|
|
|
# Existing functionality
|
|
# Existing functionality
|
|
|
|
|
... | @@ -21,7 +21,7 @@ Note: as of 0.3 there are currently two roles defined: super-admin (can do every |
... | @@ -21,7 +21,7 @@ Note: as of 0.3 there are currently two roles defined: super-admin (can do every |
|
|
|
|
|
Normally you would type in an FQDN or an IP address of the machine you want to monitor. By default Stork is being deployed using Docker. There are some example docker containers that run several sample machines that run Kea, BIND9 and two Kea instances running in failover pair. agent-bind9 is a 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 that and the agent looked for Kea and BIND9 and found only bind. It should detect BIND9 app running there.
|
|
Normally you would type in an FQDN or an IP address of the machine you want to monitor. By default Stork is being deployed using Docker. There are some example docker containers that run several sample machines that run Kea, BIND9 and two Kea instances running in failover pair. agent-bind9 is a 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 that and the agent looked for Kea and BIND9 and found only bind. It should detect BIND9 app running there.
|
|
|
|
|
|
5. **Inspect the agent-bind9 machine**. Click around. As of 0.3 the BIND9 capabilities are basic. Stork is able to check if bind9 process is running and display its version. Much more coming up in 0.4.
|
|
5. **Inspect the agent-bind9 machine**. Click around. As of 0.3 the BIND9 capabilities are basic. Stork is able to check if bind9 process is running and display its version, number of zones configured, time since it last reconfiguration and more.
|
|
|
|
|
|
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.
|
|
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.
|
|
|
|
|
... | @@ -33,19 +33,25 @@ Stork developers have several ideas how to deal with the situation, but we'd lov |
... | @@ -33,19 +33,25 @@ Stork developers have several ideas how to deal with the situation, but we'd lov |
|
|
|
|
|
Note that the Kea app running on agent-kea does not have HA enabled, so HA status is not displayed.
|
|
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 one subnet that you can inspect here.
|
|
|
|
|
|
8. **Add two Kea servers that work as HA pair**. Go to `Services`->`Machines` and click `Add New Machine`, and add `agent-kea-ha1`. Repeat for `agent-kea-ha2`.
|
|
8. **Add two Kea servers that work as HA pair**. Go to `Services`->`Machines` and click `Add New Machine`, and add `agent-kea-ha1`. Repeat for `agent-kea-ha2`.
|
|
|
|
|
|
You can now inspect the HA status of those servers.
|
|
You can now inspect the HA status of those servers.
|
|
|
|
|
|
9. **You can change your own password**. Go to `Profile` -> `Settings`.
|
|
9. **DHCPv6 support**. Stork fully supports IPv6 from the day one. Add another machine called `agent-kea6`. Notice the IPv6 subnet and several pools.
|
|
|
|
|
|
|
|
10. **All subnets in your network**. Stork lets you view and search through the subnets and pools. Go to `DHCP` and then `Subnets`. You will see all the subnets with pools in them. You can filter the subnets by type (any, DHCPv4 or DHCPv6). You can also type any string. For example, to limit the subnet to 192.0.3.0, you can search for `0.3`. Note that strings shorter than 4 characters require you to press Enter at the end. You can search for specific subnets, pools or pool boundaries.
|
|
|
|
|
|
|
|
11. **You can change your own password**. Go to `Profile` -> `Settings`.
|
|
|
|
|
|
10. **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`.
|
|
12. **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`.
|
|
|
|
|
|
11. **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.
|
|
13. **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 there's a bug in 0.3 that deletes the machines, but not the apps running on it. It is expected to be fixed shortly.
|
|
Note there's a bug in 0.3 that deletes the machines, but not the apps running on it. It is expected to be fixed shortly.
|
|
|
|
|
|
12. **Check Stork version**. You can hover your mouse over the Stork logo. It will display some information about Stork itself (version, compilation time). This works only in the latest git version and will be made available in upcoming 0.4. (Note that this does not work in the 0.3 version on line.)
|
|
14. **Check Stork version**. You can hover your mouse over the Stork logo. It will display some information about Stork itself (version, compilation time). This works only in the latest git version and will be made available in upcoming 0.4. (Note that this does not work in the 0.3 version on line.)
|
|
|
|
|
|
# Feedback
|
|
# Feedback
|
|
|
|
|
... | | ... | |