[openstack-dev] [neutron] Testing Neutron with latest OVS

Clark Boylan cboylan at sapwetik.org
Thu Jan 14 21:13:16 UTC 2016

On Thu, Jan 14, 2016, at 01:07 PM, Russell Bryant wrote:
> On 01/14/2016 03:43 PM, Assaf Muller wrote:
> > On Thu, Jan 14, 2016 at 9:28 AM, Russell Bryant <rbryant at redhat.com> wrote:
> >> On 01/13/2016 11:51 PM, Tony Breeds wrote:
> >>> The challenge for you guys is the kernel side of things but if I
> >>> understood correctly you can get the kenrel module from the ovs
> >>> source tree and just compile it against the stock ubuntu kernel
> >>> (assuming the kernel devel headers are available) is that right?
> >>
> >> It's kernel and userspace.  There's multiple current development
> >> efforts that involve changes to OpenStack, OVS userspace, and the
> >> appropriate datapath (OVS kernel module or DPDK).
> >>
> >> The consensus I'm picking up roughly is that for those working on the
> >> features, testing with source builds seems to be working fine.  It's
> >> just not something anyone wants to gate the main Neutron repo with.
> >> That seems quite reasonable.  If the features aren't in proper
> >> releases yet, I don't see gating as that important anyway.
> > 
> > I want to have voting tests for new features. For the past year the
> > OVS agent ARP responder feature has been without proper coverage, and
> > now it's the upcoming OVS firewall driver. I think that as long as we
> > compile from a specific OVS patch (And not a moving target), I don't
> > see much of a difference between gating on OVS 2.0 and gating on, for
> > example, the current tip of the OVS 2.5 branch (But continuing to
> > gate on that patch, so when the OVS 2.5 branch gets backports we
> > won't gate on those, and we'll be able to move to a new tip in our
> > own pace). As long as we pick a patch to compile against and run the
> > functional tests a few times and verify that it works, I think it's
> > reasonable. We've been gating against OVS 2.0 for the past few years,
> > that to me seems unreasonable. We're gating against an OVS version
> > nobody is using in production anymore.
> I would agree that still using OVS 2.0 doesn't make any sense.
Forgive my ignorance, but if we are gating on OVS 2.0 that is because it
is what is shipped with the distros that we test on. Are we saying that
no one uses the distro provided OVS packages to run Neutron? If not what
are they using?


More information about the OpenStack-dev mailing list