Thank you for the contribution! As you know, a team at VMware is close to releasing its port as well. Since we'll have two ports, the core OVS developers will need to evaluate each approach. I've asked the team at VMware to send out to ovs-dev an architectural description of the approach that they used. They plan to do that in the next day or two. You indicated that you were planning to do something similar. Do you know when that will be available?
I looked a bit at your implementation. It looks like it was forked a couple of months ago, and there were quite a few changes to the userspace. My guess is that a lot of that of those changes were related to building on Windows. Guru has made a lot of progress in cleanly building upstream OVS on Windows, so I hope that the userspace changes you need are minimal. (It appears that you are reusing "dpif-linux" to communicate with your kernel module, which should require even fewer changes.) Do you know how long it would take you to rebase your changes so that we can get a clean set of patches that will apply to the tip of master? This will be great to have a Hyper-V port, and we're looking forward to working with you on this. --Justin On Tue, Jun 10, 2014 at 2:06 PM, Alessandro Pilotti < apilo...@cloudbasesolutions.com> wrote: > Hi everyone, > > We recently announced the availability of our porting of Open vSwitch to > Microsoft Hyper-V: > > http://www.cloudbase.it/open-vswitch-on-hyper-v/ > > The code for both the OVS userspace tools and the Hyper-V kernel > extension is available as open source (Apache 2) and we’d be very happy to > contribute it to the OVS community. > > Repositories: > > https://github.com/cloudbase/openvswitch-hyperv > https://github.com/cloudbase/openvswitch-hyperv-kernel > > The highlights include support for GRE and VXLAN tunnels with full > compatibility for interoperability scenarios (e.g. OVS on KVM), e.g.: a vm > running on Hyper-V can seamlessly communicate with a vm running on KVM over > a VXLAN tunnel. Please see the above blog post for a complete example and > additional details. OpenStack is one of our main use cases for this > effort, but any other OVS scenario can also benefit from Windows / Hyper-V > support. > > Changes in the userspace tools can be submitted for review against the > current OVS main repository, while the Hyper-V kernel extension (where the > large bulk of the porting effort resides) can be contributed as a separate > project or integrated in the current repository based on community > preferences. > > I’ll leave architectural and implementation details to a follow up. > Please let me know if you have any questions. > > > Thanks, > > Alessandro > > > > > > > > > _______________________________________________ > dev mailing list > dev@openvswitch.org > http://openvswitch.org/mailman/listinfo/dev > >
_______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
