Use cases - Revision history

Sergey Bronnikov: update scenarios

2015-08-05T14:27:49Z

update scenarios

Sergey Bronnikov: add link to Success stories

2015-08-04T14:17:34Z

add link to Success stories

Sergey Bronnikov: Mention usecase with Docker

2015-04-09T17:43:39Z

Mention usecase with Docker

Sergey Bronnikov: Add one more scenario and usecase

2015-04-09T17:30:15Z

Add one more scenario and usecase

Botinki Kira: Robot: Automated text replacement (-VE +container)

2008-03-11T13:00:33Z

Robot: Automated text replacement (-VE +container)

Botinki Kira: Robot: Automated text replacement (-VEs +containers)

2008-03-11T09:50:27Z

Robot: Automated text replacement (-VEs +containers)

Elronxenu: Tidy grammar

2007-09-06T08:45:28Z

Tidy grammar

Kir: questions/discussions should go to discussion page

2007-01-16T14:35:24Z

questions/discussions should go to discussion page

Akrueger: /* Hosting */ Asking for some information that is missing here. Answer should be given and question removed.

2007-01-14T20:54:46Z

‎Hosting: Asking for some information that is missing here. Answer should be given and question removed.

Kir: Added stub notice

2006-06-14T12:43:41Z

Added stub notice

@@ Line 1: / Line 1: @@
-OpenVZ has a number of unique features that can be effectively used in the following scenarios:
+The high system utilization capabilities and improved performance allow containers to get the most out of an enterprise
-== Improved security ==
+== CI/CD and development operations ==
-Consider a Linux server used to serve mail, web site, and DNS. There are at least three different applications listening to and handling network requests, and any of them can contain security holes. Using OpenVZ, a server can be divided into three [[container]]s, one for each application. Thus, if the DNS server is compromised, the other applications will still be left intact due to complete isolation between containers.
+Containers offers significant benefits for CI/CD and development operations (DevOps). A key hurdle during application
-== Server consolidation ==
+== Containers and big data ==
-== Development and testing ==
+The moving of processes or data might be optimized with containers. A new process container might be virtually created on
-Developers often need access to several different Linux distributions to develop an application. Testing also needs to be performed on various software configurations. Therefore, testing and development groups often require a lot of hardware.
+Possible uses cases to provide big data and Analytics as a Service (AaaS) include:
-Alternatively, using OpenVZ developers and QAs can create multiple partitions with different Linux distributions and configurations residing on one physical server. Each container can have its own set of packages, system libraries, configuration files. You can do snapshots and rollbacks.
+* Data scientists that want to experiment and learn about big data technologies.
 == Hosting ==
@@ Line 26: / Line 37: @@
 * Much easier to administer
-== Educational ==
+== Server consolidation ==
-With OpenVZ, a separate container can be created for every student. Thus, each student gets their own root account and can do everything on their own server, e.g. experiment with firewall configuration rules (iptables).
+Consider a Linux server used to serve a bunch of services. You will have downtime for each service during OS update or setup failover cluster for each service to decrease downtime. Using OpenVZ, a server can be divided into several [[container]]s, one for each service. With [[Checkpointing and live migration|live migration]] available for [[container]]s you can migrate your services to another service and return them back after upgrading server.
-== Easy maintenance ==
+Having a separate physical server for each application is generally a good approach, it increases availability and improves security. However, separate servers lead to increased costs of hardware and collocation, and modern hardware is often underutilized in this scenario.
 == See also ==
 * [[Success stories]]

@@ Line 34: / Line 34: @@
 Consider a Linux server used to serve a bunch of services. You will have downtime for each service during OS update or setup failover cluster for each service to decrease downtime. Using OpenVZ, a server can be divided into several [[container]]s, one for each service. With [[Checkpointing and live migration|live migration]] available for [[container]]s you can migrate your services to another service and return them back after upgrading server.
-----
+== See also ==
-== Small usecases ==
+* [[Success stories]]

← Older revision		Revision as of 17:43, 9 April 2015
Line 39:		Line 39:

	* [[Virtual HSM]] is a software suite for storing and manipulating secret data outside the virtualized application environment.		* [[Virtual HSM]] is a software suite for storing and manipulating secret data outside the virtualized application environment.
		+	* Docker containers are not safe from security point of view due to poor isolation. You can setup [[Docker inside CT\|Docker inside OpenVZ]] [[container]] and it's containers there.

@@ Line 20: / Line 20: @@
 == Hosting ==
 * Isolated users
 * A container is like a real server, just very cheap
@@ Line 28: / Line 29: @@
 With OpenVZ, a separate container can be created for every student. Thus, each student gets their own root account and can do everything on their own server, e.g. experiment with firewall configuration rules (iptables).

@@ Line 5: / Line 5: @@
 == Improved security ==
-Consider a Linux server used to serve mail, web site, and DNS. There are at least three different applications listening to and handling network requests, and any of them can contain security holes. Using OpenVZ, a server can be divided into three [[VE]]s, one for each application. Thus, if the DNS server is compromised, the other applications will still be left intact due to complete isolation between containers.
+Consider a Linux server used to serve mail, web site, and DNS. There are at least three different applications listening to and handling network requests, and any of them can contain security holes. Using OpenVZ, a server can be divided into three [[container]]s, one for each application. Thus, if the DNS server is compromised, the other applications will still be left intact due to complete isolation between containers.
 == Server consolidation ==
@@ Line 11: / Line 11: @@
 Having a separate physical server for each application is generally a good approach, it increases availability and improves security. However, separate servers lead to increased costs of hardware and collocation, and modern hardware is often underutilized in this scenario.
-With OpenVZ, you can enjoy the benefits of dedicated server without such drawbacks. Create a VE for each application and use the existing hardware more efficiently. This approach can be deployed totally transparently to users using OpenVZ.
+With OpenVZ, you can enjoy the benefits of dedicated server without such drawbacks. Create a container for each application and use the existing hardware more efficiently. This approach can be deployed totally transparently to users using OpenVZ.
 == Development and testing ==
@@ Line 17: / Line 17: @@
 Developers often need access to several different Linux distributions to develop an application. Testing also needs to be performed on various software configurations. Therefore, testing and development groups often require a lot of hardware.
-Alternatively, using OpenVZ developers and QAs can create multiple partitions with different Linux distributions and configurations residing on one physical server. Each VE can have its own set of packages, system libraries, configuration files. You can do snapshots and rollbacks.
+Alternatively, using OpenVZ developers and QAs can create multiple partitions with different Linux distributions and configurations residing on one physical server. Each container can have its own set of packages, system libraries, configuration files. You can do snapshots and rollbacks.
 == Hosting ==
 * Isolated users
-* A VE is like a real server, just very cheap
+* A container is like a real server, just very cheap
 * Each user can have an individual versions of applications
 * Much easier to administer
@@ Line 27: / Line 27: @@
 == Educational ==
-With OpenVZ, a separate VE can be created for every student. Thus, each student gets their own root account and can do everything on their own server, e.g. experiment with firewall configuration rules (iptables).
+With OpenVZ, a separate container can be created for every student. Thus, each student gets their own root account and can do everything on their own server, e.g. experiment with firewall configuration rules (iptables).

← Older revision		Revision as of 12:43, 14 June 2006
Line 1:		Line 1:
		+	{{stub}}
		+
	OpenVZ has a number of unique features that can be effectively used in the following scenarios:		OpenVZ has a number of unique features that can be effectively used in the following scenarios: