Add DUT resources monitoring feature.

[yvolynets-mlnx]

Signed-off-by: Yuriy Volynets yuriyv@mellanox.com

Description of PR

Summary: DUT hardware resources monitoring feature based on HLD
Fixes #

Type of change

• [] Bug fix
• [+] Testbed and Framework(new/improvement)
• [] Test case(new/improvement)

Approach

How did you do it?

Added new pytest plugin, which triggers device HW resources monitoring on the DUT.

How did you verify/test it?

Tested on the local setup, with intentionally changed thresholds in the configuration file to trigger thresholds exceed errors.

Any platform specific information?

Supported testbed topology if it's a new test case?

Documentation

[wangxin]

If the DUT is rebooted during testing, it looks like the dut_monitor.py script on DUT would not start running again. Is there a way to restart it after rebooting?

[yvolynets-mlnx]

If the DUT is rebooted during testing, it looks like the dut_monitor.py script on DUT would not start running again. Is there a way to restart it after rebooting?

"DUTMonitorClient" class takes care of it. It will automatically restart monitoring script when device become accessible.

[prsunny]

A general question on this DUT monitor, can we also plan to have CRM monitoring here. For eg, if any alarms/warnings are raised for CRM resources. May be as a phase 2 commit?