Difference between revisions of "CLI/opt/--remote"
(Add diagram) |
m |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | The <code>--remote</code> option and image cache/proxy implementation have been deprecated in favour of criu-image-streamer. | ||
| + | |||
CRIU can use this option to migrate applications over the network. | CRIU can use this option to migrate applications over the network. | ||
| Line 19: | Line 21: | ||
</pre> | </pre> | ||
| − | [[File:CRIU-Remote.png| | + | [[File:CRIU-Remote.png|480px]] |
== Image Cache == | == Image Cache == | ||
Latest revision as of 17:58, 12 January 2024
The --remote option and image cache/proxy implementation have been deprecated in favour of criu-image-streamer.
CRIU can use this option to migrate applications over the network.
Remote[edit]
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[edit]
The option's syntax is image-cache -d --port <port>.
Image Proxy[edit]
The option's syntax is image-proxy -d --port <port> --address <dst_node>.
Video[edit]
To view an example video of process migration via Unix socket, please go to https://asciinema.org/a/GFurArJS1swuZQ5ptE7kW69E4.