Test Environment details:
- Bare Metal: Fedora release 30
- Kernel version: 5.3.8-200.fc30.x86_64
Repo/branch used:
Test precondition:
- Enable dpdk_telemetry plugin in Collectd config by un commenting below lines.
#LoadPlugin dpdk_telemetry
#<Plugin dpdk_telemetry>
# ClientSocketPath "/var/run/.client"
# DpdkSocketPath "/var/run/dpdk/rte/telemetry"
#</Plugin>
Pre-installed software/libraries:
- DPDK 19.08
- Installed Jansson library.
| # | Test Summary | Steps | Expetcted result | Result | Comments |
|---|---|---|---|---|---|
| 1 | Check dpdk-telemetry plugin behavior when DPDK running. | 1)Enable plugin in collectd.conf 2)Run DPDK 3)Run collectd | The plugin should connect to DPDK server socket and should see the DPDK port and global stats been read in stats path. | Pass | |
| 2 | Check dpdk-telemetry plugin behavior when DPDK not running and resume running again. | 1)Enable plugin in collectd.conf 2)Do not start DPDK yet 3)Run collectd 4)Now run DPDK | The plugin connection to DPDK server socket should not succeed and no stats should be read to stats path initially. Once after DPDK started, connection to server should resume and stats should be read to stats path. | Pass | |
| 3 | Check dpdk-telemetry behavior when DPDK stops running in the middle of the test and starts running again. | 1)Enable plugin in collectd.conf 2)Run DPDK 3)Run collectd 4)Stop DPDK 5)Start DPDK | The plugin should connect to DPDK server socket and should see the DPDK port and global stats been read in stats path. Once DPDK stopped, connection to server should be retried by plugin and stats update should stop. Next when DPDK started, the connection retry to server socket should be success and stats update should be resumed. | Pass |