62
edits
Changes
Created page with "CRIU can use this option to migrate applications over the network. == Remote == Add the <code>--remote</code> option to send the checkpoint data through the network and rest..."
CRIU can use this option to migrate applications over the network.
== Remote ==
Add the <code>--remote</code> option to send the checkpoint data through the network and restore the application on a different machine.
The communication is performed as follows:
At the src_node, CRIU dump sends the images through UNIX sockets to Image Proxy.
Image Proxy sends them to Image Cache via a TCP connection.
At the dst_node, Image Cache forwards the images via UNIX sockets to CRIU restore.
CRIU usage example with <code>--remote</code>:
<pre>
dst_node# criu image-cache -d --port <port>
src_node# criu image-proxy -d --port <port> --address <dat_node>
src_node# criu dump -t <pid> --remote
dst_node# criu restore --remote
</pre>
== Image Cache ==
The option's syntax is <code>image-cache -d --port</code>.
== Image Proxy ==
The option's syntax is <code>image-proxy -d --port --address $dst_node</code>.
[[Category:Live Migration]]
[[Category:Experimental]]
== Remote ==
Add the <code>--remote</code> option to send the checkpoint data through the network and restore the application on a different machine.
The communication is performed as follows:
At the src_node, CRIU dump sends the images through UNIX sockets to Image Proxy.
Image Proxy sends them to Image Cache via a TCP connection.
At the dst_node, Image Cache forwards the images via UNIX sockets to CRIU restore.
CRIU usage example with <code>--remote</code>:
<pre>
dst_node# criu image-cache -d --port <port>
src_node# criu image-proxy -d --port <port> --address <dat_node>
src_node# criu dump -t <pid> --remote
dst_node# criu restore --remote
</pre>
== Image Cache ==
The option's syntax is <code>image-cache -d --port</code>.
== Image Proxy ==
The option's syntax is <code>image-proxy -d --port --address $dst_node</code>.
[[Category:Live Migration]]
[[Category:Experimental]]