Difference between revisions of "CLI/opt/--remote"
Jump to navigation
Jump to search
(Add diagram) |
(Reduce size of diagram) |
||
| Line 19: | Line 19: | ||
</pre> | </pre> | ||
| − | [[File:CRIU-Remote.png| | + | [[File:CRIU-Remote.png|480px]] |
== Image Cache == | == Image Cache == | ||
Revision as of 20:34, 6 October 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 <port>.
Image Proxy
The option's syntax is image-proxy -d --port <port> --address <dst_node>.
Video
To view an example video of process migration via Unix socket, please go to https://asciinema.org/a/GFurArJS1swuZQ5ptE7kW69E4.