Date   

Re: [OpenDaylight TSC] All PTLs and TSC members, Please help filling in this ODL map survery

Gao Kai <gaok12@...>
 




-------- Forwarded Message --------
Subject: Re: [OpenDaylight TSC] All PTLs and TSC members, Please help filling in this ODL map survery
Date: Wed, 16 Sep 2015 16:32:04 -0700
From: katie.zhang.huawei@...
To: katie zhang <katie.zhang.huawei@...>, release@... <release@...>, tsc@... <tsc@...>



Hi:

When you and your team fill the form, if you don't want to expose your exactly location, please at least give me city, state and country instead of just a company name or city name. So google map can recognize it and i don't need to manually search your company's address since we have hundreds of people in our community. 

Thanks a lot for help making this map.

Katie   


On Sep 16, 2015, at 3:37 PM, katie zhang <katie.zhang.huawei@...> wrote:

Hi PTLs:

We are pulling projects name from current Beryllium release, if your project is not on it, you may not be able find your project in the project list, please email me to let me add your project name. 

thanks. 
katie

On Wed, Sep 16, 2015 at 2:46 PM, katie zhang <katie.zhang.huawei@...> wrote:
Hi all PTLs and TSC members: 


please fill in this form and forward it to your team member and people you know who works for ODL.


if above link is not working, please go to: 



I am making a ODL community map, so everybody got involved in ODL will be on a google based map. 

Please fill in this ODL community map survey for yourself.
 
All PTLs, please forward this form to all of your project committers to fill in, so we can have everybody on the map. I am relying on all PTLs to get the whole team to finish the survey, so we would not miss anybody on the map. :)

Really appreciate your work and help. 
--
Best

katie



--
Best

katie



Re: [OpenDaylight TSC] Fwd: Re: New committers

Y. Richard Yang
 

Hi Colin,

On Fri, Sep 11, 2015 at 2:48 PM, Colin Dixon <colin@...> wrote:
Out of curiosity, what do you mean when you say "Richard, the only committer of ALTO project at the moment"?

As I see it you have 8 committers listed here:
https://wiki.opendaylight.org/view/ALTO:Main

I think there is a misunderstanding here. When we listed the names on the preceding Web page, we thought those names would be contributors, i.e., they would participate in the project, but without the ability to commit in the sense of git approval. Hence, I am the only git committer/approver. This also explains why we added Huaming without seeking the approval of TSC. Does this clarify?

Richard
 


That's also odd because you only have 5 initial committers listed here and I don't remember the TSC approving more:
https://wiki.opendaylight.org/view/Project_Proposals:Alto#Initial_Committers

More odd is that you seem to have added  Huaming Guo as an initial committer after the project was approved on January 8th:
https://wiki.opendaylight.org/index.php?title=Project_Proposals%3AAlto&diff=26601&oldid=25169

--Colin


On Thu, Sep 10, 2015 at 10:53 PM, Gao Kai <gaok12@...> wrote:
Dear TSC,

We have carried out a public vote for three new committers in ALTO project [0].  Richard, the only committer of ALTO project at the moment, has voted +1 for all three candidates.

[0] https://lists.opendaylight.org/pipermail/alto-dev/2015-September/000217.html

Regards,
Kai

-------- Forwarded Message --------
Subject: Re: New committers
Date: Thu, 10 Sep 2015 22:33:06 -0400
From: Y. Richard Yang <yry@...>
To: Gao Kai <gaok12@...>
CC: alto-dev@... <alto-dev@...>, 张敬轩 <jingxuan.n.zhang@...>, Shu Dong <dongs2011@...>


Dear Kai,

I sure am impressed by the work of you three. As main contributors of the ALTO project, I support you three to become commiters to move the project further:
Jensen: +1
Kai: +1
Shu: +1

Richard

On Thursday, September 10, 2015, Gao Kai <gaok12@...> wrote:
Hi Richard and all,

I'd like to nominate three new committers for the ALTO project: Jensen, Kai and Shu.

Jensen has submitted a lot of commits on improving the code quality [1] by writing tests and fixing bugs and he is now a key member of the development team.

Kai ans Shu have implemented most components of ALTO Lithium release [2, 3].  They are also the actual project leaders of this project currently.

[1] https://git.opendaylight.org/gerrit/#/q/project:alto+owner:jensenzhang
[2] https://git.opendaylight.org/gerrit/#/q/owner:gaok12%40mails.tsinghua.edu.cn+status:merged+project:alto
[3] https://git.opendaylight.org/gerrit/#/q/owner:dongshu+status:merged+project:alto

Committers please vote +1, 0 or -1 for each of these developers.

Thanks.

Kai


--
Richard



_______________________________________________
TSC mailing list
TSC@...
https://lists.opendaylight.org/mailman/listinfo/tsc



_______________________________________________
alto-dev mailing list
alto-dev@...
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opendaylight.org_mailman_listinfo_alto-2Ddev&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=4G36iiEVb2m_v-0RnP2gx9KZJjYQgfvrOCE3789JGIA&m=nomUG6iXrvN5BBRA5FIhGJR3lzVqaO8KVxV0uCZ19nU&s=bZtQA2esJKKZvoNjIjYspsvxPyXb2NsiuGECN5qlj0U&e=




--
-- 
 =====================================
| Y. Richard Yang <yry@...>   |
| Professor of Computer Science       |
 =====================================


Re: [OpenDaylight TSC] Fwd: Re: New committers

Colin Dixon <colin@...>
 

Out of curiosity, what do you mean when you say "Richard, the only committer of ALTO project at the moment"?

As I see it you have 8 committers listed here:
https://wiki.opendaylight.org/view/ALTO:Main

That's also odd because you only have 5 initial committers listed here and I don't remember the TSC approving more:
https://wiki.opendaylight.org/view/Project_Proposals:Alto#Initial_Committers

More odd is that you seem to have added  Huaming Guo as an initial committer after the project was approved on January 8th:
https://wiki.opendaylight.org/index.php?title=Project_Proposals%3AAlto&diff=26601&oldid=25169

--Colin


On Thu, Sep 10, 2015 at 10:53 PM, Gao Kai <gaok12@...> wrote:
Dear TSC,

We have carried out a public vote for three new committers in ALTO project [0].  Richard, the only committer of ALTO project at the moment, has voted +1 for all three candidates.

[0] https://lists.opendaylight.org/pipermail/alto-dev/2015-September/000217.html

Regards,
Kai

-------- Forwarded Message --------
Subject: Re: New committers
Date: Thu, 10 Sep 2015 22:33:06 -0400
From: Y. Richard Yang <yry@...>
To: Gao Kai <gaok12@...>
CC: alto-dev@... <alto-dev@...>, 张敬轩 <jingxuan.n.zhang@...>, Shu Dong <dongs2011@...>


Dear Kai,

I sure am impressed by the work of you three. As main contributors of the ALTO project, I support you three to become commiters to move the project further:
Jensen: +1
Kai: +1
Shu: +1

Richard

On Thursday, September 10, 2015, Gao Kai <gaok12@...> wrote:
Hi Richard and all,

I'd like to nominate three new committers for the ALTO project: Jensen, Kai and Shu.

Jensen has submitted a lot of commits on improving the code quality [1] by writing tests and fixing bugs and he is now a key member of the development team.

Kai ans Shu have implemented most components of ALTO Lithium release [2, 3].  They are also the actual project leaders of this project currently.

[1] https://git.opendaylight.org/gerrit/#/q/project:alto+owner:jensenzhang
[2] https://git.opendaylight.org/gerrit/#/q/owner:gaok12%40mails.tsinghua.edu.cn+status:merged+project:alto
[3] https://git.opendaylight.org/gerrit/#/q/owner:dongshu+status:merged+project:alto

Committers please vote +1, 0 or -1 for each of these developers.

Thanks.

Kai


--
Richard



_______________________________________________
TSC mailing list
TSC@...
https://lists.opendaylight.org/mailman/listinfo/tsc



Re: New committers

Gao Kai <gaok12@...>
 

