This group is locked. No changes can be made to the group while it is locked.
Re: [bgpcep-dev] [openflowplugin-dev] [openflowjava-dev] [controller-dev] OF Plugin Design Updated.
|
Muthukumaran Kothandaraman <mkothand@...>
It would be better to go for latest version
as suggested by Tony. We might want to look into the following resolutions
just in case https://issues.jboss.org/issues/?jql=project%20%3D%20NETTY%20AND%20fixVersion%20%3D%20%224.0.0.x%22%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC
toggle quoted message
Show quoted text
Earlier, for protocol-plugin and codec I had used 3.2.6 because of the stability, drastically different 4.0x API , wider mindshare of experience in forums on 3.2.6 and documentation. If we account and contain Netty dependencies to limited classes, changing to newer version would not be an issue. Regards Muthukumaran (Muthu) L : 080-49141730 P(existence at t) = 1- 1/P(existence at t-1) From: "Tony Tkacik -X (ttkacik - Pantheon Technologies SRO at Cisco)" <ttkacik@...> To: "Ed Warnicke (eaw)" <eaw@...>, Abhijit Kumbhare <abhijitk@...> Cc: Muthukumaran Kothandaraman/India/IBM@IBMIN, "openflowplugin-dev@..." <openflowplugin-dev@...>, Christopher Price <christopher.price@...>, "ovsdb-dev@..." <ovsdb-dev@...>, "openflowjava-dev-bounces@..." <openflowjava-dev-bounces@...>, "openflowjava-dev@..." <openflowjava-dev@...>, "controller-dev@..." <controller-dev@...>, "bgpcep-dev@..." <bgpcep-dev@...> Date: 09/13/2013 05:11 AM Subject: RE: [bgpcep-dev] [openflowplugin-dev] [openflowjava-dev] [controller-dev] OF Plugin Design Updated. I would suggest using Netty 4.0.9-Final Still in distribution you could overrride minor number. Tony From: bgpcep-dev-bounces@...
[mailto:bgpcep-dev-bounces@...]
On Behalf Of Ed Warnicke (eaw)
Sent: Thursday, September 12, 2013 4:37 PM 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: https://git.opendaylight.org/gerrit/gitweb?p=bgpcep.git;a=blob;f=pom.xml;h=c85d766e94a6b9ad73bd831b0d79bd07dcddc205;hb=HEAD <netty.version>4.0.7.Final</netty.version> openflowjava: https://git.opendaylight.org/gerrit/gitweb?p=openflowjava.git;a=blob;f=third-party/openflowj_netty/pom.xml;h=379c6197737bc697da2d4ef685cccdbfc9024fa1;hb=HEAD <dependency> <groupId>org.jboss.netty</groupId> <artifactId>netty</artifactId> <version>3.2.6.Final</version> </dependency> ovsdb: https://git.opendaylight.org/gerrit/gitweb?p=ovsdb.git;a=blob;f=ovsdb/pom.xml;h=904febb3fdfdc9df371819f381b3620be3ab3a36;hb=b5688d33619e1a3b11af5ba9d1c8e7b0cacf59e1 <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. 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 |