Re: [Ryu-devel] Switch Connection Up Event

Hi Vinay, You can use EventSwitchEnter and EventSwitchLeave. (Note that this API is supported only by OpenFlow 1.0 and 1.3) -- from ryu.base import app_manager from ryu.controller.handler import set_ev_cls from ryu.topology import switches from ryu.topology.event import EventSwitchEnter,

Re: [Ryu-devel] Proposal: High layer RPC API

2014-02-12 12:22 GMT+09:00 YAMAMOTO Takashi : > > On Wed, 12 Feb 2014 10:28:50 +0900 > > Satoshi Kobayashi wrote: > > > >> I tried RPC API on Ryu3.6. The sample of VRRP was very helpful for me. > >> Thanks a lot! And I would like to feedback the noticed point. > >> > >> Feedback: > >> I think tha

[Ryu-devel] Switch Connection Up Event

Hi All, I am traditionally a POX user and am more familiar with the APIs used there. I have recently started using Ryu and am finding difficulty in finding the appropriate APIs. In POX there is an API which is called when a switch connects to the controller. It is _handle_ConnectionUp(). I am sear

Re: [Ryu-devel] [PATCH 1/2] topology: split out exported API from the implementation

> On Wed, 12 Feb 2014 11:09:01 +0900 (JST) > [email protected] (YAMAMOTO Takashi) wrote: > >>> On Mon, 10 Feb 2014 14:22:45 +0900 (JST) >>> [email protected] (YAMAMOTO Takashi) wrote: >>> > I prefer to move them to event.py so dependency can be solved > automatically if register

Re: [Ryu-devel] Proposal: High layer RPC API

> On Wed, 12 Feb 2014 10:28:50 +0900 > Satoshi Kobayashi wrote: > >> I tried RPC API on Ryu3.6. The sample of VRRP was very helpful for me. >> Thanks a lot! And I would like to feedback the noticed point. >> >> Feedback: >> I think that the layer of API is low for users. It is hard that a user >

Re: [Ryu-devel] [PATCH 1/2] topology: split out exported API from the implementation

On Wed, 12 Feb 2014 11:09:01 +0900 (JST) [email protected] (YAMAMOTO Takashi) wrote: >> On Mon, 10 Feb 2014 14:22:45 +0900 (JST) >> [email protected] (YAMAMOTO Takashi) wrote: >> I prefer to move them to event.py so dependency can be solved automatically if register_service()

Re: [Ryu-devel] Proposal: High layer RPC API

On Wed, 12 Feb 2014 10:28:50 +0900 Satoshi Kobayashi wrote: > I tried RPC API on Ryu3.6. The sample of VRRP was very helpful for me. > Thanks a lot! And I would like to feedback the noticed point. > > Feedback: > I think that the layer of API is low for users. It is hard that a user > writes the

Re: [Ryu-devel] [PATCH 1/2] topology: split out exported API from the implementation

> On Mon, 10 Feb 2014 14:22:45 +0900 (JST) > [email protected] (YAMAMOTO Takashi) wrote: > >>> I prefer to move them to event.py so dependency can be solved >>> automatically if register_service() is added. >> >> sorry for dropping the ball. >> >> register_service is to start event-provider

[Ryu-devel] Proposal: High layer RPC API

Hi all, I tried RPC API on Ryu3.6. The sample of VRRP was very helpful for me. Thanks a lot! And I would like to feedback the noticed point. Feedback: I think that the layer of API is low for users. It is hard that a user writes the same thing as rpc_manager.RpcVRRPManager. Proposal: I would lik

Re: [Ryu-devel] [PATCH] handler.register_service: comment

On Mon, 10 Feb 2014 14:26:33 +0900 YAMAMOTO Takashi wrote: > Signed-off-by: YAMAMOTO Takashi > --- > ryu/controller/handler.py | 11 +++ > 1 file changed, 11 insertions(+) Applied, thanks. -- Android apps run

Re: [Ryu-devel] [PATCH 1/2] topology: split out exported API from the implementation

On Mon, 10 Feb 2014 14:22:45 +0900 (JST) [email protected] (YAMAMOTO Takashi) wrote: >> I prefer to move them to event.py so dependency can be solved >> automatically if register_service() is added. > > sorry for dropping the ball. > > register_service is to start event-provider app automat