Difference between revisions of "CLI/opt/--remote"
Jump to navigation
Jump to search
m (Fix typo) |
|||
| Line 26: | Line 26: | ||
The option's syntax is <code>image-proxy -d --port --address $dst_node</code>. | The option's syntax is <code>image-proxy -d --port --address $dst_node</code>. | ||
| + | |||
| + | === Video === | ||
| + | |||
| + | To view an example video of process migration via Unix socket, please go to https://asciinema.org/a/GFurArJS1swuZQ5ptE7kW69E4. | ||
[[Category:Live Migration]] | [[Category:Live Migration]] | ||
[[Category:Experimental]] | [[Category:Experimental]] | ||
Revision as of 18:00, 28 January 2018
CRIU can use this option to migrate applications over the network.
Remote
Add the --remote 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 --remote:
dst_node# criu image-cache -d --port <port> src_node# criu image-proxy -d --port <port> --address <dst_node> src_node# criu dump -t <pid> --remote dst_node# criu restore --remote
Image Cache
The option's syntax is image-cache -d --port.
Image Proxy
The option's syntax is image-proxy -d --port --address $dst_node.
Video
To view an example video of process migration via Unix socket, please go to https://asciinema.org/a/GFurArJS1swuZQ5ptE7kW69E4.