Yes, that does seem odd. See also related Documentation bugs and patch:
https://bugs.launchpad.net/openstack-manuals/+bug/1273412 https://review.openstack.org/#/c/81858/ Regards, Tom On 01/04/14 03:42, Nathanael Burton 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. Nate On Mon, Mar 31, 2014 at 1:07 PM, <sowmini.varad...@hp.com <mailto:sowmini.varad...@hp.com>> 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 OpenStack-dev@lists.openstack.org <mailto:OpenStack-dev@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
