pinger #2

Description

Pinger can verify the network connectivity between its peer units and an
optional configured list of extra-targets. Uses status 'blocked' to signal
connectivity issues or status 'active' when all checks pass correctly.

Series:

Tags:

Pinger

Pinger is a simple network connectivity checker charm. It is intended to be
deployed with multiple units on all machines you will be using later for a
complex deployment (e.g. OpenStack or Big Data), in order to quickly verify the
connectivity between those machines works as expected.

Overview

Each Pinger unit will use ping(8) to verfiy it can successfully connect each
other peer's addresses, and any configured extra-targets. Those checks will be
performed regularly (on changing config or number of peers, as well as every 5
minutes).

After each peer unit performs its checks, a summary will be provided in the
status of the Pinger application. For example, "active OK (all 42 reachable)"
when no connectivity issues were found, or e.g. "blocked FAIL (1 of 42
unreachable)".

All checks and their results are logged. On failure, check the unit log:

juju debug-log -i unit-pinger-0 --replay --no-tail -l ERROR

(change unit-pinger-0 to the see a different unit).

Additionally, inside each unit's charm directory there's a ping.log file with
all the details ping(8) produced. Get that log like this: