On Wed, Sep 11, 2013 at 08:15:21 +1000, David Meyer wrote:

One thing we might want to keep in mind is that we want the ODP
controller to also become the primary controller people use for R&D.
Much of the work going on int he R&D community (as well as the NRENs,
world wide) is about Openflow. So it would seem that a reasonable base
edition would have the controller + openflow plugins + some basic
applications and "how to write an application" code. Just a thought
but independent of packaging we definitely will want to target this
(large and diverse) user community.

Yes, a light weight version focussed on OpenFlow would be interesting
us (SURFnet). Although multi tenancy (virtualisation) is also something
we are exploring so that we can support multiple simultaneous researchers,
projects, community networks, etc.

rvdp

On Wed, Sep 11, 2013 at 13:32:42 -0700, Srini Seetharaman wrote:

As far as I can tell, the most popular controller for R&D today is
POX. The migration of the user base from NOX to POX happened because
of POX being pure-Python, lightweight and portable. I'm not sure if
it's easy for ODP to appeal to this audience. A more tangible goal is
for ODP to take over the user base of FloodLight that is more
industry-centric.

We moved from NOX to FloodLight early last year. NOX developement
was uncertain at that time and FloodLight had some nice features
(Java, REST interface, topology discovery, topology view, host
tracking). I know of several other NREN/academic colleagues who
are using FL too. I don't know what the POX vs FL ratio is.

rvdp