Dear TSC,

We have carried out a public vote for three new committers in ALTO project [0].  Richard, the only committer of ALTO project at the moment, has voted +1 for all three candidates.

[0] https://lists.opendaylight.org/pipermail/alto-dev/2015-September/000217.html

Regards,
Kai

-------- Forwarded Message --------
Subject: Re: New committers
Date: Thu, 10 Sep 2015 22:33:06 -0400
From: Y. Richard Yang <yry@...>
To: Gao Kai <gaok12@...>
CC: alto-dev@... <alto-dev@...>, 张敬轩 <jingxuan.n.zhang@...>, Shu Dong <dongs2011@...>


Dear Kai,

I sure am impressed by the work of you three. As main contributors of the ALTO project, I support you three to become commiters to move the project further:
Jensen: +1
Kai: +1
Shu: +1

Richard

On Thursday, September 10, 2015, Gao Kai <gaok12@...> wrote:
Hi Richard and all,

I'd like to nominate three new committers for the ALTO project: Jensen, Kai and Shu.

Jensen has submitted a lot of commits on improving the code quality [1] by writing tests and fixing bugs and he is now a key member of the development team.

Kai ans Shu have implemented most components of ALTO Lithium release [2, 3].  They are also the actual project leaders of this project currently.

[1] https://git.opendaylight.org/gerrit/#/q/project:alto+owner:jensenzhang
[2] https://git.opendaylight.org/gerrit/#/q/owner:gaok12%40mails.tsinghua.edu.cn+status:merged+project:alto
[3] https://git.opendaylight.org/gerrit/#/q/owner:dongshu+status:merged+project:alto

Committers please vote +1, 0 or -1 for each of these developers.

Thanks.

Kai


--
Richard



Re: New committers

Y. Richard Yang
 

Dear Kai,

I sure am impressed by the work of you three. As main contributors of the ALTO project, I support you three to become commiters to move the project further:
Jensen: +1
Kai: +1
Shu: +1

Richard


On Thursday, September 10, 2015, Gao Kai <gaok12@...> wrote:
Hi Richard and all,

I'd like to nominate three new committers for the ALTO project: Jensen, Kai and Shu.

Jensen has submitted a lot of commits on improving the code quality [1] by writing tests and fixing bugs and he is now a key member of the development team.

Kai ans Shu have implemented most components of ALTO Lithium release [2, 3].  They are also the actual project leaders of this project currently.

[1] https://git.opendaylight.org/gerrit/#/q/project:alto+owner:jensenzhang
[2] https://git.opendaylight.org/gerrit/#/q/owner:gaok12%40mails.tsinghua.edu.cn+status:merged+project:alto
[3] https://git.opendaylight.org/gerrit/#/q/owner:dongshu+status:merged+project:alto

Committers please vote +1, 0 or -1 for each of these developers.

Thanks.

Kai


--
Richard


New committers

Gao Kai <gaok12@...>
 

Hi Richard and all,

I'd like to nominate three new committers for the ALTO project: Jensen, Kai and Shu.

Jensen has submitted a lot of commits on improving the code quality [1] by writing tests and fixing bugs and he is now a key member of the development team.

Kai ans Shu have implemented most components of ALTO Lithium release [2, 3].  They are also the actual project leaders of this project currently.

[1] https://git.opendaylight.org/gerrit/#/q/project:alto+owner:jensenzhang
[2] https://git.opendaylight.org/gerrit/#/q/owner:gaok12%40mails.tsinghua.edu.cn+status:merged+project:alto
[3] https://git.opendaylight.org/gerrit/#/q/owner:dongshu+status:merged+project:alto

Committers please vote +1, 0 or -1 for each of these developers.

Thanks.

Kai


Re: Netconf Migration

Gao Kai <gaok12@...>
 

Hi An Ho,

The patch looks good.  Thanks for the help.

Regards,
Kai

On 11/09/15 06:32, An Ho wrote:

Hi Gao Kai and ALTO Team,

 

Could a committer take a look at this gerrit patch for netconf migration from controller code base to its own separate code base.  No functionality should be affected.  Let me know if you have any questions or concerns.

 

https://git.opendaylight.org/gerrit/#/c/26465/

 

Best Regards,

An Ho

 



_______________________________________________
alto-dev mailing list
alto-dev@...
https://lists.opendaylight.org/mailman/listinfo/alto-dev


Netconf Migration

an.ho@huawei.com
 

Hi Gao Kai and ALTO Team,

 

Could a committer take a look at this gerrit patch for netconf migration from controller code base to its own separate code base.  No functionality should be affected.  Let me know if you have any questions or concerns.

 

https://git.opendaylight.org/gerrit/#/c/26465/

 

Best Regards,

An Ho

 


ALTO M2 Status

Gao Kai <gaok12@...>
 

Project: ALTO

Offset: 2

Release plan finalized:  Yes

Extra configuration or resource needed: No.

Project check list completed:   Yes

Waive from system test: No

Use CI infrastructure for system test: Yes

List of acknowledged depend project:

List of unacknowledged depend project: l2switch

 

1.    Have you completed the project checklist [0]?
Yes

*     https://git.opendaylight.org/gerrit/#/c/26022/

*     https://lists.opendaylight.org/pipermail/alto-dev/2015-August/000183.html

*     https://bugs.opendaylight.org/show_bug.cgi?id=3760

*     http://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/alto/

*     https://sonar.opendaylight.org/dashboard/index/org.opendaylight.alto:alto-parent?did=1&

*     https://git.opendaylight.org/gerrit/gitweb?p=alto.git;a=blob;f=pom.xml


2.    Does your project have any special needs in CI Infrastructure (tools or configuration)?
No

 

3.    Is your project release plan finalized?
Yes
https://wiki.opendaylight.org/view/ALTO:Beryllium_Release_Plan

*     Do you have all APIs intended to be externally consumable listed?
Yes

*     Does each API have a useful short name?
No

*     Are the Java interface and/or YANG files listed for each API?
No, the externally consumable API is RESTful.

*     Are they labeled as tentative, provisional, or stable as appropriate for each API?
No

*     Do you call out the OSGi bundles and/or Karaf features providing the API for each API?
Yes

