Leaflet - Revision history

Sergey Bronnikov: added categories

2015-08-27T11:05:16Z

added categories

Sergey Bronnikov: added link to fedora booklet sources

2015-08-27T11:04:26Z

added link to fedora booklet sources

Sergey Bronnikov: Sergey Bronnikov moved page Booklet to Leaflet

2015-08-05T14:25:39Z

Sergey Bronnikov moved page Booklet to Leaflet

195.214.232.10 at 10:58, 3 August 2015

2015-08-03T10:58:21Z

195.214.232.10 at 10:56, 3 August 2015

2015-08-03T10:56:17Z

Show changes

195.214.232.10 at 10:35, 3 August 2015

2015-08-03T10:35:25Z

Sergey Bronnikov at 16:33, 31 July 2015

2015-07-31T16:33:08Z

Syemelianova: /* Frequently Asked Questions */

2015-07-31T15:20:32Z

‎Frequently Asked Questions

Syemelianova: /* Frequently Asked Questions */

2015-07-31T15:01:23Z

‎Frequently Asked Questions

Syemelianova: /* Education */

2015-07-31T14:41:41Z

‎Education

← Older revision		Revision as of 11:05, 27 August 2015
Line 166:		Line 166:

	* [https://github.com/fedoradesign/flock2015booklet Fedora Flock 2015 booklet]		* [https://github.com/fedoradesign/flock2015booklet Fedora Flock 2015 booklet]
		+
		+	[[Category:Events‏‎]]
		+	[[Category:Design]]

← Older revision		Revision as of 11:04, 27 August 2015
Line 162:		Line 162:

	Stay tuned: https://twitter.com/_openvz_		Stay tuned: https://twitter.com/_openvz_
		+
		+	== See also ==
		+
		+	* [https://github.com/fedoradesign/flock2015booklet Fedora Flock 2015 booklet]

@@ Line 9: / Line 9: @@
 *'''Management utilities''', such as vzctl, for managing container life cycle.
-*'''Checkpoint/Restore In Userspace''', or CRIU (pronounced kree-oo, IPA: /krɪʊ/, Russian: криу), is a software tool for Linux that enables you to freeze a running application (or a part of it) and checkpoint it to a hard drive as a collection of files. You can then use the files to restore and run the application from the point it was frozen at. The distinctive feature of the CRIU project is that it is mainly implemented in user space. Docker and LXC use CRIU for migrating containers between servers.
+*'''Checkpoint/Restore In Userspace''', or CRIU (pronounced kree-oo, IPA: /krɪʊ/, Russian: криу), is a software tool for Linux that enables you to freeze a running application (or a part of it) and checkpoint it to a hard drive as a collection of files. You can then use the files to restore and run the application from the point it was frozen at. The distinctive feature of the CRIU project is that it is mainly implemented in userspace. Docker and LXC use CRIU for migrating containers between servers.
 *'''P.Haul''' is the project on top of CRIU that implements the live migration usage scenario.
@@ Line 58: / Line 58: @@
 '''2011''':
-*Jul 2011: Pavel Emelianov sends initial RFC and code. The idea of CRIU came up earlier when OpenVZ team realised that merging in-kernel checkpoint/restore was impossible. Re-implementing it in userspace looked crazy for everyone, Andrew Morton and Linus Torvalds included ("Some crazy russians").
+*Jul 2011: Pavel Emelianov sends initial RFC and code. The idea of CRIU came up earlier when OpenVZ team realized that merging in-kernel checkpoint/restore was impossible. Re-implementing it in userspace looked crazy for everyone, Andrew Morton and Linus Torvalds included ("Some crazy russians").
 *Sep 2011: Cyrill Gorcunov makes the first commit to the CRIU project.

@@ Line 5: / Line 5: @@
 OpenVZ is a project that combines the following container virtualization technologies for Linux:
-*'''Virtuozzo kernel''' is a Linux kernel with patches that implements OpenVZ kernel functionality.
+*'''Virtuozzo kernel''', a Linux kernel with patches that implements OpenVZ kernel functionality.
 *'''Management utilities''', such as vzctl, to manage container life cycle.

← Older revision		Revision as of 16:33, 31 July 2015
Line 1:		Line 1:
		+	= Container-based virtualization for Linux. Fast, lightweight, secure. Choose three. =
		+
	== What is OpenVZ? ==		== What is OpenVZ? ==

← Older revision	Revision as of 14:25, 5 August 2015
(No difference)

@@ Line 95: / Line 95: @@
 '''What is the relationship between OpenVZ and LXC?'''
-OpenVZ develops new container technology that then goes upstream into the vanilla Linux kernel. OpenVZ has about a 5 year head start on LXC, but is actively feeding technology upstream into vanilla containers. Several internal details currently differ (OpenVZ adds new system calls, vanilla uses the cgroups filesystem, new clone flags, and other mechanisms).
+OpenVZ develops new container technology that then goes upstream into the vanilla Linux kernel. OpenVZ has about a 5 year head start on LXC, but is actively feeding the technology upstream into vanilla containers. Several internal details currently differ (OpenVZ adds new system calls, vanilla uses the cgroups filesystem, new clone flags, and other mechanisms).
 '''What applications can run inside an OpenVZ container?'''

@@ Line 87: / Line 87: @@
 '''What are the highlights of OpenVZ technology?'''
-OpenVZ is highly scalable virtualization technology for Linux with near-zero overhead, strong isolation and rapid customer provisioning that's ready for production use right now. Deployment of OpenVZ improves efficiency, flexibility and quality of service in the enterprise environment.
+OpenVZ is highly scalable virtualization technology for Linux with near-zero overhead, strong isolation and rapid customer provisioning that is ready for production use right now. Deployment of OpenVZ improves efficiency, flexibility and quality of service in the enterprise environment.
 '''How is OpenVZ different from other technologies?'''
-Virtual Machines boot separate kernels on emulated hardware instances.  OpenVZ runs all containers under a single Linux kernel.  OpenVZ offers much higher density, hosting thousands of containers on a single physical server, but can only run Linux in those containers. Virtual machine solutions usually top out at a few dozen instances, but can run different operating systems in each.
+Virtual machines boot separate kernels on emulated hardware instances. OpenVZ runs all containers under a single Linux kernel. OpenVZ offers much higher density, hosting thousands of containers on a single physical server, but can only run Linux in those containers. Virtual machine solutions usually top out at a few dozen instances, but can run different operating systems in each.
 '''What is the relationship between OpenVZ and LXC?'''
-OpenVZ develops new container technology that then goes upstream into the vanilla Linux kernel.  OpenVZ has about a 5 year headstart on LXC, but is actively feeding technology upstream into vanilla containers. Several internal details currently differ (OpenVZ adds new system calls, vanilla uses the cgroups filesystem, new clone flags, and other mechanisms).
+OpenVZ develops new container technology that then goes upstream into the vanilla Linux kernel. OpenVZ has about a 5 year head start on LXC, but is actively feeding technology upstream into vanilla containers. Several internal details currently differ (OpenVZ adds new system calls, vanilla uses the cgroups filesystem, new clone flags, and other mechanisms).
 What applications can run inside an OpenVZ container?
-Applications and services do not have to be aware of OpenVZ, and most install without any modifications: Java, Oracle, DB/2, Weblogic, Websphere and many other big applications run just fine inside OpenVZ containers. However, direct access to hardware is not available by default; if required it must be provided by the system administrator.
+'''What applications can run inside an OpenVZ container?'''
 '''How scalable is OpenVZ?'''

@@ Line 150: / Line 150: @@
 === Education ===
-* Every student can have root access
+* Every student can have root access.
-* Different distributions are supported
+* Different distributions are supported.
-* No need for a lot of hardware
+* Low hardware requirements.