Description of problem:
This RFE is part of the request is to introduce logic in the fencing workflow for the engine to determine if an inability to communicate with external hosts is because it is having network connectivity issues or if there is a legitimate problem with the remote host.
As a first phase, the user should be able to list IP addresses to which we should try to ping before fencing a host. Engine should constantly ping the addresses provided and collect the ping results as an ongoing process. In order to better determine the connectivity status, the results from the last 15 seconds should be kept as a backlog for reference. This timer should be user-configurable.
We still need to discuss what are our 'success' criteria, i.e., how many pings should we send and how many should get a reply.
Sounds like infra?
See dependent bugs that are closed as wontfix after discussing that with Scott.
I believe this should be closed as well.
We have provided some fencing policies that were proven to be satisfying, and we don't plan to pursue this direction.