<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2014-04-23 13:12 GMT+02:00 Pavel Emelyanov <span dir="ltr"><<a href="mailto:xemul@parallels.com" target="_blank">xemul@parallels.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On 04/22/2014 08:21 PM, Oscar Fernández wrote:<br>
<br>
> Hi, sorry for the delay.<br>
> I tried the migration after getting your latest patches and now the dump fails as expected ;)<br>
<br>
</div>Thanks :) Now we have a good starting point.<br>
<div><br>
> Regarding to the use case, the idea is to migrate a streaming server maintaining the TCP connection.<br>
> Find attached 3 pictures representing the process.<br>
<br>
</div>OK, this makes sense to me. How do you plan to make an IP address available<br>
at Machine 1 before migration, be available on Machine 3 after it? Or there's<br>
not direct communication between Machine 2 and the server, so preserving an<br>
IP address is not critical?<br>
<br>
Thanks,<br>
Pavel<br>
</blockquote></div><br></div><div class="gmail_extra">Hi, regarding to the IP, we have considered two options:<br><ol><li>IP address isn't critic since there is no direct connection between client(Machine 2) and server.</li>
<li>IP is managed using Loc/ID split technology such as LISP.</li></ol><p>Regards<br></p></div><div class="gmail_extra">-- <br>Óscar Fernández<br>
</div></div>