Hi there, Unfortunately current implementation doesn't support this. My guess is that the developers of alto-hosttracker wrote this module mainly to

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

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: Functionality Freeze: 1. Final list of externally consumable APIs defined: No. Will be finalized together with API freeze.

---------- 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

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.

Attached is the topology we are building for SC15. Thanks -Azher On 10/9/2015 6:26 PM, Y. Richard Yang wrote:

Austin, Can you please let Azher know the issues that you fix in l2switch? Thanks! Richard -- Richard

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

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

Sorry for not replying earlier, I was trying to understand more on what was happening with the actual switches. One of the switch in the topology is Dell Z9000, this switch has buggy OF

Thanks for reviewing and merging. Thanh has added alto back to beryllium autorelease. Best Regards, An Ho From: Jensen Zhang [mailto:jingxuan.n.zhang@...] Sent: Friday, October 02, 2015 11:19

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. And we have updated the weather spreadsheet. Please

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

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

Hi Ann, The team member who will take care of it is off in the day time. We will look into it soon. Richard -- 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

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

Hi Azher, Junzhuo and Jensen will look into setting. They are having a small vacation break and will get to you soon. Richard -- Richard

Hi Junzhuo, 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