Thanks Shu! This will surely help setting up the development environment. I'll let you know if I face any issue. On Aug 1, 2015 9:54 PM, "Shu Dong" <dongs2011@...> wrote:

Tamim, We identified two interfaces that we need to finish soon: - element state interface - routing state interface The key to implement ECS is to design and implement the two interfaces. It will be

Xiao, Thank you so much! Since such an environment can be useful to others, I cc'd the others on the list. If anyone else wants to use the setup, please let us know. Richard -- Richard

Thanks Dr. Yang. I'll look into it. It makes lot of sense to think before implementing. On Aug 2, 2015 3:49 AM, "Y. Richard Yang" <yry@...> wrote:

Hi all, The request on M1 status is coming as we expected. I believe there are only two things we need to take care of

Hi Kai, Thank you for the reminding. I’ll fill in the name soon. Best, Yichen

Thanks @Kai. I just updated the doc with my IRC handler. From, Shu

Hi mingming, I'm trying to find a API to compute the link path between two hosts. So I read the code from openflowplugin (add@... and addFlow@SalFlowServiceImpl). But seems the it just ad given flows

Hi JunZhuo, I have told Shu how to invoke addflow. Now the problem is how to compute path, right? I know that there is a ad sal routing method using D algorithm. now you have find md sal

Hi Mingming, Thanks! I haven't found the AD-SAL routing function yet and I'll continue to find it. Do you have any clues or keywords to pinpoint it? Because I can only locate the MD-SAL interfaces

Hi JunZhuo, There is a suggestion. You can take packet-in as a clue(Beacause It will cause packet-out referring to path calculation). I remember It is in openflowplugin. Then try to find its

Hi Mingming, I'll try to follow your recommendation, thanks a lot! Junzhuo 2015-08-06 0:10 GMT+08:00 陈明明 <mingmingminne@...>:

Hi JunZhuo, I would like to make a supplement. There is a packet-in reason. When the value is NO MATCH It will cause packet-out. I Hope It will help you. Best

Is this something to engage the ODL TSC to look into? Richard

To clarify, it is incomplete because it handles only the case of the same-switch, as implied by Junzhuo's testing? So the contribution is to handle cross-switch routing? Thanks. Richard

Hi all, I am sorry to come back so late. I sent email to cisco's stuff last Tuesday. He replied me as below: " Hi Mingming, I am sure there is somewhere used the Dijkstra algorithm for this. I

Hi Mingming, The current status is that Dijkstra algorithm is not be used in l2switch. The related code are all been annotated. And the authors of l2switch also says this module is not complete.

To add a bit, according to my understanding: - current l2switch uses flooding based on a single, shared spanning. Hence, assume a switch with k neighbors in the spanning tree, it needs only k rules in

Richard and Junzhuo, I would highly encourage you to submit your enhancements to l2switch. Please start contributing the project. Submit your proposal for Beryllium release. -Amit From:

Hi Tamim (cc alto-dev@...) In according with: https://docs.google.com/document/d/1nx2U5WvVlCU-dierN-EF9L5iAzRrNNr1S73EzsSjAmo/edit# Everething works fine until step: *Build and run ALTO in Karaf I