Difference between revisions of "OpenVZ"
Jump to navigation
Jump to search
(Put to Category Proxmox VE 3.x) |
|||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | [[Category: | + | {{Note|Article about the old stable Proxmox VE 3.x releases}} |
| + | |||
| + | '''NOTE: OpenVZ is supported until Proxmox 3.4 and will end with Debian Wheezy security updates (expected end in April 2016)''' | ||
| + | |||
| + | OpenVZ is container-based virtualization for Linux. OpenVZ creates multiple secure, isolated containers (otherwise known as VEs or VPSs) on a single physical server enabling better server utilization and ensuring that applications do not conflict. Each container performs and executes exactly like a stand-alone server; a container can be rebooted independently and have root access, users, IP addresses, memory, processes, files, applications, system libraries and configuration files. | ||
| + | |||
| + | Currently all Proxmox VE Appliances are OpenVZ based and are "production ready". | ||
| + | |||
| + | For details see [http://openvz.org/ OpenVZ]. | ||
| + | |||
| + | [[Category:Proxmox VE 3.x]] | ||
Latest revision as of 15:10, 13 October 2016
|
Note: Article about the old stable Proxmox VE 3.x releases |
NOTE: OpenVZ is supported until Proxmox 3.4 and will end with Debian Wheezy security updates (expected end in April 2016)
OpenVZ is container-based virtualization for Linux. OpenVZ creates multiple secure, isolated containers (otherwise known as VEs or VPSs) on a single physical server enabling better server utilization and ensuring that applications do not conflict. Each container performs and executes exactly like a stand-alone server; a container can be rebooted independently and have root access, users, IP addresses, memory, processes, files, applications, system libraries and configuration files.
Currently all Proxmox VE Appliances are OpenVZ based and are "production ready".
For details see OpenVZ.