You're not off base. This has actually *almost* reached the mainline in the form of a fast_discovery component which subclasses/tweaks some stuff from discovery, but just never quite has. I wanted the code a bit cleaner than it was, and I think there were some subtleties I wanted to get "right" (since you can, for example, send LLDPs on a link immediately after it goes up in order to speed re-discovery, etc.).
We've also had a variant which uses discovery to find the topology *once* and then stops and assumes that anything from then on are just up/downs of the discovered topology (no changes). This was especially nice with, e.g., Mininet. -- Murphy On Nov 7, 2014, at 2:20 PM, Alison Chan <chan7...@kettering.edu> wrote: > Hello, > > Would it be useful for openflow.discovery to raise LinkEvents when it > detects a switch port going down? Currently, it only raises LinkEvents > for removals when a link times out, which could be several seconds > after the link actually goes down. I would think it would be of some > value to raise a LinkEvent immediately on detecting that the switch > port went down. Am I way off base here? > > Cheers, > -- > Alison Chan > Kettering University > chan7...@kettering.edu > +1 909 278 7753
