This group is locked. No changes can be made to the group while it is locked.
|
Re: alto pids
Gao Kai <gaok12@...>
Hi there,
toggle quoted messageShow quoted text
Unfortunately current implementation doesn't support this. My guess is that the developers of alto-hosttracker wrote this module mainly to support the Endpoint Cost Service instead of the Network Map/Cost Map so they didn't implement PID partition. I'll forward your e-mail to confirm that. However, in an internal meeting this July we did discuss about PID partition using hosttracker so I think there might be some progress on that. Besides, you can report it as a bug by visiting https://bugs.opendaylight.org/enter_bug.cgi?product=alto. Since there are some major changes in the latest release and we have limited manpower, I can't really guarantee that this issue can be fixed soon enough. :( We really appreciate your participation and we look forward to getting more feedbacks from you. Thanks very much! Regards, Kai On 20/10/15 22:46,
adenisiewicz@... wrote:
Is it possibility to define pids for the network created in mininet that is read by hosttracker-network-map? When I try, all hosts are grouped into one pid. _______________________________________________ alto-dev mailing list alto-dev@... https://lists.opendaylight.org/mailman/listinfo/alto-dev
|
|
|
|
Re: alto pids
Jensen Zhang
Actually, we are discussing about it recently. We have not yet implemented a way to define pids automatically. And as you see, we just group all hosts into one pid. A possible solution now is to set a new network map manually from cli. However, it is not a good solution. Users still would like to get automatic network map. Maybe we can provide a default algorithm to generate pids, or allow users to define the algorithm by themselves.Best,
Is it possibility to define pids for the network created in mininet that is read by hosttracker-network-map?
|
|
|
|
alto pids
adenisiewicz@...
Is it possibility to define pids for the network created in mininet that is read by hosttracker-network-map?
When I try, all hosts are grouped into one pid.
|
|
|
|
ALTO M3 Status
Gao Kai <gaok12@...>
ALTO M3 status:
Functionality Freeze: 1.
Final list of externally consumable APIs defined: 2.
Are all your inter-project dependencies resolved (i.e., have
the other projects you were counting on given you what you
needed)? 3.
Were there any project-specific deliverables planned for
this milestone? Karaf Features Defined: 4.
Are all your project's features that are intended for
release added to the features.xml and checked into the
integration git repository? **
(please provide link to features.xml) **
(please provide link to the gerrit patch that checks into
the integration git repository) 5.
List all top-level, user-facing, and stable Karaf features
for your project. alto-core: the framework of the ALTO
implementation in ODL Documentation: 6. List the kinds of documentation you will provide including at least: **
One user/operator guide section per user-facing feature.
7.
Have you checked in the AsciiDoc outlines to the docs
repository?
Integration
and Test: 8.
Have you started automated system testing for your top-level
features.
9.
Have you filled out basic system test plan template for each
top-level feature (karaf and not karaf) and a comprehensive
system test plan template including functionality, cluster,
scalability, performance, longevity/stability for each
stable feature?
|
|
|
|
[alto] ALTO WG Virtual Interim Meeting: October 27, 2015
Y. Richard Yang
---------- Forwarded message ---------- From: IESG Secretary <iesg-secretary@...> Date: Tue, Oct 13, 2015 at 2:32 PM Subject: [alto] ALTO WG Virtual Interim Meeting: October 27, 2015 To: IETF Announcement List <ietf-announce@...> Cc: alto@... The Application-Layer Traffic Optimization (alto) working group will hold a virtual interim meeting on Tuesday October 27, 2015. Agenda to be distributed on the ALTO WG mailing list. WebEx information: Tuesday, October 27, 2015 9:00am Eastern Daylight Time (GMT-04:00) (6:00am PDT, 8:00am CDT) Host: ALTO Working Group Meeting number: 641 665 277 Meeting password: 1234 Meeting link: https://urldefense.proofpoint.com/v2/url?u=https-3A__ietf.webex.com_ietf_j.php-3FMTID-3Dmde69e1a7c7b46c6fe63ab9d6401508e0&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=4G36iiEVb2m_v-0RnP2gx9KZJjYQgfvrOCE3789JGIA&m=OvfjPmJtW1EQa6NyJoAEByeiWVFzjEx949LzU6wQjE4&s=9a4gjAn9CSIuQr1aUuNpxHX7DNVUXeEtmXCWkL8yAtQ&e= Audio connection: 1-877-668-4493 Call-in toll free number (US/Canada) 1-650-479-3208 Call-in toll number (US/Canada) _______________________________________________ alto mailing list alto@... https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_alto&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=4G36iiEVb2m_v-0RnP2gx9KZJjYQgfvrOCE3789JGIA&m=OvfjPmJtW1EQa6NyJoAEByeiWVFzjEx949LzU6wQjE4&s=NwMK2hVPIqjGFYvmr04UDcoIZ8_g0qFwlAzQ8e8Rkzs&e= -- ===================================== | Y. Richard Yang <yry@...> | | Professor of Computer Science | =====================================
|
|
|
|
Re: ODL L2 project
Austin
Hi Azher, Sorry for the delay. I modified the L2Switch not for fixing bugs, but for improving it. The original L2Switch uses spinning tree to flood every packet on the network, which is not effective. And ODL does not have a service to provide routing information. So basically what I did is: 1. Replace spin tree with shortest path algorithm to build a p2p flow between two hosts; 2. Add APIs to provide routing information. An issue is that openflow-plugin, a module what L2Switch depends on, has some bugs. So L2Switch may not compact with every switch. I'll try to solve your problem by reading the spec of Dell Z9100 and the docs of openflow-plugin. Regards, Austin (Junzhuo) 2015-10-10 9:26 GMT+08:00 Y. Richard Yang <yang.r.yang@...>:
Austin,
|
|
|
|
Re: ODL L2 project
Azher Mughal <azher@...>
Attached is the topology we are building for SC15.
toggle quoted messageShow quoted text
Thanks -Azher On 10/9/2015 6:26 PM, Y. Richard Yang
wrote:
Austin,
|
|
|
|
Re: ODL L2 project
Y. Richard Yang <yang.r.yang@...>
Austin,
toggle quoted messageShow quoted text
Can you please let Azher know the issues that you fix in l2switch? Thanks! Richard
On Friday, October 9, 2015, Azher Mughal <azher@...> wrote:
-- Richard
|
|
|
|
Re: [alto-design] Re: ODL L2 project
Azher Mughal <azher@...>
Hi Richard,
On 10/9/2015 1:36 PM, Y. Richard Yang
wrote:
I agree. This specific issue seems to be related with just the Dell Z9000 only. This has the OpenFlow implementation but code is only under maintenance. So hopefully Dell will release some upgraded firmware to get this fixed. I remember you mentioned some of the code improvements in l2switch, can you please list the bug fixes or improvements you have made ? We are getting ready for the SC15 conference and the current arp manager of the ODL has issues, and it would be nice to have a better error free l2switch from you. Please let me know. Thanks -Azher
|
|
|
|
Re: [alto-design] Re: ODL L2 project
Y. Richard Yang <yang.r.yang@...>
Azher, Problems with real switches can always be hard to debug. We do not have this mentioned switch, and hence it is great to know about this issue. I feel that such issues can be addressed by a more robust l2switch module, which we can propose to l2switch, make sense? Richard
On Fri, Oct 9, 2015 at 11:03 AM, Azher Mughal <azher@...> wrote:
|
|
|
|
Re: [alto-design] Re: ODL L2 project
Azher Mughal <azher@...>
Sorry for not replying earlier, I was trying to understand more on
what was happening with the actual switches.
toggle quoted messageShow quoted text
One of the switch in the topology is Dell Z9000, this switch has buggy OF implementation and was passing the hosts and link info from one instance to other, thus completely confusing the whole topology. I might have more questions regarding the Python flow insertion into Lithium :) Thanks -Azher On 9/30/2015 11:41 PM, Junzhuo Wang
wrote:
|
|
|
|
Re: Alto Breaking Beryllium Autorelease
an.ho@huawei.com
Thanks for reviewing and merging. Thanh has added alto back to beryllium autorelease.
Best Regards, An Ho
From: Jensen Zhang [mailto:jingxuan.n.zhang@...]
Thanks, An. It's our mistake. We have merged this patch and fixed the bug. I think ALTO has not been blocking Autorelease now. Please confirm it. Please inform me if there is still something wrong.
Thanks, Jensen
2015-10-03 4:52 GMT+08:00 An Ho <An.Ho@...>: Based on what Tony said during the TSC call, this may be caused by the new stricter yang parser. I believe this patch here [1] addresses the issue. Can someone take a look, review, and merge. I have updated the weather spreadsheet with the relevant patch number [2].
Best Regards, An Ho
[1] https://git.opendaylight.org/gerrit/#/c/27788/
From: Jensen Zhang [mailto:jingxuan.n.zhang@...]
Hi Ann, Very sorry to reply you so late. But could you please reconfirm this bug? I means that it is really a mistake. Actually, I am always tracing this bug during these days. And when I built our project yesterday, I got a totally different error log from before. Even more, when I built it just now,
I found there had been no error. But I didn't modify any code during these several days. So I guess this bug is caused by yangtools, and it seems that the members of yangtools have fixed it. Thanks! Jensen
2015-10-02 1:07 GMT+08:00 Y. Richard Yang <yry@...>: Hi Ann,
The team member who will take care of it is off in the day time. We will look into it soon.
Richard
Hi ALTO Team,
Could someone from the team take a look at this bug [1]. It is currently breaking Beryllium autorelease.
[ERROR] Failed to execute goal org.opendaylight.yangtools:yang-maven-plugin:0.8.0-Daily-v201509292141:generate-sources (default) on project alto-model: yang-to-sources: Unable to parse yang files from /opt/jenkins/workspace/autorelease-daily-beryllium/alto/alto-model/src/main/yang: Some of FULL_DECLARATION modifiers for statements were not resolved. ->
Best Regards, An Ho
|
|
|
|
Re: Alto Breaking Beryllium Autorelease
Jensen Zhang
Thanks, An. It's our mistake. We have merged this patch and fixed the bug. I think ALTO has not been blocking Autorelease now. Please confirm it. Please inform me if there is still something wrong.And we have updated the weather spreadsheet.
|
|
|
|
Re: Alto Breaking Beryllium Autorelease
an.ho@huawei.com
Based on what Tony said during the TSC call, this may be caused by the new stricter yang parser. I believe this patch here [1] addresses the issue. Can someone take a look, review, and merge. I have updated the weather spreadsheet with the relevant patch number [2].
Best Regards, An Ho
[1] https://git.opendaylight.org/gerrit/#/c/27788/ [2] https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=2030147923
From: Jensen Zhang [mailto:jingxuan.n.zhang@...]
Hi Ann, Very sorry to reply you so late. But could you please reconfirm this bug? I means that it is really a mistake. Actually, I am always tracing this bug during these days. And when I built our project yesterday, I got a totally different error log from before. Even more, when I built it just now, I found there had been
no error. But I didn't modify any code during these several days. So I guess this bug is caused by yangtools, and it seems that the members of yangtools have fixed it. Thanks! Jensen
2015-10-02 1:07 GMT+08:00 Y. Richard Yang <yry@...>: Hi Ann,
The team member who will take care of it is off in the day time. We will look into it soon.
Richard
Hi ALTO Team,
Could someone from the team take a look at this bug [1]. It is currently breaking Beryllium autorelease.
[ERROR] Failed to execute goal org.opendaylight.yangtools:yang-maven-plugin:0.8.0-Daily-v201509292141:generate-sources (default) on project alto-model: yang-to-sources: Unable to parse yang files from /opt/jenkins/workspace/autorelease-daily-beryllium/alto/alto-model/src/main/yang: Some of FULL_DECLARATION modifiers for statements were not resolved. ->
Best Regards, An Ho
|
|
|
|
Re: Alto Breaking Beryllium Autorelease
Jensen Zhang
Hi Ann, Very sorry to reply you so late. But could you please reconfirm this bug? I means that it is really a mistake.Excuse me, is Beryllium autorelease still blocked by this bug now? If not, please cancel Blocker. And since there is no error now, please close this bug.
Hi Ann,
|
|
|
|
Re: Alto Breaking Beryllium Autorelease
Y. Richard Yang
Hi Ann,
toggle quoted messageShow quoted text
The team member who will take care of it is off in the day time. We will look into it soon. Richard
On Thursday, October 1, 2015, An Ho <An.Ho@...> wrote:
-- Richard
|
|
|
|
Alto Breaking Beryllium Autorelease
an.ho@huawei.com
Hi ALTO Team,
Could someone from the team take a look at this bug [1]. It is currently breaking Beryllium autorelease.
[ERROR] Failed to execute goal org.opendaylight.yangtools:yang-maven-plugin:0.8.0-Daily-v201509292141:generate-sources (default) on project alto-model: yang-to-sources: Unable to parse yang files from /opt/jenkins/workspace/autorelease-daily-beryllium/alto/alto-model/src/main/yang: Some of FULL_DECLARATION modifiers for statements were not resolved. ->
Best Regards, An Ho
[1] https://bugs.opendaylight.org/show_bug.cgi?id=4371
|
|
|
|
Re: [alto-design] Re: ODL L2 project
Austin
Hi Azher, As I know the latest version of L2Switch is 0.3.0-SNAPSHOT. So may I ask your the source of the code? Gerrit or Github? And could you give me the real topology of your network? I’ll test it because I’m not sure the L2Switch work fine with multi-NIC hosts. If you want to push your own flow entry. The setting should be fine but I saw no default flow in your switches. Because normally all switch should have a default flow entry. The HostTracker may not working if the LLDP or ARP packets are not sent to controller properly. Regards, Junzhuo
|
|
|
|
Re: ODL L2 project
Y. Richard Yang <yang.r.yang@...>
Hi Azher,
toggle quoted messageShow quoted text
Junzhuo and Jensen will look into setting. They are having a small vacation break and will get to you soon. Richard
On Wednesday, September 30, 2015, Azher Mughal <azher@...> wrote:
-- Richard
|
|
|
|
Re: [alto-design] Re: ODL L2 project
Azher Mughal <azher@...>
Hi Junzhuo,
toggle quoted messageShow quoted text
Please see this topology. I am using the daily snapshots of Lithium 0.3.2 http://131.215.207.90:8080/index.html#/topology The problem I see is when l2-switch (and host tracker) is enabled , hosts start to appear on different nodes as you can see in the picture below. Our intention to use l2-switch is to get the topology and hosts automatically discovered, but not to let it push the flow rules by itself. Thus I apply these two configs to ODL: is-proactive-flood-mode=false is-learning-only-mode=true But still hosts appear to multiple nodes. Any suggestions ? Thanks -AZher  On 9/30/2015 6:03 AM, Junzhuo Wang
wrote:
Hi Azher,
|
|
|
