On Fri, Oct 12, 2012 at 07:39:21AM +0900, FUJITA Tomonori wrote:
> On Thu, 11 Oct 2012 17:17:24 +0900
> Isaku Yamahata <[email protected]> wrote:
>
> > For discovery, it's interested only in datapath/port
> > appearance/disappearance.
> > With this, discovery app would not have to handle OFP events directly.
>
> Can you describe how this is necessary for the GRE app, not for
> discovery app?
Here's update commit message.
dpset: add port{add, delete, modify} event for convenience and helper functions
It is sometimes commonly interesting to track datapath/port
appearance/disappearance. The applications usually want to see that ports
appear after datapath becomes ready, and ports disappear when datapath is dead.
It requires to handle properly events, hand shaking, port_mod event,
switch_feature_reply. So introduce a common layer to handle them.
GRE tunnel is interested in datapath/port appearance/disappearance.
With this, tunnel app doesn't have to handle those conditions.
Discovery is interested only in datapath/port appearance/disappearance.
With this, discovery app would not have to handle OFP events directly.
--
yamahata
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Ryu-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ryu-devel
