Restriction in choosing the sender and receiver ports.

[subh007]

In current implementation, we can't choose the sender port because in most of the test cases of_ports[0] is used to send packets and of_ports is list of sorted port_ids.

It will be good idea if we can choose the sender and receiver port.

eg. if we have config_port = { 3:eth3, 2:eth2, 1:eth1}
then it results of_ports = [1,2,3] ( because of sorting on dict keys) and it leads to eth1 to be sender and eth2 be receiver in most of the cases.

So, I am thinking to overcome this problem, we can introduce a new list port_order list in config which will define sender and receiver ports.
eg.
let say port_order = [3,2,1] (3 will be sender and 2 will be receiver)

Please let me know your thoughts.

[jonstout]

This is kind of a cool idea. I imagine we would simply define a set of sort funcs. The most important thing for testing though, is that we can exactly reproduce the test. So we can't randomize port selection, and we need to know for each test case the port mapping used.

You should add this issue to the floodlight fork too. Any future work we may do will use that code base.