[Ndn-interest] Data Accessibility in VM Live Migration over NDN
Lan Wang (lanwang)
lanwang at memphis.edu
Mon Mar 2 10:13:08 PST 2015
This depends on the strategy. It could work in the way you described. Or the edge router could forward the interest using one of the delegated names. It should bring back data. If there's no data back, then it could try another one of the delegated names.
Note that in NDN, the delegated names are names too, not addresses. For example, /ndnsim/net could be delegated to /com/att/user/alex/ndnsim.
On Mar 2, 2015, at 2:40 AM, Muhammad Hosain Abdollahi Sabet <M.AbdollahiSabet at mail.sbu.ac.ir<mailto:M.AbdollahiSabet at mail.sbu.ac.ir>> wrote:
Let assume we have tow copies and the MAP-AND-ENCAP mechanism implemented. Which route would be selected? I mean, the edge router sends the interest to both addresses(the old one, and the new old received from NDNS), right? Then depending on the measurements done by itself(the edge router), future interest will be sent to the designated route, and the endpoint application won't notify any of this. Am I right?
From: Ndn-interest on behalf of Xiaoke Jiang
Sent: Sat 2/28/2015 9:38 PM
To: Dejiang Zhou
Cc: ndn-interest at lists.cs.ucla.edu<mailto:ndn-interest at lists.cs.ucla.edu>
Subject: Re: [Ndn-interest] Data Accessibility in VM Live Migration over NDN
Here is my opinion to your question. What mentioned here seems to be producer mobility support, which is on-going research among NDN. A straightforward solution is to let UMICH router announce the a prefix /ndn/cn/edu/tongji/vm/ping to routing system. Besides the routing approach, there are some proposals too address this problem
1) Kite: http://named-data.net/publications/techreports/tr-ndn20-kite/ <http://named-data.net/publications/techreports/tr-ndn20-kite/>
2) LINK+ Map-and-Encap: may also helps but need more efforts: http://named-data.net/techreport/ndn-0004-3-scaling-ndn-routing.pdf <http://named-data.net/techreport/ndn-0004-3-scaling-ndn-routing.pdf>
p.s., I wonder why not keep the original copy of the vm after migration, therefore you would have two copies can serve future requests.
> On 28 Feb, 2015, at 2:12 am, Dejiang Zhou <dejiang_zhou at 163.com<mailto:dejiang_zhou at 163.com>> wrote:
> Hi everyone,
> I have been studying VM live migration over NDN for mouths and taking some experiments in NDN testbed.
> VM is migrated from China to America with source host connecting NDN testbed node of Tongji and destination host in America connecting UMICH testbed node. Data in VM can be accessed by other host at the beginning. Name of Data can be "/ndn/cn/edu/tongji/vm/ping". However, this Data cannot be accessed after migration because the name of Data is not registered to FIB of other host. Other host is able to access the Data before migration because Interest can be forwarded to Tongji University by name prefix "/ndn/cn/edu/tongji". In contrast, Interest with name "/ndn/cn/edu/tongji/vm/ping" cannot be forwarded to VM after migration because VM is behind UMICH testbed node but name prefix of the requested Data is not "/ndn/edu/umich".
> Does anyone have an idea for solving the problem? I think the rule of the solution is that name of Data in VM should not be changed after migration.
> Best regards,
> Dejiang Zhou
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu<mailto:Ndn-interest at lists.cs.ucla.edu>
Ndn-interest mailing list
Ndn-interest at lists.cs.ucla.edu<mailto:Ndn-interest at lists.cs.ucla.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ndn-interest