1) OK, ARP Handler is gone. 2) I reduced the GBP Renderers box to now only cover half of the OF and OVSDB boxes 3) No better phrase that I know of and that's what we used in the Hydrogen diagram as

Hi Srini: As I understand it,the renderers actually do sit below the SAL, so I want to show them that way. On the data plane icons, I would like to keep these consistent with the Hydrogen diagram and

The meeting minutes from today (9/24) are

It seems as though we had to respin to avoid the -RC2 version suffix anyway. I *thnk* this patch will end up in those artifacts as a consequence. --Colin

I agree, AFAIK this is not a blocking issue.

OK - this looks like it has been merged - so if we wind up respinning it will be included. Fixed the bug number in the thread title (2061 not 2026). I agree that this would not be something that we

My gut reaction would be that this is the kind of thing which we won't respin the release artifacts for, but if we wind up respinning the release artifacts should be included. I'm open to other

Hi Openflow Committers - Luis discovered a bug (2026) in openflow and I pushed a patch (https://git.opendaylight.org/gerrit/11511). The fix was straight forward but since the test also tested for the

+1 I wasn't suggesting it to save time, but instead to make sure people can attend all 3 and that we have them in the right order. --Colin On Sep 23, 2014 4:36 PM, "Robert Varga" <nite@...> wrote:

So, moving that date to October 23rd is something which I believe is just fixing the document to be internally consistent and gives an extra (almost) week. I just made that change [0]. I think that

For Colin's point #2, how about pulling up the GBP into the green rectangle and carving out a portion of the SAL to make it all fit? With the devices in the bottom, how about changing it to these

A few questions/suggestions: 1.) can we remove the ARP Handler or move it into the l2switch where I think it resides now. That will actually save space. 2.) If anyone has a suggestion for how to make

Hello again TSC and members of the Helium Release: Thanks to all for the great feedback on the Helium diagram. It has all been incorporated into the pretty version of the diagram you see

Colin, I believe the date for "Last call for new projects eligible to join" currently is Oct 17 - it will help if that could be pushed to Oct 31 in my opinion (to have more involved discussions before

Hello Members of the TSC: Please consider this email as a notice that the election process for the 2014 TSC Chairperson has begun. As was discussed, This is a TSC Member self-nomination process only:

For obvious reasons you really should bring in some non-Cisco folks to help lead the controller refactoring discussion. I am sure that Devin or Tom P are available. *) --Tom

Hello Phil, thanks for updating the slides and keeping general track of this. After glancing through the agenda, several thoughts pop to mind: I think Salon 5's

My take is that we try to make as much progress as we can in a serious way over the next two weeks (including at the summit) and see where we get rather than pushing it out off hand. That being said,

I think these three kind of build on top of each other, so I think it might make sense to overflow Ed's switch/device model to Tuesday just to give the Monday topics sink in.

Another question that isn't in the template, but will likely come up is whether your project understand and is prepared to participate in stability releases of Helium after the Helium release. --Colin