[PATCH-next 0/1] Parallel Ping patch

From: Christos Sfakianakis <csfakian(a)redhat.com&gt;

Added scenario for parallelism in ping tests.

- Added ping_* params to offer customization capapbility to the user
- Assume the two endpoints have equal-lenght ip lists assigned to them
  (e.g 3 x IPv4, 2 x IPv6 ip's)
- Exluded link-local IPv6 addresses from the pings
- Preserved the traditional sequence of looping over the ip versions to
  perform the pings.
- Bidirectional pings (ping_bidirect) are coded to run simultaneously
- Parallel pings (ping_parallel) are also coded to run simultaneously

An example showing the timing relations is given below.

ENDPOINT 1               <=>            ENDPOINT 2
ipv4.1                   ...            ipv4.2
ipv4.3                   ...            ipv4.4
++++++                                  ++++++
ipv6.1                   ...            ipv6.2
ipv6.3                   ...            ipv6.4

Parameters chosen:
    - ping_parallel = True
    - ping_bidirect = True

Result will be:
--------------------------------------------------------
#TIMING# ENDPT1                #Direction#       ENDPT2
--------------------------------------------------------
TIME t1: ipv4.1                   -->            ipv4.2
TIME t1: ipv4.1                   <--            ipv4.2
TIME t1: ipv4.3                   -->            ipv4.4
TIME t1: ipv4.3                   <--            ipv4.4
=======================================================
TIME t2: ipv6.1                   -->            ipv6.2
TIME t2: ipv6.1                   <--            ipv6.2 
TIME t2: ipv6.3                   -->            ipv6.4
TIME t2: ipv6.3                   <--            ipv6.4

Christos Sfakianakis (1):
  Edit IpAddress, RecipeCommon.Ping, BaseEnrtRecipe

 lnst/Common/IpAddress.py            |   8 +-
 lnst/RecipeCommon/Ping.py           |  60 +++++++++++++++
 lnst/Recipes/ENRT/BaseEnrtRecipe.py | 110 +++++++++++++++++++++++++++-
 3 files changed, 173 insertions(+), 5 deletions(-)

-- 
2.17.1