OpenVZ has a number of unique features that can be effectively used in the following scenarios:
== Improved security ==The high system utilization capabilities and improved performance allow containers to get the most out of an enterprisesystem’s infrastructure. With a common kernel among containers, OS management is far less impacted than for a VM-basedsystem.
Consider a Linux server used to serve mail, web site, == CI/CD 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 VEs.development operations ==
== Server consolidation == Containers offers significant benefits for CI/CD and development operations (DevOps). A key hurdle during applicationdevelopment is the point when finished code is turned over to the testing and production side. Often, an application that ranfine for the developer doesn’t run during production testing. Containers are well suited for application development sinceyou can define all of the elements of an application environment within the container. This means if the application runs inthe development container it will run in a final production container that matches it. With containers, testing can beaccomplished without disrupting other applications. Container startup is much quicker than VMs, allowing on-demandexecution of CI processes and quicker testing cycles. Application updates can also be facilitated through independentreleases of many containerized micro-services. This agility allows for limited or dark releases and rollback changes at themicro-service level.
Having a separate physical server for each application is generally a good approach, it increases availability == Containers and improves security. However, separate servers lead to increased costs of hardware and collocation, and modern hardware is often underutilized in this scenario.big data ==
With OpenVZThe moving of processes or data might be optimized with containers. A new process container might be virtually created ona data storage container, you or a data container can enjoy the benefits be created and filled on a process container. Much of Big Data is reallyLittle Data buried inside huge amounts of dedicated server without unrelated data. A light-weight process may efficiently extract a small dataset andsend it to a parallel computer such drawbacks. Create as a VE GPU for each application and use the existing hardware more efficientlyprocessing. This approach can Other processes might be deployed totally transparently characterized by both volume andtype and need to users using OpenVZrequest more storage for explosively growing processes.
== Development Possible uses cases to provide big data and testing ==Analytics as a Service (AaaS) include:
* Data scientists that want to experiment and learn about big data technologies.* Developers often that need access to several different Linux distributions to develop an applicationa locally accessible big data development environment. Testing also needs * Users that want to be performed on various software configurations. Therefore, testing and development groups often require share a lot of hardware. Alternatively, using OpenVZ developers big data application quickly 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 filessafely.
A better way is to use OpenVZ. You can use different Linux distributions for different [[VE]]s residing on one physical server. Each [[VE]] can have its own set of packages, system libraries, configuration files.== Hosting ==
== Hosting ==
* Isolated users
* A VE container is like a real server, just very cheap* Each user can have his own an individual versions of applications* Much easier to adminadminister == Server consolidation == 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. 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 container for each application and use the existing hardware more efficiently. This approach can be deployed totally transparently to users using OpenVZ.
== Educational See also ==
With OpenVZ, a separate VE can be created for every student* [[Success stories]]* [http://h20195. Thus, each student gets their own root account and can do everything on their own server, ewww2.ghp. experiment with firewall configuration rules (iptables)com/V2/getpdf.aspx/4AA5-9251ENW.pdf?ver=1.0 Technical white paper: Linux container technology]
