Difference between revisions of "Integration"

From CRIU
Jump to navigation Jump to search
m (→‎Wayland/Weston: Not X-server, but weston.)
Line 29: Line 29:
 
{{Status|under investigation}}
 
{{Status|under investigation}}
 
* Ruslan Kuprieiev plans to [http://lists.openvz.org/pipermail/criu/2015-January/018875.html patch] Weston to let CRIU C/R graphical apps
 
* Ruslan Kuprieiev plans to [http://lists.openvz.org/pipermail/criu/2015-January/018875.html patch] Weston to let CRIU C/R graphical apps
 +
 +
== The <code>file</code> utility ==
 +
{{Status|not started}}
 +
* Need to reformat the images' header not to contain unique magic values and submit a patch to <code>file</code> tool to identify those.
  
 
[[Category:Plans]]
 
[[Category:Plans]]

Revision as of 11:50, 5 March 2015

CRIU is not so easy to be used as a standalone tool -- it works best integrated into other software. This page lists such software and provides details about the current status.

OpenVZ

Status: in progress

Currently, vzctl supports CRIU for checkpoint/restore of upstream containers (i.e. when non-OpenVZ kernel is used). Commands vzctl suspend and vzctl restore fully work. Live migration doesn't work yet as it requires support for vzctl suspend {--suspend, --dump, --kill, --restore} which is not yet implemented as it requires a separate daemon to hold the state of a partially checkpointed container (or an ability from criu tool to do that).

LXC/LXD

Status: ready

Docker

Status: in progress

CoreOS Rocket

Status: not started

OpenMPI

Status: stalled

  • Adrian Reber did first version of patches

Wayland/Weston

Status: under investigation

  • Ruslan Kuprieiev plans to patch Weston to let CRIU C/R graphical apps

The file utility

Status: not started

  • Need to reformat the images' header not to contain unique magic values and submit a patch to file tool to identify those.