Checkbox Provider - Base

Need a job for Ethernet throughput testing

Bug #1837031 reported by Jerry Kao on 2019-07-18

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Checkbox Provider - Base	Fix Released	Medium	Nara Huang	Checkbox Provider - Base 0.50.0

Bug Description

We hit a Ethernet throughput in Somerville project, lp:1833208. Though performance is not part of certification, we need to secure a baseline for networking performance.

The idea is to add a iperf test for Ethernet connection in between of hotplug and remove Ethernet. We can setup an iperf server in lab environment. Create a fully automatic test case to test transfer/receive with command 'iperf -c <iperf server ip-address> -i 5 -t 30 -r' and set the criteria as 100M.

The iperf server ip-address needs to be recorded in plainbox.conf.

Tags:

Related branches

~narahuang/plainbox-provider-checkbox/+git/plainbox-provider-checkbox:add-iperf3-reverse

Merged into plainbox-provider-checkbox:master at revision edd8f0bcde9cb946ab5242b73fad7cd697822d3f

Jonathan Cave (community): Approve on 2019-09-06

Sylvain Pineau (community): Approve on 2019-09-06

Pierre Equoy: Approve on 2019-09-06

Jerry Kao (jerry.kao) on 2019-07-18

tags:	added: ce-qa-concern
Changed in plainbox-provider-checkbox:
status:	New → Confirmed
importance:	Undecided → Medium

Revision history for this message

Jerry Kao (jerry.kao) wrote on 2019-07-18:

Output of the command 'iperf -c <iperf server ip-address> -i 5 -t 30 -r'

u@u-Unidentified-System:~$ iperf -c 10.101.50.175 -i 5 -t 30 -r
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
------------------------------------------------------------
Client connecting to 10.101.50.175, TCP port 5001
TCP window size: 332 KByte (default)
------------------------------------------------------------
[ 4] local 10.101.51.102 port 38426 connected with 10.101.50.175 port 5001
[ ID] Interval Transfer Bandwidth
[ 4] 0.0- 5.0 sec 558 MBytes 936 Mbits/sec
[ 4] 5.0-10.0 sec 557 MBytes 935 Mbits/sec
[ 4] 10.0-15.0 sec 558 MBytes 936 Mbits/sec
[ 4] 15.0-20.0 sec 557 MBytes 934 Mbits/sec
[ 4] 20.0-25.0 sec 557 MBytes 935 Mbits/sec
[ 4] 25.0-30.0 sec 558 MBytes 935 Mbits/sec
[ 4] 0.0-30.0 sec 3.27 GBytes 935 Mbits/sec
[ 4] local 10.101.51.102 port 5001 connected with 10.101.50.175 port 34058
[ 4] 0.0- 5.0 sec 556 MBytes 934 Mbits/sec
[ 4] 5.0-10.0 sec 561 MBytes 941 Mbits/sec
[ 4] 10.0-15.0 sec 561 MBytes 941 Mbits/sec
[ 4] 15.0-20.0 sec 561 MBytes 941 Mbits/sec
[ 4] 20.0-25.0 sec 560 MBytes 940 Mbits/sec
[ 4] 25.0-30.0 sec 560 MBytes 940 Mbits/sec
[ 4] 0.0-30.0 sec 3.28 GBytes 939 Mbits/sec
[SUM] 0.0-30.0 sec 3.82 GBytes 1.09 Gbits/sec

Revision history for this message

Jerry Kao (jerry.kao) wrote on 2019-07-18:

An existing job is available

https://git.launchpad.net/plainbox-provider-checkbox/tree/units/ethernet/jobs.pxu#n62

unit: template
template-resource: device
template-filter: device.category == 'NETWORK'
plugin: shell
category_id: com.canonical.plainbox::ethernet
id: ethernet/multi_nic_device{__index__}_{interface}
_summary: Multi-NIC Iperf stress testing for NIC {interface}
estimated_duration: 7400.0
requires:
package.name == 'iperf' or executable.name == 'iperf'
package.name == 'ethtool' or executable.name == 'ethtool'
package.name == 'nmap' or executable.name == 'nmap'
user: root
environ: TEST_TARGET_IPERF
command: network test -i {interface} -t iperf --scan-timeout 3600 --fail-threshold 80 --runtime 900 --num_runs 4
_description:
This test uses iperf to ensure network devices pass data at an acceptable
minimum percentage of advertized speed.

Revision history for this message

Jerry Kao (jerry.kao) wrote on 2019-08-13:

@Nara, Please help to check whether above job is leveragerable?
Thanks!

Changed in plainbox-provider-checkbox:
assignee:	nobody → Nara Huang (narahuang)

Nara Huang (narahuang) on 2019-10-29

Changed in plainbox-provider-checkbox:
status:	Confirmed → Fix Committed

Sylvain Pineau (sylvain-pineau) on 2019-10-29

Changed in plainbox-provider-checkbox:
milestone:	none → 0.50.0

Revision history for this message

Ray Chen (ray.chen) wrote on 2019-11-14:

This issue was fixed in 50rc2 and verified passed.

Test result: https://certification.canonical.com/hardware/201803-26153/submission/154353/

~$ checkbox-cli --versio
checkbox-ng: 1.6.0rc2
checkbox-support: 0.43.0rc2
com.canonical.ce:oem: 1.0
certification-client: 0.38.0rc2
plainbox-provider-checkbox: 0.50.0rc2
plainbox-provider-resource-generic: 0.42.0rc2
plainbox-provider-sru: 1.14.0rc1
plainbox-provider-tpm2: 1.11.0rc2

Test output:

INFO:root:-------------------- Test Run Number 1 --------------------
INFO:root:Using 1 thread.
INFO:root:Avg Transfer speed: 905.7111111111111 Mb/s
INFO:root:90.57% of theoretical max 1000 Mb/s
INFO:root:Average CPU utilization: 0.0%
INFO:root:
INFO:root:-------------------- Test Run Number 2 --------------------
INFO:root:Using 1 thread.
INFO:root:Avg Transfer speed: 907.1 Mb/s
INFO:root:90.71% of theoretical max 1000 Mb/s
INFO:root:Average CPU utilization: 0.0%
INFO:root:
INFO:root:-------------------- Test Run Number 3 --------------------
INFO:root:Using 1 thread.
INFO:root:Avg Transfer speed: 906.3555555555556 Mb/s
INFO:root:90.64% of theoretical max 1000 Mb/s
INFO:root:Average CPU utilization: 0.0%
INFO:root:
INFO:root:-------------------- Test Run Number 4 --------------------
INFO:root:Using 1 thread.
INFO:root:Avg Transfer speed: 907.6111111111111 Mb/s
INFO:root:90.76% of theoretical max 1000 Mb/s
INFO:root:Average CPU utilization: 0.0%
INFO:root: