[apologies to nox-dev folks -- I tried to have this conversation offline, but it looks like it's come back online. If folks are uninterested, please let us know. I certainly don't want to look like I'm trying to drum up support for floodlight on the nox-dev list. IMHO, both controllers have their uses and the openflow ecosystem is definitely made better by having as many controllers as possible.]
Hi Hiroyasu, I dropped this list from the CC because my guess is that most NOX developers are more interested in NOX than floodlight... I'm not sure why you chose to re-add the list, but... in any case, my answers are inline. On Mon, Mar 19, 2012 at 2:24 AM, Hiroyasu Ohyama <[email protected]> wrote: > > I'm sorry for my neglecting to follow your project and the > representation to a lack of respect for seniors. > But when I checked Floodlight before, it required to modify the > source-code of Floodlight itself and to restart after re-compiling. > > That was the intenstion of my statement. I definitely understood that and your statement was correct... for an older version of floodlight. All I wanted to say was that the statement was no longer true for current versions of floodlight. > I'm not sure about how user defined applications are treated in > Floodlight internal. > > Can Floodlight dynamically add/switch user defined OpenFlow controller > application ? There is a slide deck with explanation of the module system off of floodlight.openflowhub.org and a tutorial at http://www.openflowhub.org/display/floodlightcontroller/Module+loading+system. But, the short story is that a floodlight module is any java class that implements the IFloodlightModule interface. A module can export zero or more services, and lists dependencies on other services. Given a configuration file with a list of modules to load, floodlight automatically loads, at run time, all of the desired services. So, in this way, it's a lot like nox's module system, except it's java and jython-based instead of C++ and python based. To add a new module, you do not have to change any existing floodlight code. The big difference between nox and floodlight's module system in my mind is that floodlight splits the notion of a module and a service where for nox these are coupled. The result is that you can change the underlying implementation of a service by loading a different module, but modules that depend on that service don't have to change. Hope this helps, - Rob .
