<div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><p class="MsoNormal"><span lang="EN-US" style="font-family: Helvetica, sans-serif;">Hi Xiaoke,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family: Helvetica, sans-serif;"> </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family: Helvetica, sans-serif;">Thank you for your advice.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family: Helvetica, sans-serif;">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.</span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family: Helvetica, sans-serif;">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family: Helvetica, sans-serif;"> </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family: Helvetica, sans-serif;">Dejiang Zhou<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family: Helvetica, sans-serif;">2015-3-3</span><span lang="EN-US"><o:p></o:p></span></p><br><br><br><br><div></div><div id="divNeteaseMailCard"></div><br>At 2015-03-01 02:08:16, "Xiaoke Jiang" <shock.jiang@gmail.com> wrote:<br> <blockquote id="isReplyContent" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi Dejiang, <div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>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<div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>1) Kite: <a href="http://named-data.net/publications/techreports/tr-ndn20-kite/" class="">http://named-data.net/publications/techreports/tr-ndn20-kite/</a> </div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>2) LINK+ Map-and-Encap: may also helps but need more efforts: <a href="http://named-data.net/techreport/ndn-0004-3-scaling-ndn-routing.pdf" class="">http://named-data.net/techreport/ndn-0004-3-scaling-ndn-routing.pdf</a></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span></div><div class="">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.</div><div class=""><br class=""></div><div class=""><div class="">
<div class="">Xiaoke (Shock)</div><div class=""><br class=""></div><br class="Apple-interchange-newline">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 28 Feb, 2015, at 2:12 am, Dejiang Zhou <<a href="mailto:dejiang_zhou@163.com" class="">dejiang_zhou@163.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="line-height: 1.7; font-size: 14px; font-family: Arial;" class=""><div class=""><span style="font-family: 'Times New Roman'; font-size: 16px; line-height: 1.7; text-indent: 21pt;" class="">Hi everyone,</span></div><div class=""><span style="font-family: 'Times New Roman'; font-size: 16px; line-height: 1.7; text-indent: 21pt;" class=""> I have been studying VM live migration over NDN for mouths and taking some experiments in NDN testbed.</span></div><div class=""><span style="font-family: 'Times New Roman'; font-size: 16px; line-height: 1.7; text-indent: 21pt;" class=""> 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 ¡°/<span class="typoRed" evid="1425118065818.2659" id="1425118065818.2659">ndn</span>/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 ¡°/<span class="typoRed" evid="1425118065818.3113" id="1425118065818.3113">ndn</span>/cn/edu/tongji¡±. In contrast, Interest with name ¡°/<span class="typoRed" evid="1425118065818.439" id="1425118065818.439">ndn</span>/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".</span></div><div class=""><span style="font-family: 'Times New Roman'; font-size: 16px; line-height: 1.7; text-indent: 21pt;" class=""> 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.</span></div><div class=""><span style="font-family: 'Times New Roman'; font-size: 16px; line-height: 1.7; text-indent: 21pt;" class="">Best regards,</span></div><div class=""><span class="typoRed" evid="1425118065818.421" id="1425118065818.421" style="font-family: 'Times New Roman'; font-size: 16px; line-height: 1.7; text-indent: 21pt;">Dejiang</span><span style="font-family: 'Times New Roman'; font-size: 16px; line-height: 1.7; text-indent: 21pt;" class=""> </span><span style="font-family: 'Times New Roman'; font-size: 16px; line-height: 1.7; text-indent: 21pt;" class="">Zhou</span></div></div><br class=""><br class=""><span title="neteasefooter" class=""><span id="netease_mail_footer" class=""></span></span>_______________________________________________<br class="">Ndn-interest mailing list<br class=""><a href="mailto:Ndn-interest@lists.cs.ucla.edu" class="">Ndn-interest@lists.cs.ucla.edu</a><br class="">http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest<br class=""></div></blockquote></div><br class=""></div></div></blockquote></div><br><br><span title="neteasefooter"><span id="netease_mail_footer"></span></span>