P.Haul - Revision history

Avagin at 18:51, 4 November 2018

2018-11-04T18:51:34Z

Radostin: Update URL for go-criu

2018-11-01T18:19:08Z

Update URL for go-criu

Xemul: /* Further development plans */

2017-08-18T13:41:15Z

Further development plans

Xemul: /* Further development plans */

2017-07-06T13:47:37Z

Further development plans

Xemul: /* Source */

2017-07-06T13:44:53Z

Source

Xemul at 13:43, 6 July 2017

2017-07-06T13:43:31Z

Xemul: Created page with "P.Haul is an extension to CRIU that makes live migration with CRIU possible."

2017-07-06T13:24:33Z

Created page with "P.Haul is an extension to CRIU that makes live migration with CRIU possible."

New page

P.Haul is an extension to CRIU that makes [[live migration]] with CRIU possible.

@@ Line 43: / Line 43: @@
 * Add API for FS migration (if necessary)
 * Fix [[Py-P.Haul]] to use this library as a core
 [[Category: Live migration]]
 [[Category: New features]]

← Older revision		Revision as of 18:19, 1 November 2018
Line 1:		Line 1:
−	P.Haul is an extension to CRIU that makes [[live migration]] with CRIU possible. The effort first appeared as [[Py-P.Haul\|python script(s)]], but due to high complexity of python code integration, it was switched into Go. Right now the sources are in [https://github.com/~~xemul/criu/tree~~/criu-~~dev/phaul~~ criu~~-dev branch, <code>phaul/</code> subdir~~].	+	P.Haul is an extension to CRIU that makes [[live migration]] with CRIU possible. The effort first appeared as [[Py-P.Haul\|python script(s)]], but due to high complexity of python code integration, it was switched into Go. Right now the sources are in [https://github.com/checkpoint-restore/go-criu go-criu] repository.

	== Description ==		== Description ==

← Older revision		Revision as of 13:41, 18 August 2017
Line 45:		Line 45:

	[[Category: Live migration]]		[[Category: Live migration]]
−	[[Category: ~~Development~~]]	+	[[Category: New features]]

@@ Line 34: / Line 34: @@
 == Further development plans ==
 [[Category: Live migration]]
 [[Category: Development]]

@@ Line 21: / Line 21: @@
 Source is to call <code>phaul.MakePhaulClient</code> routine, it also returns a handler (and go error). Arguments are more complex.
-;<code>PhaulLocal</code> interface
+The first is <code>PhaulLocal</code> interface. This one has the single method called <code>DumpCopyRestore</code>. Once p.haul client and server agree, that all preparations (pre-dumps) are done and it's time to call full dump, copy images and call full restore, this method is called. It's up to go-phaul caller to implement this method, as dumping processes is very engine-specific. E.g. OpenVZ, Docker, LXC all have [[CLI|different ways]] of invoking the <code>criu dump</code> operation. In turn, the method accepts
 * <code>criu.Criu</code> -- a handler to Criu object from [[go wrappers]] using which client may invoke the dump action
@@ Line 29: / Line 27: @@
 * <code>last_client_images_path</code> string denoting where the last dump-s are. Needed to configure the [[incremental dumps]] for this final step
-;<code>PhaulRemote</code> interface
+Next goes the <code>PhaulRemote</code> interface with a set of methods, that client wants to be called on the server object. It's up to the caller to provide the RPC method for this. E.g. in phaul test the server handler is passed as is as this argument.
 After these preparations, the <code>client.Migrate()</code> is to be called.

← Older revision		Revision as of 13:43, 6 July 2017
Line 1:		Line 1:
−	P.Haul is an extension to CRIU that makes [[live migration]] with CRIU possible.	+	P.Haul is an extension to CRIU that makes [[live migration]] with CRIU possible. The effort first appeared as [[Py-P.Haul\|python script(s)]], but due to high complexity of python code integration, it was switched into Go. Right now the sources are in [https://github.com/xemul/criu/tree/criu-dev/phaul criu-dev branch, <code>phaul/</code> subdir].
		+
		+	== Description ==
		+
		+	P.Haul library is the pair of Go classes, one to be launched on the source node, the other one on the destination. Users are to import the source into their projects and call function directly. No CLI provided (yet).
		+
		+	=== Configuration ===
		+
		+	Both source and destination should create a <code>PhaulConfig</code> object that configures client and server. The fields are
		+
		+	* <code>Pid</code> -- the pid of the process subtree to live migrate
		+	* <code>Memfd</code> -- file descriptor via which CRIU will send processes' memory contents
		+	* <code>Wdir</code> -- path where CRIU can put intermediate files (images, logs, etc.)
		+
		+	=== Destination ===
		+
		+	Destination process is to call <code>phaul.MakePhaulServer</code> routine, that returns back a handler (and go error). Argument is the <code>PhaulConfig</code> object described above.
		+
		+	=== Source ===
		+
		+	Source is to call <code>phaul.MakePhaulClient</code> routine, it also returns a handler (and go error). Arguments are more complex.
		+
		+	;<code>PhaulLocal</code> interface
		+
		+	This one has the single method called <code>DumpCopyRestore</code>. Once p.haul client and server agree, that all preparations (pre-dumps) are done and it's time to call full dump, copy images and call full restore, this method is called. It's up to go-phaul caller to implement this method, as dumping processes is very engine-specific. E.g. OpenVZ, Docker, LXC all have [[CLI\|different ways]] of invoking the <code>criu dump</code> operation. In turn, the method accepts
		+
		+	* <code>criu.Criu</code> -- a handler to Criu object from [[go wrappers]] using which client may invoke the dump action
		+	* <code>PhaulConfig</code> object
		+	* <code>last_client_images_path</code> string denoting where the last dump-s are. Needed to configure the [[incremental dumps]] for this final step
		+
		+	;<code>PhaulRemote</code> interface
		+
		+	This is an interface with a set of methods, that client wants to be called on the server object. It's up to the caller to provide the RPC method for this. E.g. in phaul test the server handler is passed as is as this argument.
		+
		+	;<code>PhaulConfig</code>
		+
		+
		+	After these preparations, the <code>client.Migrate()</code> is to be called.
		+
		+	== Further development plans ==
		+
		+	[[Category: Live migration]]
		+	[[Category: Development]]