1,734
edits
Changes
update scenarios
== Improved security CI/CD and development operations ==
== Server consolidation Containers and big data ==
* Isolated users
* A VE container is like a real server, just very cheap
* Each user can have an individual versions of applications
* Much easier to administer
== Educational 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. == See also ==