Comment 5 for bug 2046202

Nobuto, I think the icmp packet loss here was happening with check_iperf=true, and the ping mesh is not adding too much to the story. When the check_iperf is enabled then the execution is the following:
- ping mtu check
- iperf speed test

And the ping mtu check with the current code is using the config settings from the charm, where the default ping_tries set to 20, and due to the async execution of the ping it is happening as fast as possible, so if you have 9 nodes, this will mean 9x20 pings with 9k packet size happening within 1-2secs. And those steps repeated for example on half of the units, and a usual 9 node deployment with vlans consist of 9 x 7 units.

So if the usage of the check_iperf is not suggested, then it would be great to deprecate this option, or add documentation for the config option that explains the drawback of the usage.