[PATCH v1] cleanup: rename base classes

[Honnappa Nagarahalli]

<snip>
> 
> > > The current naming of the base elements DTS works with is a bit
> > > confusing, which this patch attemps to ameliorate. The basic
> > > elements could be divided into and described in short as follows:
> > > * A node: a broad term encompassing a host where any of the DTS
> > > elements are present. This could be a physical or virtualized server
> > > or a container.
> 
> OK
> 
> > > * The control node: the host where DTS runs
> 
> OK
> 
> > > * An SUT (system under test) node: This is where DPDK along with the
> > > tested hardware resides. The system comprises DPDK and the hardware.
> 
> Is there any difference between a SUT and a "tested node"?
> 
> > > * A traffic generator node: The node where the traffic generator is
> > > present, such as Trex, Scapy or a hardware traffic generator (e.g.
> > > IXIA)
> 
> OK
> 
> > > All references to DUT were removed. This is because it was used to
> > > mean both the server where DPDK/NIC are present and the DUT (device
> > > under test, i.e. the NIC) in different contexts. Where applicable,
> > > DUT was replaced with NIC and the rest were replaced with SUT. With
> > > this change, it's clear what's meant and the abbreviations are very
> > > different, which removes that layer of confusion.
> 
> "NIC" does not mean it is a device under test.
> Also we could have other kind of devices under test, like crypto cards.
May be for other cards, we could use "XxxAccelerator"? We could leave "NIC" as is.

> 
> > > Rename the following classes:
> > > Crb -> Node
> > > Dut -> SutNode
> > > Tester -> TrafficGeneratorNode
> > > DPDKdut -> DpdkSut
> > > DPDKtester -> DpdkTrafficGenerator
> > > VirtDut -> VirtSut
> > > CrbsConf -> TopologyConf
> > > PktgenConf -> PacketGeneratorConf
> 
> I think you need to choose between "TrafficGenerator" and
> "PacketGenerator".
+1 for a single term

>