VETH device - Revision history

Kir: add to external cat

2016-11-02T01:09:30Z

add to external cat

Kir: improved (better names in syntax, define "inner" and "outer", clarifications)

2016-11-02T00:16:00Z

improved (better names in syntax, define "inner" and "outer", clarifications)

Kir: improve the description

2016-11-02T00:07:11Z

improve the description

Kir: formatting, typos

2016-11-01T06:45:39Z

formatting, typos

Xemul at 13:55, 25 October 2016

2016-10-25T13:55:01Z

Xemul at 10:50, 26 September 2016

2016-09-26T10:50:06Z

Xemul at 10:14, 21 September 2016

2016-09-21T10:14:02Z

Xemul: Created page with "Category: Empty articles Category: HOWTO Category: API"

2016-09-08T23:11:31Z

Created page with "Category: Empty articles Category: HOWTO Category: API"

New page

[[Category: Empty articles]]
[[Category: HOWTO]]
[[Category: API]]

← Older revision		Revision as of 01:09, 2 November 2016
Line 16:		Line 16:
	[[Category: API]]		[[Category: API]]
	[[Category: Network]]		[[Category: Network]]
		+	[[Category: External]]

@@ Line 1: / Line 1: @@
 == Checkpoint ==
-VETH is an interconnected pair of devices in two different network namespace. Checkpointing a network namespace with an VETH device in it doesn't require any special options for CRIU. Upon checkpoint, information about one end of VETH pair is saved to [[images]], when this device dies (together with the containing namespace), and the other end dies instantly, too, as it has no peer.
+VETH is an interconnected pair of devices in two different network namespace. With CRIU, you can checkpoint a network namespace with an VETH device in it (called "inner" device) doesn't require any special options for CRIU. Upon checkpoint, information about the inner VETH device is saved to [[images]], when this device dies (together with the containing namespace), and the other end (called "outer" device) dies instantly, too, for the lack of peer.
 == Restore ==
-When you restore a net namespace with a VETH device end in it, CRIU creates a VETH pair automatically. By default, the "outer" device name is autogenerated by the kernel, which is not convenient. Option <code>--external</code> ([[RPC]] equivalent is <code>opts.external</code> field) can be used to set that name explicitly.
+When you restore a net namespace with a VETH device end in it, CRIU creates a VETH pair automatically. By default, the outer device name is autogenerated by the kernel, which is not convenient. Option <code>--external</code> (or [[RPC]] equivalent field <code>opts.external</code>) can be used to set that name explicitly.
-The syntax is <code>--external veth[''NAME'']:''HOSTNAME''@''BRIDGE''</code>, with the <code>@''BRIDGE''</code> part being optional. Here ''NAME'' is an "inner" VETH device name, and ''HOSTNAME'' is the "outer" VETH device name. If <code>@''BRIDGE''</code> is specified, the ''HOSTNAME'' device is added to the appropriate bridge device.
+The syntax is <code>--external veth[''inner_dev'']:''outer_dev''@''bridge''</code>, with the <code>@''bridge''</code> part being optional. Here ''inner_dev'' is an "inner" VETH device name, and ''outer_dev'' is the "outer" VETH device name. If <code>@''bridge''</code> is specified, the ''outer_dev'' device is added to that bridge.
 == Obsoleted option ==
-Option <code>--veth-pair NAME=HOSTNAME[@BRIDGE]</code> (or corresponding [[RPC]] field <code>opts.veths</code>) was used in old versions of CRIU for the same effect as <code>--external veth</code>. This option is now obsolete and will be [[deprecation|deprecated]] soon.
+Option <code>--veth-pair ''inner_dev''=''outer_dev''[@''bridge'']</code> (or corresponding [[RPC]] field <code>opts.veths</code>) was used in old versions of CRIU for the same effect as <code>--external veth</code>. This option is now obsolete and will be [[deprecation|deprecated]] soon.
 [[Category: HOWTO]]
 [[Category: API]]
 [[Category: Network]]

