Re: [sfc-dev] [groupbasedpolicy-dev] [openflowplugin-dev] How can we fix multiple masters issue better for openflowplugin?
Yang, Yi Y <yi.y.yang@...>
We discussed two possible implementations. But flow conflict detection will be pain point, so far it is just under research, there isn’t a good enough way to fix this. Option II can avaoid this pain point, but every related project must cooperate and coordinate with each other. Openflowplugin programmer is the layler I suggest, it should be only one entry to program openflow tables and rules, it should provide high level APIs and uniformly manage all the resources, including table ID, flow ID, flow priority, etc. It can merge multiple flow entries from every projects into a flow entry if possible, welcome your comments and hope you can take them into Opendaylight Summit for more discussion, I can’t make it.
From: Prem sankar G [mailto:prem.sankar.g@...]
Sent: Friday, July 24, 2015 2:07 AM
To: Brady Allen Johnson; Yang, Yi Y; Abhijit Kumbhare
Cc: sfc-dev@...; lacp-dev@...; openflowplugin-dev@...; Manohar SL; groupbasedpolicy-dev@...; ovsdb-dev@...; Gaurav Bhagwani; Prakash N N; Hariharan_Sethuraman@...; Hema Gopalkrishnan; C_Venkataraghavan@...; Thomas Bachman; Keith Burns
Subject: RE: [sfc-dev] [groupbasedpolicy-dev] [openflowplugin-dev] How can we fix multiple masters issue better for openflowplugin?
I see other design discussion similar to this topic being proposed. –
- Common Network Abstraction
- Co-existence of multiple projects in the same pipeline via a “stack” approach
If there is an agreement, we can look to combine them and have a longer discussion.
From: Brady Allen Johnson
On 07/20/2015 09:36 AM, Yang, Yi Y wrote: