I am not sure where these changes stem from. From my understanding, this
enforces the creation of a DPDK environment for the TG, regardless if
it's needed or not.
The only scenario I can think of this being useful is when paired with
T-Rex. But like I've mentioned before, since the TG node is managed by
the traffic generator class, I don't see why DTS should concern itself
to setting up DPDK on the TG.
Logically, what I am thinking is that if T-Rex has an underlying DPDK
requirement, then it should be the duty of the T-Rex Traffic Generator
class to manage this. This behaviour should be agnostic to the overall
test run, who should only care about our DPDK testing environment and a
traffic generator.
Please let me know if I am missing something.