@@ Line 1: / Line 1: @@
-When you restore a net namespace with a VETH device end in it, CRIU will create the other end of the pair in the net namespace you launch CRIU from. By default its name will be the one generated by the veth kernel driver. Not to scan through all the net devices trying to find one, you can use the --external option (<code>opts.external</code> field in [[RPC]]) in the form <code>--external veth[''NAME'']:''HOSTNAME''@''BRIDGE''</code> (the <code>@''BRIDGE''</code> part is optional). When used, a device named <code>''NAME''</code> in a newly restored namespace will be linked with the <code>''HOSTNAME''</code> one in the CRIU namespace and, optionally, the host-side device will be added to the <code>''BRIDGE''</code> bridge device.
+== Checkpoint ==
-== Old days ==
+VETH is an interconnected pair of devices in two different network namespace. Checkpointing a network namespace with an VETH device in it doesn't require any special options for CRIU. Upon checkpoint, information about one end of VETH pair is saved to [[images]], when this device dies (together with the containing namespace), and the other end dies instantly, too, as it has no peer.
-For now CRIU the same functionality was controlled with the <code>--veth-pair NAME=HOSTNAME[@BRIDGE]</code> option and <code>opts.veths</code> [[RPC]] field. Soon this option will be [[deprecation|deprecated]].
+== Restore ==
 [[Category: HOWTO]]
 [[Category: API]]
 [[Category: Network]]

← Older revision		Revision as of 06:45, 1 November 2016
Line 1:		Line 1:
−	When you restore a net namespace with a VETH device end in it, CRIU will create the other end of the pair in the net namespace you launch CRIU from. By default its name will be the one generated by the veth kernel driver. Not to scan through all the net devices trying to find one, you can use the --external option (<code>opts.external</code> field in [[RPC]]) in the form <code>--external veth[NAME]:HOSTNAME{@BRIDGE}</code> (the <code>@BRIDGE</code> part is optional). When used a device named <code>''NAME''</code> in a newly restored namespace will be linked with the <code>''HOSTNAME''</code> one in the CRIU namespace and optionally the host-side device will be ~~adder~~ to the <code>''BRIDGE''</code> bridge device.	+	When you restore a net namespace with a VETH device end in it, CRIU will create the other end of the pair in the net namespace you launch CRIU from. By default its name will be the one generated by the veth kernel driver. Not to scan through all the net devices trying to find one, you can use the --external option (<code>opts.external</code> field in [[RPC]]) in the form <code>--external veth[''NAME'']:''HOSTNAME''@''BRIDGE''</code> (the <code>@''BRIDGE''</code> part is optional). When used, a device named <code>''NAME''</code> in a newly restored namespace will be linked with the <code>''HOSTNAME''</code> one in the CRIU namespace and, optionally, the host-side device will be added to the <code>''BRIDGE''</code> bridge device.

	== Old days ==		== Old days ==

@@ Line 1: / Line 1: @@
 When you restore a net namespace with a VETH device end in it, CRIU will create the other end of the pair in the net namespace you launch CRIU from. By default its name will be the one generated by the veth kernel driver. Not to scan through all the net devices trying to find one, you can use the --external option (<code>opts.external</code> field in [[RPC]]) in the form <code>--external veth[NAME]:HOSTNAME{@BRIDGE}</code> (the <code>@BRIDGE</code> part is optional). When used a device named <code>''NAME''</code> in a newly restored namespace will be linked with the <code>''HOSTNAME''</code> one in the CRIU namespace and optionally the host-side device will be adder to the <code>''BRIDGE''</code> bridge device.
-In the older version of CRIU the same functionality was controlled with the <code>--veth-pair NAME=HOSTNAME[@BRIDGE]</code> option and <code>opts.veths</code> [[RPC]] field.
+== Old days ==
 [[Category: HOWTO]]
 [[Category: API]]
 [[Category: Network]]

← Older revision		Revision as of 10:14, 21 September 2016
Line 2:		Line 2:
	[[Category: HOWTO]]		[[Category: HOWTO]]
	[[Category: API]]		[[Category: API]]
		+	[[Category: Network]]