Shuva, At an application level (l2switch) works good with stable/beryllium branch. Issue arises only with new plugin (ofp master branch)
Changing at application level seems not a good idea. Please let us know. Regards, Sai MarapaReddy On Tue, Aug 2, 2016 at 3:25 AM, Shuva Jyoti Kar < [email protected]> wrote: > Sai, > > > > As discussed the fix of appending the priority to the flowid to guarantee > its uniqueness is not a good fix. > > > > While debugging we notice the flowid of both the flows are same, hence > this issue occurs. The flowRegistryKey generation and comparison happens > correctly. > > > > Is it possible to handle it at the application level (l2switch) itself? As > I see in the l2switch code, the ProactiveFloodFlowWriter and > InitialFlowWriter have independent atomic counters, can we unify it to > guarantee unique flow-id ? > > > > We just need to ensure that applications provide the ofplugin unique > flowId. Using the datastore for provisioning will gurantee the uniqueness > since flowkey (that wraps the flowId) has to be unique for the Datastore > write to succeed. > > > > Lets discuss it . Please pour in your thoughts. > > > > Thanks > > Shuva >
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
