On Mon, Mar 31, 2014 at 2:42 PM, Nathanael Burton <[email protected]> wrote: > Also, how does this work for RHEL-based distros where they tend to backport > new kernel features? For instance vxlan support was added in the kernel for > RHEL6.5 which is 2.6.32-based... That changeset looks like it breaks > Neutron for ovs + vxlan on RHEL distros. > The change as I coded it won't work for this case. I wasn't aware of the changes being made by the Red Hat folks to backport VXLAN support. I'd be curious to here from them on-list if they backported the upstream Linux kernel VXLAN support or the OVS VXLAN support. My guess would be the former.
Thanks, Kyle > Nate > > > On Mon, Mar 31, 2014 at 1:07 PM, <[email protected]> wrote: >> >> >> openstack-dev, >> >> A question about the fix from https://review.openstack.org/#/c/82931 >> >> After this fix, the neutron code now explicitly checks for kernel >> version 3.13- was this deliberate? (I was using an older 3.11 version >> before, and did not seem to have any issues before this change). >> >> Is there a specific kernel patch that ovs-vxlan is dependant on? >> >> Thanks >> Sowmini >> >> _______________________________________________ >> OpenStack-dev mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
