[ovs-discuss] Behaviour change in OpenVSwitch

[Ben Pfaff]

On Fri, Jun 05, 2015 at 07:02:13PM +1200, Tony van der Peet wrote:
> Turns out that the only behaviour change is a slight timing change. If I
> put a 0.2s sleep into the outer loop of the test I can make is pass
> reliably. In other words, the flows are still being deleted correctly, it's
> just that the test is so quick in changing the flows and expecting to be
> able to test the new flow that it's seeing a failure.
> 
> In the real world, there would of course be much less chance of this sort
> of coordination between data and flow changes, so I am satisfied that
> OpenVSwitch continues to operate in the same high quality way that I have
> always experienced.

Does the test have an OpenFlow barrier between the flow table change and
the packet?  I'm considering a change to OVS that would make OVS wait
until datapath flows are up-to-date before replying to a barrier
request.