Re: [openflowplugin-dev] How can we fix multiple masters issue better for openflowplugin?


Yang, Yi Y <yi.y.yang@...>
 

Hema, good point, we need to fix the conflict before a flow is written to MDSAL data store, but this won’t impact we add this middle layer into openflowplugin, the reason to put it to openflowplugin is openflowplugin is a good hosting place for such middle layer. You can consider it is a component of openflowplugin, all the projects will call APIs from this component to program openflow tables and flows.

 

From: Hema Gopalkrishnan [mailto:hema.gopalkrishnan@...]
Sent: Thursday, July 16, 2015 7:00 PM
To: Yang, Yi Y; Hariharan_Sethuraman@...; abhijitkoss@...; lacp-dev@...
Cc: C_Venkataraghavan@...; ovsdb-dev@...; groupbasedpolicy-dev@...; sfc-dev@...; openflowplugin-dev@...; Gaurav Bhagwani; Manohar SL; Prakash N N
Subject: RE: [openflowplugin-dev] How can we fix multiple masters issue better for openflowplugin?

 

I feel that the openflow plugin may not the place to detect the flow / table conflict. When the flow / table request reaches the openflow plugin, the NSFs / application would have already configured the flows and tables in the Config datastore of md-sal. So, taking any corrective action may be difficult.

 

We had proposed that conflict detection to be done even before the NSFs /application write to the config datastore. Any thoughts ?

 

From: Yang, Yi Y [mailto:yi.y.yang@...]
Sent: 16 July 2015 14:51
To: Hema Gopalkrishnan; Hariharan_Sethuraman@...; abhijitkoss@...; lacp-dev@...
Cc: C_Venkataraghavan@...; ovsdb-dev@...; groupbasedpolicy-dev@...; sfc-dev@...; openflowplugin-dev@...; Gaurav Bhagwani; Manohar SL; Prakash N N
Subject: RE: [openflowplugin-dev] How can we fix multiple masters issue better for openflowplugin?

 

I’m very glad to hear many guys have realized this issue, Prem Sankar created this wiki page https://wiki.opendaylight.org/view/OF_pipeline, this is a start point, please add other projects which used openflowplugin so that we can know how urgent this issue is. As Abhijit Kumbhare (openflowplugin project lead) commented, I think openflowplugin is the best place to implement this, I strongly suggest Abhijit Kumbhare can help make this become reality as early as possible, I want to work on it, but I need to hear your ideas if you have better ideas.

 

From: Hema Gopalkrishnan [mailto:hema.gopalkrishnan@...]
Sent: Thursday, July 16, 2015 4:51 PM
To: Hariharan_Sethuraman@...; abhijitkoss@...; Yang, Yi Y; lacp-dev@...
Cc: C_Venkataraghavan@...; ovsdb-dev@...; groupbasedpolicy-dev@...; sfc-dev@...; openflowplugin-dev@...; Gaurav Bhagwani; Manohar SL; Prakash N N
Subject: RE: [openflowplugin-dev] How can we fix multiple masters issue better for openflowplugin?

 

Hi Yi / Abhijit,

 

   We had proposed an idea in the ODL India forum on similar lines of Flow Conflict Prevention. Here is the link to the presentation.

 

We are interested in any discussion on this topic.

 

Regards,

Hema.

From: openflowplugin-dev-bounces@... [mailto:openflowplugin-dev-bounces@...] On Behalf Of Hariharan_Sethuraman@...
Sent: 16 July 2015 11:47
To:
abhijitkoss@...; yi.y.yang@...; lacp-dev@...
Cc:
C_Venkataraghavan@...; ovsdb-dev@...; groupbasedpolicy-dev@...; sfc-dev@...; openflowplugin-dev@...
Subject: Re: [openflowplugin-dev] How can we fix multiple masters issue better for openflowplugin?

 

+ lacp-dev

 

From: openflowplugin-dev-bounces@... [mailto:openflowplugin-dev-bounces@...] On Behalf Of Abhijit Kumbhare
Sent: Wednesday, July 15, 2015 8:03 PM
To: Yang, Yi Y
Cc:
ovsdb-dev@...; groupbasedpolicy-dev@...; sfc-dev@...; openflowplugin-dev@...
Subject: Re: [openflowplugin-dev] How can we fix multiple masters issue better for openflowplugin?

 

Yi,

 

This is a good topic - and OpenFlow plugin will likely be a good place for this. Are you planning to work on this? Why don't you join the next OpenFlow plugin meeting (at least for part of the meeting) to discuss more?

 

As you mention probably some kind of a flow conflict detection and resolution module is needed.

 

Thanks,

Abhijit

 

 

On Tue, Jul 14, 2015 at 8:24 PM, Yang, Yi Y <yi.y.yang@...> wrote:

Hi, All

 

Maybe some of you know several projects in ODL have implemented their own openflow writers for programming openflow rules, the end part of the mail are some info I collected. My question is how they work together if we install all of them? Every writer will create table 0, can it work normally? How can we fix it if not? The most important issue is they are duplicating efforts, what if we can provide a good middle layer in openflowplugin or in a separate project in order that all the operations are synchronized and coordinated? I kick off this discussion here is to let all the developers discuss it in open mind.

 

I think we can consolidate these unnecessary duplicate efforts into a separate project or part of openflowplugin, it is very necessary to provide only one entry to program openflow tables and rules, these operations must be efficiently synchronized and managed and coordinated, the direct benefits are as below:

 

1.       Fix table conflict

2.       Reduce number of tables: all the user scenarios have ingress and egress tables although they have different names or purposes

3.       Fix multiple master/writer synchronization

4.       Provide high level APIs for simplifying use for consumers

5.       Optimization will be visible for all the users (APIs consumers)

6.       Openflowplugin evolution or update will be invisible for all the users (API consumers)

7.       You can list more items here if you can imagine J

 

Welcome your great ideas and look forward to seeing we can bear fruit.

 

GBP

====

Table 0: Port Security, Ingress

Table 1: Ingress NAT Mapper

Table 2: Source Mapper

Table 3: Destination Mapper

Table 4: Policy Enforcer

Table 5: Egress NAT Mapper

Table 6: External Mapper

 

 

SFC

===

Table 0, Transport Ingress

Table 1, Path Mapper

Table 2, Next Hop

Table 10, Transport Egress

 

OVSDB Netvirt

==============

Table 0: Classifier

Table 10: Director

Table 20: Distributed ARP Responder

Table 30: DNAT for inbound floating-ip traffic

Table 40: Egress Acces-control

Table 50: Distributed LBaaS

Table 60: Distributed Virtual Routing (DVR)

Table 70: Layer 3 forwarding/lookup service

Table 80: Layer2 rewrite service

Table 90: Ingress Acces-control

Table 100: SNAT for traffic accessing external network

Table 110: Layer2 mac,vlan based forwarding


_______________________________________________
openflowplugin-dev mailing list
openflowplugin-dev@...
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

 

Join z.archive.ovsdb-dev@lists.opendaylight.org to automatically receive all group messages.