Re: [Ryu-devel] example code Openflow client talking to Ryu controller

Yes - I totally understand. Those things are very easy. My app intends to only send PortStats request. On Thu, Mar 8, 2018 at 8:23 PM, knet solutions wrote: > Just for monitoring, if you use openflow it will be more complicated, as > you need to handle the mandatory

Re: [Ryu-devel] example code Openflow client talking to Ryu controller

Just for monitoring, if you use openflow it will be more complicated, as you need to handle the mandatory Openflow messages in the agent. On Fri, Mar 9, 2018 at 9:49 AM, Shivaram Mysore wrote: > Hi Suresh > Call this as an openflow agent. I really want to use

Re: [Ryu-devel] example code Openflow client talking to Ryu controller

Hi Suresh Call this as an openflow agent. I really want to use openflow only. I am not interested in snmp. Thanks /Shivaram ::Sent from my mobile device:: > On Mar 8, 2018, at 8:16 PM, knet solutions wrote: > > + It can be pull or poll mechanism. its quite

Re: [Ryu-devel] example code Openflow client talking to Ryu controller

+ It can be pull or poll mechanism. its quite straight forward implementation. ​ -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org!

Re: [Ryu-devel] example code Openflow client talking to Ryu controller

Hi Shivaram, If you use openflow protocol to talk to controller, then in theory its Openflow agent only. The another method is, >From the Host machine Use some standard protocol (such as SNMP) or your own proprietry to report the statistics to the controller(obviously you need to write the

Re: [Ryu-devel] example code Openflow client talking to Ryu controller

Hi Iwase Thanks. I am not trying to implement a openflow agent. Think of this as a simple tutorial where this is written as a client server application with Ryu controller as the openflow server accepting Openflow client requests. I am trying to help write a client using Ryu's Openflow

Re: [Ryu-devel] example code Openflow client talking to Ryu controller

Hi Shivaram (and thanks Suresh!) You mean you want to defined own stats message structure? I think you can use OFPExperimenterMultipart (or inherit it) to describe your own message, but also need to implement your switch to send that message.

Re: [Ryu-devel] example code Openflow client talking to Ryu controller

Hi Iwase, Let me clarify the use case a little bit more. Lets say, you run on Linux # ethtool -S enp1s0 you will get a bunch of NIC stats. I want to wrap the same in an openflow message and send it to a Ryu controller running my special Ryu App which will connect to this client and - ask

Re: [Ryu-devel] example code Openflow client talking to Ryu controller

Hi Shivaram, You mean you need to send some (stats?) message from Ryu controller to another Ryu controller, right? H... Ryu implements the OpenFlow parsers as "Controller side", parsers for "from switch" messages have no "serialize()" method (some of messages have both "serialize()" and