On 3/3/26 11:07 AM, Timothy Redaelli via dev wrote: > Currently, the 'ovstest' package is not included in the default setup.py > configuration. However, downstream packaging guidelines (such as the new > Fedora Python Packaging Guidelines [1]) imply that all files installed > into Python library directories should be managed by standard PyPA tools > like setuptools. > > Add a separate setup.py for ovstest (in python/ovstest/), allowing it to > be built and installed as its own independent Python package. This avoids > coupling it to the main 'ovs' package build and lets packagers install it > using standard Python build mechanisms. > > This package is a dependency for utilities such as 'ovs-l3ping' and > 'ovs-test'. > > [1] https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/ > > Signed-off-by: Timothy Redaelli <[email protected]> > ---
Hi, Timothy. Thanks for the patch. It seems like a lot of changes for not a lot of benefits. What I mean is that the only users of the ovstest python module outside the unit tests are ovs-test and ovs-l3ping applications. And these applications do not seem to be used much. I, for one, never actually used them and I'm not sure if anyone from the current active OVS developers have experience using them. Users also are more familiar with standard network testing tools like iperf. The ovs-test and ovs-l3ping were more useful in the early days when there were bugs in the linux kernel affecting OVS work. These days we have most of basic use cases covered with our system tests instead. So, my suggestion would be to just delete these tools and clean up the ovstest module from the code that is only used by those tools. This way we will not need to package the library at all. Best regards, Ilya Maximets. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