4.    All project dependencies (requests on other project's release plans) have been acknowledged and documented by upstream projects?
No 

5.    Were there any project-specific deliverables planned for this milestone?
No

 

Integration and Test:

 

1.    Will your project have top-level features not requiring system test?
No

2.    Will your project use the OpenDaylight CI infrastructure for testing top-level features requiring system test?
Yes



Dependency notification - ALTO depends on l2switch

Gao Kai <gaok12@...>
 

Dear L2Switch team,

The ALTO project formally makes a request for the dependency on L2Switch.

We use the information collected by host tracker to determine the location of a certain host.

Best Regards,
Kai


Dependency notification - ALTO depends on l2switch

Gao Kai <gaok12@...>
 

Dear L2Switch team,

The ALTO project formally makes a request for the dependency on L2Switch.

We use the information collected by host tracker to determine the location of a certain host.

Best Regards,
Kai


Dependency notification - ALTO depends on l2switch

Gao Kai <gaok12@...>
 

Dear L2Switch team,

The ALTO project formally makes a request for the dependency on L2Switch.

We use the information collected by host tracker to determine the location of a certain host.

Best Regards,
Kai


The time schedule about Lenovo's ECS deployment.

Austin
 

Hi Richard,

@Jensen and I have discussed the time schedule to cooperate with Lenovo. The major issues we didn't sync up with Lenovo are listed here:

1. The detail configuration of Lenovo's data center;
2. The requirements of ECS service from Lenovo;
3. The architecture of our ECS design;
4. Other details of our ECS implementation.

So we desire a summarize sync up, which is not late than 8th, Sept. Beijing time, directly to their development team. And we may have multiply meetings with their dev team to talk about their requirements and our limitations in next week (7th to 13th). Then we can quickly iterate our ECS design in the following two weeks (14th to 27th). Finally we may give a final version to Lenovo in the week of National Day.

Best regards,
Junzhuo


Re: Error dependecy "org.codehaus.jackson"

Danny
 

Hi Jensen

It was very helpful your reply.

1. I am using now com.fasterxml.jackson.core

2. At present I am modifying the Northbound module, because I am doing some tests recovering ALTO information of my Neo4j graph database (Not from MD-SAL data store), so I need only the input parameters (for example "id" in the retrieveNetworkMap function), after I create a RFC7285NetworkMap variable and to assigns its properties (for example "meta" and "map") from my ALTO information (recovered from a query to Neo4j) and return the request.

Thanks again

Ss

Danny

On Thu, Aug 27, 2015 at 10:45 PM, Jensen Zhang <jingxuan.n.zhang@...> wrote:
Hi Danny,

Projects in OpenDaylight use OSGi framework, and they need to be installed in karaf as features [1].

Because you introduce a new package into alto-northbound, you have to add new bundles or features in the 'odl-alto-northbound' feature. (It will be located in 'features/src/main/features/features.xml' or 'features/src/main/resources/features.xml'.)

But for your problem, I don't suggest you use org.codehaus.jackson in alto-northbound, unless necessary. Because:

1. You can use com.fasterxml.jackson.core [2], since this is a newer jackson implementation than org.codehaus.jackson. And we have imported bundles for this into alto-commons which is an dependency of alto-northbound, so you can just repleace the dependency declaration in alto-northbound by this new one.
2. But you'd better not use jackson in northbound module. It is just a front-end and it should not implement any complex logic. You can implement your functions in alto-services or alto-provider. For example, the implementation of 'getNetworkMap' is in 'alto-services/provider/simple-alto/src/main/java/org/opendaylight/alto/services/provider/simple/SimpleAltoService.java'.

Hope this is helpful to you.

---
Thanks,
Jensen

2015-08-28 4:44 GMT+08:00 Danny Alex Lachos Perez <dlachosper@...>:
Hi Jensen,

I have a problem when I want to use the "jackson" library in my ALTO project.

I am modifying the alto-Northbound project, I am adding a few code lines:

=======================================================
In pox file of alto-Northbound project I added:

<dependency>
      <groupId>org.codehaus.jackson</groupId>
      <artifactId>jackson-core-asl</artifactId>
      <version>1.9.7</version>          
    </dependency>

in imports add:

org.codehaus.jackson.jackson-core-asl.*
========================================================
In Java code (AltoNorthbound.java), I added:

import org.codehaus.jackson.JsonNode;
...
JsonNode rows = response.getEntity(JsonNode.class);
============================================================

The error is:
java.lang.NoClassDefFoundError: org/codehaus/jackson/JsonNode
    at org.opendaylight.alto.northbound.AltoNorthbound.REST_Query(AltoNorthbound.java:234)
    at org.opendaylight.alto.northbound.AltoNorthbound.retrieveNetworkMap(AltoNorthbound.java:166)

========================================================

Ss

Danny



Re: [release] survival guides for M2 and M3?

Gao Kai
 

Hi everyone,

I just received this email from the release mailing list and I think everyone should at least take a look at the links below.

Regards,
Kai


-------- Forwarded Message --------
Subject: Re: [release] survival guides for M2 and M3?
Date: Thu, 27 Aug 2015 15:24:51 +0000
From: An Ho <An.Ho@...>
To: Colin Dixon <colin@...>, tsc@... <tsc@...>, release@... <release@...>


Hi Colin,

 

This is a very good suggestion.  I’ve created a wiki page which I will soon populate based on my previous experience with M2 and M3.  But other folks should feel free to add their own thoughts as well.

 

https://wiki.opendaylight.org/view/Release:Guides:M2

https://wiki.opendaylight.org/view/Release:Guides:M3

 

Best Regards,

An Ho

 

From: release-bounces@... [mailto:release-bounces@...] On Behalf Of Colin Dixon
Sent: Thursday, August 27, 2015 7:44 AM
To: tsc@...; release@...
Subject: [release] survival guides for M2 and M3?

 

There's substantially more that needs to be done for M2 and M3 than M1 and we have a bunch of new projects in Beryllium. To help that, it would be useful if people that had been through it a few times could provide some form of guide to getting through it.

Is anyone willing to take that on?

Cheers,

--Colin




Re: Error dependecy "org.codehaus.jackson"

Jensen Zhang
 

Hi Danny,

Projects in OpenDaylight use OSGi framework, and they need to be installed in karaf as features [1].

Because you introduce a new package into alto-northbound, you have to add new bundles or features in the 'odl-alto-northbound' feature. (It will be located in 'features/src/main/features/features.xml' or 'features/src/main/resources/features.xml'.)

But for your problem, I don't suggest you use org.codehaus.jackson in alto-northbound, unless necessary. Because:

1. You can use com.fasterxml.jackson.core [2], since this is a newer jackson implementation than org.codehaus.jackson. And we have imported bundles for this into alto-commons which is an dependency of alto-northbound, so you can just repleace the dependency declaration in alto-northbound by this new one.
2. But you'd better not use jackson in northbound module. It is just a front-end and it should not implement any complex logic. You can implement your functions in alto-services or alto-provider. For example, the implementation of 'getNetworkMap' is in 'alto-services/provider/simple-alto/src/main/java/org/opendaylight/alto/services/provider/simple/SimpleAltoService.java'.

Hope this is helpful to you.

---

Hi Jensen,

I have a problem when I want to use the "jackson" library in my ALTO project.

I am modifying the alto-Northbound project, I am adding a few code lines:

=======================================================
In pox file of alto-Northbound project I added:

<dependency>
      <groupId>org.codehaus.jackson</groupId>
      <artifactId>jackson-core-asl</artifactId>
      <version>1.9.7</version>          
    </dependency>

in imports add:

org.codehaus.jackson.jackson-core-asl.*
========================================================
In Java code (AltoNorthbound.java), I added:

import org.codehaus.jackson.JsonNode;
...
JsonNode rows = response.getEntity(JsonNode.class);
============================================================

The error is:
java.lang.NoClassDefFoundError: org/codehaus/jackson/JsonNode
    at org.opendaylight.alto.northbound.AltoNorthbound.REST_Query(AltoNorthbound.java:234)
    at org.opendaylight.alto.northbound.AltoNorthbound.retrieveNetworkMap(AltoNorthbound.java:166)

========================================================

Ss

Danny


Error dependecy "org.codehaus.jackson"

Danny
 

Hi Jensen,

I have a problem when I want to use the "jackson" library in my ALTO project.

I am modifying the alto-Northbound project, I am adding a few code lines:

=======================================================
In pox file of alto-Northbound project I added:

<dependency>
      <groupId>org.codehaus.jackson</groupId>
      <artifactId>jackson-core-asl</artifactId>
      <version>1.9.7</version>          
    </dependency>

in imports add:

org.codehaus.jackson.jackson-core-asl.*
========================================================
In Java code (AltoNorthbound.java), I added:

import org.codehaus.jackson.JsonNode;
...
JsonNode rows = response.getEntity(JsonNode.class);
============================================================

The error is:
java.lang.NoClassDefFoundError: org/codehaus/jackson/JsonNode
    at org.opendaylight.alto.northbound.AltoNorthbound.REST_Query(AltoNorthbound.java:234)
    at org.opendaylight.alto.northbound.AltoNorthbound.retrieveNetworkMap(AltoNorthbound.java:166)

========================================================

Ss

Danny


Re: Few questions on ALTO and ONOS

dongshu
 

Hi Danny,

I just updated the doc as you suggested. Thanks a lot.

From,
Shu

On Sat, Aug 22, 2015 at 8:53 PM, Danny Alex Lachos Perez <dlachosper@...> wrote:
Hi all.

Thank for your answer.

As Jensen mentioned, I was using the MASTER branch. Now I am using the STABLE/LITHIUM branch and I already have available http://localhost:8181/apidoc/explorer/index.html. Now, I will continue testing some others ALTO Features and any other question or problem I will write. We at University of Campinas are developing a proof of concept of ALTO server implementation (for IXP-related use cases) based on Neo4j graph DB and OpenDaylight.

So once again, many thanks.

Ss

Danny

ps: I think that the manual (https://docs.google.com/document/d/1nx2U5WvVlCU-dierN-EF9L5iAzRrNNr1S73EzsSjAmo/edit#) could be updated because It is not clearly specified what kind of branch should be downloaded.


On Fri, Aug 21, 2015 at 1:19 PM, Jensen Zhang <jingxuan.n.zhang@...> wrote:
Hi Danny,

I just notice that the version of odl-alto-provider you used is 0.2.0-SNAPSHOT, so I guess that you were using the latest master branch code in the ODL gerrit, right? This branch is unstable, and still has some bugs which are not fixed by us. So I suggest you try the stable/lithium branch, and I think the odl-alto-provider feature can work well in this branch. Also, we will fix bugs and make master branch work as soon as possible. But this is a developing branch and we are adding many new functions for it, so I cannot make sure it is stable.

The apidoc explorer (http://localhost:8181/apidoc/explorer/index.html) is provided by ODL (https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Restconf_API_Explorer), and it is independent of odl-alto-* feature. So I guess the karaf was not set up normally, if you couldn't connect to it. You can check the karaf log for more details, or post it up so that we can help you solve the problem better.

Best,
Jensen

2015-08-21 22:21 GMT+08:00 Danny Alex Lachos Perez <dlachosper@...>:
Hi Tamim (cc alto-dev@...)

In according with:

Everething works fine until step:
*Build and run ALTO in Karaf

I install a feature, for example:
feature:install odl-alto-provider

After that, I should be able to:

but I cant: "Unable to connect"

When I review the feature information:

feature:info odl-alto-provider
Feature odl-alto-provider 0.2.0-SNAPSHOT
Description:
  OpenDaylight :: alto :: Provider
Feature has no configuration
Feature configuration files:
  etc/opendaylight/karaf/03-alto.xml
Feature depends on:
  odl-alto-model 0.2.0-SNAPSHOT
  odl-mdsal-broker 1.3.0-SNAPSHOT
  odl-l2switch-hosttracker 0.3.0-SNAPSHOT
  odl-l2switch-addresstracker 0.3.0-SNAPSHOT
Feature contains followed bundles:
  mvn:org.opendaylight.alto/alto-provider/0.2.0-SNAPSHOT
Feature has no conditionals.


and review if the bundles are installed
bundle:list -s | grep alto
204 | Resolved |  80 | 0.2.0.SNAPSHOT                            | org.opendaylight.alto.model  
233 | Resolved |  80 | 0.3.0.SNAPSHOT                            | org.opendaylight.l2switch.addresstracker.impl                           
234 | Resolved |  80 | 0.3.0.SNAPSHOT                            | org.opendaylight.l2switch.hosttracker.model                             
235 | Resolved |  80 | 0.3.0.SNAPSHOT                            | org.opendaylight.l2switch.hosttracker.impl

None of the bundles are installed

Another things is that when I review the activated ports:
 nmap chimay
Starting Nmap 6.40 ( http://nmap.org ) at 2015-08-21 11:15 BRT
Nmap scan report for chimay (127.0.1.1)
Host is up (0.00022s latency).
Not shown: 996 closed ports
PORT     STATE SERVICE
22/tcp   open  ssh
53/tcp   open  domain
111/tcp  open  rpcbind
1099/tcp open  rmiregistry


The 8181 port is not activited

I dont know exactly what happen,

Thank

Ss

Danny

On Sat, Aug 1, 2015 at 10:54 PM, Shu Dong <dongs2011@...> wrote:
Hi Tamim,

Sorry for the delay, I just saw your email.

I wrote a doc for people to get into ODL and ALTO quickly. You can start from it: https://docs.google.com/document/d/1nx2U5WvVlCU-dierN-EF9L5iAzRrNNr1S73EzsSjAmo/edit#. Also, there some local code changes including interop tests and the new ECS implementation we have not pushed into ODL Gerrit but we will soon. I will remind you when the code has been updated. 

Hope it helps. Thanks a lot.

From,
Shu

On Sun, Aug 2, 2015 at 9:38 AM, MD I. Islam <tamim@...> wrote:

Thanks Dr. Yang. My skype ID: tamim_217. I'm visiting Cincinnati. Still I will attend the meeting over phone.

On Aug 1, 2015 9:32 PM, "Y. Richard Yang" <yry@...> wrote:
@Shu, thanks a lot for providing the update! 

@Tamim, we do not use a single VM. Let's see what we can do to get the sharing-with-you started.

We will have a sync up at 10 pm (US ET) today. If you get this email in time, please send me your Skype so that I can add you.

Thanks!

Richard 

On Sunday, August 2, 2015, MD I. Islam <tamim@...> wrote:

Thanks Shu! Is it possible to share the VM (development environment) with me? I'm new to ODL. Having everything setup would be very helpful for me to start with.

Thanks
Tamim

On Aug 1, 2015 1:32 PM, "Shu Dong" <dongs2011@...> wrote:
Hi Tamim and Richard,

Here is how we compute the ECS now. We get the routing path from source host to dest host first, and then compute the endpoint cost according to the routing path and cost metric (e.g. bandwidth, hopcount). 

Computing routing path in ODL is the core of the design and the details are explained as follows:
1. We get the attachment points of source host and dest host, let's call it start_switch and end_switch, by L2Switch.
2. We read flow table of start_switch and find the matched flow entry according to src host IP and dst host IP. If matched flow entry is found, we get next switch from the flow entry, then we repeat this step to chase next switch until we get to end_switch.
4. If there is no matched flow entry, we will force ODL controller to compute a new routing path, by either invoking the path computing function or sending a fake packet. Once the path computing is done, we repeat step 2 until we get to end_switch.

In this way, we get the routing path. Following is the pseudo code:

sw_id = get_attachment_point(src)
dst_sw_id = get_attachment_point(dst)
while (sw_id != dst_sw_id) {
  r <- loop_up(src, dst) in sw_id's flow table
  if (!r) {
    forceComputeRoutingPath(src, dst)
    r <- loop_up(src, dst) in sw_id's flow table
  } 
  sw_id = get_sw_id(r) 
}
 

Once we get the routing path, we can compute endpoint costs based on different cost metrics. Hopcount is easy to compute while bandwidth is a little more complicated since we have to get the bandwidth of each link at first.

@Richard The following is what we have done during the past three days:
1. Get attachment point of host by host IP address. Done. (Shu, Xiao)
2. Look up flow table to get matching flow entry and next switch. Almost Done. (Xiao, Shu)
3. Figure out how to force ODL controller to compute routing path. In progress. (Mingming)
4. Setting up a mininet + controller test environment in our lab. (Junzhuo, Xiao)
5. Some code refactoring. (Shu)

Things left to be done:
1. Figure out how to force ODL controller to compute routing path.
2. Figure out how to get bandwidth of each link.
3. Combine all the parts together.

From tomorrow, we will focus on left problems. Mingming has made some progress in the first one but it will be great if we have someone else to help.

Thanks a lot.

From,
Shu


On Sat, Aug 1, 2015 at 11:55 PM, Y. Richard Yang <yry@...> wrote:
Dear Tamim,

Thanks for the update. We had a mini design summit on ECS last week. The plan is to have a running version in two weeks. Given your questions, it is a good idea that we write down the design soon so that we can all work together. 

@Shu/Junzhuo: I believe that you are leading the ECS design. Can you write down the discussion soon so that we can discuss with Tamim and others.

Thanks!

Richard

On Sat, Aug 1, 2015 at 11:32 AM, MD I. Islam <tamim@...> wrote:
Hi

Could you please advise me if I have understood ECS correctly? 

I was told, in the first step, we calculate the shortest hop-count assuming that the link metric is 1. Do we just implement a shortest-path algorithm for the topology graph based on the data from TopologyManager?

Next step is to figure out a natural interface, in ODL, to configure link metrics and compute routing cost. Do we design a YANG model to configure link properties (link cost metrics)? Currently I don't see link properties (such as delay, bandwidth) in NodeConnector or TopologyUserLinkConfig. Am I missing anything? Do we have to design a data structure to store the cost metric for each link?

Which version of ODL do I look into? I don't see TopologyManager code in the Lithium release. I only see the class files. Am I missing anything? However I see the TopologyManager in Hydrogen release. 

Looking forward to your suggestions.

Thanks
Tamim  

.

On Fri, Jul 17, 2015 at 11:19 PM, MD I. Islam <tamim@...> wrote:

Thanks Kai! I'm looking into it.

On Jul 17, 2015 11:07 PM, "Y. Richard Yang" <yry@...> wrote:
Tamim,

Yes. As Kai pointed out, the TopologyManager is a good place to get started. Could you please start to take a look and then we can sync up?

Thanks!

Richard 

On Saturday, July 18, 2015, Gao Kai <godrickk@...> wrote:
There was a topologymanager in earlier releases you might look into.

On 18/07/15 02:14, MD I. Islam wrote:
That sounds great. Is there an ODL service that I can use to get the network topology and link metric? 

On Fri, Jul 17, 2015 at 1:36 PM, Y. Richard Yang <yry@...> wrote:
Tamim,

On Saturday, July 18, 2015, MD I. Islam <mislam4@...> wrote:
Yeah, interested. Is that the Endpoint Cost Service?
 
Yes. You got it.

 
What are the metrics we are considering? 

One basic step is to make sure we get shortest path fully right. A natural link metric is 1, and we get shortest hop count. A next step is to figure out a natural interface, in ODL, to configure link metrics, and we compute routing cost. A third component in ODL to conduct traffic engineering.

Let's get a couple proposals out in next week. How does this sound?

Richard 
 

On Fri, Jul 17, 2015 at 12:45 PM, Y. Richard Yang <yry@...> wrote:
Dear Tamim,

Wonderful! 

Per my personal wish list, a main feature that I want to improve on is high quality ECS service, based on various metrics. Any interest?

Richard

On Sat, Jul 18, 2015 at 12:35 AM, MD I. Islam <mislam4@...> wrote:
Yeah, sure. I'm interested on adding features to the ALTO ODL server. Please let me know what you want me to do.

Thanks
Tamim

On Fri, Jul 17, 2015 at 12:12 PM, Y. Richard Yang <yry@...> wrote:
Dear Tamim,

Thanks a lot for the questions. Sorry for the late reply, as I am working on a few deadlines. How about we schedule a time to discuss the items in details later next week?

In the mean time, are you interested in engaging more in the alto effort? For example, we are working on adding more features to the ODL server. Any interest in getting engaged?

Thanks!

Richard

On Thu, Jul 16, 2015 at 2:27 PM, MD I. Islam <mislam4@...> wrote:

I have few questions in mind.

How can we get the dynamic cost map from OpenFlow switch? Do we use OpenFlow meter? Are we considering about dynamic cost-map at all? As there will be multiple competing flows, so available bandwidth will change over time. Please advise.

Can we also create a paradigm to cache contents in the SDN controller (or in a controller app)? I think, this shouldn't be in the context of ALTO, but still would be very helpful. For example, if multiple clients watch a live video on a campus network, we should be able to cache the video slices in the controller. Then controller can push the content proactivly without notifying the clients. Again controller can serve the content in a reactive manner through a north bound protocol.

Today I was trying to write a simple application in ONOS. I was trying the VM from sdnhub. I could run ONOS. The sample Foo program compiled, but I couldn't load it on Karaf. If you have a VM that has the development environment setup, that will be very helpful to start.

Please don't hesitate to let me know if i get anything wrong. Looking forward to your suggestions.

Thanks
Tamim




--
-- 
 =====================================
| Y. Richard Yang <yry@...>   |
| Professor of Computer Science       |
 =====================================




--
-- 
 =====================================
| Y. Richard Yang <yry@...>   |
| Professor of Computer Science       |
 =====================================

_______________________________________________
alto-dev mailing list
alto-dev@...
https://lists.opendaylight.org/mailman/listinfo/alto-dev




--
Richard

_______________________________________________
alto-dev mailing list
alto-dev@...
https://lists.opendaylight.org/mailman/listinfo/alto-dev




_______________________________________________
alto-dev mailing list
alto-dev@...
https://lists.opendaylight.org/mailman/listinfo/alto-dev



--
Richard

_______________________________________________
alto-dev mailing list
alto-dev@...
https://lists.opendaylight.org/mailman/listinfo/alto-dev





--
-- 
 =====================================
| Y. Richard Yang <yry@...>   |
| Professor of Computer Science       |
 =====================================

--
You received this message because you are subscribed to the Google Groups "alto-design" group.
To unsubscribe from this group and stop receiving emails from it, send an email to alto-design+unsubscribe@....
To post to this group, send email to alto-design@....
To view this discussion on the web visit https://groups.google.com/d/msgid/alto-design/CANUuoLqi%3DU_mcv1gm5Rgf0p48PdLX3V_xrHLngwk%2BADCrEmFsg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.



--
Richard


_______________________________________________
alto-dev mailing list
alto-dev@...
https://lists.opendaylight.org/mailman/listinfo/alto-dev



_______________________________________________
alto-dev mailing list
alto-dev@...
https://lists.opendaylight.org/mailman/listinfo/alto-dev





Re: Few questions on ALTO and ONOS

Danny
 

Hi all.

Thank for your answer.

As Jensen mentioned, I was using the MASTER branch. Now I am using the STABLE/LITHIUM branch and I already have available http://localhost:8181/apidoc/explorer/index.html. Now, I will continue testing some others ALTO Features and any other question or problem I will write. We at University of Campinas are developing a proof of concept of ALTO server implementation (for IXP-related use cases) based on Neo4j graph DB and OpenDaylight.

So once again, many thanks.

Ss

Danny

ps: I think that the manual (https://docs.google.com/document/d/1nx2U5WvVlCU-dierN-EF9L5iAzRrNNr1S73EzsSjAmo/edit#) could be updated because It is not clearly specified what kind of branch should be downloaded.


On Fri, Aug 21, 2015 at 1:19 PM, Jensen Zhang <jingxuan.n.zhang@...> wrote:
Hi Danny,

I just notice that the version of odl-alto-provider you used is 0.2.0-SNAPSHOT, so I guess that you were using the latest master branch code in the ODL gerrit, right? This branch is unstable, and still has some bugs which are not fixed by us. So I suggest you try the stable/lithium branch, and I think the odl-alto-provider feature can work well in this branch. Also, we will fix bugs and make master branch work as soon as possible. But this is a developing branch and we are adding many new functions for it, so I cannot make sure it is stable.

The apidoc explorer (http://localhost:8181/apidoc/explorer/index.html) is provided by ODL (https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Restconf_API_Explorer), and it is independent of odl-alto-* feature. So I guess the karaf was not set up normally, if you couldn't connect to it. You can check the karaf log for more details, or post it up so that we can help you solve the problem better.

Best,
Jensen

2015-08-21 22:21 GMT+08:00 Danny Alex Lachos Perez <dlachosper@...>:
Hi Tamim (cc alto-dev@...)

In according with:

Everething works fine until step:
*Build and run ALTO in Karaf

I install a feature, for example:
feature:install odl-alto-provider

After that, I should be able to:

but I cant: "Unable to connect"

When I review the feature information:

feature:info odl-alto-provider
Feature odl-alto-provider 0.2.0-SNAPSHOT
Description:
  OpenDaylight :: alto :: Provider
Feature has no configuration
Feature configuration files:
  etc/opendaylight/karaf/03-alto.xml
Feature depends on:
  odl-alto-model 0.2.0-SNAPSHOT
  odl-mdsal-broker 1.3.0-SNAPSHOT
  odl-l2switch-hosttracker 0.3.0-SNAPSHOT
  odl-l2switch-addresstracker 0.3.0-SNAPSHOT
Feature contains followed bundles:
  mvn:org.opendaylight.alto/alto-provider/0.2.0-SNAPSHOT
Feature has no conditionals.


and review if the bundles are installed
bundle:list -s | grep alto
204 | Resolved |  80 | 0.2.0.SNAPSHOT                            | org.opendaylight.alto.model  
233 | Resolved |  80 | 0.3.0.SNAPSHOT                            | org.opendaylight.l2switch.addresstracker.impl                           
234 | Resolved |  80 | 0.3.0.SNAPSHOT                            | org.opendaylight.l2switch.hosttracker.model                             
235 | Resolved |  80 | 0.3.0.SNAPSHOT                            | org.opendaylight.l2switch.hosttracker.impl

None of the bundles are installed

Another things is that when I review the activated ports:
 nmap chimay
Starting Nmap 6.40 ( http://nmap.org ) at 2015-08-21 11:15 BRT
Nmap scan report for chimay (127.0.1.1)
Host is up (0.00022s latency).
Not shown: 996 closed ports
PORT     STATE SERVICE
22/tcp   open  ssh
53/tcp   open  domain
111/tcp  open  rpcbind
1099/tcp open  rmiregistry


The 8181 port is not activited

I dont know exactly what happen,

Thank

Ss

Danny

On Sat, Aug 1, 2015 at 10:54 PM, Shu Dong <dongs2011@...> wrote:
Hi Tamim,

Sorry for the delay, I just saw your email.

I wrote a doc for people to get into ODL and ALTO quickly. You can start from it: https://docs.google.com/document/d/1nx2U5WvVlCU-dierN-EF9L5iAzRrNNr1S73EzsSjAmo/edit#. Also, there some local code changes including interop tests and the new ECS implementation we have not pushed into ODL Gerrit but we will soon. I will remind you when the code has been updated. 

Hope it helps. Thanks a lot.

From,
Shu

On Sun, Aug 2, 2015 at 9:38 AM, MD I. Islam <tamim@...> wrote:

Thanks Dr. Yang. My skype ID: tamim_217. I'm visiting Cincinnati. Still I will attend the meeting over phone.

On Aug 1, 2015 9:32 PM, "Y. Richard Yang" <yry@...> wrote:
@Shu, thanks a lot for providing the update! 

@Tamim, we do not use a single VM. Let's see what we can do to get the sharing-with-you started.

We will have a sync up at 10 pm (US ET) today. If you get this email in time, please send me your Skype so that I can add you.

Thanks!

Richard 

On Sunday, August 2, 2015, MD I. Islam <tamim@...> wrote:

Thanks Shu! Is it possible to share the VM (development environment) with me? I'm new to ODL. Having everything setup would be very helpful for me to start with.

Thanks
Tamim

On Aug 1, 2015 1:32 PM, "Shu Dong" <dongs2011@...> wrote:
Hi Tamim and Richard,

Here is how we compute the ECS now. We get the routing path from source host to dest host first, and then compute the endpoint cost according to the routing path and cost metric (e.g. bandwidth, hopcount). 

Computing routing path in ODL is the core of the design and the details are explained as follows:
1. We get the attachment points of source host and dest host, let's call it start_switch and end_switch, by L2Switch.
2. We read flow table of start_switch and find the matched flow entry according to src host IP and dst host IP. If matched flow entry is found, we get next switch from the flow entry, then we repeat this step to chase next switch until we get to end_switch.
4. If there is no matched flow entry, we will force ODL controller to compute a new routing path, by either invoking the path computing function or sending a fake packet. Once the path computing is done, we repeat step 2 until we get to end_switch.

In this way, we get the routing path. Following is the pseudo code:

sw_id = get_attachment_point(src)
dst_sw_id = get_attachment_point(dst)
while (sw_id != dst_sw_id) {
  r <- loop_up(src, dst) in sw_id's flow table
  if (!r) {
    forceComputeRoutingPath(src, dst)
    r <- loop_up(src, dst) in sw_id's flow table
  } 
  sw_id = get_sw_id(r) 
}
 

Once we get the routing path, we can compute endpoint costs based on different cost metrics. Hopcount is easy to compute while bandwidth is a little more complicated since we have to get the bandwidth of each link at first.

@Richard The following is what we have done during the past three days:
1. Get attachment point of host by host IP address. Done. (Shu, Xiao)
2. Look up flow table to get matching flow entry and next switch. Almost Done. (Xiao, Shu)
3. Figure out how to force ODL controller to compute routing path. In progress. (Mingming)
4. Setting up a mininet + controller test environment in our lab. (Junzhuo, Xiao)
5. Some code refactoring. (Shu)

Things left to be done:
1. Figure out how to force ODL controller to compute routing path.
2. Figure out how to get bandwidth of each link.
3. Combine all the parts together.

From tomorrow, we will focus on left problems. Mingming has made some progress in the first one but it will be great if we have someone else to help.

Thanks a lot.

From,
Shu


On Sat, Aug 1, 2015 at 11:55 PM, Y. Richard Yang <yry@...> wrote:
Dear Tamim,

Thanks for the update. We had a mini design summit on ECS last week. The plan is to have a running version in two weeks. Given your questions, it is a good idea that we write down the design soon so that we can all work together. 

@Shu/Junzhuo: I believe that you are leading the ECS design. Can you write down the discussion soon so that we can discuss with Tamim and others.

Thanks!

Richard

On Sat, Aug 1, 2015 at 11:32 AM, MD I. Islam <tamim@...> wrote:
Hi

Could you please advise me if I have understood ECS correctly? 

I was told, in the first step, we calculate the shortest hop-count assuming that the link metric is 1. Do we just implement a shortest-path algorithm for the topology graph based on the data from TopologyManager?

Next step is to figure out a natural interface, in ODL, to configure link metrics and compute routing cost. Do we design a YANG model to configure link properties (link cost metrics)? Currently I don't see link properties (such as delay, bandwidth) in NodeConnector or TopologyUserLinkConfig. Am I missing anything? Do we have to design a data structure to store the cost metric for each link?

Which version of ODL do I look into? I don't see TopologyManager code in the Lithium release. I only see the class files. Am I missing anything? However I see the TopologyManager in Hydrogen release. 

Looking forward to your suggestions.

Thanks
Tamim  

.

On Fri, Jul 17, 2015 at 11:19 PM, MD I. Islam <tamim@...> wrote:

Thanks Kai! I'm looking into it.

On Jul 17, 2015 11:07 PM, "Y. Richard Yang" <yry@...> wrote:
Tamim,

Yes. As Kai pointed out, the TopologyManager is a good place to get started. Could you please start to take a look and then we can sync up?

Thanks!

Richard 

On Saturday, July 18, 2015, Gao Kai <godrickk@...> wrote:
There was a topologymanager in earlier releases you might look into.

On 18/07/15 02:14, MD I. Islam wrote:
That sounds great. Is there an ODL service that I can use to get the network topology and link metric? 

On Fri, Jul 17, 2015 at 1:36 PM, Y. Richard Yang <yry@...> wrote:
Tamim,

On Saturday, July 18, 2015, MD I. Islam <mislam4@...> wrote:
Yeah, interested. Is that the Endpoint Cost Service?
 
Yes. You got it.

 
What are the metrics we are considering? 

One basic step is to make sure we get shortest path fully right. A natural link metric is 1, and we get shortest hop count. A next step is to figure out a natural interface, in ODL, to configure link metrics, and we compute routing cost. A third component in ODL to conduct traffic engineering.

Let's get a couple proposals out in next week. How does this sound?

Richard 
 

On Fri, Jul 17, 2015 at 12:45 PM, Y. Richard Yang <yry@...> wrote:
Dear Tamim,

Wonderful! 

Per my personal wish list, a main feature that I want to improve on is high quality ECS service, based on various metrics. Any interest?

Richard

On Sat, Jul 18, 2015 at 12:35 AM, MD I. Islam <mislam4@...> wrote:
Yeah, sure. I'm interested on adding features to the ALTO ODL server. Please let me know what you want me to do.

Thanks
Tamim

On Fri, Jul 17, 2015 at 12:12 PM, Y. Richard Yang <yry@...> wrote:
Dear Tamim,

Thanks a lot for the questions. Sorry for the late reply, as I am working on a few deadlines. How about we schedule a time to discuss the items in details later next week?

In the mean time, are you interested in engaging more in the alto effort? For example, we are working on adding more features to the ODL server. Any interest in getting engaged?

Thanks!

Richard

On Thu, Jul 16, 2015 at 2:27 PM, MD I. Islam <mislam4@...> wrote:

I have few questions in mind.

How can we get the dynamic cost map from OpenFlow switch? Do we use OpenFlow meter? Are we considering about dynamic cost-map at all? As there will be multiple competing flows, so available bandwidth will change over time. Please advise.

Can we also create a paradigm to cache contents in the SDN controller (or in a controller app)? I think, this shouldn't be in the context of ALTO, but still would be very helpful. For example, if multiple clients watch a live video on a campus network, we should be able to cache the video slices in the controller. Then controller can push the content proactivly without notifying the clients. Again controller can serve the content in a reactive manner through a north bound protocol.

Today I was trying to write a simple application in ONOS. I was trying the VM from sdnhub. I could run ONOS. The sample Foo program compiled, but I couldn't load it on Karaf. If you have a VM that has the development environment setup, that will be very helpful to start.

Please don't hesitate to let me know if i get anything wrong. Looking forward to your suggestions.

Thanks
Tamim




--
-- 
 =====================================
| Y. Richard Yang <yry@...>   |
| Professor of Computer Science       |
 =====================================




--
-- 
 =====================================
| Y. Richard Yang <yry@...>   |
| Professor of Computer Science       |
 =====================================

_______________________________________________
alto-dev mailing list
alto-dev@...
https://lists.opendaylight.org/mailman/listinfo/alto-dev




--
Richard

_______________________________________________
alto-dev mailing list
alto-dev@...
https://lists.opendaylight.org/mailman/listinfo/alto-dev




_______________________________________________
alto-dev mailing list
alto-dev@...
https://lists.opendaylight.org/mailman/listinfo/alto-dev



--
Richard

_______________________________________________
alto-dev mailing list
alto-dev@...
https://lists.opendaylight.org/mailman/listinfo/alto-dev





--
-- 
 =====================================
| Y. Richard Yang <yry@...>   |
| Professor of Computer Science       |
 =====================================

--
You received this message because you are subscribed to the Google Groups "alto-design" group.
To unsubscribe from this group and stop receiving emails from it, send an email to alto-design+unsubscribe@....
To post to this group, send email to alto-design@....
To view this discussion on the web visit https://groups.google.com/d/msgid/alto-design/CANUuoLqi%3DU_mcv1gm5Rgf0p48PdLX3V_xrHLngwk%2BADCrEmFsg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.



--
Richard


_______________________________________________
alto-dev mailing list
alto-dev@...
https://lists.opendaylight.org/mailman/listinfo/alto-dev



_______________________________________________
alto-dev mailing list
alto-dev@...
https://lists.opendaylight.org/mailman/listinfo/alto-dev




Re: Few questions on ALTO and ONOS

Jensen Zhang
 

Hi Danny,

I just notice that the version of odl-alto-provider you used is 0.2.0-SNAPSHOT, so I guess that you were using the latest master branch code in the ODL gerrit, right? This branch is unstable, and still has some bugs which are not fixed by us. So I suggest you try the stable/lithium branch, and I think the odl-alto-provider feature can work well in this branch. Also, we will fix bugs and make master branch work as soon as possible. But this is a developing branch and we are adding many new functions for it, so I cannot make sure it is stable.

The apidoc explorer (http://localhost:8181/apidoc/explorer/index.html) is provided by ODL (https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Restconf_API_Explorer), and it is independent of odl-alto-* feature. So I guess the karaf was not set up normally, if you couldn't connect to it. You can check the karaf log for more details, or post it up so that we can help you solve the problem better.

Best,
Jensen

2015-08-21 22:21 GMT+08:00 Danny Alex Lachos Perez <dlachosper@...>:

Hi Tamim (cc alto-dev@...)

In according with:

Everething works fine until step:
*Build and run ALTO in Karaf

I install a feature, for example:
feature:install odl-alto-provider

After that, I should be able to:

but I cant: "Unable to connect"

When I review the feature information:

feature:info odl-alto-provider
Feature odl-alto-provider 0.2.0-SNAPSHOT
Description:
  OpenDaylight :: alto :: Provider
Feature has no configuration
Feature configuration files:
  etc/opendaylight/karaf/03-alto.xml
Feature depends on:
  odl-alto-model 0.2.0-SNAPSHOT
  odl-mdsal-broker 1.3.0-SNAPSHOT
  odl-l2switch-hosttracker 0.3.0-SNAPSHOT
  odl-l2switch-addresstracker 0.3.0-SNAPSHOT
Feature contains followed bundles:
  mvn:org.opendaylight.alto/alto-provider/0.2.0-SNAPSHOT
Feature has no conditionals.


and review if the bundles are installed
bundle:list -s | grep alto
204 | Resolved |  80 | 0.2.0.SNAPSHOT                            | org.opendaylight.alto.model  
233 | Resolved |  80 | 0.3.0.SNAPSHOT                            | org.opendaylight.l2switch.addresstracker.impl                           
234 | Resolved |  80 | 0.3.0.SNAPSHOT                            | org.opendaylight.l2switch.hosttracker.model                             
235 | Resolved |  80 | 0.3.0.SNAPSHOT                            | org.opendaylight.l2switch.hosttracker.impl

None of the bundles are installed

Another things is that when I review the activated ports:
 nmap chimay
Starting Nmap 6.40 ( http://nmap.org ) at 2015-08-21 11:15 BRT
Nmap scan report for chimay (127.0.1.1)
Host is up (0.00022s latency).
Not shown: 996 closed ports
PORT     STATE SERVICE
22/tcp   open  ssh
53/tcp   open  domain
111/tcp  open  rpcbind
1099/tcp open  rmiregistry


The 8181 port is not activited

I dont know exactly what happen,

Thank

Ss

Danny

On Sat, Aug 1, 2015 at 10:54 PM, Shu Dong <dongs2011@...> wrote:
Hi Tamim,

Sorry for the delay, I just saw your email.

I wrote a doc for people to get into ODL and ALTO quickly. You can start from it: https://docs.google.com/document/d/1nx2U5WvVlCU-dierN-EF9L5iAzRrNNr1S73EzsSjAmo/edit#. Also, there some local code changes including interop tests and the new ECS implementation we have not pushed into ODL Gerrit but we will soon. I will remind you when the code has been updated. 

Hope it helps. Thanks a lot.

From,
Shu

On Sun, Aug 2, 2015 at 9:38 AM, MD I. Islam <tamim@...> wrote:

Thanks Dr. Yang. My skype ID: tamim_217. I'm visiting Cincinnati. Still I will attend the meeting over phone.

On Aug 1, 2015 9:32 PM, "Y. Richard Yang" <yry@...> wrote:
@Shu, thanks a lot for providing the update! 

@Tamim, we do not use a single VM. Let's see what we can do to get the sharing-with-you started.

We will have a sync up at 10 pm (US ET) today. If you get this email in time, please send me your Skype so that I can add you.

Thanks!

Richard 

On Sunday, August 2, 2015, MD I. Islam <tamim@...> wrote:

Thanks Shu! Is it possible to share the VM (development environment) with me? I'm new to ODL. Having everything setup would be very helpful for me to start with.

Thanks
Tamim

On Aug 1, 2015 1:32 PM, "Shu Dong" <dongs2011@...> wrote:
Hi Tamim and Richard,

Here is how we compute the ECS now. We get the routing path from source host to dest host first, and then compute the endpoint cost according to the routing path and cost metric (e.g. bandwidth, hopcount). 

Computing routing path in ODL is the core of the design and the details are explained as follows:
1. We get the attachment points of source host and dest host, let's call it start_switch and end_switch, by L2Switch.
2. We read flow table of start_switch and find the matched flow entry according to src host IP and dst host IP. If matched flow entry is found, we get next switch from the flow entry, then we repeat this step to chase next switch until we get to end_switch.
4. If there is no matched flow entry, we will force ODL controller to compute a new routing path, by either invoking the path computing function or sending a fake packet. Once the path computing is done, we repeat step 2 until we get to end_switch.

In this way, we get the routing path. Following is the pseudo code:

sw_id = get_attachment_point(src)
dst_sw_id = get_attachment_point(dst)
while (sw_id != dst_sw_id) {
  r <- loop_up(src, dst) in sw_id's flow table
  if (!r) {
    forceComputeRoutingPath(src, dst)
    r <- loop_up(src, dst) in sw_id's flow table
  } 
  sw_id = get_sw_id(r) 
}
 

Once we get the routing path, we can compute endpoint costs based on different cost metrics. Hopcount is easy to compute while bandwidth is a little more complicated since we have to get the bandwidth of each link at first.

@Richard The following is what we have done during the past three days:
1. Get attachment point of host by host IP address. Done. (Shu, Xiao)
2. Look up flow table to get matching flow entry and next switch. Almost Done. (Xiao, Shu)
3. Figure out how to force ODL controller to compute routing path. In progress. (Mingming)
4. Setting up a mininet + controller test environment in our lab. (Junzhuo, Xiao)
5. Some code refactoring. (Shu)

Things left to be done:
1. Figure out how to force ODL controller to compute routing path.
2. Figure out how to get bandwidth of each link.
3. Combine all the parts together.

From tomorrow, we will focus on left problems. Mingming has made some progress in the first one but it will be great if we have someone else to help.

Thanks a lot.

From,
Shu


On Sat, Aug 1, 2015 at 11:55 PM, Y. Richard Yang <yry@...> wrote:
Dear Tamim,

Thanks for the update. We had a mini design summit on ECS last week. The plan is to have a running version in two weeks. Given your questions, it is a good idea that we write down the design soon so that we can all work together. 

@Shu/Junzhuo: I believe that you are leading the ECS design. Can you write down the discussion soon so that we can discuss with Tamim and others.

Thanks!

Richard

On Sat, Aug 1, 2015 at 11:32 AM, MD I. Islam <tamim@...> wrote:
Hi

Could you please advise me if I have understood ECS correctly? 

I was told, in the first step, we calculate the shortest hop-count assuming that the link metric is 1. Do we just implement a shortest-path algorithm for the topology graph based on the data from TopologyManager?

Next step is to figure out a natural interface, in ODL, to configure link metrics and compute routing cost. Do we design a YANG model to configure link properties (link cost metrics)? Currently I don't see link properties (such as delay, bandwidth) in NodeConnector or TopologyUserLinkConfig. Am I missing anything? Do we have to design a data structure to store the cost metric for each link?

Which version of ODL do I look into? I don't see TopologyManager code in the Lithium release. I only see the class files. Am I missing anything? However I see the TopologyManager in Hydrogen release. 

Looking forward to your suggestions.

Thanks
Tamim  

.

On Fri, Jul 17, 2015 at 11:19 PM, MD I. Islam <tamim@...> wrote:

Thanks Kai! I'm looking into it.

On Jul 17, 2015 11:07 PM, "Y. Richard Yang" <yry@...> wrote:
Tamim,

Yes. As Kai pointed out, the TopologyManager is a good place to get started. Could you please start to take a look and then we can sync up?

Thanks!

Richard 

On Saturday, July 18, 2015, Gao Kai <godrickk@...> wrote:
There was a topologymanager in earlier releases you might look into.

On 18/07/15 02:14, MD I. Islam wrote:
That sounds great. Is there an ODL service that I can use to get the network topology and link metric? 

On Fri, Jul 17, 2015 at 1:36 PM, Y. Richard Yang <yry@...> wrote:
Tamim,

On Saturday, July 18, 2015, MD I. Islam <mislam4@...> wrote:
Yeah, interested. Is that the Endpoint Cost Service?
 
Yes. You got it.

 
What are the metrics we are considering? 

One basic step is to make sure we get shortest path fully right. A natural link metric is 1, and we get shortest hop count. A next step is to figure out a natural interface, in ODL, to configure link metrics, and we compute routing cost. A third component in ODL to conduct traffic engineering.

Let's get a couple proposals out in next week. How does this sound?

Richard 
 

On Fri, Jul 17, 2015 at 12:45 PM, Y. Richard Yang <yry@...> wrote:
Dear Tamim,

Wonderful! 

Per my personal wish list, a main feature that I want to improve on is high quality ECS service, based on various metrics. Any interest?

Richard

On Sat, Jul 18, 2015 at 12:35 AM, MD I. Islam <mislam4@...> wrote:
Yeah, sure. I'm interested on adding features to the ALTO ODL server. Please let me know what you want me to do.

Thanks
Tamim

On Fri, Jul 17, 2015 at 12:12 PM, Y. Richard Yang <yry@...> wrote:
Dear Tamim,

Thanks a lot for the questions. Sorry for the late reply, as I am working on a few deadlines. How about we schedule a time to discuss the items in details later next week?

In the mean time, are you interested in engaging more in the alto effort? For example, we are working on adding more features to the ODL server. Any interest in getting engaged?

Thanks!

Richard

On Thu, Jul 16, 2015 at 2:27 PM, MD I. Islam <mislam4@...> wrote:

I have few questions in mind.

How can we get the dynamic cost map from OpenFlow switch? Do we use OpenFlow meter? Are we considering about dynamic cost-map at all? As there will be multiple competing flows, so available bandwidth will change over time. Please advise.

Can we also create a paradigm to cache contents in the SDN controller (or in a controller app)? I think, this shouldn't be in the context of ALTO, but still would be very helpful. For example, if multiple clients watch a live video on a campus network, we should be able to cache the video slices in the controller. Then controller can push the content proactivly without notifying the clients. Again controller can serve the content in a reactive manner through a north bound protocol.

Today I was trying to write a simple application in ONOS. I was trying the VM from sdnhub. I could run ONOS. The sample Foo program compiled, but I couldn't load it on Karaf. If you have a VM that has the development environment setup, that will be very helpful to start.

Please don't hesitate to let me know if i get anything wrong. Looking forward to your suggestions.

Thanks
Tamim




--
-- 
 =====================================
| Y. Richard Yang <yry@...>   |
| Professor of Computer Science       |
 =====================================




--
-- 
 =====================================
| Y. Richard Yang <yry@...>   |
| Professor of Computer Science       |
 =====================================

_______________________________________________
alto-dev mailing list
alto-dev@...
https://lists.opendaylight.org/mailman/listinfo/alto-dev




--
Richard

_______________________________________________
alto-dev mailing list
alto-dev@...
https://lists.opendaylight.org/mailman/listinfo/alto-dev




_______________________________________________
alto-dev mailing list
alto-dev@...
https://lists.opendaylight.org/mailman/listinfo/alto-dev



--
Richard

_______________________________________________
alto-dev mailing list
alto-dev@...
https://lists.opendaylight.org/mailman/listinfo/alto-dev





--
-- 
 =====================================
| Y. Richard Yang <yry@...>   |
| Professor of Computer Science       |
 =====================================

--
You received this message because you are subscribed to the Google Groups "alto-design" group.
To unsubscribe from this group and stop receiving emails from it, send an email to alto-design+unsubscribe@....
To post to this group, send email to alto-design@....
To view this discussion on the web visit https://groups.google.com/d/msgid/alto-design/CANUuoLqi%3DU_mcv1gm5Rgf0p48PdLX3V_xrHLngwk%2BADCrEmFsg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.



--
Richard


_______________________________________________
alto-dev mailing list
alto-dev@...
https://lists.opendaylight.org/mailman/listinfo/alto-dev



_______________________________________________
alto-dev mailing list
alto-dev@...
https://lists.opendaylight.org/mailman/listinfo/alto-dev


321 - 340 of 542