Series to rework how testbed topologies are defined within the dts configuration. Bugzilla ID 1360 originally asked for a rework to define physical NIC devices on nodes. However, defining testbeds purely by device negates the ability to create specific, multi-device testers running performance tests, for example. We could keep the device design specified, but adding in this flexibility might make configuration more puzzling and complicated than necessary. Instead, it may make sense to use unique identifiers on ports/interfaces, and have DTS users select ports based on these identifiers within test run configuration; that is what this series achieves.
Nicholas Pratte (3): dts: rework port attributes in config module dts: rework testbed_model Port objects to contain unique identifiers dts: rework test suite and dts runner to include test_run configs dts/conf.yaml | 32 ++++++------- dts/framework/config/__init__.py | 12 +++-- dts/framework/config/conf_yaml_schema.json | 52 +++++++++++++--------- dts/framework/config/types.py | 19 +++++--- dts/framework/runner.py | 16 +++++-- dts/framework/test_suite.py | 33 +++++++++----- dts/framework/testbed_model/port.py | 45 +++++-------------- 7 files changed, 113 insertions(+), 96 deletions(-) -- 2.44.0
