Hi Azher, I could help you to solve the L2Switch issue but I need to know which branch you’re working and your test condition. The problem you mentioned seems not appears here. But we only test the

Hi Azher, It was great to you yesterday. I cc'd the alto-team. Jensen/Junzhuo/Tony: Azher from CalTech mentioned that an issue they are facing is that ODL l2switch (HostTracker) made one host appears

Hi Jensen, Please make it public so that we can get feedback. Did you follow Wendy's new version? Thanks! Richard -- Richard

Yeah, I have created a branch based on 'stable/lithium' to implement sse in our ODL/ALTO server. And I will update it this week. But it is just a repo in our local server. Shall we make it public?

Wendy has already implemented this draft in her server. It will be great if we can do the same soon. Richard ---------- Forwarded message ---------- From: Wendy Roome <w.roome@...> Date: Tuesday,

Hi Amit I’m trying to merge my code to master branch by hand (refactor my code as well) but the master branch seems not working at all. My modification based on stable/lithium tag. So I can’t test

Hi Amit I will submit the patch soon to ODL repo. Regards, Junzhuo 2015-09-28 2:21 GMT+08:00 Amit Mandke (ammandke) <ammandke@...>:

That sounds great. It is hard to follow code change in different repository. Please submit your patches to ODL repo. I would recommend incremental smaller(working) patches than one big change if

Hi l2switch team, I have changed the l2switch to construct flow entries to build shortest path between hosts and also provide the routing information to other modules. I'm very happy to submit my code

Richard, Revised Incremental Updates draft attached. (Yes, this time I really did attach it). I moved the keep-alive section to a sub-section of Section 6.6. That is a server requirement, so it seems

Richard, Thanks for your comments. My responses in-line. Yes, I expected that. Do you think it is worth mentioning that in the section? Because the SSE specification recommends that as a keep-alive.

Wendy, Here is some feedback: - I liked the addition of the changes-since-00 section. It helps. I believe that it will be removed at the final stage. - Sec. 4.3: Why not use the empty event

Hi Richard, I am updating ALTO client to 01 version. It should be finished in four days as I have another ppt to finish. BR G.Robert

Wonderful! I am available to conduct a code review soon. Let's schedule a time and get the piece in. Thank you so much! Richard -- ===================================== | Y. Richard Yang <yry@...>

Dear Richard, It is out of question. Your suggestion is reasonable. BR G.Robert Chen From: yang.r.yang@... [mailto:yang.r.yang@...]On Behalf Of Y. Richard Yang Sent: Friday, September 18,

Robert, It is great to have your contribution! I know that you have contributed an ALTO client when we conducted the previous interop in July. My feeling is that after we conduct a code review and you

Dear Richard,Wendy,Xiao,Xin, Thanks. I want to be committer and I shall do more on ALTO. BR G.Robert Chen From: alto-dev-bounces@... [mailto:alto-dev-bounces@...]On Behalf Of Y. Richard

Dear Wendy, Xiao, Xin, May I propose the following changes to committers: 1. Proposal: Add Kai, Shu, Jensen, as new committers. Justification (copy from Kai's summary): "Jensen has submitted

Colin, The three requests make sense. Let us follow the procedure and get them done soon. Thanks for the guidance! Richard

So, when the project proposal was approved, it was this: https://wiki.opendaylight.org/index.php?title=Project_Proposals:Alto&oldid=25169 There were 4 committers listed: * Xiao Shi (Shixiao) (Yale