Good idea, I just setup Trello for Integration group, we do not want to step into same issue :)

It would help if we use Trello effectively to avoid effort duplication :) -Madhu

I agree 100%. --Colin Luis Gomez <luis.gomez@...> wrote on 11/07/2013 02:16:07 PM: > From: Luis Gomez <luis.gomez@...> > To: Colin Dixon/Austin/IBM@IBMUS, "<affinity- > dev@...>" <affinity-dev@...>,

Hi Colin, I support the idea of having apps and features doing something useful with very few (b) or no configuration (a). Only concern is for those that do not require configuration (a), at least

thx, and aswin's suggestion sounds like a good idea

Both library and plugin are just under different package. The bundle isolation is not done yet. Aswin also had a suggestion to keep jsonrpc as it's own library. This change will be done in master

hi madhu, I switched to master and lib/plugin division is gone, is this right ?

Collapse is done. Please port any pending changes in the netty branch to the Master and continue hacking. We ported most of the Configuration Services to the new infra. Please submit a patch and fix

For what it's worth, I'm in the process of removing the requirements to configure SimpleFowarding so that it acts as a normal L2 switch across all the ports in the system when there's no

Expanding the invite to all the dev aliases. Based on the discussion on this email thread and over IRC, we are calling for a 1+ hr webex meeting tomorrow (11/07/2013 @ 12pm PST). Webex details @

My only concern is that it may be too awesome :) Thanks for everyones work on it and the opportunity to participate. I think we should be close to 10 different organizations both vendor and non-vendor

Hi Devs, We got most of the fixes that we originally targeted for in the netty branch and planning to collapse it back to master today. Please let us know if you have any inputs/concerns. -Madhu

Hi all, I have a more general question here (I cc controller dev): maybe I am missing something but why the simple forwarding application is always on in the controller (i.e. creating flows for all

Hi Ed, When someone runs run.sh and send some configuration to Affinity, OpenDOVE, or VTN, the Virtualization Edition does something useful. It requires some configuration, but it does something

Hideyuki, My one concern on removing simple forwarding is to make sure that we have a virtualization edition that, when someone runs run.sh, *does* something useful (ie, pinball works) without

Hi Virtualization Edition people, Do any projects in the Virtualization Edition need sample bundles? - org.opendaylight.controller.samples.loadbalancer -

Yes & Yes. The current implementation is not based on a modeling language (such as JsonSchema / Yang). But, we have JSON schema based modeling as well - which is the default for

I think odl-openflow also has this kind of lib/plugin devision. Is is correct to say maybe the lib part should fall in the sal layer, so there is a general modeling for the SB component while plugin

Hi Hugo, Thanks for bringing this up and sharing your views on this. I will share mine here and the possible ways to address it in ODL with its current architecture / design / principles. We should

Heya all, Yesterday evening (CET ;-) ) i was having a nice chat with Madhu. We were talking about ways to make the OVSDB plugin as generic as possible to make sure we can talk to just about any ovsdb