I'm on it. The status is that I'm now refactoring the networking part of vdsm to enable us to use different configuration tools for setting interfaces. This will allow to have a open vSwitch back end for configuring the bridges.
For 3.3 we will have the refactoring done. http://www.ovirt.org/Feature/NetworkReloaded I don't think we'll have open vSwitch hitting at the same point, as I'm targeting first to have ifcfg and iproute2 based configuration, but once the API of the refactoring is more stable, maybe somebody can try to do it on parallel. Frankly though, I think it will have to be for the following point release. Best, Toni ----- Original Message ----- > From: "Jiri Belka" <jbe...@redhat.com> > To: users@ovirt.org > Sent: Friday, March 15, 2013 2:12:14 PM > Subject: [Users] openvswitch intergration status > > Hi, > > is there a plan to integrate openvswitch, if so what's status? > > Basic bridging sucks, and now everything is virtual, no? :) > > Maybe some benefits: > > * decreases cost for special (legacy) enterprise switches > * virtualization buzzword included > * one can simulate switch in ovirt > (that was my start to investigate, i wanted to have a trunk port > pointing to virtualized FW and couple of vlans with guests, not > possible right now in ovirt, each vlan = one iface) > * there's backward compatibility > - see http://packages.debian.org/sid/openvswitch-brcompat > > Let's be hype :D > > jbelka > _______________________________________________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
