Hi Gunther, I've used openvswitch+wicked successfully, though in a fairly limited fashion (ie. basic ovs bridge configured through wicked on my host to allow network access for KVM virtual machines). As I recall, I had to do some manual manipulation for the bridge to actually be manipulated by the ovs userspace commands: 1. ovs-vsctl add-br + add bridging port - ovs db is now aware of the bridge 2. create basic ifcfg-ovsbr0 3. wicked ifup ovsbr0 - I believe ovsbr0 appeared as a generic ethernet device from wicked's point of view. At this point, your vm's should be able to communicate with ovsbr0. On reboot, I believe the ovsbr0 will be created using the standard linux bridging tools (provided the ifcfg-ovsbr0 file specifies this interface as a bridge of course). As such, ovs userspace will not see it, but brctl will. I recall reading that ovs used to have a brcompat package but this is now deprecated. However, the datapath should be handled by the ovs openvswitch kernel module. Could you describe in more detail how you're testing ovs+wicked, along with ifcfg- files you're created? Wicked logs would be helpful as well. You can enable wicked debugs by adding DEBUG="all" to /etc/sysconfig/network/config. Thanks, -Karol On Fri, May 02, 2014 at 12:28:55PM +0200, Günther J. Niederwimmer wrote:
Hello,
I have tested wicked and openvswitch (KVM) this is in the moment ending with no network and a broken YaST2 Module. :-(
Can I found any Doku or example to configure this correct, or is this not implemented and I have to change to if up / down without wicked ? -- mit freundlichen Grüßen / best Regards,
Günther J. Niederwimmer -- To unsubscribe, e-mail: wicked-devel+unsubscribe@opensuse.org To contact the owner, e-mail: wicked-devel+owner@opensuse.org