Re: Few questions on ALTO and ONOS
Y. Richard Yang
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:
-- ===================================== | Y. Richard Yang <yry@...> | | Professor of Computer Science | ===================================== |
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: Few questions on ALTO and ONOS
MD I. Islam <mislam4@...>
Yeah, interested. Is that the Endpoint Cost Service? What are the metrics we are considering?
On Fri, Jul 17, 2015 at 12:45 PM, Y. Richard Yang <yry@...> wrote:
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: Few questions on ALTO and ONOS
Y. Richard Yang
Tamim,
On Saturday, July 18, 2015, MD I. Islam <mislam4@...> wrote:
Yes. You got it.
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
-- Richard |
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: Few questions on ALTO and ONOS
MD I. Islam <mislam4@...>
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, |
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: Few questions on ALTO and ONOS
Gao Kai
There was a topologymanager in earlier
releases you might look into.
toggle quoted message
Show quoted text
On 18/07/15 02:14, MD I. Islam wrote:
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: Few questions on ALTO and ONOS
Y. Richard Yang
Tamim,
toggle quoted message
Show quoted text
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:
-- Richard |
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: Few questions on ALTO and ONOS
MD I. Islam <tamim@...>
Thanks Kai! I'm looking into it. On Jul 17, 2015 11:07 PM, "Y. Richard Yang" <yry@...> wrote:
Tamim, |
||||||||||||||||||||||||
|
||||||||||||||||||||||||
[release] [Reminder] Beryllium Offset 0 M1 status is due on 7/23 (Thursday)
Gao Kai <gaok12@...>
Hi all,
I believe we should update the file too. I filled in some information but wasn't able to create the wiki page of the release plan (probably due to priority reason?) so someone please creates the page with the templates provided in [2]. Thanks! Regards, Kai -------- Forwarded Message --------
Hello offset 0 projects:
M1 status is due on 7/23, please fill the spreadsheet [1], columns with red font are required fields. Declaration email PTL and Test contact Published drafted release plan, template in [2]
Thanks, George
[1] https://docs.google.com/spreadsheets/d/1o9L1q5OYl9T6ZwBEkAuPSoostFMIsjp4mh2FDawuk20/edit#gid=0 [2] https://wiki.opendaylight.org/view/Simultaneous_Release:Per-Project_Beryllium_Release_Plan_Template
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: alto-dev Digest, Vol 6, Issue 16
dongshu
Hi Kai, I didn't figure out how to create the wiki page either ... Since Yichen is our new documentation leader, I think it's better for him to take over this, as a opportunity to get familiar with the project. @Yichen, could you help us to create the wiki page? Thanks a lot! From, Shu On Fri, Jul 24, 2015 at 8:00 PM, <alto-dev-request@...> wrote: Send alto-dev mailing list submissions to |
||||||||||||||||||||||||
|
||||||||||||||||||||||||
[release] [Reminder - Action Required for Offset 1project] Please submit M1 status by 7/30 Thursday
Gao Kai
Hi all, Even though ALTO is an Offset 2 project, it would be better if we can get prepared for M1. @Shu, would you please make sure everyone has subscribed the alto-dev mailing list so we can discuss development issues here? Many thanks! @Yichen, please figure out how to write with wiki and asciidoc (they have much in common). You might want to subscribe to the doc mailing list and also download the docs project. I reckon the M1 deadline would be next week. Let’s sort things out before that. Regards, ———— Forwarded Message ———— Subject: [release] [Reminder - Action Required for Offset 1project] Please submit M1 status by 7/30 Thursday Date: Thu, 30 Jul 2015 06:46:18 +0000 From: George Zhao George.Y.Zhao@... Hello Offset 1 PTLs, Please email with the following information and update spreadsheet [1], the due date is 7/30 Thursday. Offset: 1 Project Lead (elected): Project Contact: Test Contact: Documentation Contact: Published Draft Release plan: (url) Main Page: (url) [1] https://docs.google.com/spreadsheets/d/1o9L1q5OYl9T6ZwBEkAuPSoostFMIsjp4mh2FDawuk20/edit#gid=0 Thanks, George
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: [release] [Reminder - Action Required for Offset 1project] Please submit M1 status by 7/30 Thursday
dongshu
Sure. Thanks very much for reminding us @Kai. On Thu, Jul 30, 2015 at 8:55 PM, Gao Kai <godrickk@...> wrote:
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: [release] [Reminder - Action Required for Offset 1project] Please submit M1 status by 7/30 Thursday
Yichen Qian
Sure. I’ll try to figure it out.
toggle quoted message
Show quoted text
Best, Yichen
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: Invitation: ALTO Lithium Visible Benefits @ Fri Jul 24, 2015 15:00 - 15:30 (ccain@linuxfoundation.org)
Y. Richard Yang
Dear Art, Casey,
Sorry for the late reply--I was traveling back to office in the last two days. The following week works better for me as well. Please pick a time. I am mostly open. Thanks! Richard On Wed, Jul 29, 2015 at 6:05 PM, Art Fewell <afewell@...> wrote:
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: Few questions on ALTO and ONOS
MD I. Islam <tamim@...>
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:
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: Few questions on ALTO and ONOS
Y. Richard Yang
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:
-- ===================================== | Y. Richard Yang <yry@...> | | Professor of Computer Science | ===================================== |
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: [alto-design] Re: Few questions on ALTO and ONOS
dongshu
Hi Tamim and Richard, 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) { } 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:
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: [alto-design] Re: Few questions on ALTO and ONOS
MD I. Islam <tamim@...>
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 On Aug 1, 2015 1:32 PM, "Shu Dong" <dongs2011@...> wrote:
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: Few questions on ALTO and ONOS
Y. Richard Yang
@Shu, thanks a lot for providing the update!
toggle quoted message
Show quoted text
@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:
--
Richard |
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: Few questions on ALTO and ONOS
MD I. Islam <tamim@...>
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! |
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: Few questions on ALTO and ONOS
dongshu
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:
|
||||||||||||||||||||||||
|