WP/What are containers - Revision history

Kir: io bandwidth limit is avail in openvz

2015-05-08T20:48:26Z

io bandwidth limit is avail in openvz

Kir: rm unnecessary header

2015-05-08T20:47:51Z

rm unnecessary header

Sergey Bronnikov: Parallels Containers -> Virtuozzo

2015-05-08T11:41:29Z

Parallels Containers -> Virtuozzo

Kir: Reverted edits by 201.95.253.60 (talk) to last revision by 209.119.62.91

2011-11-28T03:38:49Z

Reverted edits by 201.95.253.60 (talk) to last revision by 209.119.62.91

201.95.253.60: /* Memory */

2011-11-28T03:37:33Z

‎Memory

209.119.62.91: /* Performance and density */

2011-04-07T02:02:56Z

‎Performance and density

Kir: /* Bridge-based (veth) / rm extra

2011-03-31T12:48:07Z

‎Bridge-based (veth): rm extra *

Kir: /* Performance and density */ FIXME

2011-03-31T12:42:35Z

‎Performance and density: FIXME

Kir: incorporated feedback from dev@

2011-03-31T12:22:37Z

incorporated feedback from dev@

Show changes

Kir: /* Checkpointing and live migration */ moar

2011-03-24T16:02:08Z

‎Checkpointing and live migration: moar

@@ Line 94: / Line 94: @@
 * '''Disk I/O priority'''. Containers compete for I/O operations, and can affect each other if they use the same disk drive. OpenVZ introduces a per-container I/O priority, which can be used to e.g. decrease the "bad guy" I/O rate in order to not trash the other containers.
-* '''Disk I/O bandwidth'''. I/O bandwidth (in bytes per second) can be limited per-container (currently only available in commercial Virtuozzo).
+* '''Disk I/O bandwidth'''. I/O bandwidth (in bytes per second) can be limited per-container.
 === Memory ===

← Older revision		Revision as of 20:47, 8 May 2015
Line 1:		Line 1:
−	~~= OpenVZ Linux Containers technology whitepaper =~~
−	~~<s><big><big><b>{{PDFlink\|[[Media:What are containers.pdf\|Download in PDF]]}}</b></big></big></s>~~
−
	OpenVZ is an open source virtualization technology for Linux that enables the partitioning of a single physical Linux machine into multiple smaller independent units called containers.		OpenVZ is an open source virtualization technology for Linux that enables the partitioning of a single physical Linux machine into multiple smaller independent units called containers.

@@ Line 97: / Line 97: @@
 * '''Disk I/O priority'''. Containers compete for I/O operations, and can affect each other if they use the same disk drive. OpenVZ introduces a per-container I/O priority, which can be used to e.g. decrease the "bad guy" I/O rate in order to not trash the other containers.
-* '''Disk I/O bandwidth'''. I/O bandwidth (in bytes per second) can be limited per-container (currently only available in commercial Parallels Virtuozzo Containers).
+* '''Disk I/O bandwidth'''. I/O bandwidth (in bytes per second) can be limited per-container (currently only available in commercial Virtuozzo).
 === Memory ===

@@ Line 99: / Line 99: @@
 * '''Disk I/O bandwidth'''. I/O bandwidth (in bytes per second) can be limited per-container (currently only available in commercial Parallels Virtuozzo Containers).
-If you want to get read, this is how you solhud write.
+=== Memory ===
 === Miscellaneous resources ===

@@ Line 99: / Line 99: @@
 * '''Disk I/O bandwidth'''. I/O bandwidth (in bytes per second) can be limited per-container (currently only available in commercial Parallels Virtuozzo Containers).
-=== Memory ===
+If you want to get read, this is how you solhud write.
 === Miscellaneous resources ===

@@ Line 181: / Line 181: @@
 === Performance and density ===
-* {{FIXME|need to add data}}
+* See [[Performance]]
 === Limitations ===

@@ Line 170: / Line 170: @@
 * '''DHCP''' and dynamic IP addresses are possible
 * Broadcasting have negative performance impact (it is delivered separately to each CT)
 ==== Real network device in a container ====

← Older revision		Revision as of 12:42, 31 March 2011
Line 182:		Line 182:

	=== Performance and density ===		=== Performance and density ===
		+	* {{FIXME\|need to add data}}

	=== Limitations ===		=== Limitations ===

@@ Line 117: / Line 117: @@
 == Checkpointing and live migration ==
-Live migration is an ability to move a running container from one physical server to another without a shutdown or service interruption. Live migration is based on checkpointing, it does not require any special hardware, disk or networking setup.
+'''Checkpointing''' is an OpenVZ kernel feature that makes it able to freeze a running container (i.e. pause all its processes) and dump its complete in-kernel state into a file on disk. Such a dump file contains everything about processes inside a container: their memory, opened files, network connections, states etc. Then, a running container can be restored from the dump file and continue to run normally. The concept is somewhat similar to suspend-to-disk, only for a single container and much faster.
-Checkpointing is an OpenVZ kernel feature that makes it able to freeze a running container (i.e. pause all its processes) and dump its complete in-kernel state into a file on disk. Such a dump file contains everything about processes inside a container: their memory, opened files, network connections, states etc. It is possible to restore a container from a dump file and resume its execution, with. From inside the container it looks like a mere jump forward in time, there are no other side effects. Container can also be restored on a different system, and if its file system is the same it will continue to run as is on a new system.
+A container can be restored from a dump file on a different physical server, opening the door for live migration.
-Checkpointing is currently supported for x86, x86_64 (previously it was also supported on IA64).
+'''Live migration''' is an ability to move a running container from one physical server to another without a shutdown or service interruption. Network connections are migrated as well, so from a user's point of view it looks like some delay in response. OpenVZ live migration does not require any special hardware, disk or networking setup. It is implemented in the following way:
-{{FIXME|: what else?}}
+# Run rsync to copy container files to the destination system (the container is still running)
 == Miscellaneous topics ==