On 4/12/24 16:46, Adam Williamson wrote:
it seems since I last looked at this, NM has grown some level of openvswitch support, but it seems to be limited, and I don't know off- hand if it's sufficient for what openQA needs. I will need to look into that. https://github.com/NetworkManager/NetworkManager/blob/main/man/nm-openvswitch.xml
I've attempted to use it on a couple occasions, and I've never been able to get it to work. It requires creating 3 different objects, in the correct order, with exactly the right settings. And AFAIK, it still doesn't support setting the internal port to the same name as the bridge itself, which is the default behavior of ovs-vsctl and the network scripts, so it's a disruptive change to the network configuration even if it can be made to work. -- ======================================================================== Google Where SkyNet meets Idiocracy ======================================================================== -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
