Integration - Revision history

Radostin at 10:13, 17 September 2021

2021-09-17T10:13:41Z

2021-09-17T10:08:48Z

Add OpenJDK

2021-09-17T10:02:39Z

Drop CoreOS Rocket

2019-03-13T17:41:46Z

+podman

2018-01-29T17:30:52Z

Virtuozzo/OpenVZ

2016-10-19T06:25:29Z

Shell

2016-10-19T06:25:04Z

Screen/TMUX

2016-10-04T23:35:46Z

Virtuozzo/OpenVZ: vz7 update

2016-10-04T23:13:56Z

Virtuozzo/OpenVZ: git.openvz.org is no more :(

2016-10-04T23:07:40Z

Systemd: fix formatting

@@ Line 56: / Line 56: @@
 == Other ==
-== OpenJDK ==
+=== OpenJDK ===
 {{Status|started}}

← Older revision		Revision as of 10:08, 17 September 2021
Line 55:		Line 55:

	== Other ==		== Other ==
		+
		+	== OpenJDK ==
		+	{{Status\|started}}
		+
		+	The [https://openjdk.java.net/projects/crac/ CRaC] (Coordinated Restore at Checkpoint) Project researches coordination of Java programs with mechanisms to checkpoint (make an image of, snapshot) a Java instance while it is executing. Restoring from the image could be a solution to some of the problems with the start-up and warm-up times. The primary aim of the Project is to develop a new standard mechanism-agnostic API to notify Java programs about the checkpoint and restore events. Other research activities will include, but will not be limited to, integration with existing checkpoint/restore mechanisms and development of new ones, changes to JVM and JDK to make images smaller and ensure they are correct.
		+
		+	* [https://openjdk.java.net/projects/crac/index.html OpenJDK: CRaC Project]
		+	* [https://wiki.openjdk.java.net/display/crac CRaC Wiki]
		+	* [https://github.com/openjdk/crac CRaC Repository]

	=== OpenMPI ===		=== OpenMPI ===

@@ Line 32: / Line 32: @@
 * [https://podman.io/ Project homepage]
 * [https://podman.io/blogs/2018/10/10/checkpoint-restore.html Blog entry about adding the support]
 == Tools and utilities ==

← Older revision		Revision as of 17:41, 13 March 2019
Line 27:		Line 27:

	''See also: [[Docker]] C/R''		''See also: [[Docker]] C/R''
		+
		+	== Podman ==
		+	{{Status\|ready}}
		+	* [https://podman.io/ Project homepage]
		+	* [https://podman.io/blogs/2018/10/10/checkpoint-restore.html Blog entry about adding the support]

	=== CoreOS Rocket ===		=== CoreOS Rocket ===

@@ Line 6: / Line 6: @@
 {{Status|ready}}
-As of Virtuozzo 7, CRIU is fully integrated and supported. Older OpenVZ releases used in-kernel checkpoint/restore functionality, now superseded by CRIU.
+As of Virtuozzo/OpenVZ 7, CRIU is fully integrated and supported. Older OpenVZ releases used in-kernel checkpoint/restore functionality, now superseded by CRIU.
 * [https://openvz.org/ OpenVZ]

← Older revision		Revision as of 06:25, 19 October 2016
Line 49:		Line 49:

	It would be nice to have bash (or other shell) to launch criu with <code>--restore-sibling</code> option and get new kid processes from it. Right now we workaround it with "[[shell jobs]]".		It would be nice to have bash (or other shell) to launch criu with <code>--restore-sibling</code> option and get new kid processes from it. Right now we workaround it with "[[shell jobs]]".
		+
		+	''See also: [[Shell jobs]]''

	== Other ==		== Other ==

← Older revision		Revision as of 06:25, 19 October 2016
Line 42:		Line 42:

	* Jerome [https://github.com/jpetazzo/critmux did] this some time ago		* Jerome [https://github.com/jpetazzo/critmux did] this some time ago
		+
		+	''See also: [[Screen]]''

	=== Shell ===		=== Shell ===

@@ Line 8: / Line 8: @@
 Currently, vzctl supports CRIU for checkpoint/restore of upstream containers (i.e. when non-OpenVZ kernel is used). Commands <code>vzctl suspend</code> and <code>vzctl restore</code> fully work. Live migration doesn't work yet as it requires support for <code>vzctl suspend {--suspend, --dump, --kill, --restore}</code> 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).
 * [https://openvz.org Project homepage]
 * [https://openvz.org/Virtuozzo Virtuozzo] is a virtualization and automation solution built on top of OpenVZ.

@@ Line 73: / Line 73: @@
 === Systemd ===
 {{Status|not started}}
- Migrating
+Adrian suggested that migrating
- processes from one system to another works, depending on the process,
+processes from one system to another works, depending on the process,
- pretty good. Migrating a process under systemd's control might be
+pretty good. Migrating a process under systemd's control might be
- possible by just killing the process on the source side but it cannot
+possible by just killing the process on the source side but it cannot
- become a child process of systemd on the destination of the migration
+become a child process of systemd on the destination of the migration
- without systemd knowing how to restore a process and thus making it a
+without systemd knowing how to restore a process and thus making it a
- child process of systemd (--restore-sibling).
+child process of systemd (--restore-sibling).
 [[Category:Plans]]
 [[Category:Development]]