Re: [bgpcep-dev] [openflowplugin-dev] [openflowjava-dev] [controller-dev] OF Plugin Design Updated.


Robert Varga -X (rovarga - Pantheon Technologies SRO@Cisco) <rovarga@...>
 

I suggest standardizing on 4.0.x. There has been significant API rework for the 4.0.x series. Patch to move bgpcep forward to 4.0.8 is forthcoming.

 

Bye,

Robert

 

From: bgpcep-dev-bounces@... [mailto:bgpcep-dev-bounces@...] On Behalf Of Ed Warnicke (eaw)
Sent: Friday, September 13, 2013 1:37 AM
To: Abhijit Kumbhare
Cc: Muthukumaran Kothandaraman; openflowplugin-dev@...; Christopher Price; ovsdb-dev@...; openflowjava-dev-bounces@...; openflowjava-dev@...; controller-dev@...; bgpcep-dev@...
Subject: Re: [bgpcep-dev] [openflowplugin-dev] [openflowjava-dev] [controller-dev] OF Plugin Design Updated.

 

We may want to settle onto a single version of netty throughout ODL… here's what I see so far:

 

bgpcep: 

<netty.version>4.0.7.Final</netty.version>

 

openflowjava:

 <dependency>

       <groupId>org.jboss.netty</groupId>

       <artifactId>netty</artifactId>

       <version>3.2.6.Final</version>

 </dependency>

 

ovsdb:

<dependency>

     <groupId>io.netty</groupId>

     <artifactId>netty-all</artifactId>

     <version>4.0.8.Final</version>

</dependency>

 

Ed

 

On Sep 12, 2013, at 4:38 PM, Abhijit Kumbhare <abhijitk@...>

 wrote:



The netty pipeline layout (after the version negotiation) is now a part of the OpenFlow library. They have the rough idea of the interactions with the plugin at https://wiki.opendaylight.org/view/Openflow_Protocol_Library:Main and the architecture at https://wiki.opendaylight.org/images/0/02/Openflow_Protocol_Library.pdf. I will let Tony Tkacik or Michael Rehak/Michal Polkorab answer the question with respect to the details on how the pipeline is done in the OpenFlow library.

<graycol.gif>Muthukumaran Kothandaraman ---09/12/2013 01:26:56 PM---Hi Abhijit, I think I was not quiet clear

From: Muthukumaran Kothandaraman <mkothand@...>
To: Abhijit Kumbhare/San Jose/IBM@IBMUS,
Cc: Christopher Price <christopher.price@...>, "controller-dev@..." <controller-dev@...>, "openflowjava-dev@..." <openflowjava-dev@...>, openflowjava-dev-bounces@..., "openflowplugin-dev@..." <openflowplugin-dev@...>, Prasanna Huddar <prasanna.huddar@...>
Date: 09/12/2013 01:26 PM
Subject: Re: [openflowjava-dev] [controller-dev] OF Plugin Design Updated.





Hi Abhijit, 

I think I was not quiet clear


My question was primarily if we had nailed-down how this would be realized in Netty context - as Chris mentions, that cannot be overlooked as only a programming detail
because pipeline layout and their variances thereof  is the basic implementation aspect of plugin
 

Regards

Muthukumaran (Muthu)
L  : 080-49141730

P(existence at t) = 1- 1/P(existence at t-1)
 



From:        
Abhijit Kumbhare <abhijitk@...> 
To:        
Christopher Price <christopher.price@...> 
Cc:        
"controller-dev@..." <controller-dev@...>, Muthukumaran Kothandaraman/India/IBM@IBMIN, "openflowjava-dev@..." <openflowjava-dev@...>, openflowjava-dev-bounces@..., "openflowplugin-dev@..." <openflowplugin-dev@...>, Prasanna Huddar <prasanna.huddar@...> 
Date:        
09/13/2013 01:45 AM 
Subject:        
Re: [openflowjava-dev] [controller-dev] OF Plugin Design Updated. 





The negotiation will be actually handled in the plugin - however once the negotiation is done, the version detection & switching to either the OF 1.0 or 1.3 codec will be handled in the OF library.


<graycol.gif>Christopher Price ---09/12/2013 01:09:38 PM---Adding the library dev to the thread. The negotiation decisions are policy driven through the plugin

From:
Christopher Price <christopher.price@...>
To:
Muthukumaran Kothandaraman <mkothand@...>, Prasanna Huddar <prasanna.huddar@...>,
Cc:
"openflowjava-dev@..." <openflowjava-dev@...>, "controller-dev@..." <controller-dev@...>, "openflowplugin-dev@..." <openflowplugin-dev@...>
Date:
09/12/2013 01:09 PM
Subject:
Re: [openflowjava-dev] [controller-dev] OF Plugin Design Updated.
Sent by:
openflowjava-dev-bounces@...





Adding the library dev to the thread.
The negotiation decisions are policy driven through the plugin (connection mgr (where applicable) –> plugin –> library), but the negotiation machinery and Netty aspects are library implemented.  These are good questions to come to complete clarity and agreement on!
/ Chris

From:
Muthukumaran Kothandaraman <
mkothand@...>
Date:
Thursday, September 12, 2013 12:57 PM
To:
Prasanna Huddar <
prasanna.huddar@...>
Cc:
"
controller-dev@..." <controller-dev@...>, "controller-dev-bounces@..." <controller-dev-bounces@...>, "openflowplugin-dev@..." <openflowplugin-dev@...>
Subject:
Re: [controller-dev] OF Plugin Design Updated.


Hi Prasanna,

Had a few clarifications

1. Are we going with Netty 4.0x for the implementation ?
2. Do we change the Netty Channel pipeline once version-negotiation is completed ?
  More like following
 
     When 1.0 OF Header version is encountered (no need for version-negotiation)
             - Pipeline would only contain :  "ofmessage1_0decoder", "ofmessage1_0encoder", "idle", "handler"
 

     When 1.3 OF Header version is encountered
             -
Pipeline would only contain :  "ofmessage1_3decoder", "ofmessage1_3encoder", "idle", "handler"

     When 1.3 OF Header version is encountered and 1.0 is negotiated - Assuming that this case to be supported for sake of completion
             -
Pipeline would only contain :  "ofmessage1_0decoder", "ofmessage1_0encoder", "idle", "handler"

     When 1.3 OF Header version is encountered and 1.3 is negotiated - MOST LIKELY case
             -
Pipeline would only contain :  "ofmessage1_3decoder", "ofmessage1_3encoder", "idle", "handler"                

 And in order to accomplish "When 1.0/1.3 is negotiated" action, we would have a "version-detector" in all above pipeline configurations which uses only the header-version?
 



     

Regards

Muthukumaran (Muthu)
L  : 080-49141730

P(existence at t) = 1- 1/P(existence at t-1)
 



From:        
Prasanna Huddar <prasanna.huddar@...>
To:        
"
controller-dev@..." <controller-dev@...>, "openflowplugin-dev@..." <openflowplugin-dev@...>
Date:        
09/12/2013 10:27 PM
Subject:        
[controller-dev] OF Plugin Design Updated.
Sent by:        
controller-dev-bounces@...





Hello,

           Updated the Plugin design as per the discussion in Hackfest.


https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:Design


-Prasanna_______________________________________________
controller-dev mailing list

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

https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev

_______________________________________________
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.