Magpie will check ICMP, DNS, MTU and rx/tx speed between itself and any
peer units deployed - deploy more than one magpie unit for meaningful results.
Magpie is a charm used for testing the networking of a juju provider/substrate.
Simply deploy more than one Magpie charm and watch the status messages and
Magpie will test:
MTU and transfer speed are tested with iperf2
Status messages will show the unit numbers that have issues - if there are
no problems, there will not be a verbose status message.
All actions, strings, queries and actions are logged in the juju logs.
The MTU size reported by iperf is sometimes 8 or 12 bytes less than the configured
MTU on the interface. This is due to TCP options not being included in the measurement,
and therefore we ignore that difference and report everything OK.
In addition to ICMP and DNS status messages, if a networking problem is
detected, the workload status of the agent which has found the issues
will be set to blocked.
This layer will set the following states:
Note: work stopped on these states as it is currently unlikely magpie will be consumed
as a layer.
Please open an issue against this github repo if more states are required.
juju deploy magpie -n 2
juju deploy magpie -n 1 --to lxd:1
This charm also supports the following config values:
description: Check if local hostname is resolvable
description: DNS Server to use (default: system default)
description: Number of DNS resolution attempts per query
description: Timeout in seconds per DNS query try
description: Timeout in seconds per ICMP request
description: Number of ICMP packets per ping
Desired MTU for all nodes - block if the unit MTU is different
(accounting for encapsulation). 0 disables.
Minimum transfer speed in mbits/s required to pass the test.
juju set magpie dns_server=184.108.40.206 required_mtu=9000 min_speed=1000