ping: always save rtt data, influxdb ignore empty data 69/44969/1
authorRoss Brattain <ross.b.brattain@intel.com>
Wed, 11 Oct 2017 22:16:53 +0000 (15:16 -0700)
committerRoss Brattain <ross.b.brattain@intel.com>
Fri, 13 Oct 2017 06:22:42 +0000 (06:22 +0000)
commitf05d3844c6f43310618b62d942442b2f05f91551
tree959827f15921ff02aaac15c6aec3dce4fe99e5e7
parent204bed26efa57ca0de15534d9268bb4d61f7e0fa
ping: always save rtt data, influxdb ignore empty data

If the SLA was failing we were raising AssertionError and not storing
the rtt in the data dict.  This caused influxdb parse errors because the
data was empty.

Fixup influxdb to ignore records with no data, so we don't try to parse
no data.

Change the ping logic to always record the rtt result even if the SLA
was not met.

Also fixup ping logic in cases where ping does not return results.  If
SLA is defined use SLA * 10 otherwise use large float that doesn't break
the grafana scale too much, maybe 999999

JIRA: YARDSTICK-809

Change-Id: Id2d51216581644a80e8c7b9aa98919a766008adf
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
(cherry picked from commit af011b16787e8fd9fc6f918b1d1427dd1be562ec)
dashboard/opnfv_yardstick_tc037.json
dashboard/opnfv_yardstick_tc038.json
dashboard/opnfv_yardstick_tc070.json
dashboard/opnfv_yardstick_tc071.json
dashboard/opnfv_yardstick_tc072.json
yardstick/benchmark/scenarios/networking/ping.py
yardstick/dispatcher/influxdb.py