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 Openflow messages in the ag
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 openflow only. I am
> not interest
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 straight forward implementation.
+ 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! http://sdm.link/slashdot
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 liste
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
messag
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.
https://github.com/osrg/ryu/blob/master/ryu/ofproto
I think, you are trying to implement the openflow agent for the NIC
card.In my perspective ,its not related to Controller stuff.
On Thu, Mar 8, 2018 at 10:14 AM, Shivaram Mysore
wrote:
> Hi Iwase,
> Let me clarify the use case a little bit more.
>
> Lets say, you run on Linux
> # ethtool -S
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 for
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 "par
Hi,
I am looking for example Ryu API usage where Ryu framework is used to
construct a Openflow message sent to Ryu controller.
Use case is that I just want to send say, network statistics to Ryu
Openflow controller where I have a Ryu application that is listening to
Openflow stats and meter messag
11 matches
Mail list logo
