Hi Koby, Yes in the very past (Be and ages before Be) we used to have this problem of flow- group reordering and even group- group reordering at times.
In Bo (with He plugin), there was a bug raised for the same( https://bugs.opendaylight.org/show_bug.cgi?id=6073) and a fix coded in FlowNodeReconciliationImpl and associated classed to take care of it ( https://git.opendaylight.org/gerrit/#/c/40429/) .Do you still find it happening? In the current release as well as in Bo also with the Li-plugin we did not see any issues with the testing that we have done. Also, there is a new FRM(called as FRS, haven't tested it well enough ) but that fixes some of these aspects. Please try out and let us know :) Br,shuva On Thu, Jan 12, 2017 at 5:14 PM, Aizer, Koby <[email protected]> wrote: > Hi openflowplugin, > > > > In netvirt we have cases where a group installation is immediately > followed by a flow installation which outputs to that group. > > > > However it seems that (at least in the past, helium) even when there is a > syncWrite for the group and then a syncWrite for the flow, the ordered is > not necessarily maintained when sending the openflow messages – causing the > flow installation to fail. > > Therefore you can find several places where Thread.sleep() was used > between the group & flow installations. > > > > I was wondering whether this limitation still exists, and if it does > whether there is some way to enforce the ordering and remove those sleeps. > > If ordering cannot be enforced, is there a way to wait for the group > installation to happen (not ideal, but at least better than sleeping)? > > > > Thanks, > > Koby > > _______________________________________________ > openflowplugin-dev mailing list > [email protected] > https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev > >
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
