Hi everyone, In addition to the code repositories made previously available, here’s a wiki document describing our OVS Hyper-V porting architecture and implementation:
http://wiki.cloudbase.it/ovs-hyperv-architecture Please let me know if you have any questions on the document or any specific Hyper-V porting feature. With the idea of adding support for Hyper-V in the upstream OVS repository, I’d like also to start a discussion topic on continuos integration (CI) testing for proposed patchsets. A CI framework becomes particularly important in the moment in which multiple platforms are potentially affected by new code contributions. The experience that we gathered by working on the OpenStack Hyper-V CI proved that developers tend to focus on a relatively narrow platform range (mostly Linux in this context), leading to potential regressions in other platforms (e.g. Windows) if those are not properly caught during code review. Core reviewers tend also to be expert on a given platform and might not be aware of issues that new code contributions might arise on other platforms. This is particularly important for kernel drivers like in this case, as issues can lead to kernel panics (Windows blue screens), OS freezes and critical security issues. Thanks, Alessandro On 11 Jun 2014, at 00:06, Alessandro Pilotti <apilo...@cloudbasesolutions.com<mailto: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<mailto:dev@openvswitch.org> http://openvswitch.org/mailman/listinfo/dev
_______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
