[Ndn-interest] Data Accessibility in VM Live Migration over NDN
dejiang_zhou at 163.com
Tue Mar 3 04:09:22 PST 2015
Thank you for your advice.
I looked on the papers you mentioned these days. I think both two ways are good solutions for problem of producer mobility. We will try to use it in our VM live migration experiment for checking if it works.
In some times, we should start VM live migration because source host becomes overload. Therefore, the VM in source host need shut down after VM migration.
At 2015-03-01 02:08:16, "Xiaoke Jiang" <shock.jiang at gmail.com> wrote:
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/
2) LINK+ Map-and-Encap: may also helps but need more efforts: 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> wrote:
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.
Ndn-interest mailing list
Ndn-interest at lists.cs.ucla.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ndn-interest