https://wiki.openvz.org/api.php?action=feedcontributions&feedformat=atom&user=Vporokhov 2026-05-14T14:58:32Z User contributions MediaWiki 1.31.1 https://wiki.openvz.org/index.php?title=Comparison&diff=23029 2018-09-19T13:10:48Z

<p>Vporokhov: /* Feature comparison of different virtualization solutions */</p> <hr /> <div>{{Note|This comparison doesn't include Docker, because Docker is not a virtualization solution. It automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of operating-system-level virtualization.&lt;ref&gt;[https://en.wikipedia.org/wiki/Docker_(software) Wikipedia article about Docker]&lt;/ref&gt;}}<br /> <br /> <br /> == Disclaimer ==<br /> <br /> The information regarding Virtuozzo 7 is provided by [http://www.virtuozzo.com Virtuozzo]. Here is the Virtuozzo's statement regarding this information:<br /> <br /> :#The information contained herein is intended to outline general product direction and should not be relied upon in making purchasing decisions.<br /> :#The content is for informational purposes only and may not be incorporated into any contract.<br /> :#The information presented is not a commitment, promise, or legal obligation to deliver any material, code or functionality.<br /> :#Any references to the development, release, and timing of any features or functionality described for these products remains at Virtuozzo’s sole discretion.<br /> :#Product capabilities, timeframes and features are subject to change and should not be viewed as Virtuozzo commitments.<br /> <br /> The information regarding all other solutions are taken by authors from public sources only. This information can be changed by any OpenVZ Wiki user without any notice and author's review or approval.<br /> <br /> <br /> == Feature comparison of different virtualization solutions ==<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> ! Feature<br /> ! Description<br /> ! OpenVZ<br /> ! Virtuozzo&amp;nbsp;6 (PCS 6)<br /> ! OpenVZ&amp;nbsp;7<br /> ! [https://virtuozzo.com/products/virtuozzo-containers/ Virtuozzo&amp;nbsp;7]<br /> ! LXC<br /> ! Proxmox VE<br /> ! Microsoft Hyper-V 2012 R2<br /> ! RHEV 3.5<br /> ! Citrix XenServer 6.5<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|1. Virtualization platform<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.1. Overview<br /> |-<br /> |'''HW virtualization support (Hypervisor)'''<br /> |Full emulation of underneath hardware level: full isolation guest environment, no dependencies from host OS, overhead for hypervisor layer.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''OS-level virtualization (Containers)'''<br /> |Sharing the same instance of host OS: high density, high performance, high dependencies from host OS.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Hypervisor technology'''<br /> |Technology that enables to run Virtual Machines.<br /> |{{No}}<br /> |Parallels Desktop Monitor<br /> |KVM<br /> |KVM<br /> |None<br /> |KVM<br /> |Hyper-V<br /> |KVM<br /> |Xen<br /> |-<br /> |'''Windows guest OS additional support'''<br /> |WHQL-signed drivers, SVVP certification<br /> |N/A<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Containers technology'''<br /> |Technology that enables to run Containers.<br /> |Virtuozzo Containers<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Linux containers<br /> |LXC (moved from OpenVZ since 4.0)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.2. Memory<br /> |-<br /> |'''Memory Overcommit'''<br /> |Ability to present more memory to virtual machines than physically available <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, with new VCMMD memory management<br /> |{{Yes}}, with new VCMMD memory management and different policies<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Page sharing'''<br /> |Memory (RAM) savings through sharing identical memory pages across virtual machines<br /> |{{Yes}}<br /> |{{Yes}}, only for CTs<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> |'''Online Memory Management for VM'''<br /> |Ability to change amount of RAM for CT and VM without reboot<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |N/A<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|2. Management<br /> |-<br /> !colspan=&quot;11&quot;|2.1. General<br /> |-<br /> |'''Unified management tool for CTs and VMs'''<br /> |Single tool for managing both containers and virtual machines (if applicable)<br /> |N/A<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''OpenStack integration'''<br /> |Integration with OpenStack components ([http://docs.openstack.org/developer/nova/support-matrix.html see details])<br /> |{{Yes}}, only Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated GUI'''<br /> |Centralized multi-server management<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}, Parallels Virtual Automation (PVA)<br /> |{{No}}<br /> |{{Yes}}, [https://virtuozzo.com/support/pva/Virtual Automator]<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}<br /> |{{Yes}}, System Center Virtual Machine Manager<br /> |{{Yes}}, RHEV Manager<br /> |{{Yes}}, XenCenter<br /> |-<br /> !colspan=&quot;11&quot;|2.2. Upgrade &amp; Backup<br /> |-<br /> |'''Live VE snapshot'''<br /> |Ability to take a snapshot of a virtual environment while the guest OS is running (e.g. for roll-back or backup purposes)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated Backup'''<br /> |Are backup plugins/tools provided to backup virtual environments (over and above the ability to perform classic backup using agents in the guests)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Backup Integration API'''<br /> |Integration with 3rd party backup applications for backup of the virtual environment.<br /> |{{No}} (only through snapshots)<br /> |{{Yes}}<br /> |{{No}} (only through snapshots, new version is not finished yet)<br /> |{{No}} (only through snapshots, new version is not finished yet)<br /> |{{No}} (only through snapshots)<br /> |{{Yes}} (vzdump)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot;|2.3. Others<br /> |-<br /> |'''VEs Templates (VM, CT)'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |{{Yes}} (CT only)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}} <br /> |{{Yes}} (OpenVZ templates)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''P2V migration'''<br /> |Integrated or added P2V (or V2V) capability in order to convert physical systems to virtual environment.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}, 3rd party tools<br /> |{{No}}<br /> |{{No}}, 3rd party tools<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|3. VE Mobility and HA<br /> |-<br /> !colspan=&quot;11&quot;|3.1. VE Mobility<br /> |-<br /> |'''Live Migration'''<br /> |Ability to migrate virtual machines between hosts without perceived downtime<br /> |{{Yes}}, but with no zero downtime<br /> |{{Yes}}, Kernel-Level Migration<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|3.2. HA / DR<br /> |-<br /> |'''Integrated HA'''<br /> |Recover virtual environment in case of host failures through restart on alternative hosts (downtime = restart time)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|4. Network and Storage<br /> |-<br /> !colspan=&quot;11&quot;|4.1. Storage<br /> |-<br /> |'''Supported Storage'''<br /> |Supported types of Storage (DAS, NAS or SAN)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS, NAS (NFS, ZFS), SAN (iSCSI), Ceph <br /> |DAS, NAS (SMB), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |-<br /> |'''Virtual Disk Format'''<br /> |Supported format(s) of the virtual disks for the virtual machines<br /> |CT - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |Any<br /> |Qcow2, vmdk, raw<br /> |vhdx, vhd, pass-though (raw)<br /> |Qcow2, raw disk<br /> |vhd, raw disk<br /> |-<br /> |'''Thin Disk Provisioning'''<br /> |Ability to over-commit overall disk space by dynamically growing the size of virtual disks based on actual usage rather than pre-allocating full size.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, depends on disk format (dm-thin)<br /> |{{Yes}}, depends on underlying storage driver<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Software-defined Storage'''<br /> |Enhanced storage capability e.g. providing a virtual SAN through virtualized 'local' storage <br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS, sheepdog)<br /> |{{Yes}}, Storage Spaces<br /> |{{Yes}}, Red Hat Storage<br /> |{{No}}<br /> |-<br /> |'''Storage QoS'''<br /> |Ability to control Quality of Service for Storage I/O or Throughput for CT/VM<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}, VMs only<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|4.2. Network<br /> |-<br /> |'''Network QoS'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |{{Yes}}, with Open vSwitch <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|5. Others – most of features are relevant only for Virtuozzo editions<br /> |-<br /> |'''Memory deduplication for binary files'''<br /> |Memory and IOPS deduplication management that enables/disables caching for Container directories and files, verifies cache integrity, checks Containers for cache errors, and purges the cache if needed<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{No}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''Completely isolated disk subsystem for CTs'''<br /> |<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, with LVM<br /> |{{Yes}}, LVM, ZFS, or loop devices<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''API\SDK'''<br /> |<br /> |OpenVZ API for Ruby, LibVirt<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |LibLXC, API for Ruby, Python 2, Haskell, Go<br /> |Proxmox VE uses a REST like API (JSON data format)<br /> |Windows SDK<br /> |RHEV-M API: REST API, SDKs<br /> |XenAPI, XenServer SDKs<br /> |-<br /> |'''Image Catalog integration'''<br /> |Integration with 3rd-party image catalog services of popular server applications and development environments that can be installed with one click.<br /> |{{No}}<br /> |{{Yes}} Application Image Catalog [https://virtuozzo.com/introducing-the-virtuozzo-application-catalog/ Virtuozzo Application Catalog]<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}} (Turnkey)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Kernel update without reboot'''<br /> |Integrated ability to upgrade kernel or install security patches without downtime.<br /> |{{No}}, only 3d party tools<br /> |{{Yes}}, Rebootless Kernel Update<br /> |{{No}}<br /> |{{Yes}} [https://readykernel.com/ ReadyKernel Service]<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |N/A<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |-<br /> |'''Power Panel'''<br /> |A tool used for managing particular virtual machines and containers by their end users.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Secure for using in public networks'''<br /> |<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|6. Commercial<br /> |-<br /> |'''Open Source'''<br /> |<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}} (but there is Open Source edition(oVirt))<br /> |{{No}} (but there is Open Source edition)<br /> |-<br /> |'''License\Subscription'''<br /> |<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, Enterprise Edition<br /> |-<br /> |'''Support'''<br /> |<br /> |Both community and commercial support<br /> |Commercial support<br /> |Community support<br /> |Commercial Support<br /> |Yes, Canonical Ltd.<br /> |Both community and commercial support<br /> |Commercial support<br /> |Commercial support<br /> |Both community and commercial support<br /> |-<br /> |'''EOL policy'''<br /> |<br /> |[[Releases|5 years of support]]<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |TBD<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |<br /> |<br /> |[https://support.microsoft.com/en-us/lifecycle/search/default.aspx?alpha=hyper-v 11 years of support]]<br /> |<br /> |<br /> |-<br /> |}</div>

Vporokhov https://wiki.openvz.org/index.php?title=Comparison&diff=23028 2018-09-19T13:05:21Z

<p>Vporokhov: </p> <hr /> <div>{{Note|This comparison doesn't include Docker, because Docker is not a virtualization solution. It automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of operating-system-level virtualization.&lt;ref&gt;[https://en.wikipedia.org/wiki/Docker_(software) Wikipedia article about Docker]&lt;/ref&gt;}}<br /> <br /> <br /> == Disclaimer ==<br /> <br /> The information regarding Virtuozzo 7 is provided by [http://www.virtuozzo.com Virtuozzo]. Here is the Virtuozzo's statement regarding this information:<br /> <br /> :#The information contained herein is intended to outline general product direction and should not be relied upon in making purchasing decisions.<br /> :#The content is for informational purposes only and may not be incorporated into any contract.<br /> :#The information presented is not a commitment, promise, or legal obligation to deliver any material, code or functionality.<br /> :#Any references to the development, release, and timing of any features or functionality described for these products remains at Virtuozzo’s sole discretion.<br /> :#Product capabilities, timeframes and features are subject to change and should not be viewed as Virtuozzo commitments.<br /> <br /> The information regarding all other solutions are taken by authors from public sources only. This information can be changed by any OpenVZ Wiki user without any notice and author's review or approval.<br /> <br /> <br /> == Feature comparison of different virtualization solutions ==<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> ! Feature<br /> ! Description<br /> ! OpenVZ<br /> ! Virtuozzo&amp;nbsp;6 (PCS 6)<br /> ! OpenVZ&amp;nbsp;7<br /> ! [https://virtuozzo.com/products/virtuozzo-containers/ Virtuozzo&amp;nbsp;7]<br /> ! LXC<br /> ! Proxmox VE<br /> ! Microsoft Hyper-V 2012 R2<br /> ! RHEV 3.5<br /> ! Citrix XenServer 6.5<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|1. Virtualization platform<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.1. Overview<br /> |-<br /> |'''HW virtualization support (Hypervisor)'''<br /> |Full emulation of underneath hardware level: full isolation guest environment, no dependencies from host OS, overhead for hypervisor layer.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''OS-level virtualization (Containers)'''<br /> |Sharing the same instance of host OS: high density, high performance, high dependencies from host OS.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Hypervisor technology'''<br /> |Technology that enables to run Virtual Machines.<br /> |{{No}}<br /> |Parallels Desktop Monitor<br /> |KVM<br /> |KVM<br /> |None<br /> |KVM<br /> |Hyper-V<br /> |KVM<br /> |Xen<br /> |-<br /> |'''Windows guest OS additional support'''<br /> |WHQL-signed drivers, SVVP certification<br /> |N/A<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Containers technology'''<br /> |Technology that enables to run Containers.<br /> |Virtuozzo Containers<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Linux containers<br /> |LXC (moved from OpenVZ since 4.0)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.2. Memory<br /> |-<br /> |'''Memory Overcommit'''<br /> |Ability to present more memory to virtual machines than physically available <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, with new VCMMD memory management<br /> |{{Yes}}, with new VCMMD memory management and different policies<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Page sharing'''<br /> |Memory (RAM) savings through sharing identical memory pages across virtual machines<br /> |{{Yes}}<br /> |{{Yes}}, only for CTs<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> |'''Online Memory Management for VM'''<br /> |Ability to change amount of RAM for CT and VM without reboot<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |N/A<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|2. Management<br /> |-<br /> !colspan=&quot;11&quot;|2.1. General<br /> |-<br /> |'''Unified management tool for CTs and VMs'''<br /> |Single tool for managing both containers and virtual machines (if applicable)<br /> |N/A<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''OpenStack integration'''<br /> |Integration with OpenStack components ([http://docs.openstack.org/developer/nova/support-matrix.html see details])<br /> |{{Yes}}, only Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated GUI'''<br /> |Centralized multi-server management<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}, Parallels Virtual Automation (PVA)<br /> |{{No}}<br /> |{{Yes}}, [https://virtuozzo.com/support/pva/Virtual Automator]<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}<br /> |{{Yes}}, System Center Virtual Machine Manager<br /> |{{Yes}}, RHEV Manager<br /> |{{Yes}}, XenCenter<br /> |-<br /> !colspan=&quot;11&quot;|2.2. Upgrade &amp; Backup<br /> |-<br /> |'''Live VE snapshot'''<br /> |Ability to take a snapshot of a virtual environment while the guest OS is running (e.g. for roll-back or backup purposes)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated Backup'''<br /> |Are backup plugins/tools provided to backup virtual environments (over and above the ability to perform classic backup using agents in the guests)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Backup Integration API'''<br /> |Integration with 3rd party backup applications for backup of the virtual environment.<br /> |{{No}} (only through snapshots)<br /> |{{Yes}}<br /> |{{No}} (only through snapshots, new version is not finished yet)<br /> |{{No}} (only through snapshots, new version is not finished yet)<br /> |{{No}} (only through snapshots)<br /> |{{Yes}} (vzdump)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot;|2.3. Others<br /> |-<br /> |'''VEs Templates (VM, CT)'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |{{Yes}} (CT only)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}} <br /> |{{Yes}} (OpenVZ templates)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''P2V migration'''<br /> |Integrated or added P2V (or V2V) capability in order to convert physical systems to virtual environment.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}, 3rd party tools<br /> |{{No}}<br /> |{{No}}, 3rd party tools<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|3. VE Mobility and HA<br /> |-<br /> !colspan=&quot;11&quot;|3.1. VE Mobility<br /> |-<br /> |'''Live Migration'''<br /> |Ability to migrate virtual machines between hosts without perceived downtime<br /> |{{Yes}}, but with no zero downtime<br /> |{{Yes}}, Kernel-Level Migration<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|3.2. HA / DR<br /> |-<br /> |'''Integrated HA'''<br /> |Recover virtual environment in case of host failures through restart on alternative hosts (downtime = restart time)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|4. Network and Storage<br /> |-<br /> !colspan=&quot;11&quot;|4.1. Storage<br /> |-<br /> |'''Supported Storage'''<br /> |Supported types of Storage (DAS, NAS or SAN)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS, NAS (NFS, ZFS), SAN (iSCSI), Ceph <br /> |DAS, NAS (SMB), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |-<br /> |'''Virtual Disk Format'''<br /> |Supported format(s) of the virtual disks for the virtual machines<br /> |CT - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |Any<br /> |Qcow2, vmdk, raw<br /> |vhdx, vhd, pass-though (raw)<br /> |Qcow2, raw disk<br /> |vhd, raw disk<br /> |-<br /> |'''Thin Disk Provisioning'''<br /> |Ability to over-commit overall disk space by dynamically growing the size of virtual disks based on actual usage rather than pre-allocating full size.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, depends on disk format (dm-thin)<br /> |{{Yes}}, depends on underlying storage driver<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Software-defined Storage'''<br /> |Enhanced storage capability e.g. providing a virtual SAN through virtualized 'local' storage <br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS, sheepdog)<br /> |{{Yes}}, Storage Spaces<br /> |{{Yes}}, Red Hat Storage<br /> |{{No}}<br /> |-<br /> |'''Storage QoS'''<br /> |Ability to control Quality of Service for Storage I/O or Throughput for CT/VM<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}, VMs only<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|4.2. Network<br /> |-<br /> |'''Network QoS'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |{{Yes}}, with Open vSwitch <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|5. Others – most of features are relevant only for Virtuozzo editions<br /> |-<br /> |'''Memory deduplication for binary files'''<br /> |Memory and IOPS deduplication management that enables/disables caching for Container directories and files, verifies cache integrity, checks Containers for cache errors, and purges the cache if needed<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{No}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''Completely isolated disk subsystem for CTs'''<br /> |<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, with LVM<br /> |{{Yes}}, LVM, ZFS, or loop devices<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''API\SDK'''<br /> |<br /> |OpenVZ API for Ruby, LibVirt<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |LibLXC, API for Ruby, Python 2, Haskell, Go<br /> |Proxmox VE uses a REST like API (JSON data format)<br /> |Windows SDK<br /> |RHEV-M API: REST API, SDKs<br /> |XenAPI, XenServer SDKs<br /> |-<br /> |'''Image Catalog integration'''<br /> |Integration with 3rd-party image catalog services of popular server applications and development environments that can be installed with one click.<br /> |{{No}}<br /> |{{Yes}} Application Image Catalog [https://virtuozzo.com/introducing-the-virtuozzo-application-catalog/ Virtuozzo Application Catalog]<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}} (Turnkey)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Kernel update without reboot'''<br /> |Integrated ability to upgrade kernel or install security patches without downtime.<br /> |{{No}}, only 3d party tools<br /> |{{Yes}}, Rebootless Kernel Update<br /> |{{No}}<br /> |{{Yes}} [https://readykernel.com/ ReadyKernel Service]<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |N/A<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |-<br /> |'''Power Panel'''<br /> |A tool used for managing particular virtual machines and containers by their end users.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Secure for using in public networks'''<br /> |<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|6. Commercial<br /> |-<br /> |'''Open Source'''<br /> |<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}} (but there is Open Source edition(oVirt))<br /> |{{No}} (but there is Open Source edition)<br /> |-<br /> |'''License\Subscription'''<br /> |<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, Enterprise Edition<br /> |-<br /> |'''Support'''<br /> |<br /> |Both community and commercial support<br /> |Commercial support<br /> |Community support<br /> |Commercial Support<br /> |Yes, Canonical Ltd.<br /> |Both community and commercial support<br /> |Commercial support<br /> |Commercial support<br /> |Both community and commercial support<br /> |-<br /> |'''EOL policy'''<br /> |<br /> |[[Releases|5 years of support]]<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |TBD<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |<br /> |<br /> |[https://support.microsoft.com/en-us/lifecycle/search/default.aspx?alpha=hyper-v 11 years of support]]<br /> |<br /> |<br /> |-<br /> |}</div>

Vporokhov https://wiki.openvz.org/index.php?title=Comparison&diff=23027 2018-09-19T13:04:22Z

<p>Vporokhov: </p> <hr /> <div>{{Note|This comparison doesn't include Docker, because Docker is not a virtualization solution. It automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of operating-system-level virtualization.&lt;ref&gt;[https://en.wikipedia.org/wiki/Docker_(software) Wikipedia article about Docker]&lt;/ref&gt;}}<br /> <br /> <br /> == Disclaimer ==<br /> <br /> The information regarding Virtuozzo 7 is provided by [http://www.virtuozzo.com Virtuozzo]. Here is the Virtuozzo's statement regarding this information:<br /> <br /> :#The information contained herein is intended to outline general product direction and should not be relied upon in making purchasing decisions.<br /> :#The content is for informational purposes only and may not be incorporated into any contract.<br /> :#The information presented is not a commitment, promise, or legal obligation to deliver any material, code or functionality.<br /> :#Any references to the development, release, and timing of any features or functionality described for these products remains at Virtuozzo’s sole discretion.<br /> :#Product capabilities, timeframes and features are subject to change and should not be viewed as Virtuozzo commitments.<br /> <br /> The information regarding all other solutions are taken by authors from public sources only. This information can be changed by any OpenVZ Wiki user without any notice and author's review or approval.<br /> <br /> <br /> == Feature comparison of different virtualization solutions ==<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> ! Feature<br /> ! Description<br /> ! OpenVZ<br /> ! Virtuozzo&amp;nbsp;6 (PCS 6)<br /> ! OpenVZ&amp;nbsp;7<br /> ! [https://virtuozzo.com/products/virtuozzo-containers/ Virtuozzo&amp;nbsp;7]<br /> ! LXC<br /> ! Proxmox VE<br /> ! Microsoft Hyper-V 2012 R2<br /> ! RHEV 3.5<br /> ! Citrix XenServer 6.5<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|1. Virtualization platform<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.1. Overview<br /> |-<br /> |'''HW virtualization support (Hypervisor)'''<br /> |Full emulation of underneath hardware level: full isolation guest environment, no dependencies from host OS, overhead for hypervisor layer.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''OS-level virtualization (Containers)'''<br /> |Sharing the same instance of host OS: high density, high performance, high dependencies from host OS.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Hypervisor technology'''<br /> |Technology that enables to run Virtual Machines.<br /> |{{No}}<br /> |Parallels Desktop Monitor<br /> |KVM<br /> |KVM<br /> |None<br /> |KVM<br /> |Hyper-V<br /> |KVM<br /> |Xen<br /> |-<br /> |'''Windows guest OS additional support'''<br /> |WHQL-signed drivers, SVVP certification<br /> |N/A<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Containers technology'''<br /> |Technology that enables to run Containers.<br /> |Virtuozzo Containers<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Linux containers<br /> |LXC (moved from OpenVZ since 4.0)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.2. Memory<br /> |-<br /> |'''Memory Overcommit'''<br /> |Ability to present more memory to virtual machines than physically available <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, with new VCMMD memory management<br /> |{{Yes}}, with new VCMMD memory management and different policies<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Page sharing'''<br /> |Memory (RAM) savings through sharing identical memory pages across virtual machines<br /> |{{Yes}}<br /> |{{Yes}}, only for CTs<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> |'''Online Memory Management for VM'''<br /> |Ability to change amount of RAM for CT and VM without reboot<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |N/A<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|2. Management<br /> |-<br /> !colspan=&quot;11&quot;|2.1. General<br /> |-<br /> |'''Unified management tool for CTs and VMs'''<br /> |Single tool for managing both containers and virtual machines (if applicable)<br /> |N/A<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''OpenStack integration'''<br /> |Integration with OpenStack components ([http://docs.openstack.org/developer/nova/support-matrix.html see details])<br /> |{{Yes}}, only Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated GUI'''<br /> |Centralized multi-server management<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}, Parallels Virtual Automation (PVA)<br /> |{{No}}<br /> |{{Yes}}, [https://virtuozzo.com/support/pva/Virtual Automator]<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}<br /> |{{Yes}}, System Center Virtual Machine Manager<br /> |{{Yes}}, RHEV Manager<br /> |{{Yes}}, XenCenter<br /> |-<br /> !colspan=&quot;11&quot;|2.2. Upgrade &amp; Backup<br /> |-<br /> |'''Live VE snapshot'''<br /> |Ability to take a snapshot of a virtual environment while the guest OS is running (e.g. for roll-back or backup purposes)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated Backup'''<br /> |Are backup plugins/tools provided to backup virtual environments (over and above the ability to perform classic backup using agents in the guests)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Backup Integration API'''<br /> |Integration with 3rd party backup applications for backup of the virtual environment.<br /> |{{No}} (only through snapshots)<br /> |{{Yes}}<br /> |{{No}} (only through snapshots, new version is not finished yet)<br /> |{{No}} (only through snapshots, new version is not finished yet)<br /> |{{No}} (only through snapshots)<br /> |{{Yes}} (vzdump)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot;|2.3. Others<br /> |-<br /> |'''VEs Templates (VM, CT)'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |{{Yes}} (CT only)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}} <br /> |{{Yes}} (OpenVZ templates)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''P2V migration'''<br /> |Integrated or added P2V (or V2V) capability in order to convert physical systems to virtual environment.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}, 3rd party tools<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|3. VE Mobility and HA<br /> |-<br /> !colspan=&quot;11&quot;|3.1. VE Mobility<br /> |-<br /> |'''Live Migration'''<br /> |Ability to migrate virtual machines between hosts without perceived downtime<br /> |{{Yes}}, but with no zero downtime<br /> |{{Yes}}, Kernel-Level Migration<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|3.2. HA / DR<br /> |-<br /> |'''Integrated HA'''<br /> |Recover virtual environment in case of host failures through restart on alternative hosts (downtime = restart time)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|4. Network and Storage<br /> |-<br /> !colspan=&quot;11&quot;|4.1. Storage<br /> |-<br /> |'''Supported Storage'''<br /> |Supported types of Storage (DAS, NAS or SAN)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS, NAS (NFS, ZFS), SAN (iSCSI), Ceph <br /> |DAS, NAS (SMB), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |-<br /> |'''Virtual Disk Format'''<br /> |Supported format(s) of the virtual disks for the virtual machines<br /> |CT - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |Any<br /> |Qcow2, vmdk, raw<br /> |vhdx, vhd, pass-though (raw)<br /> |Qcow2, raw disk<br /> |vhd, raw disk<br /> |-<br /> |'''Thin Disk Provisioning'''<br /> |Ability to over-commit overall disk space by dynamically growing the size of virtual disks based on actual usage rather than pre-allocating full size.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, depends on disk format (dm-thin)<br /> |{{Yes}}, depends on underlying storage driver<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Software-defined Storage'''<br /> |Enhanced storage capability e.g. providing a virtual SAN through virtualized 'local' storage <br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS, sheepdog)<br /> |{{Yes}}, Storage Spaces<br /> |{{Yes}}, Red Hat Storage<br /> |{{No}}<br /> |-<br /> |'''Storage QoS'''<br /> |Ability to control Quality of Service for Storage I/O or Throughput for CT/VM<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}, VMs only<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|4.2. Network<br /> |-<br /> |'''Network QoS'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |{{Yes}}, with Open vSwitch <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|5. Others – most of features are relevant only for Virtuozzo editions<br /> |-<br /> |'''Memory deduplication for binary files'''<br /> |Memory and IOPS deduplication management that enables/disables caching for Container directories and files, verifies cache integrity, checks Containers for cache errors, and purges the cache if needed<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{No}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''Completely isolated disk subsystem for CTs'''<br /> |<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, with LVM<br /> |{{Yes}}, LVM, ZFS, or loop devices<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''API\SDK'''<br /> |<br /> |OpenVZ API for Ruby, LibVirt<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |LibLXC, API for Ruby, Python 2, Haskell, Go<br /> |Proxmox VE uses a REST like API (JSON data format)<br /> |Windows SDK<br /> |RHEV-M API: REST API, SDKs<br /> |XenAPI, XenServer SDKs<br /> |-<br /> |'''Image Catalog integration'''<br /> |Integration with 3rd-party image catalog services of popular server applications and development environments that can be installed with one click.<br /> |{{No}}<br /> |{{Yes}} Application Image Catalog [https://virtuozzo.com/introducing-the-virtuozzo-application-catalog/ Virtuozzo Application Catalog]<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}} (Turnkey)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Kernel update without reboot'''<br /> |Integrated ability to upgrade kernel or install security patches without downtime.<br /> |{{No}}, only 3d party tools<br /> |{{Yes}}, Rebootless Kernel Update<br /> |{{No}}<br /> |{{Yes}} [https://readykernel.com/ ReadyKernel Service]<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |N/A<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |-<br /> |'''Power Panel'''<br /> |A tool used for managing particular virtual machines and containers by their end users.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Secure for using in public networks'''<br /> |<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|6. Commercial<br /> |-<br /> |'''Open Source'''<br /> |<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}} (but there is Open Source edition(oVirt))<br /> |{{No}} (but there is Open Source edition)<br /> |-<br /> |'''License\Subscription'''<br /> |<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, Enterprise Edition<br /> |-<br /> |'''Support'''<br /> |<br /> |Both community and commercial support<br /> |Commercial support<br /> |Community support<br /> |Commercial Support<br /> |Yes, Canonical Ltd.<br /> |Both community and commercial support<br /> |Commercial support<br /> |Commercial support<br /> |Both community and commercial support<br /> |-<br /> |'''EOL policy'''<br /> |<br /> |[[Releases|5 years of support]]<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |TBD<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |<br /> |<br /> |[https://support.microsoft.com/en-us/lifecycle/search/default.aspx?alpha=hyper-v 11 years of support]]<br /> |<br /> |<br /> |-<br /> |}</div>

Vporokhov https://wiki.openvz.org/index.php?title=Comparison&diff=23026 2018-09-19T12:59:15Z

<p>Vporokhov: /* Feature comparison of different virtualization solutions */</p> <hr /> <div>{{Note|This comparison doesn't include Docker, because Docker is not a virtualization solution. It automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of operating-system-level virtualization.&lt;ref&gt;[https://en.wikipedia.org/wiki/Docker_(software) Wikipedia article about Docker]&lt;/ref&gt;}}<br /> <br /> <br /> == Disclaimer ==<br /> <br /> The information regarding Virtuozzo 7 is provided by [http://www.virtuozzo.com Virtuozzo]. Here is the Virtuozzo's statement regarding this information:<br /> <br /> :#The information contained herein is intended to outline general product direction and should not be relied upon in making purchasing decisions.<br /> :#The content is for informational purposes only and may not be incorporated into any contract.<br /> :#The information presented is not a commitment, promise, or legal obligation to deliver any material, code or functionality.<br /> :#Any references to the development, release, and timing of any features or functionality described for these products remains at Virtuozzo’s sole discretion.<br /> :#Product capabilities, timeframes and features are subject to change and should not be viewed as Virtuozzo commitments.<br /> <br /> The information regarding all other solutions are taken by authors from public sources only. This information can be changed by any OpenVZ Wiki user without any notice and author's review or approval.<br /> <br /> <br /> == Feature comparison of different virtualization solutions ==<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> ! Feature<br /> ! Description<br /> ! OpenVZ<br /> ! Virtuozzo&amp;nbsp;6 (PCS 6)<br /> ! OpenVZ&amp;nbsp;7<br /> ! [https://virtuozzo.com/products/virtuozzo-containers/ Virtuozzo&amp;nbsp;7]<br /> ! LXC<br /> ! Proxmox VE<br /> ! Microsoft Hyper-V 2012 R2<br /> ! RHEV 3.5<br /> ! Citrix XenServer 6.5<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|1. Virtualization platform<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.1. Overview<br /> |-<br /> |'''HW virtualization support (Hypervisor)'''<br /> |Full emulation of underneath hardware level: full isolation guest environment, no dependencies from host OS, overhead for hypervisor layer.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''OS-level virtualization (Containers)'''<br /> |Sharing the same instance of host OS: high density, high performance, high dependencies from host OS.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Hypervisor technology'''<br /> |Technology that enables to run Virtual Machines.<br /> |{{No}}<br /> |Parallels Desktop Monitor<br /> |KVM<br /> |KVM<br /> |None<br /> |KVM<br /> |Hyper-V<br /> |KVM<br /> |Xen<br /> |-<br /> |'''Windows guest OS additional support'''<br /> |WHQL-signed drivers, SVVP certification<br /> |N/A<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Containers technology'''<br /> |Technology that enables to run Containers.<br /> |Virtuozzo Containers<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Linux containers<br /> |LXC (moved from OpenVZ since 4.0)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.2. Memory<br /> |-<br /> |'''Memory Overcommit'''<br /> |Ability to present more memory to virtual machines than physically available <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, with new VCMMD memory management<br /> |{{Yes}}, with new VCMMD memory management and different policies<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Page sharing'''<br /> |Memory (RAM) savings through sharing identical memory pages across virtual machines<br /> |{{Yes}}<br /> |{{Yes}}, only for CTs<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> |'''Online Memory Management for VM'''<br /> |Ability to change amount of RAM for CT and VM without reboot<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |N/A<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|2. Management<br /> |-<br /> !colspan=&quot;11&quot;|2.1. General<br /> |-<br /> |'''Unified management tool for CTs and VMs'''<br /> |Single tool for managing both containers and virtual machines (if applicable)<br /> |N/A<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''OpenStack integration'''<br /> |Integration with OpenStack components ([http://docs.openstack.org/developer/nova/support-matrix.html see details])<br /> |{{Yes}}, only Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated GUI'''<br /> |Centralized multi-server management<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}, Parallels Virtual Automation (PVA)<br /> |{{No}}<br /> |{{Yes}}, [https://virtuozzo.com/support/pva/Virtual Automator]<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}<br /> |{{Yes}}, System Center Virtual Machine Manager<br /> |{{Yes}}, RHEV Manager<br /> |{{Yes}}, XenCenter<br /> |-<br /> !colspan=&quot;11&quot;|2.2. Upgrade &amp; Backup<br /> |-<br /> |'''Live VE snapshot'''<br /> |Ability to take a snapshot of a virtual environment while the guest OS is running (e.g. for roll-back or backup purposes)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated Backup'''<br /> |Are backup plugins/tools provided to backup virtual environments (over and above the ability to perform classic backup using agents in the guests)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Backup Integration API'''<br /> |Integration with 3rd party backup applications for backup of the virtual environment.<br /> |{{No}} (only through snapshots)<br /> |{{Yes}}<br /> |{{No}} (only through snapshots, new version is not finished yet)<br /> |{{No}} (only through snapshots, new version is not finished yet)<br /> |{{No}} (only through snapshots)<br /> |{{Yes}} (vzdump)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot;|2.3. Others<br /> |-<br /> |'''VEs Templates (VM, CT)'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |{{Yes}} (CT only)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}} <br /> |{{Yes}} (OpenVZ templates)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''P2V migration'''<br /> |Integrated or added P2V (or V2V) capability in order to convert physical systems to virtual environment.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}, 3rd party tools<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|3. VE Mobility and HA<br /> |-<br /> !colspan=&quot;11&quot;|3.1. VE Mobility<br /> |-<br /> |'''Live Migration'''<br /> |Ability to migrate virtual machines between hosts without perceived downtime<br /> |{{Yes}}, but with no zero downtime<br /> |{{Yes}}, Kernel-Level Migration<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|3.2. HA / DR<br /> |-<br /> |'''Integrated HA'''<br /> |Recover virtual environment in case of host failures through restart on alternative hosts (downtime = restart time)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|4. Network and Storage<br /> |-<br /> !colspan=&quot;11&quot;|4.1. Storage<br /> |-<br /> |'''Supported Storage'''<br /> |Supported types of Storage (DAS, NAS or SAN)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS, NAS (NFS, ZFS), SAN (iSCSI), Ceph <br /> |DAS, NAS (SMB), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |-<br /> |'''Virtual Disk Format'''<br /> |Supported format(s) of the virtual disks for the virtual machines<br /> |CT - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |Any<br /> |Qcow2, vmdk, raw<br /> |vhdx, vhd, pass-though (raw)<br /> |Qcow2, raw disk<br /> |vhd, raw disk<br /> |-<br /> |'''Thin Disk Provisioning'''<br /> |Ability to over-commit overall disk space by dynamically growing the size of virtual disks based on actual usage rather than pre-allocating full size.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, depends on disk format (dm-thin)<br /> |{{Yes}}, depends on underlying storage driver<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Software-defined Storage'''<br /> |Enhanced storage capability e.g. providing a virtual SAN through virtualized 'local' storage <br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS, sheepdog)<br /> |{{Yes}}, Storage Spaces<br /> |{{Yes}}, Red Hat Storage<br /> |{{No}}<br /> |-<br /> |'''Storage QoS'''<br /> |Ability to control Quality of Service for Storage I/O or Throughput for CT/VM<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}, VMs only<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|4.2. Network<br /> |-<br /> |'''Network QoS'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |{{Yes}}, with Open vSwitch <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|5. Others – most of features are relevant only for Virtuozzo editions<br /> |-<br /> |'''Memory deduplication for binary files'''<br /> |Memory and IOPS deduplication management that enables/disables caching for Container directories and files, verifies cache integrity, checks Containers for cache errors, and purges the cache if needed<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{No}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''Completely isolated disk subsystem for CTs'''<br /> |<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, with LVM<br /> |{{Yes}}, LVM, ZFS, or loop devices<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''API\SDK'''<br /> |<br /> |OpenVZ API for Ruby, LibVirt<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |LibLXC, API for Ruby, Python 2, Haskell, Go<br /> |Proxmox VE uses a REST like API (JSON data format)<br /> |Windows SDK<br /> |RHEV-M API: REST API, SDKs<br /> |XenAPI, XenServer SDKs<br /> |-<br /> |'''Image Catalog integration'''<br /> |Integration with 3rd-party image catalog services of popular server applications and development environments that can be installed with one click.<br /> |{{No}}<br /> |{{Yes}} Application Image Catalog [https://virtuozzo.com/introducing-the-virtuozzo-application-catalog/ Virtuozzo Application Catalog]<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}} (Turnkey)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Kernel update without reboot'''<br /> |Integrated ability to upgrade kernel or install security patches without downtime.<br /> |{{No}}, only 3d party tools<br /> |{{Yes}}, Rebootless Kernel Update<br /> |{{No}}<br /> |{{Yes}} [https://readykernel.com/ ReadyKernel Service]<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |N/A<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |-<br /> |'''Power Panel'''<br /> |A tool used for managing particular virtual machines and containers by their end users.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Secure for using in public networks'''<br /> |<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|6. Commercial<br /> |-<br /> |'''Open Source'''<br /> |<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}} (but there is Open Source edition(oVirt))<br /> |{{No}} (but there is Open Source edition)<br /> |-<br /> |'''License\Subscription'''<br /> |<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, Enterprise Edition<br /> |-<br /> |'''Support'''<br /> |<br /> |Both community and commercial support<br /> |Commercial support<br /> |Community support<br /> |Commercial Support<br /> |Yes, Canonical Ltd.<br /> |Both community and commercial support<br /> |Commercial support<br /> |Commercial support<br /> |Both community and commercial support<br /> |-<br /> |'''EOL policy'''<br /> |<br /> |[[Releases|5 years of support]]<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |TBD<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |<br /> |<br /> |[https://support.microsoft.com/en-us/lifecycle/search/default.aspx?alpha=hyper-v 11 years of support]]<br /> |<br /> |<br /> |-<br /> |}</div>

Vporokhov https://wiki.openvz.org/index.php?title=Comparison&diff=23025 2018-09-19T12:57:14Z

<p>Vporokhov: /* Feature comparison of different virtualization solutions */</p> <hr /> <div>{{Note|This comparison doesn't include Docker, because Docker is not a virtualization solution. It automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of operating-system-level virtualization.&lt;ref&gt;[https://en.wikipedia.org/wiki/Docker_(software) Wikipedia article about Docker]&lt;/ref&gt;}}<br /> <br /> <br /> == Disclaimer ==<br /> <br /> The information regarding Virtuozzo 7 is provided by [http://www.virtuozzo.com Virtuozzo]. Here is the Virtuozzo's statement regarding this information:<br /> <br /> :#The information contained herein is intended to outline general product direction and should not be relied upon in making purchasing decisions.<br /> :#The content is for informational purposes only and may not be incorporated into any contract.<br /> :#The information presented is not a commitment, promise, or legal obligation to deliver any material, code or functionality.<br /> :#Any references to the development, release, and timing of any features or functionality described for these products remains at Virtuozzo’s sole discretion.<br /> :#Product capabilities, timeframes and features are subject to change and should not be viewed as Virtuozzo commitments.<br /> <br /> The information regarding all other solutions are taken by authors from public sources only. This information can be changed by any OpenVZ Wiki user without any notice and author's review or approval.<br /> <br /> <br /> == Feature comparison of different virtualization solutions ==<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> ! Feature<br /> ! Description<br /> ! OpenVZ<br /> ! Virtuozzo&amp;nbsp;6 (PCS 6)<br /> ! OpenVZ&amp;nbsp;7<br /> ! [https://virtuozzo.com/products/virtuozzo-containers/ Virtuozzo&amp;nbsp;7]<br /> ! LXC<br /> ! Proxmox VE<br /> ! Microsoft Hyper-V 2012 R2<br /> ! RHEV 3.5<br /> ! Citrix XenServer 6.5<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|1. Virtualization platform<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.1. Overview<br /> |-<br /> |'''HW virtualization support (Hypervisor)'''<br /> |Full emulation of underneath hardware level: full isolation guest environment, no dependencies from host OS, overhead for hypervisor layer.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''OS-level virtualization (Containers)'''<br /> |Sharing the same instance of host OS: high density, high performance, high dependencies from host OS.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Hypervisor technology'''<br /> |Technology that enables to run Virtual Machines.<br /> |{{No}}<br /> |Parallels Desktop Monitor<br /> |KVM<br /> |KVM<br /> |None<br /> |KVM<br /> |Hyper-V<br /> |KVM<br /> |Xen<br /> |-<br /> |'''Windows guest OS additional support'''<br /> |WHQL-signed drivers, SVVP certification<br /> |N/A<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Containers technology'''<br /> |Technology that enables to run Containers.<br /> |Virtuozzo Containers<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Linux containers<br /> |LXC (moved from OpenVZ since 4.0)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.2. Memory<br /> |-<br /> |'''Memory Overcommit'''<br /> |Ability to present more memory to virtual machines than physically available <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, with new VCMMD memory management<br /> |{{Yes}}, with new VCMMD memory management and different policies<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Page sharing'''<br /> |Memory (RAM) savings through sharing identical memory pages across virtual machines<br /> |{{Yes}}<br /> |{{Yes}}, only for CTs<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> |'''Online Memory Management for VM'''<br /> |Ability to change amount of RAM for CT and VM without reboot<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |N/A<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|2. Management<br /> |-<br /> !colspan=&quot;11&quot;|2.1. General<br /> |-<br /> |'''Unified management tool for CTs and VMs'''<br /> |Single tool for managing both containers and virtual machines (if applicable)<br /> |N/A<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''OpenStack integration'''<br /> |Integration with OpenStack components ([http://docs.openstack.org/developer/nova/support-matrix.html see details])<br /> |{{Yes}}, only Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated GUI'''<br /> |Centralized multi-server management<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}, Parallels Virtual Automation (PVA)<br /> |{{No}}<br /> |{{Yes}}, [https://virtuozzo.com/support/pva/Virtual Automator]<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}<br /> |{{Yes}}, System Center Virtual Machine Manager<br /> |{{Yes}}, RHEV Manager<br /> |{{Yes}}, XenCenter<br /> |-<br /> !colspan=&quot;11&quot;|2.2. Upgrade &amp; Backup<br /> |-<br /> |'''Live VE snapshot'''<br /> |Ability to take a snapshot of a virtual environment while the guest OS is running (e.g. for roll-back or backup purposes)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated Backup'''<br /> |Are backup plugins/tools provided to backup virtual environments (over and above the ability to perform classic backup using agents in the guests)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Backup Integration API'''<br /> |Integration with 3rd party backup applications for backup of the virtual environment.<br /> |{{No}} (only through snapshots)<br /> |{{Yes}}<br /> |{{No}} (only through snapshots, new version is not finished yet)<br /> |{{No}} (only through snapshots, new version is not finished yet)<br /> |{{No}} (only through snapshots)<br /> |{{Yes}} (vzdump)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot;|2.3. Others<br /> |-<br /> |'''VEs Templates (VM, CT)'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |{{Yes}} (CT only)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}} <br /> |{{Yes}} (OpenVZ templates)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''P2V migration'''<br /> |Integrated or added P2V (or V2V) capability in order to convert physical systems to virtual environment.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}, 3rd party tools<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|3. VE Mobility and HA<br /> |-<br /> !colspan=&quot;11&quot;|3.1. VE Mobility<br /> |-<br /> |'''Live Migration'''<br /> |Ability to migrate virtual machines between hosts without perceived downtime<br /> |{{Yes}}, but with no zero downtime<br /> |{{Yes}}, Kernel-Level Migration<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|3.2. HA / DR<br /> |-<br /> |'''Integrated HA'''<br /> |Recover virtual environment in case of host failures through restart on alternative hosts (downtime = restart time)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|4. Network and Storage<br /> |-<br /> !colspan=&quot;11&quot;|4.1. Storage<br /> |-<br /> |'''Supported Storage'''<br /> |Supported types of Storage (DAS, NAS or SAN)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS, NAS (NFS, ZFS), SAN (iSCSI), Ceph <br /> |DAS, NAS (SMB), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |-<br /> |'''Virtual Disk Format'''<br /> |Supported format(s) of the virtual disks for the virtual machines<br /> |CT - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |Any<br /> |Qcow2, vmdk, raw<br /> |vhdx, vhd, pass-though (raw)<br /> |Qcow2, raw disk<br /> |vhd, raw disk<br /> |-<br /> |'''Thin Disk Provisioning'''<br /> |Ability to over-commit overall disk space by dynamically growing the size of virtual disks based on actual usage rather than pre-allocating full size.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, depends on disk format (dm-thin)<br /> |{{Yes}}, depends on underlying storage driver<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Software-defined Storage'''<br /> |Enhanced storage capability e.g. providing a virtual SAN through virtualized 'local' storage <br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS, sheepdog)<br /> |{{Yes}}, Storage Spaces<br /> |{{Yes}}, Red Hat Storage<br /> |{{No}}<br /> |-<br /> |'''Storage QoS'''<br /> |Ability to control Quality of Service for Storage I/O or Throughput for CT/VM<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}, VMs only<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|4.2. Network<br /> |-<br /> |'''Network QoS'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |{{Yes}}, with Open vSwitch <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|5. Others – most of features are relevant only for Virtuozzo editions<br /> |-<br /> |'''Memory deduplication for binary files'''<br /> |Memory and IOPS deduplication management that enables/disables caching for Container directories and files, verifies cache integrity, checks Containers for cache errors, and purges the cache if needed<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{No}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''Completely isolated disk subsystem for CTs'''<br /> |<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, with LVM<br /> |{{Yes}}, LVM, ZFS, or loop devices<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''API\SDK'''<br /> |<br /> |OpenVZ API for Ruby, LibVirt<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |LibLXC, API for Ruby, Python 2, Haskell, Go<br /> |Proxmox VE uses a REST like API (JSON data format)<br /> |Windows SDK<br /> |RHEV-M API: REST API, SDKs<br /> |XenAPI, XenServer SDKs<br /> |-<br /> |'''Image Catalog integration'''<br /> |Integration with 3rd-party image catalog services of popular server applications and development environments that can be installed with one click.<br /> |{{No}}<br /> |{{Yes}} Application Image Catalog [https://virtuozzo.com/introducing-the-virtuozzo-application-catalog/ Virtuozzo Application Catalog]<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}} (Turnkey)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Kernel update without reboot'''<br /> |Integrated ability to upgrade kernel or install security patches without downtime.<br /> |{{No}}, only 3d party tools<br /> |{{Yes}}, Rebootless Kernel Update<br /> |{{No}}<br /> |{{Yes}} [https://readykernel.com/ ReadyKernel Service]<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |N/A<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |-<br /> |'''Power Panel'''<br /> |A tool used for managing particular virtual machines and containers by their end users.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Secure for using in public networks'''<br /> |<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|6. Commercial<br /> |-<br /> |'''Open Source'''<br /> |<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}} (but there is Open Source edition(oVirt))<br /> |{{No}} (but there is Open Source edition)<br /> |-<br /> |'''License\Subscription'''<br /> |<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, Enterprise Edition<br /> |-<br /> |'''Support'''<br /> |<br /> |Both community and commercial support<br /> |Commercial support<br /> |Community support<br /> |Commercial Support<br /> |Yes, Canonical Ltd.<br /> |Both community and commercial support<br /> |Commercial support<br /> |Commercial support<br /> |Both community and commercial support<br /> |-<br /> |'''EOL policy'''<br /> |<br /> |[[Releases|5 years of support]]<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |TBD<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |<br /> |<br /> |[https://support.microsoft.com/en-us/lifecycle/search/default.aspx?alpha=hyper-v 11 years of support]]<br /> |<br /> |<br /> |-<br /> |}</div>

Vporokhov https://wiki.openvz.org/index.php?title=Comparison&diff=22658 2017-06-16T12:05:25Z

<p>Vporokhov: /* Feature comparison of different virtualization solutions */</p> <hr /> <div>{{Note|This comparison doesn't include Docker, because Docker is not a virtualization solution. It automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of operating-system-level virtualization.&lt;ref&gt;[https://en.wikipedia.org/wiki/Docker_(software) Wikipedia article about Docker]&lt;/ref&gt;}}<br /> <br /> <br /> == Disclaimer ==<br /> <br /> The information regarding Virtuozzo 7 is provided by [http://www.virtuozzo.com Virtuozzo]. Here is the Virtuozzo's statement regarding this information:<br /> <br /> :#The information contained herein is intended to outline general product direction and should not be relied upon in making purchasing decisions.<br /> :#The content is for informational purposes only and may not be incorporated into any contract.<br /> :#The information presented is not a commitment, promise, or legal obligation to deliver any material, code or functionality.<br /> :#Any references to the development, release, and timing of any features or functionality described for these products remains at Virtuozzo’s sole discretion.<br /> :#Product capabilities, timeframes and features are subject to change and should not be viewed as Virtuozzo commitments.<br /> <br /> The information regarding all other solutions are taken by authors from public sources only. This information can be changed by any OpenVZ Wiki user without any notice and author's review or approval.<br /> <br /> <br /> == Feature comparison of different virtualization solutions ==<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> ! Feature<br /> ! Description<br /> ! OpenVZ<br /> ! Virtuozzo&amp;nbsp;6 (PCS 6)<br /> ! OpenVZ&amp;nbsp;7<br /> ! [https://virtuozzo.com/products/virtuozzo-containers/ Virtuozzo&amp;nbsp;7]<br /> ! LXC<br /> ! Proxmox VE<br /> ! Microsoft Hyper-V 2012 R2<br /> ! RHEV 3.5<br /> ! Citrix XenServer 6.5<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|1. Virtualization platform<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.1. Overview<br /> |-<br /> |'''HW virtualization support (Hypervisor)'''<br /> |Full emulation of underneath hardware level: full isolation guest environment, no dependencies from host OS, overhead for hypervisor layer.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''OS-level virtualization (Containers)'''<br /> |Sharing the same instance of host OS: high density, high performance, high dependencies from host OS.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Hypervisor technology'''<br /> |Technology that enables to run Virtual Machines.<br /> |{{No}}<br /> |Parallels Desktop Monitor<br /> |KVM<br /> |KVM<br /> |None<br /> |KVM<br /> |Hyper-V<br /> |KVM<br /> |Xen<br /> |-<br /> |'''Windows guest OS additional support'''<br /> |WHQL-signed drivers, SVVP certification<br /> |N/A<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Containers technology'''<br /> |Technology that enables to run Containers.<br /> |Virtuozzo Containers<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Linux containers<br /> |LXC (moved from OpenVZ since 4.0)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.2. Memory<br /> |-<br /> |'''Memory Overcommit'''<br /> |Ability to present more memory to virtual machines than physically available <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, with new VCMMD memory management<br /> |{{Yes}}, with new VCMMD memory management and different policies<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Page sharing'''<br /> |Memory (RAM) savings through sharing identical memory pages across virtual machines<br /> |{{Yes}}<br /> |{{Yes}}, only for CTs<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> |'''Online Memory Management for VM'''<br /> |Ability to change amount of RAM for CT and VM without reboot<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |N/A<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|2. Management<br /> |-<br /> !colspan=&quot;11&quot;|2.1. General<br /> |-<br /> |'''Unified management tool for CTs and VMs'''<br /> |Single tool for managing both containers and virtual machines (if applicable)<br /> |N/A<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''OpenStack integration'''<br /> |Integration with OpenStack components ([http://docs.openstack.org/developer/nova/support-matrix.html see details])<br /> |{{Yes}}, only Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated GUI'''<br /> |Centralized multi-server management<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}, Parallels Virtual Automation (PVA)<br /> |{{No}}<br /> |{{Yes}}, [https://virtuozzo.com/support/pva/ Virtual Automator]<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}<br /> |{{Yes}}, System Center Virtual Machine Manager<br /> |{{Yes}}, RHEV Manager<br /> |{{Yes}}, XenCenter<br /> |-<br /> !colspan=&quot;11&quot;|2.2. Upgrade &amp; Backup<br /> |-<br /> |'''Live VE snapshot'''<br /> |Ability to take a snapshot of a virtual environment while the guest OS is running (e.g. for roll-back or backup purposes)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated Backup'''<br /> |Are backup plugins/tools provided to backup virtual environments (over and above the ability to perform classic backup using agents in the guests)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Backup Integration API'''<br /> |Integration with 3rd party backup applications for backup of the virtual environment.<br /> |{{No}} (only through snapshots)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}} (only through snapshots)<br /> |{{Yes}} (vzdump)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot;|2.3. Others<br /> |-<br /> |'''VEs Templates (VM, CT)'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |{{Yes}} (CT only)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}} <br /> |{{Yes}} (OpenVZ templates)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''P2V migration'''<br /> |Integrated or added P2V (or V2V) capability in order to convert physical systems to virtual environment.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}, 3rd party tools<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|3. VE Mobility and HA<br /> |-<br /> !colspan=&quot;11&quot;|3.1. VE Mobility<br /> |-<br /> |'''Live Migration'''<br /> |Ability to migrate virtual machines between hosts without perceived downtime<br /> |{{Yes}}, but with no zero downtime<br /> |{{Yes}}, Kernel-Level Migration<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|3.2. HA / DR<br /> |-<br /> |'''Integrated HA'''<br /> |Recover virtual environment in case of host failures through restart on alternative hosts (downtime = restart time)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|4. Network and Storage<br /> |-<br /> !colspan=&quot;11&quot;|4.1. Storage<br /> |-<br /> |'''Supported Storage'''<br /> |Supported types of Storage (DAS, NAS or SAN)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS, NAS (NFS, ZFS), SAN (iSCSI), Ceph <br /> |DAS, NAS (SMB), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |-<br /> |'''Virtual Disk Format'''<br /> |Supported format(s) of the virtual disks for the virtual machines<br /> |CT - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |Any<br /> |Qcow2, vmdk, raw<br /> |vhdx, vhd, pass-though (raw)<br /> |Qcow2, raw disk<br /> |vhd, raw disk<br /> |-<br /> |'''Thin Disk Provisioning'''<br /> |Ability to over-commit overall disk space by dynamically growing the size of virtual disks based on actual usage rather than pre-allocating full size.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, depends on disk format (dm-thin)<br /> |{{Yes}}, depends on underlying storage driver<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Virtual SAN'''<br /> |Enhanced storage capability e.g. providing a virtual SAN through virtualized 'local' storage <br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS, sheepdog)<br /> |{{Yes}}, Storage Spaces<br /> |{{Yes}}, Red Hat Storage<br /> |{{No}}<br /> |-<br /> |'''Storage QoS'''<br /> |Ability to control Quality of Service for Storage I/O or Throughput for CT/VM<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}, VMs only<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|4.2. Network<br /> |-<br /> |'''Network QoS'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |{{Yes}}, with Open vSwitch <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|5. Others – most of features are relevant only for Virtuozzo editions<br /> |-<br /> |'''Memory deduplication for binary files'''<br /> |Memory and IOPS deduplication management that enables/disables caching for Container directories and files, verifies cache integrity, checks Containers for cache errors, and purges the cache if needed<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{No}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''Completely isolated disk subsystem for CTs'''<br /> |<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, with LVM<br /> |{{Yes}}, LVM, ZFS, or loop devices<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''API\SDK'''<br /> |<br /> |OpenVZ API for Ruby, LibVirt<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |LibLXC, API for Ruby, Python 2, Haskell, Go<br /> |Proxmox VE uses a REST like API (JSON data format)<br /> |Windows SDK<br /> |RHEV-M API: REST API, SDKs<br /> |XenAPI, XenServer SDKs<br /> |-<br /> |'''Image Catalog integration'''<br /> |Integration with 3rd-party image catalog services of popular server applications and development environments that can be installed with one click.<br /> |{{No}}<br /> |{{Yes}} Application Image Catalog [https://virtuozzo.com/introducing-the-virtuozzo-application-catalog/ Virtuozzo Application Catalog]<br /> |{{No}}<br /> |{{Yes}} Application Image Catalog [https://virtuozzo.com/introducing-the-virtuozzo-application-catalog/ Virtuozzo Application Catalog]<br /> |{{No}}<br /> |{{Yes}} (Turnkey)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Kernel update without reboot'''<br /> |Integrated ability to upgrade kernel or install security patches without downtime.<br /> |{{No}}, only 3d party tools<br /> |{{Yes}}, Rebootless Kernel Update<br /> |{{No}}<br /> |{{Yes}} [https://readykernel.com/ ReadyKernel Service]<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |N/A<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |-<br /> |'''Power Panel'''<br /> |A tool used for managing particular virtual machines and containers by their end users.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Secure for using in public networks'''<br /> |<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|6. Commercial<br /> |-<br /> |'''Open Source'''<br /> |<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}} (but there is Open Source edition(oVirt))<br /> |{{No}} (but there is Open Source edition)<br /> |-<br /> |'''License\Subscription'''<br /> |<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, Enterprise Edition<br /> |-<br /> |'''Support'''<br /> |<br /> |Both community and commercial support<br /> |Commercial support<br /> |Community support<br /> |Commercial Support<br /> |Yes, Canonical Ltd.<br /> |Both community and commercial support<br /> |Commercial support<br /> |Commercial support<br /> |Both community and commercial support<br /> |-<br /> |'''EOL policy'''<br /> |<br /> |[[Releases|5 years of support]]<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |TBD<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |<br /> |<br /> |[https://support.microsoft.com/en-us/lifecycle/search/default.aspx?alpha=hyper-v 11 years of support]]<br /> |<br /> |<br /> |-<br /> |}</div>

Vporokhov https://wiki.openvz.org/index.php?title=Setup_OpenStack_with_Virtuozzo_7&diff=22610 2017-04-21T11:50:01Z

<p>Vporokhov: /* Installing OpenStack with help of packstack on Virtuozzo 7 (*Production Setup*) */</p> <hr /> <div>{{Virtuozzo}}<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> This article describes how to install OpenStack on [[Virtuozzo]] 7.<br /> == Introduction ==<br /> <br /> Virtuozzo 7 supports OpenStack as cloud management solution since version 6. With Virtuozzo 7 we are going to add a lot of new capabilities to OpenStack integration. <br /> <br /> This guide describes two ways of installing OpenStack on Virtuozzo nodes. The first is for quick/development/POC needs. The second is for production. Please keep in mind that devstack allows you to install OpenStack for demo/POC/development purposes only. That means it will be reset after host reboot.<br /> <br /> You need the following infrastructure to setup OpenStack with Virtuozzo 7:<br /> #controller host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a controller and Virtuozzo containers host.<br /> #compute host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a virtual machines host.<br /> <br /> == Prerequisites ==<br /> <br /> You need to install and update your Virtuozzo nodes first. Install Virtuozzo 7 on your controller and compute hosts as usual. You can use basic (local) or Virtuozzo Storage. Update Virtuozzo hosts<br /> $ yum update -y<br /> <br /> If you have br0 bridge configured as an IP interface, then you should move an IP address assigned to it to the physical ethernet interface bridged to br0.<br /> You can check you configuration with the following command:<br /> <br /> $ if=$(brctl show | grep '^br0' | awk ' { print $4 }') &amp;&amp; addr=$(ip addr | grep -w 'br0' | grep inet | awk ' {print $2} ') &amp;&amp; gw=$(ip route | grep default | awk ' { print $3 } ') &amp;&amp; echo &quot;My interface is '$if', gateway is '$gw', IP address '$addr'&quot;<br /> <br /> For instance you have the following output after execution the above script:<br /> <br /> My interface is 'en33', gateway is '192.168.190.2', IP address '192.168.190.134/24'.<br /> <br /> Then edit your /etc/sysconfig/network-scripts/ifcfg-ens33 to have the following content and remove BRIDGE=&quot;br0&quot; string from it:<br /> ...<br /> ONBOOT=yes<br /> IPADDR=192.168.190.134<br /> GATEWAY=192.168.190.2<br /> PREFIX=24<br /> ...<br /> <br /> Remove /etc/sysconfig/network-scripts/ifcfg-br0 file.<br /> <br /> $ rm /etc/sysconfig/network-scripts/ifcfg-br0<br /> <br /> Then restart network service:<br /> <br /> $ systemctl restart network<br /> <br /> == Setup OpenStack Controller Node with Virtuozzo Containers Support (*Developer/POC Setup*) == &lt;!--T:1--&gt;<br /> <br /> &lt;!--T:3--&gt;<br /> You are able to setup OpenStack controller node together with compute node on the same server for demo or test purpose. In this case compute node with Virtuozzo Containers support will be deployed. You can add another compute node with containers or VMs anytime you want as described in Setup OpenStack Compute Node section.<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> $ yum install git -y<br /> <br /> Clone virtuozzo scripts:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Storage Cluster. <br /> <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show Virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the CONTROLLER node. Please read full script description here https://github.com/virtuozzo/virtuozzo-openstack-scripts/blob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.25 --password Virtuozzo1! --use_provider_network true --fixed_range 192.168.0.0/24 --floating_range 10.24.41.0/24 --floating_pool &quot;start=10.24.41.151,end=10.24.41.199&quot; --public_gateway 10.24.41.1 --gateway 192.168.0.1 --vzstorage vstorage1 --mode ALL <br /> <br /> Run the script on your CONTROLLER node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> Installation can take up to 30 minutes depending on your Internet connection speed. Finished!<br /> <br /> == Setup OpenStack Compute Node (*Developer/POC Setup*) ==<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> $ yum install git -y<br /> <br /> Clone Virtuozzo scripts to your COMPUTE node:<br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd /vz/virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Cluster. <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show the virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the COMPUTE node. Please read script description here https://github.com/virtuozzo/virtuozzo-openstack-scripts/blob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.26 --password Virtuozzo1! --use_provider_network true --mode COMPUTE --controller 10.24.41.25 <br /> <br /> Run the script on your COMPUTE node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> == How to change Virtualization Type to Virtual Machines on the Compute Node ==<br /> <br /> If you want to use virtual machines instead of containers on your compute node you need to change virtualization type to KVM on the selected compute node.<br /> <br /> Open nova configuration file:<br /> $ vi /etc/nova/nova.conf<br /> <br /> Change the following lines:<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = qcow2<br /> connection_uri = vz:///system<br /> <br /> Delete the line:<br /> inject_partition = -2<br /> <br /> Save the file.<br /> <br /> Restart nova-compute service:<br /> $ su stack<br /> $ screen -r<br /> Press Ctrl-c<br /> $ sg libvirtd '/usr/bin/nova-compute --config-file /etc/nova/nova.conf' &amp; echo $! &gt;/vz/stack/status/stack/n-cpu.pid; fg || echo &quot;n-cpu failed to start&quot; | tee &quot;/vz/stack/status/stack/n-cpu.failure&quot;<br /> <br /> To exit from screen session:<br /> Press Ctrl+a+d<br /> <br /> == How to redeploy OpenStack on the same nodes ==<br /> <br /> Your OpenStack setup will be reset after node restart. To redeploy OpenStack on the same nodes do the following:<br /> # &lt;code&gt;cd /vz/virtuozzo-openstack-scripts&lt;/code&gt;<br /> # &lt;code&gt;git pull&lt;/code&gt;<br /> # Run ./setup_devstack_vz7.sh with options you need.<br /> <br /> == Installing OpenStack with help of packstack on [[Virtuozzo]] 7 (*Production Setup*) == <br /> <br /> <br /> * Install Virtuozzo Platform Release package to all Virtuozzo OpenStack nodes:<br /> <br /> $ yum install vz-platform-release<br /> <br /> * Install packstack package:<br /> <br /> $ yum install openstack-packstack<br /> <br /> * Download sample Vz7 packstack answer file:<br /> <br /> $ wget https://raw.githubusercontent.com/virtuozzo/virtuozzo-openstack-scripts/master/vz7-packstack-ocata.txt<br /> <br /> * Edit vz7-packstack-ocata.txt enabling/disabling necessary services<br /> * Replace all references to 'localhost' and '127.0.0.1' host addresses to correct valuses<br /> * Set all passwords parameters containing PW_PLACEHOLDER string to some meaninful values<br /> * If you are going to use Virtuozzo Storage as a Cinder Volume backend set the following parameters:<br /> <br /> # Enable Virtuozzo Storage<br /> CONFIG_VSTORAGE_ENABLED=y<br /> <br /> # VStorage cluster name.<br /> CONFIG_VSTORAGE_CLUSTER_NAME=<br /> <br /> # VStorage cluster password.<br /> CONFIG_VSTORAGE_CLUSTER_PASSWORD= <br /> <br /> * Then run packstack:<br /> <br /> $ packstack --answer-file=vz7-packstack-ocata.txt<br /> <br /> == Install and configure a nova controller node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:18--&gt;<br /> <br /> &lt;!--T:19--&gt;<br /> * Follow instructions on [http://docs.openstack.org/newton/install-guide-rdo/nova-controller-install.html OpenStack.org]<br /> <br /> * Download the container [http://updates.virtuozzo.com/server/virtuozzo/en_us/odin/7/techpreview-ct/centos7-exe.hds.tar.gz image]<br /> * Unpack it<br /> <br /> $ tar -xzvf centos7-exe.hds.tar.gz<br /> <br /> * Upload the image to glance:<br /> NOTE: this image was created for testing purposes only. Don't use it in production as is!<br /> <br /> $ glance image-create --name centos7-exe --disk-format ploop --min-ram 512 --min-disk 1 --container-format bare --property vm_mode=exe --property hypervisor_type=vz --property cinder_img_volume_type=vstorage-ploop --file centos7-exe.hds<br /> <br /> $ glance image-create --name centos7-hvm --disk-format qcow2 --min-ram 1024 --min-disk 10 --container-format bare --property cinder_img_volume_type=vstorage-qcow2 --file CentOS-7-x86_64-GenericCloud.qcow2<br /> <br /> * CentOS image one can get here [http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.qcow2 ]<br /> <br /> == Install and configure a compute node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> Please use this chapter if you are going to run containers OR virtual machines on your compute node, but not containers AND virtual machines simultaneously. If you need to run containers and VMs simultaneously, please use next chapter.<br /> <br /> * Follow instructions on [http://docs.openstack.org/newton/install-guide-rdo/nova-compute-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> force_raw_images = False<br /> pointer_model = ps2mouse<br /> <br /> [libvirt]<br /> ...<br /> vzstorage_mount_user = nova<br /> vzstorage_mount_group = root<br /> virt_type = parallels<br /> images_type = ploop<br /> connection_uri = vz:///system<br /> <br /> * Remove 'cpu_mode' parameter or set the following:<br /> <br /> cpu_mode = none<br /> <br /> * Then restart nova-compute service:<br /> <br /> $ systemctl restart openstack-nova-compute.service<br /> <br /> * If you plan to run Virtual Machines on your Compute node, change 'images_type' parameter to 'qcow2'<br /> <br /> == Install and configure a block storage node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> If you are going to run containers AND virtual machines simultaneously on your compute node you have to use this approach.<br /> <br /> * Follow instructions on [http://docs.openstack.org/mitaka/install-guide-rdo/cinder-controller-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/cinder/cinder.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> enabled_backends = lvmdriver-1,vstorage-ploop,vstorage-qcow2<br /> ...<br /> <br /> [vstorage-ploop]<br /> vzstorage_default_volume_format = ploop<br /> vzstorage_shares_config = /etc/cinder/vzstorage-shares-vstorage.conf<br /> volume_driver = cinder.volume.drivers.vzstorage.VZStorageDriver<br /> volume_backend_name = vstorage-ploop<br /> <br /> [vstorage-qcow2]<br /> vzstorage_default_volume_format = qcow2<br /> vzstorage_shares_config = /etc/cinder/vzstorage-shares-vstorage.conf<br /> volume_driver = cinder.volume.drivers.vzstorage.VZStorageDriver<br /> volume_backend_name = vstorage-qcow2<br /> <br /> * Create /etc/cinder/vzstorage-shares-vstorage.conf with the following content:<br /> <br /> YOUR-CLUSTER-NAME [&quot;-u&quot;, &quot;cinder&quot;, &quot;-g&quot;, &quot;root&quot;, &quot;-m&quot;, &quot;0770&quot;]<br /> <br /> * Create two new volume types:<br /> <br /> $ cinder type-create vstorage-qcow2<br /> $ cinder type-key vstorage-qcow2 set volume_backend_name=vstorage-qcow2<br /> <br /> $ cinder type-create vstorage-ploop<br /> $ cinder type-key vstorage-ploop set volume_backend_name=vstorage-ploop<br /> <br /> * Create directory for storage logs:<br /> <br /> $ mkdir /var/log/pstorage<br /> <br /> * Authenticate your Virtuozzo Storage client nodes in oreser to allow them to mount cluster:<br /> <br /> $ echo $CLUSTER_PASSWD | vstorage auth-node -c YOUR-CLUSTER-NAME -P<br /> <br /> * Then restart cinder services:<br /> <br /> $ systemctl restart openstack-cinder-api<br /> $ systemctl restart openstack-cinder-scheduler<br /> $ systemctl restart openstack-cinder-volume<br /> <br /> == How to create a new image ploop image ready to upload to Glance == &lt;!--T:17--&gt;<br /> <br /> * Select os template. The following templates are possible: vzlinux-7, centos-7, ubuntu-16.04, ubuntu-14.04, debian-8.0, centos-6, debian-8.0-x86_64-minimal<br /> <br /> $ ct=centos-7<br /> <br /> * Create a new container based on necessary os distribution<br /> <br /> $ prlctl create glance-$ct --vmtype ct --ostemplate $ct<br /> <br /> * Set IP address and DNS to be able to connect to internet from the container<br /> <br /> $ prlctl set glance-$ct --ipadd IPADDR --nameserver DNS_IPADDR<br /> <br /> * Add additional network adapter<br /> <br /> $ prlctl set glance-$ct --device-add net --network Bridged --dhcp on<br /> <br /> * Start the container<br /> <br /> $ prlctl start glance-$ct<br /> <br /> * Install cloud-init packet<br /> <br /> $ prlctl exec glance-$ct yum install cloud-init -y<br /> <br /> * Stop the container and mount it<br /> <br /> $ prlctl stop glance-$ct<br /> $ prlctl mount glance-$ct<br /> <br /> * Store the container uuid<br /> <br /> $ uuid=$(vzlist glance-$ct | awk ' NR&gt;1 { print $1 }') <br /> <br /> * Remove the following modules from cloud.cfg<br /> <br /> $ sed -i '/- growpart/d' /vz/root/$uuid/etc/cloud/cloud.cfg<br /> $ sed -i '/- resizefs/d' /vz/root/$uuid/etc/cloud/cloud.cfg<br /> <br /> * Prepare network scripts<br /> <br /> cat &gt; /vz/root/$uuid/etc/sysconfig/network-scripts/ifcfg-eth0 &lt;&lt; _EOF<br /> DEVICE=eth0<br /> ONBOOT=yes<br /> NM_CONTROLLED=no<br /> BOOTPROTO=dhcp<br /> _EOF<br /> <br /> * If you need more than one network adapters within a container, make as many copies as you need <br /> <br /> $ cp /vz/root/$uuid/etc/sysconfig/network-scripts/ifcfg-eth0 /vz/root/$uuid/etc/sysconfig/network-scripts/ifcfg-eth1<br /> $ sed -i '/eth0/eth1' /vz/root/$uuid/etc/sysconfig/network-scripts/ifcfg-eth1<br /> <br /> * Perform some cleanup<br /> <br /> $ rm -f /vz/root/$uuid/etc/sysconfig/network-scripts/ifcfg-venet0*<br /> $ rm -f /vz/root/$uuid/etc/resolv.conf<br /> <br /> * Create ploop disk and copy files<br /> <br /> $ mkdir /tmp/ploop-$ct<br /> $ ploop init -s 950M /tmp/ploop-$ct/$ct.hds<br /> $ mkdir /tmp/ploop-$ct/dst<br /> $ ploop mount -m /tmp/ploop-$ct/dst /tmp/ploop-$ct/DiskDescriptor.xml<br /> $ cp -Pr --preserve=all /vz/root/$uuid/* /tmp/ploop-$ct/dst/<br /> $ ploop umount -m /tmp/ploop-$ct/dst/<br /> <br /> * Unmount the container<br /> <br /> $ prlctl umount glance-$ct<br /> <br /> * Now the image tmp/ploop-$ct/$ct.hds is ready to be uploaded to Glance<br /> <br /> == See also == &lt;!--T:100--&gt;<br /> * [http://docs.openstack.org/newton/install-guide-rdo/nova-controller-install.html Controller Node Installation Guide]<br /> * [http://docs.openstack.org/newton/install-guide-rdo/nova-compute-install.html Compute Node Installation Guide]<br /> * [http://docs.openstack.org/newton/install-guide-rdo/environment-packages.html OpenStack Installation Guide]<br /> * [https://docs.openvz.org/ Virtuozzo Documentation]<br /> * [[Virtuozzo ecosystem]]<br /> <br /> &lt;/translate&gt;<br /> <br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Setup_OpenStack_with_Virtuozzo_7&diff=22609 2017-04-21T11:40:04Z

<p>Vporokhov: /* Installing OpenStack with help of packstack on Virtuozzo 7 (*Production Setup*) */</p> <hr /> <div>{{Virtuozzo}}<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> This article describes how to install OpenStack on [[Virtuozzo]] 7.<br /> == Introduction ==<br /> <br /> Virtuozzo 7 supports OpenStack as cloud management solution since version 6. With Virtuozzo 7 we are going to add a lot of new capabilities to OpenStack integration. <br /> <br /> This guide describes two ways of installing OpenStack on Virtuozzo nodes. The first is for quick/development/POC needs. The second is for production. Please keep in mind that devstack allows you to install OpenStack for demo/POC/development purposes only. That means it will be reset after host reboot.<br /> <br /> You need the following infrastructure to setup OpenStack with Virtuozzo 7:<br /> #controller host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a controller and Virtuozzo containers host.<br /> #compute host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a virtual machines host.<br /> <br /> == Prerequisites ==<br /> <br /> You need to install and update your Virtuozzo nodes first. Install Virtuozzo 7 on your controller and compute hosts as usual. You can use basic (local) or Virtuozzo Storage. Update Virtuozzo hosts<br /> $ yum update -y<br /> <br /> If you have br0 bridge configured as an IP interface, then you should move an IP address assigned to it to the physical ethernet interface bridged to br0.<br /> You can check you configuration with the following command:<br /> <br /> $ if=$(brctl show | grep '^br0' | awk ' { print $4 }') &amp;&amp; addr=$(ip addr | grep -w 'br0' | grep inet | awk ' {print $2} ') &amp;&amp; gw=$(ip route | grep default | awk ' { print $3 } ') &amp;&amp; echo &quot;My interface is '$if', gateway is '$gw', IP address '$addr'&quot;<br /> <br /> For instance you have the following output after execution the above script:<br /> <br /> My interface is 'en33', gateway is '192.168.190.2', IP address '192.168.190.134/24'.<br /> <br /> Then edit your /etc/sysconfig/network-scripts/ifcfg-ens33 to have the following content and remove BRIDGE=&quot;br0&quot; string from it:<br /> ...<br /> ONBOOT=yes<br /> IPADDR=192.168.190.134<br /> GATEWAY=192.168.190.2<br /> PREFIX=24<br /> ...<br /> <br /> Remove /etc/sysconfig/network-scripts/ifcfg-br0 file.<br /> <br /> $ rm /etc/sysconfig/network-scripts/ifcfg-br0<br /> <br /> Then restart network service:<br /> <br /> $ systemctl restart network<br /> <br /> == Setup OpenStack Controller Node with Virtuozzo Containers Support (*Developer/POC Setup*) == &lt;!--T:1--&gt;<br /> <br /> &lt;!--T:3--&gt;<br /> You are able to setup OpenStack controller node together with compute node on the same server for demo or test purpose. In this case compute node with Virtuozzo Containers support will be deployed. You can add another compute node with containers or VMs anytime you want as described in Setup OpenStack Compute Node section.<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> $ yum install git -y<br /> <br /> Clone virtuozzo scripts:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Storage Cluster. <br /> <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show Virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the CONTROLLER node. Please read full script description here https://github.com/virtuozzo/virtuozzo-openstack-scripts/blob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.25 --password Virtuozzo1! --use_provider_network true --fixed_range 192.168.0.0/24 --floating_range 10.24.41.0/24 --floating_pool &quot;start=10.24.41.151,end=10.24.41.199&quot; --public_gateway 10.24.41.1 --gateway 192.168.0.1 --vzstorage vstorage1 --mode ALL <br /> <br /> Run the script on your CONTROLLER node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> Installation can take up to 30 minutes depending on your Internet connection speed. Finished!<br /> <br /> == Setup OpenStack Compute Node (*Developer/POC Setup*) ==<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> $ yum install git -y<br /> <br /> Clone Virtuozzo scripts to your COMPUTE node:<br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd /vz/virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Cluster. <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show the virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the COMPUTE node. Please read script description here https://github.com/virtuozzo/virtuozzo-openstack-scripts/blob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.26 --password Virtuozzo1! --use_provider_network true --mode COMPUTE --controller 10.24.41.25 <br /> <br /> Run the script on your COMPUTE node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> == How to change Virtualization Type to Virtual Machines on the Compute Node ==<br /> <br /> If you want to use virtual machines instead of containers on your compute node you need to change virtualization type to KVM on the selected compute node.<br /> <br /> Open nova configuration file:<br /> $ vi /etc/nova/nova.conf<br /> <br /> Change the following lines:<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = qcow2<br /> connection_uri = vz:///system<br /> <br /> Delete the line:<br /> inject_partition = -2<br /> <br /> Save the file.<br /> <br /> Restart nova-compute service:<br /> $ su stack<br /> $ screen -r<br /> Press Ctrl-c<br /> $ sg libvirtd '/usr/bin/nova-compute --config-file /etc/nova/nova.conf' &amp; echo $! &gt;/vz/stack/status/stack/n-cpu.pid; fg || echo &quot;n-cpu failed to start&quot; | tee &quot;/vz/stack/status/stack/n-cpu.failure&quot;<br /> <br /> To exit from screen session:<br /> Press Ctrl+a+d<br /> <br /> == How to redeploy OpenStack on the same nodes ==<br /> <br /> Your OpenStack setup will be reset after node restart. To redeploy OpenStack on the same nodes do the following:<br /> # &lt;code&gt;cd /vz/virtuozzo-openstack-scripts&lt;/code&gt;<br /> # &lt;code&gt;git pull&lt;/code&gt;<br /> # Run ./setup_devstack_vz7.sh with options you need.<br /> <br /> == Installing OpenStack with help of packstack on [[Virtuozzo]] 7 (*Production Setup*) == <br /> <br /> <br /> * Install Virtuozzo Platform Release package:<br /> <br /> $ yum install vz-platform-release<br /> <br /> * Install packstack package:<br /> <br /> $ yum install openstack-packstack<br /> <br /> * Download sample Vz7 packstack answer file:<br /> <br /> $ wget https://raw.githubusercontent.com/virtuozzo/virtuozzo-openstack-scripts/master/vz7-packstack-ocata.txt<br /> <br /> * Edit vz7-packstack-ocata.txt enabling/disabling necessary services<br /> * Replace all references to 'localhost' and '127.0.0.1' host addresses to correct valuses<br /> * Set all passwords parameters containing PW_PLACEHOLDER string to some meaninful values<br /> * If you are going to use Virtuozzo Storage as a Cinder Volume backend set the following parameters:<br /> <br /> # Enable Virtuozzo Storage<br /> CONFIG_VSTORAGE_ENABLED=y<br /> <br /> # VStorage cluster name.<br /> CONFIG_VSTORAGE_CLUSTER_NAME=<br /> <br /> # VStorage cluster password.<br /> CONFIG_VSTORAGE_CLUSTER_PASSWORD= <br /> <br /> * Then run packstack:<br /> <br /> $ packstack --answer-file=vz7-packstack-ocata.txt<br /> <br /> == Install and configure a nova controller node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:18--&gt;<br /> <br /> &lt;!--T:19--&gt;<br /> * Follow instructions on [http://docs.openstack.org/newton/install-guide-rdo/nova-controller-install.html OpenStack.org]<br /> <br /> * Download the container [http://updates.virtuozzo.com/server/virtuozzo/en_us/odin/7/techpreview-ct/centos7-exe.hds.tar.gz image]<br /> * Unpack it<br /> <br /> $ tar -xzvf centos7-exe.hds.tar.gz<br /> <br /> * Upload the image to glance:<br /> NOTE: this image was created for testing purposes only. Don't use it in production as is!<br /> <br /> $ glance image-create --name centos7-exe --disk-format ploop --min-ram 512 --min-disk 1 --container-format bare --property vm_mode=exe --property hypervisor_type=vz --property cinder_img_volume_type=vstorage-ploop --file centos7-exe.hds<br /> <br /> $ glance image-create --name centos7-hvm --disk-format qcow2 --min-ram 1024 --min-disk 10 --container-format bare --property cinder_img_volume_type=vstorage-qcow2 --file CentOS-7-x86_64-GenericCloud.qcow2<br /> <br /> * CentOS image one can get here [http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.qcow2 ]<br /> <br /> == Install and configure a compute node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> Please use this chapter if you are going to run containers OR virtual machines on your compute node, but not containers AND virtual machines simultaneously. If you need to run containers and VMs simultaneously, please use next chapter.<br /> <br /> * Follow instructions on [http://docs.openstack.org/newton/install-guide-rdo/nova-compute-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> force_raw_images = False<br /> pointer_model = ps2mouse<br /> <br /> [libvirt]<br /> ...<br /> vzstorage_mount_user = nova<br /> vzstorage_mount_group = root<br /> virt_type = parallels<br /> images_type = ploop<br /> connection_uri = vz:///system<br /> <br /> * Remove 'cpu_mode' parameter or set the following:<br /> <br /> cpu_mode = none<br /> <br /> * Then restart nova-compute service:<br /> <br /> $ systemctl restart openstack-nova-compute.service<br /> <br /> * If you plan to run Virtual Machines on your Compute node, change 'images_type' parameter to 'qcow2'<br /> <br /> == Install and configure a block storage node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> If you are going to run containers AND virtual machines simultaneously on your compute node you have to use this approach.<br /> <br /> * Follow instructions on [http://docs.openstack.org/mitaka/install-guide-rdo/cinder-controller-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/cinder/cinder.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> enabled_backends = lvmdriver-1,vstorage-ploop,vstorage-qcow2<br /> ...<br /> <br /> [vstorage-ploop]<br /> vzstorage_default_volume_format = ploop<br /> vzstorage_shares_config = /etc/cinder/vzstorage-shares-vstorage.conf<br /> volume_driver = cinder.volume.drivers.vzstorage.VZStorageDriver<br /> volume_backend_name = vstorage-ploop<br /> <br /> [vstorage-qcow2]<br /> vzstorage_default_volume_format = qcow2<br /> vzstorage_shares_config = /etc/cinder/vzstorage-shares-vstorage.conf<br /> volume_driver = cinder.volume.drivers.vzstorage.VZStorageDriver<br /> volume_backend_name = vstorage-qcow2<br /> <br /> * Create /etc/cinder/vzstorage-shares-vstorage.conf with the following content:<br /> <br /> YOUR-CLUSTER-NAME [&quot;-u&quot;, &quot;cinder&quot;, &quot;-g&quot;, &quot;root&quot;, &quot;-m&quot;, &quot;0770&quot;]<br /> <br /> * Create two new volume types:<br /> <br /> $ cinder type-create vstorage-qcow2<br /> $ cinder type-key vstorage-qcow2 set volume_backend_name=vstorage-qcow2<br /> <br /> $ cinder type-create vstorage-ploop<br /> $ cinder type-key vstorage-ploop set volume_backend_name=vstorage-ploop<br /> <br /> * Create directory for storage logs:<br /> <br /> $ mkdir /var/log/pstorage<br /> <br /> * Authenticate your Virtuozzo Storage client nodes in oreser to allow them to mount cluster:<br /> <br /> $ echo $CLUSTER_PASSWD | vstorage auth-node -c YOUR-CLUSTER-NAME -P<br /> <br /> * Then restart cinder services:<br /> <br /> $ systemctl restart openstack-cinder-api<br /> $ systemctl restart openstack-cinder-scheduler<br /> $ systemctl restart openstack-cinder-volume<br /> <br /> == How to create a new image ploop image ready to upload to Glance == &lt;!--T:17--&gt;<br /> <br /> * Select os template. The following templates are possible: vzlinux-7, centos-7, ubuntu-16.04, ubuntu-14.04, debian-8.0, centos-6, debian-8.0-x86_64-minimal<br /> <br /> $ ct=centos-7<br /> <br /> * Create a new container based on necessary os distribution<br /> <br /> $ prlctl create glance-$ct --vmtype ct --ostemplate $ct<br /> <br /> * Set IP address and DNS to be able to connect to internet from the container<br /> <br /> $ prlctl set glance-$ct --ipadd IPADDR --nameserver DNS_IPADDR<br /> <br /> * Add additional network adapter<br /> <br /> $ prlctl set glance-$ct --device-add net --network Bridged --dhcp on<br /> <br /> * Start the container<br /> <br /> $ prlctl start glance-$ct<br /> <br /> * Install cloud-init packet<br /> <br /> $ prlctl exec glance-$ct yum install cloud-init -y<br /> <br /> * Stop the container and mount it<br /> <br /> $ prlctl stop glance-$ct<br /> $ prlctl mount glance-$ct<br /> <br /> * Store the container uuid<br /> <br /> $ uuid=$(vzlist glance-$ct | awk ' NR&gt;1 { print $1 }') <br /> <br /> * Remove the following modules from cloud.cfg<br /> <br /> $ sed -i '/- growpart/d' /vz/root/$uuid/etc/cloud/cloud.cfg<br /> $ sed -i '/- resizefs/d' /vz/root/$uuid/etc/cloud/cloud.cfg<br /> <br /> * Prepare network scripts<br /> <br /> cat &gt; /vz/root/$uuid/etc/sysconfig/network-scripts/ifcfg-eth0 &lt;&lt; _EOF<br /> DEVICE=eth0<br /> ONBOOT=yes<br /> NM_CONTROLLED=no<br /> BOOTPROTO=dhcp<br /> _EOF<br /> <br /> * If you need more than one network adapters within a container, make as many copies as you need <br /> <br /> $ cp /vz/root/$uuid/etc/sysconfig/network-scripts/ifcfg-eth0 /vz/root/$uuid/etc/sysconfig/network-scripts/ifcfg-eth1<br /> $ sed -i '/eth0/eth1' /vz/root/$uuid/etc/sysconfig/network-scripts/ifcfg-eth1<br /> <br /> * Perform some cleanup<br /> <br /> $ rm -f /vz/root/$uuid/etc/sysconfig/network-scripts/ifcfg-venet0*<br /> $ rm -f /vz/root/$uuid/etc/resolv.conf<br /> <br /> * Create ploop disk and copy files<br /> <br /> $ mkdir /tmp/ploop-$ct<br /> $ ploop init -s 950M /tmp/ploop-$ct/$ct.hds<br /> $ mkdir /tmp/ploop-$ct/dst<br /> $ ploop mount -m /tmp/ploop-$ct/dst /tmp/ploop-$ct/DiskDescriptor.xml<br /> $ cp -Pr --preserve=all /vz/root/$uuid/* /tmp/ploop-$ct/dst/<br /> $ ploop umount -m /tmp/ploop-$ct/dst/<br /> <br /> * Unmount the container<br /> <br /> $ prlctl umount glance-$ct<br /> <br /> * Now the image tmp/ploop-$ct/$ct.hds is ready to be uploaded to Glance<br /> <br /> == See also == &lt;!--T:100--&gt;<br /> * [http://docs.openstack.org/newton/install-guide-rdo/nova-controller-install.html Controller Node Installation Guide]<br /> * [http://docs.openstack.org/newton/install-guide-rdo/nova-compute-install.html Compute Node Installation Guide]<br /> * [http://docs.openstack.org/newton/install-guide-rdo/environment-packages.html OpenStack Installation Guide]<br /> * [https://docs.openvz.org/ Virtuozzo Documentation]<br /> * [[Virtuozzo ecosystem]]<br /> <br /> &lt;/translate&gt;<br /> <br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Comparison&diff=22571 2017-03-18T09:22:15Z

<p>Vporokhov: </p> <hr /> <div>{{Note|This comparison doesn't include Docker, because Docker is not a virtualization solution. It automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of operating-system-level virtualization.&lt;ref&gt;[https://en.wikipedia.org/wiki/Docker_(software) Wikipedia article about Docker]&lt;/ref&gt;}}<br /> <br /> <br /> == Disclaimer ==<br /> <br /> The information regarding Virtuozzo 7 is provided by [http://www.virtuozzo.com Virtuozzo]. Here is the Virtuozzo's statement regarding this information:<br /> <br /> :#The information contained herein is intended to outline general product direction and should not be relied upon in making purchasing decisions.<br /> :#The content is for informational purposes only and may not be incorporated into any contract.<br /> :#The information presented is not a commitment, promise, or legal obligation to deliver any material, code or functionality.<br /> :#Any references to the development, release, and timing of any features or functionality described for these products remains at Virtuozzo’s sole discretion.<br /> :#Product capabilities, timeframes and features are subject to change and should not be viewed as Virtuozzo commitments.<br /> <br /> The information regarding all other solutions are taken by authors from public sources only. This information can be changed by any OpenVZ Wiki user without any notice and author's review or approval.<br /> <br /> <br /> == Feature comparison of different virtualization solutions ==<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> ! Feature<br /> ! Description<br /> ! OpenVZ<br /> ! Virtuozzo&amp;nbsp;6 (PCS 6)<br /> ! OpenVZ&amp;nbsp;7<br /> ! [https://virtuozzo.com/products/virtuozzo-containers/ Virtuozzo&amp;nbsp;7]<br /> ! LXC<br /> ! Proxmox VE<br /> ! Microsoft Hyper-V 2012 R2<br /> ! RHEV 3.5<br /> ! Citrix XenServer 6.5<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|1. Virtualization platform<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.1. Overview<br /> |-<br /> |'''HW virtualization support (Hypervisor)'''<br /> |Full emulation of underneath hardware level: full isolation guest environment, no dependencies from host OS, overhead for hypervisor layer.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''OS-level virtualization (Containers)'''<br /> |Sharing the same instance of host OS: high density, high performance, high dependencies from host OS.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Hypervisor technology'''<br /> |Technology that enables to run Virtual Machines.<br /> |{{No}}<br /> |Parallels Desktop Monitor<br /> |KVM<br /> |KVM<br /> |None<br /> |KVM<br /> |Hyper-V<br /> |KVM<br /> |Xen<br /> |-<br /> |'''Windows guest OS additional support'''<br /> |WHQL-signed drivers, SVVP certification<br /> |N/A<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Containers technology'''<br /> |Technology that enables to run Containers.<br /> |Virtuozzo Containers<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Linux containers<br /> |LXC (moved from OpenVZ since 4.0)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.2. Memory<br /> |-<br /> |'''Memory Overcommit'''<br /> |Ability to present more memory to virtual machines than physically available <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, with new VCMMD memory management<br /> |{{Yes}}, with new VCMMD memory management and different policies<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Page sharing'''<br /> |Memory (RAM) savings through sharing identical memory pages across virtual machines<br /> |{{Yes}}<br /> |{{Yes}}, only for CTs<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> |'''Online Memory Management for VM'''<br /> |Ability to change amount of RAM for CT and VM without reboot<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |N/A<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|2. Management<br /> |-<br /> !colspan=&quot;11&quot;|2.1. General<br /> |-<br /> |'''Unified management tool for CTs and VMs'''<br /> |Single tool for managing both containers and virtual machines (if applicable)<br /> |N/A<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''OpenStack integration'''<br /> |Integration with OpenStack components ([http://docs.openstack.org/developer/nova/support-matrix.html see details])<br /> |{{Yes}}, only Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated GUI'''<br /> |Centralized multi-server management<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}, Parallels Virtual Automation (PVA)<br /> |{{No}}<br /> |{{Yes}}, [https://virtuozzo.com/support/pva/ Virtual Automator]<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}<br /> |{{Yes}}, System Center Virtual Machine Manager<br /> |{{Yes}}, RHEV Manager<br /> |{{Yes}}, XenCenter<br /> |-<br /> !colspan=&quot;11&quot;|2.2. Upgrade &amp; Backup<br /> |-<br /> |'''Live VE snapshot'''<br /> |Ability to take a snapshot of a virtual environment while the guest OS is running (e.g. for roll-back or backup purposes)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated Backup'''<br /> |Are backup plugins/tools provided to backup virtual environments (over and above the ability to perform classic backup using agents in the guests)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Backup Integration API'''<br /> |Integration with 3rd party backup applications for backup of the virtual environment.<br /> |{{No}} (only through snapshots)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}} (only through snapshots)<br /> |{{Yes}} (vzdump)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot;|2.3. Others<br /> |-<br /> |'''VEs Templates (VM, CT)'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |{{Yes}} (CT only)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}} <br /> |{{Yes}} (OpenVZ templates)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''P2V migration'''<br /> |Integrated or added P2V (or V2V) capability in order to convert physical systems to virtual environment.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}, 3rd party tools<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|3. VE Mobility and HA<br /> |-<br /> !colspan=&quot;11&quot;|3.1. VE Mobility<br /> |-<br /> |'''Live Migration'''<br /> |Ability to migrate virtual machines between hosts without perceived downtime<br /> |{{Yes}}, but with no zero downtime<br /> |{{Yes}}, Kernel-Level Migration<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|3.2. HA / DR<br /> |-<br /> |'''Integrated HA'''<br /> |Recover virtual environment in case of host failures through restart on alternative hosts (downtime = restart time)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|4. Network and Storage<br /> |-<br /> !colspan=&quot;11&quot;|4.1. Storage<br /> |-<br /> |'''Supported Storage'''<br /> |Supported types of Storage (DAS, NAS or SAN)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS, NAS (NFS, ZFS), SAN (iSCSI), Ceph <br /> |DAS, NAS (SMB), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |-<br /> |'''Virtual Disk Format'''<br /> |Supported format(s) of the virtual disks for the virtual machines<br /> |CT - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |Any<br /> |Qcow2, vmdk, raw<br /> |vhdx, vhd, pass-though (raw)<br /> |Qcow2, raw disk<br /> |vhd, raw disk<br /> |-<br /> |'''Thin Disk Provisioning'''<br /> |Ability to over-commit overall disk space by dynamically growing the size of virtual disks based on actual usage rather than pre-allocating full size.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, depends on disk format (dm-thin)<br /> |{{Yes}}, depends on underlying storage driver<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Virtual SAN'''<br /> |Enhanced storage capability e.g. providing a virtual SAN through virtualized 'local' storage <br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS, sheepdog)<br /> |{{Yes}}, Storage Spaces<br /> |{{Yes}}, Red Hat Storage<br /> |{{No}}<br /> |-<br /> |'''Storage QoS'''<br /> |Ability to control Quality of Service for Storage I/O or Throughput for CT/VM<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}, VMs only<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|4.2. Network<br /> |-<br /> |'''Network QoS'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |{{Yes}}, with Open vSwitch <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|5. Others – most of features are relevant only for Virtuozzo editions<br /> |-<br /> |'''Memory deduplication for binary files'''<br /> |Memory and IOPS deduplication management that enables/disables caching for Container directories and files, verifies cache integrity, checks Containers for cache errors, and purges the cache if needed<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{No}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''Completely isolated disk subsystem for CTs'''<br /> |<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, with LVM<br /> |{{Yes}}, LVM, ZFS, or loop devices<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''API\SDK'''<br /> |<br /> |OpenVZ API for Ruby, LibVirt<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |LibLXC, API for Ruby, Python 2, Haskell, Go<br /> |Proxmox VE uses a REST like API (JSON data format)<br /> |Windows SDK<br /> |RHEV-M API: REST API, SDKs<br /> |XenAPI, XenServer SDKs<br /> |-<br /> |'''Image Catalog integration'''<br /> |Integration with 3rd-party image catalog services of popular server applications and development environments that can be installed with one click.<br /> |{{No}}<br /> |{{Yes}} Application Image Catalog [https://virtuozzo.com/introducing-the-virtuozzo-application-catalog/ Virtuozzo Application Catalog]<br /> |{{No}}<br /> |{{Yes}} Application Image Catalog [https://virtuozzo.com/introducing-the-virtuozzo-application-catalog/ Virtuozzo Application Catalog]<br /> |{{No}}<br /> |{{Yes}} (Turnkey)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Kernel update without reboot'''<br /> |Integrated ability to upgrade kernel or install security patches without downtime.<br /> |{{No}}, only 3d party tools<br /> |{{Yes}}, Rebootless Kernel Update<br /> |{{No}}<br /> |{{Yes}} [https://readykernel.com/ ReadyKernel Service]<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |N/A<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |-<br /> |'''Power Panel'''<br /> |A tool used for managing particular virtual machines and containers by their end users.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Secure for using in public networks'''<br /> |<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|6. Commercial<br /> |-<br /> |'''Open Source'''<br /> |<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}} (but there is Open Source edition(oVirt))<br /> |{{No}} (but there is Open Source edition)<br /> |-<br /> |'''License\Subscription'''<br /> |<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, Enterprise Edition<br /> |-<br /> |'''Support'''<br /> |<br /> |Both community and commercial support<br /> |Commercial support<br /> |Community support<br /> |Commercial Support<br /> |Yes, Canonical Ltd.<br /> |Both community and commercial support<br /> |Commercial support<br /> |Commercial support<br /> |Both community and commercial support<br /> |-<br /> |'''EOL policy'''<br /> |<br /> |[[Releases|5 years of support]]<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |TBD<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |<br /> |<br /> |[https://support.microsoft.com/en-us/lifecycle/search/default.aspx?alpha=hyper-v 11 years of support]]<br /> |<br /> |<br /> |-<br /> |}</div>

Vporokhov https://wiki.openvz.org/index.php?title=Comparison&diff=22570 2017-03-18T09:20:43Z

<p>Vporokhov: /* Feature comparison of different virtualization solutions */</p> <hr /> <div>{{Note|This comparison doesn't include Docker, because Docker is not a virtualization solution. It automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of operating-system-level virtualization.&lt;ref&gt;[https://en.wikipedia.org/wiki/Docker_(software) Wikipedia article about Docker]&lt;/ref&gt;}}<br /> <br /> <br /> == Disclaimer ==<br /> <br /> The information regarding Virtuozzo 7 is provided by [http://www.virtuozzo.com Virtuozzo]. Here is the Virtuozzo's statement regarding this information:<br /> <br /> :#The information contained herein is intended to outline general product direction and should not be relied upon in making purchasing decisions.<br /> :#The content is for informational purposes only and may not be incorporated into any contract.<br /> :#The information presented is not a commitment, promise, or legal obligation to deliver any material, code or functionality.<br /> :#Any references to the development, release, and timing of any features or functionality described for these products remains at Virtuozzo’s sole discretion.<br /> :#Product capabilities, timeframes and features are subject to change and should not be viewed as Virtuozzo commitments.<br /> <br /> The information regarding all other solutions are taken by authors from public sources only. This information can be changed by any OpenVZ Wiki user without any notice and author's review or approval.<br /> <br /> <br /> == Feature comparison of different virtualization solutions ==<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> ! Feature<br /> ! Description<br /> ! OpenVZ<br /> ! Virtuozzo&amp;nbsp;6 (PCS 6)<br /> ! OpenVZ&amp;nbsp;7<br /> ! [https://virtuozzo.com/products/virtuozzo-containers/ Virtuozzo&amp;nbsp;7]<br /> ! LXC<br /> ! Proxmox VE<br /> ! Microsoft Hyper-V 2012 R2<br /> ! RHEV 3.5<br /> ! Citrix XenServer 6.5<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|1. Virtualization platform<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.1. Overview<br /> |-<br /> |'''HW virtualization support (Hypervisor)'''<br /> |Full emulation of underneath hardware level: full isolation guest environment, no dependencies from host OS, overhead for hypervisor layer.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''OS-level virtualization (Containers)'''<br /> |Sharing the same instance of host OS: high density, high performance, high dependencies from host OS.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Hypervisor technology'''<br /> |Technology that enables to run Virtual Machines.<br /> |{{No}}<br /> |Parallels Desktop Monitor<br /> |KVM<br /> |KVM<br /> |None<br /> |KVM<br /> |Hyper-V<br /> |KVM<br /> |Xen<br /> |-<br /> |'''Windows guest OS additional support'''<br /> |WHQL-signed drivers, SVVP certification<br /> |N/A<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Containers technology'''<br /> |Technology that enables to run Containers.<br /> |Virtuozzo Containers<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Linux containers<br /> |LXC (moved from OpenVZ since 4.0)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.2. Memory<br /> |-<br /> |'''Memory Overcommit'''<br /> |Ability to present more memory to virtual machines than physically available <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, with new VCMMD memory management<br /> |{{Yes}}, with new VCMMD memory management and different policies<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Page sharing'''<br /> |Memory (RAM) savings through sharing identical memory pages across virtual machines<br /> |{{Yes}}<br /> |{{Yes}}, only for CTs<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> |'''Online Memory Management for VM'''<br /> |Ability to change amount of RAM for CT and VM without reboot<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |N/A<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|2. Management<br /> |-<br /> !colspan=&quot;11&quot;|2.1. General<br /> |-<br /> |'''Unified management tool for CTs and VMs'''<br /> |Single tool for managing both containers and virtual machines (if applicable)<br /> |N/A<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''OpenStack integration'''<br /> |Integration with OpenStack components ([http://docs.openstack.org/developer/nova/support-matrix.html see details])<br /> |{{Yes}}, only Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated GUI'''<br /> |Centralized multi-server management<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}, Parallels Virtual Automation (PVA)<br /> |{{No}}<br /> |{{Yes}}, [https://virtuozzo.com/support/pva/ Virtual Automator]<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}<br /> |{{Yes}}, System Center Virtual Machine Manager<br /> |{{Yes}}, RHEV Manager<br /> |{{Yes}}, XenCenter<br /> |-<br /> !colspan=&quot;11&quot;|2.2. Upgrade &amp; Backup<br /> |-<br /> |'''Live VE snapshot'''<br /> |Ability to take a snapshot of a virtual environment while the guest OS is running (e.g. for roll-back or backup purposes)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated Backup'''<br /> |Are backup plugins/tools provided to backup virtual environments (over and above the ability to perform classic backup using agents in the guests)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Backup Integration API'''<br /> |Integration with 3rd party backup applications for backup of the virtual environment.<br /> |{{No}} (only through snapshots)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}} (only through snapshots)<br /> |{{Yes}} (vzdump)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot;|2.3. Others<br /> |-<br /> |'''VEs Templates (VM, CT)'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |{{Yes}} (CT only)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}} <br /> |{{Yes}} (OpenVZ templates)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''P2V migration'''<br /> |Integrated or added P2V (or V2V) capability in order to convert physical systems to virtual environment.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}, 3rd party tools<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|3. VE Mobility and HA<br /> |-<br /> !colspan=&quot;11&quot;|3.1. VE Mobility<br /> |-<br /> |'''Live Migration'''<br /> |Ability to migrate virtual machines between hosts without perceived downtime<br /> |{{Yes}}, but with no zero downtime<br /> |{{Yes}}, Kernel-Level Migration<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''DRS/Host Maintenance Mode'''<br /> |Ability to put host into maintenance mode which will automatically live migrate all VEs onto other available hosts so that the host can be brought shut down safely<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Distributed Power Management'''<br /> |Distributed Power Management features Ability to automatically migrate VEs onto fewer hosts and power off unused capacity (hosts), wake systems back up when required <br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|3.2. HA / DR<br /> |-<br /> |'''Integrated HA'''<br /> |Recover virtual environment in case of host failures through restart on alternative hosts (downtime = restart time)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|4. Network and Storage<br /> |-<br /> !colspan=&quot;11&quot;|4.1. Storage<br /> |-<br /> |'''Supported Storage'''<br /> |Supported types of Storage (DAS, NAS or SAN)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS, NAS (NFS, ZFS), SAN (iSCSI), Ceph <br /> |DAS, NAS (SMB), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |-<br /> |'''Virtual Disk Format'''<br /> |Supported format(s) of the virtual disks for the virtual machines<br /> |CT - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |Any<br /> |Qcow2, vmdk, raw<br /> |vhdx, vhd, pass-though (raw)<br /> |Qcow2, raw disk<br /> |vhd, raw disk<br /> |-<br /> |'''Thin Disk Provisioning'''<br /> |Ability to over-commit overall disk space by dynamically growing the size of virtual disks based on actual usage rather than pre-allocating full size.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, depends on disk format (dm-thin)<br /> |{{Yes}}, depends on underlying storage driver<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Virtual SAN'''<br /> |Enhanced storage capability e.g. providing a virtual SAN through virtualized 'local' storage <br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS, sheepdog)<br /> |{{Yes}}, Storage Spaces<br /> |{{Yes}}, Red Hat Storage<br /> |{{No}}<br /> |-<br /> |'''Storage QoS'''<br /> |Ability to control Quality of Service for Storage I/O or Throughput for CT/VM<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}, VMs only<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|4.2. Network<br /> |-<br /> |'''Network QoS'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |{{Yes}}, with Open vSwitch <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|5. Others – most of features are relevant only for Virtuozzo editions<br /> |-<br /> |'''Memory deduplication for binary files'''<br /> |Memory and IOPS deduplication management that enables/disables caching for Container directories and files, verifies cache integrity, checks Containers for cache errors, and purges the cache if needed<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{No}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''Completely isolated disk subsystem for CTs'''<br /> |<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, with LVM<br /> |{{Yes}}, LVM, ZFS, or loop devices<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''API\SDK'''<br /> |<br /> |OpenVZ API for Ruby, LibVirt<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |LibLXC, API for Ruby, Python 2, Haskell, Go<br /> |Proxmox VE uses a REST like API (JSON data format)<br /> |Windows SDK<br /> |RHEV-M API: REST API, SDKs<br /> |XenAPI, XenServer SDKs<br /> |-<br /> |'''Image Catalog integration'''<br /> |Integration with 3rd-party image catalog services of popular server applications and development environments that can be installed with one click.<br /> |{{No}}<br /> |{{Yes}} Application Image Catalog [https://virtuozzo.com/introducing-the-virtuozzo-application-catalog/ Virtuozzo Application Catalog]<br /> |{{No}}<br /> |{{Yes}} Application Image Catalog [https://virtuozzo.com/introducing-the-virtuozzo-application-catalog/ Virtuozzo Application Catalog]<br /> |{{No}}<br /> |{{Yes}} (Turnkey)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Kernel update without reboot'''<br /> |Integrated ability to upgrade kernel or install security patches without downtime.<br /> |{{No}}, only 3d party tools<br /> |{{Yes}}, Rebootless Kernel Update<br /> |{{No}}<br /> |{{Yes}} [https://readykernel.com/ ReadyKernel Service]<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |N/A<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |-<br /> |'''Power Panel'''<br /> |A tool used for managing particular virtual machines and containers by their end users.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Secure for using in public networks'''<br /> |<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|6. Commercial<br /> |-<br /> |'''Open Source'''<br /> |<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}} (but there is Open Source edition(oVirt))<br /> |{{No}} (but there is Open Source edition)<br /> |-<br /> |'''License\Subscription'''<br /> |<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, Enterprise Edition<br /> |-<br /> |'''Support'''<br /> |<br /> |Both community and commercial support<br /> |Commercial support<br /> |Community support<br /> |Commercial Support<br /> |Yes, Canonical Ltd.<br /> |Both community and commercial support<br /> |Commercial support<br /> |Commercial support<br /> |Both community and commercial support<br /> |-<br /> |'''EOL policy'''<br /> |<br /> |[[Releases|5 years of support]]<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |TBD<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |<br /> |<br /> |[https://support.microsoft.com/en-us/lifecycle/search/default.aspx?alpha=hyper-v 11 years of support]]<br /> |<br /> |<br /> |-<br /> |}</div>

Vporokhov https://wiki.openvz.org/index.php?title=Setup_OpenStack_with_Virtuozzo_7&diff=22554 2017-03-01T15:01:15Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> This article describes how to install OpenStack on [[Virtuozzo]] 7.<br /> == Introduction ==<br /> <br /> Virtuozzo 7 supports OpenStack as cloud management solution since version 6. With Virtuozzo 7 we are going to add a lot of new capabilities to OpenStack integration. <br /> <br /> This guide describes two ways of installing OpenStack on Virtuozzo nodes. The first is for quick/development/POC needs. The second is for production. Please keep in mind that devstack allows you to install OpenStack for demo/POC/development purposes only. That means it will be reset after host reboot.<br /> <br /> You need the following infrastructure to setup OpenStack with Virtuozzo 7:<br /> #controller host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a controller and Virtuozzo containers host.<br /> #compute host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a virtual machines host.<br /> <br /> == Prerequisites ==<br /> <br /> You need to install and update your Virtuozzo nodes first. Install Virtuozzo 7 on your controller and compute hosts as usual. You can use basic (local) or Virtuozzo Storage. Update Virtuozzo hosts<br /> $ yum update -y<br /> <br /> If you have br0 bridge configured as an IP interface, then you should move an IP address assigned to it to the physical ethernet interface bridged to br0.<br /> You can check you configuration with the following command:<br /> <br /> $ if=$(brctl show | grep '^br0' | awk ' { print $4 }') &amp;&amp; addr=$(ip addr | grep -w 'br0' | grep inet | awk ' {print $2} ') &amp;&amp; gw=$(ip route | grep default | awk ' { print $3 } ') &amp;&amp; echo &quot;My interface is '$if', gateway is '$gw', IP address '$addr'&quot;<br /> <br /> For instance you have the following output after execution the above script:<br /> <br /> My interface is 'en33', gateway is '192.168.190.2', IP address '192.168.190.134/24'.<br /> <br /> Then edit your /etc/sysconfig/network-scripts/ifcfg-ens33 to have the following content and remove BRIDGE=&quot;br0&quot; string from it:<br /> ...<br /> ONBOOT=yes<br /> IPADDR=192.168.190.134<br /> GATEWAY=192.168.190.2<br /> PREFIX=24<br /> ...<br /> <br /> Remove /etc/sysconfig/network-scripts/ifcfg-br0 file.<br /> <br /> $ rm /etc/sysconfig/network-scripts/ifcfg-br0<br /> <br /> Then restart network service:<br /> <br /> $ systemctl restart network<br /> <br /> == Setup OpenStack Controller Node with Virtuozzo Containers Support (*Developer/POC Setup*) == &lt;!--T:1--&gt;<br /> <br /> &lt;!--T:3--&gt;<br /> You are able to setup OpenStack controller node together with compute node on the same server for demo or test purpose. In this case compute node with Virtuozzo Containers support will be deployed. You can add another compute node with containers or VMs anytime you want as described in Setup OpenStack Compute Node section.<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> $ yum install git -y<br /> <br /> Clone virtuozzo scripts:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Storage Cluster. <br /> <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show Virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the CONTROLLER node. Please read full script description here https://github.com/virtuozzo/virtuozzo-openstack-scripts/blob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.25 --password Virtuozzo1! --use_provider_network true --fixed_range 192.168.0.0/24 --floating_range 10.24.41.0/24 --floating_pool &quot;start=10.24.41.151,end=10.24.41.199&quot; --public_gateway 10.24.41.1 --gateway 192.168.0.1 --vzstorage vstorage1 --mode ALL <br /> <br /> Run the script on your CONTROLLER node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> Installation can take up to 30 minutes depending on your Internet connection speed. Finished!<br /> <br /> == Setup OpenStack Compute Node (*Developer/POC Setup*) ==<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> $ yum install git -y<br /> <br /> Clone Virtuozzo scripts to your COMPUTE node:<br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd /vz/virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Cluster. <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show the virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the COMPUTE node. Please read script description here https://github.com/virtuozzo/virtuozzo-openstack-scripblob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.26 --password Virtuozzo1! --use_provider_network true --mode COMPUTE --controller 10.24.41.25 <br /> <br /> Run the script on your COMPUTE node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> == How to change Virtualization Type to Virtual Machines on the Compute Node ==<br /> <br /> If you want to use virtual machines instead of containers on your compute node you need to change virtualization type to KVM on the selected compute node.<br /> <br /> Open nova configuration file:<br /> $ vi /etc/nova/nova.conf<br /> <br /> Change the following lines:<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = qcow2<br /> connection_uri = vz:///system<br /> <br /> Delete the line:<br /> inject_partition = -2<br /> <br /> Save the file.<br /> <br /> Restart nova-compute service:<br /> $ su stack<br /> $ screen -r<br /> Press Ctrl-c<br /> $ sg libvirtd '/usr/bin/nova-compute --config-file /etc/nova/nova.conf' &amp; echo $! &gt;/vz/stack/status/stack/n-cpu.pid; fg || echo &quot;n-cpu failed to start&quot; | tee &quot;/vz/stack/status/stack/n-cpu.failure&quot;<br /> <br /> To exit from screen session:<br /> Press Ctrl+a+d<br /> <br /> == How to redeploy OpenStack on the same nodes ==<br /> <br /> Your OpenStack setup will be reset after node restart. To redeploy OpenStack on the same nodes do the following:<br /> # &lt;code&gt;cd /vz/virtuozzo-openstack-scripts&lt;/code&gt;<br /> # &lt;code&gt;git pull&lt;/code&gt;<br /> # Run ./setup_devstack_vz7.sh with options you need.<br /> <br /> == Installing OpenStack with help of packstack on [[Virtuozzo]] 7 (*Production Setup*) == <br /> <br /> <br /> * Create a new repo file:<br /> <br /> cat &gt; /etc/yum.repos.d/virtuozzo-extra.repo &lt;&lt; _EOF<br /> [virtuozzo-extra]<br /> name=Virtuozzo Extra<br /> baseurl=http://repo.virtuozzo.com/openstack/newton/x86_64/os/<br /> enabled=1<br /> gpgcheck=1<br /> priority=50<br /> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-Virtuozzo-7<br /> _EOF<br /> <br /> * Add RDO repository:<br /> <br /> $ yum install https://rdoproject.org/repos/rdo-release.rpm<br /> <br /> * Install packstack package:<br /> <br /> $ yum install openstack-packstack<br /> <br /> * Download sample Vz7 packstack answer file:<br /> <br /> $ wget https://raw.githubusercontent.com/virtuozzo/virtuozzo-openstack-scripts/master/vz7-packstack-sample.txt<br /> <br /> * Edit vz7-packstack-sample.txt enabling/disabling necessary services. Also make sure you have correct IP addresses specified by the following parameters in the file:<br /> <br /> CONFIG_CONTROLLER_HOST<br /> CONFIG_COMPUTE_HOSTS<br /> CONFIG_NETWORK_HOSTS<br /> CONFIG_AMQP_HOST<br /> CONFIG_MARIADB_HOST<br /> CONFIG_REDIS_HOST<br /> <br /> * Change CONFIG_DEFAULT_PASSWORD parameter!!!<br /> * Then run packstack:<br /> <br /> $ packstack --answer-file vz7-packstack-sample.txt<br /> <br /> == Install and configure a nova controller node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:18--&gt;<br /> <br /> &lt;!--T:19--&gt;<br /> * Follow instructions on [http://docs.openstack.org/newton/install-guide-rdo/nova-controller-install.html OpenStack.org]<br /> * Change disk_formats string in /etc/glance/glance-api.conf so that it contains 'ploop'. Like this:<br /> <br /> disk_formats = ami,ari,aki,vhd,vmdk,raw,qcow2,vdi,iso,ploop<br /> <br /> * Restart glance-api service:<br /> <br /> systemctl restart openstack-glance-api.service<br /> <br /> * Download the container [http://updates.virtuozzo.com/server/virtuozzo/en_us/odin/7/techpreview-ct/centos7-exe.hds.tar.gz image]<br /> * Unpack it<br /> <br /> $ tar -xzvf centos7-exe.hds.tar.gz<br /> <br /> * Upload the image to glance:<br /> NOTE: this image was created for testing purposes only. Don't use it in production as is!<br /> <br /> $ glance image-create --name centos7-exe --disk-format ploop --container-format bare --property vm_mode=exe --property hypervisor_type=vz --property cinder_img_volume_type=vstorage-ploop --file centos7-exe.hds<br /> <br /> $ glance image-create --name centos7-hvm --disk-format qcow2 --container-format bare --property cinder_img_volume_type=vstorage-qcow2 --file CentOS-7-x86_64-GenericCloud.qcow2<br /> <br /> * CentOS image one can get from [http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.qcow2 here]<br /> <br /> == Install and configure a compute node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> Please use this chapter if you are going to run containers OR virtual machines on your compute node, but not containers AND virtual machines simultaneously. If you need to run containers and VMs simultaneously, please use next chapter.<br /> <br /> * Follow instructions on [http://docs.openstack.org/newton/install-guide-rdo/nova-compute-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> force_raw_images = False<br /> pointer_model = ps2mouse<br /> <br /> [libvirt]<br /> ...<br /> vzstorage_mount_group = root<br /> virt_type = parallels<br /> images_type = ploop<br /> connection_uri = vz:///system<br /> <br /> * Remove 'cpu_mode' parameter or set the following:<br /> <br /> cpu_mode=none<br /> <br /> * Then restart nova-compute service:<br /> <br /> $ systemctl restart openstack-nova-compute.service<br /> <br /> * If you plan to run Virtual Machines on your Compute node, change 'images_type' parameter to 'qcow2'<br /> <br /> == Install and configure a block storage node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> If you are going to run containers AND virtual machines simultaneously on your compute node you have to use this approach.<br /> <br /> * Follow instructions on [http://docs.openstack.org/mitaka/install-guide-rdo/cinder-controller-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/cinder/cinder.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> enabled_backends = lvmdriver-1,vstorage-ploop,vstorage-qcow2<br /> ...<br /> <br /> [vstorage-ploop]<br /> vzstorage_default_volume_format = ploop<br /> vzstorage_shares_config = /etc/cinder/vzstorage-shares-vstorage.conf<br /> volume_driver = cinder.volume.drivers.vzstorage.VZStorageDriver<br /> volume_backend_name = vstorage-ploop<br /> <br /> [vstorage-qcow2]<br /> vzstorage_default_volume_format = qcow2<br /> vzstorage_shares_config = /etc/cinder/vzstorage-shares-vstorage.conf<br /> volume_driver = cinder.volume.drivers.vzstorage.VZStorageDriver<br /> volume_backend_name = vstorage-qcow2<br /> <br /> * Create /etc/cinder/vzstorage-shares-vstorage.conf with the following content:<br /> <br /> YOUR-CLUSTER-NAME [&quot;-u&quot;, &quot;cinder&quot;, &quot;-g&quot;, &quot;root&quot;, &quot;-m&quot;, &quot;0770&quot;]<br /> <br /> * Create two new volume types:<br /> <br /> $ cinder type-create vstorage-qcow2<br /> $ cinder type-key vstorage-qcow2 set volume_backend_name=vstorage-qcow2<br /> <br /> $ cinder type-create vstorage-ploop<br /> $ cinder type-key vstorage-ploop set volume_backend_name=vstorage-ploop<br /> <br /> * Create directory for storage logs:<br /> <br /> $ mkdir /var/log/pstorage<br /> <br /> * Authenticate your Virtuozzo Storage client nodes in oreser to allow them to mount cluster:<br /> <br /> $ echo $CLUSTER_PASSWD | vstorage auth-node -c cc -P<br /> <br /> * Then restart cinder services:<br /> <br /> $ systemctl restart openstack-cinder-api<br /> $ systemctl restart openstack-cinder-scheduler<br /> $ systemctl restart openstack-cinder-volume<br /> <br /> == How to create a new image ploop image ready to upload to Glance == &lt;!--T:17--&gt;<br /> <br /> * Select os template. The following templates are possible: vzlinux-7, centos-7, ubuntu-16.04, ubuntu-14.04, debian-8.0, centos-6, debian-8.0-x86_64-minimal<br /> <br /> $ ct=centos-7<br /> <br /> * Create a new container based on necessary os distribution<br /> <br /> $ prlctl create glance-$ct --vmtype ct --ostemplate $ct<br /> <br /> * Set IP address and DNS to be able to connect to internet from the container<br /> <br /> $ prlctl set glance-$ct --ipadd IPADDR --nameserver DNS_IPADDR<br /> <br /> * Add additional network adapter<br /> <br /> $ prlctl set glance-$ct --device-add net --network Bridged --dhcp on<br /> <br /> * Start the container<br /> <br /> $ prlctl start glance-$ct<br /> <br /> * Install cloud-init packet<br /> <br /> $ prlctl exec glance-$ct yum install cloud-init -y<br /> <br /> * Remove the following modules from cloud.cfg<br /> <br /> $ prlctl exec glance-$ct sed -i '/- growpart/d' /etc/cloud/cloud.cfg<br /> $ prlctl exec glance-$ct sed -i '/- resizefs/d' /etc/cloud/cloud.cfg<br /> <br /> * Prepare network scripts<br /> <br /> cat &gt; /etc/sysconfig/network-scripts/ifcfg-eth0 &lt;&lt; _EOF<br /> DEVICE=eth0<br /> ONBOOT=yes<br /> NM_CONTROLLED=no<br /> BOOTPROTO=dhcp<br /> _EOF<br /> <br /> * If you need more than one network adapters withing a container, make as many copies as you need <br /> <br /> $ prlctl exec glance-$ct cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1<br /> $ prlctl exec glance-$ct sed -i '/eth0/eth1' /etc/sysconfig/network-scripts/ifcfg-eth1<br /> <br /> * Perform some cleanup<br /> <br /> $ rm -f /etc/sysconfig/network-scripts/ifcfg-venet0*<br /> $ rm -f /etc/resolv.conf<br /> <br /> * Stop the container<br /> <br /> $ prlctl stop glance-$ct<br /> <br /> * Create ploop disk and copy files<br /> <br /> $ mkdir /tmp/ploop-$ct<br /> $ ploop init -s 950M /tmp/ploop-$ct/$ct.hds<br /> $ mkdir /tmp/ploop-$ct/dst<br /> $ ploop mount -m /tmp/ploop-$ct/dst /tmp/ploop-$ct/DiskDescriptor.xml<br /> $ prlctl mount glance-$ct<br /> $ id=$(vzlist glance-$ct | awk ' NR&gt;1 { print $1 }')<br /> $ cp -Pr --preserve=all /vz/root/$id/* /tmp/ploop-$ct/dst/<br /> $ prlctl umount glance-$ct<br /> $ ploop umount -m /tmp/ploop-$ct/dst/<br /> <br /> * Now the image tmp/ploop-$ct/$ct.hds is ready to be uploaded to Glance<br /> <br /> == See also == &lt;!--T:100--&gt;<br /> * [http://docs.openstack.org/newton/install-guide-rdo/nova-controller-install.html Controller Node Installation Guide]<br /> * [http://docs.openstack.org/newton/install-guide-rdo/nova-compute-install.html Compute Node Installation Guide]<br /> * [http://docs.openstack.org/newton/install-guide-rdo/environment-packages.html OpenStack Installation Guide]<br /> * [https://docs.openvz.org/ Virtuozzo Documentation]<br /> * [[Virtuozzo ecosystem]]<br /> <br /> &lt;/translate&gt;<br /> <br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Setup_OpenStack_with_Virtuozzo_7&diff=22553 2017-03-01T14:59:27Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> This article describes how to install OpenStack on [[Virtuozzo]] 7.<br /> == Introduction ==<br /> <br /> Virtuozzo 7 supports OpenStack as cloud management solution since version 6. With Virtuozzo 7 we are going to add a lot of new capabilities to OpenStack integration. <br /> <br /> This guide describes two ways of installing OpenStack on Virtuozzo nodes. The first is for quick/development/POC needs. The second is for production. Please keep in mind that devstack allows you to install OpenStack for demo/POC/development purposes only. That means it will be reset after host reboot.<br /> <br /> You need the following infrastructure to setup OpenStack with Virtuozzo 7:<br /> #controller host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a controller and Virtuozzo containers host.<br /> #compute host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a virtual machines host.<br /> <br /> == Prerequisites ==<br /> <br /> You need to install and update your Virtuozzo nodes first. Install Virtuozzo 7 on your controller and compute hosts as usual. You can use basic (local) or Virtuozzo Storage. Update Virtuozzo hosts<br /> $ yum update -y<br /> <br /> If you have br0 bridge configured as an IP interface, then you should move an IP address assigned to it to the physical ethernet interface bridged to br0.<br /> You can check you configuration with the following command:<br /> <br /> $ if=$(brctl show | grep '^br0' | awk ' { print $4 }') &amp;&amp; addr=$(ip addr | grep -w 'br0' | grep inet | awk ' {print $2} ') &amp;&amp; gw=$(ip route | grep default | awk ' { print $3 } ') &amp;&amp; echo &quot;My interface is '$if', gateway is '$gw', IP address '$addr'&quot;<br /> <br /> For instance you have the following output after execution the above script:<br /> <br /> My interface is 'en33', gateway is '192.168.190.2', IP address '192.168.190.134/24'.<br /> <br /> Then edit your /etc/sysconfig/network-scripts/ifcfg-ens33 to have the following content and remove BRIDGE=&quot;br0&quot; string from it:<br /> ...<br /> ONBOOT=yes<br /> IPADDR=192.168.190.134<br /> GATEWAY=192.168.190.2<br /> PREFIX=24<br /> ...<br /> <br /> Remove /etc/sysconfig/network-scripts/ifcfg-br0 file.<br /> <br /> $ rm /etc/sysconfig/network-scripts/ifcfg-br0<br /> <br /> Then restart network service:<br /> <br /> $ systemctl restart network<br /> <br /> == Setup OpenStack Controller Node with Virtuozzo Containers Support (*Developer/POC Setup*) == &lt;!--T:1--&gt;<br /> <br /> &lt;!--T:3--&gt;<br /> You are able to setup OpenStack controller node together with compute node on the same server for demo or test purpose. In this case compute node with Virtuozzo Containers support will be deployed. You can add another compute node with containers or VMs anytime you want as described in Setup OpenStack Compute Node section.<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> $ yum install git -y<br /> <br /> Clone virtuozzo scripts:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Storage Cluster. <br /> <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show Virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the CONTROLLER node. Please read full script description here https://github.com/virtuozzo/virtuozzo-openstack-scripts/blob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.25 --password Virtuozzo1! --use_provider_network true --fixed_range 192.168.0.0/24 --floating_range 10.24.41.0/24 --floating_pool &quot;start=10.24.41.151,end=10.24.41.199&quot; --public_gateway 10.24.41.1 --gateway 192.168.0.1 --vzstorage vstorage1 --mode ALL <br /> <br /> Run the script on your CONTROLLER node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> Installation can take up to 30 minutes depending on your Internet connection speed. Finished!<br /> <br /> == Setup OpenStack Compute Node (*Developer/POC Setup*) ==<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> $ yum install git -y<br /> <br /> Clone Virtuozzo scripts to your COMPUTE node:<br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd /vz/virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Cluster. <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show the virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the COMPUTE node. Please read script description here https://github.com/virtuozzo/virtuozzo-openstack-scripblob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.26 --password Virtuozzo1! --use_provider_network true --mode COMPUTE --controller 10.24.41.25 <br /> <br /> Run the script on your COMPUTE node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> == How to change Virtualization Type to Virtual Machines on the Compute Node ==<br /> <br /> If you want to use virtual machines instead of containers on your compute node you need to change virtualization type to KVM on the selected compute node.<br /> <br /> Open nova configuration file:<br /> $ vi /etc/nova/nova.conf<br /> <br /> Change the following lines:<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = qcow2<br /> connection_uri = vz:///system<br /> <br /> Delete the line:<br /> inject_partition = -2<br /> <br /> Save the file.<br /> <br /> Restart nova-compute service:<br /> $ su stack<br /> $ screen -r<br /> Press Ctrl-c<br /> $ sg libvirtd '/usr/bin/nova-compute --config-file /etc/nova/nova.conf' &amp; echo $! &gt;/vz/stack/status/stack/n-cpu.pid; fg || echo &quot;n-cpu failed to start&quot; | tee &quot;/vz/stack/status/stack/n-cpu.failure&quot;<br /> <br /> To exit from screen session:<br /> Press Ctrl+a+d<br /> <br /> == How to redeploy OpenStack on the same nodes ==<br /> <br /> Your OpenStack setup will be reset after node restart. To redeploy OpenStack on the same nodes do the following:<br /> # &lt;code&gt;cd /vz/virtuozzo-openstack-scripts&lt;/code&gt;<br /> # &lt;code&gt;git pull&lt;/code&gt;<br /> # Run ./setup_devstack_vz7.sh with options you need.<br /> <br /> == Installing OpenStack with help of packstack on [[Virtuozzo]] 7 (*Production Setup*) == <br /> <br /> <br /> * Create a new repo file:<br /> <br /> cat &gt; /etc/yum.repos.d/virtuozzo-extra.repo &lt;&lt; _EOF<br /> [virtuozzo-extra]<br /> name=Virtuozzo Extra<br /> baseurl=http://repo.virtuozzo.com/openstack/newton/x86_64/os/<br /> enabled=1<br /> gpgcheck=1<br /> priority=50<br /> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-Virtuozzo-7<br /> _EOF<br /> <br /> * Add RDO repository:<br /> <br /> $ yum install https://rdoproject.org/repos/rdo-release.rpm<br /> <br /> * Install packstack package:<br /> <br /> $ yum install openstack-packstack<br /> <br /> * Download sample Vz7 packstack answer file:<br /> <br /> $ wget https://raw.githubusercontent.com/virtuozzo/virtuozzo-openstack-scripts/master/vz7-packstack-sample.txt<br /> <br /> * Edit vz7-packstack-sample.txt enabling/disabling necessary services. Also make sure you have correct IP addresses specified by the following parameters in the file:<br /> <br /> CONFIG_CONTROLLER_HOST<br /> CONFIG_COMPUTE_HOSTS<br /> CONFIG_NETWORK_HOSTS<br /> CONFIG_AMQP_HOST<br /> CONFIG_MARIADB_HOST<br /> CONFIG_REDIS_HOST<br /> <br /> * Change CONFIG_DEFAULT_PASSWORD parameter!!!<br /> * Then run packstack:<br /> <br /> $ packstack --answer-file vz7-packstack-sample.txt<br /> <br /> == Install and configure a nova controller node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:18--&gt;<br /> <br /> &lt;!--T:19--&gt;<br /> * Follow instructions on [http://docs.openstack.org/newton/install-guide-rdo/nova-controller-install.html OpenStack.org]<br /> * Change disk_formats string in /etc/glance/glance-api.conf so that it contains 'ploop'. Like this:<br /> <br /> disk_formats = ami,ari,aki,vhd,vmdk,raw,qcow2,vdi,iso,ploop<br /> <br /> * Restart glance-api service:<br /> <br /> systemctl restart openstack-glance-api.service<br /> <br /> * Download the container [http://updates.virtuozzo.com/server/virtuozzo/en_us/odin/7/techpreview-ct/centos7-exe.hds.tar.gz image]<br /> * Unpack it<br /> <br /> $ tar -xzvf centos7-exe.hds.tar.gz<br /> <br /> * Upload the image to glance:<br /> NOTE: this image was created for testing purposes only. Don't use it in production as is!<br /> <br /> $ glance image-create --name centos7-exe --disk-format ploop --container-format bare --property vm_mode=exe --property hypervisor_type=vz --property cinder_img_volume_type=vstorage-ploop --file centos7-exe.hds<br /> <br /> $ glance image-create --name centos7-hvm --disk-format qcow2 --container-format bare --property cinder_img_volume_type=vstorage-qcow2 --file CentOS-7-x86_64-GenericCloud.qcow2<br /> <br /> * CentOS image one can get from [http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.qcow2 here]<br /> <br /> == Install and configure a compute node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> Please use this chapter if you are going to run containers OR virtual machines on your compute node, but not containers AND virtual machines simultaneously. If you need to run containers and VMs simultaneously, please use next chapter.<br /> <br /> * Follow instructions on [http://docs.openstack.org/newton/install-guide-rdo/nova-compute-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> force_raw_images = False<br /> pointer_model = ps2mouse<br /> <br /> [libvirt]<br /> ...<br /> vzstorage_mount_group = root<br /> virt_type = parallels<br /> images_type = ploop<br /> connection_uri = vz:///system<br /> <br /> * Remove 'cpu_mode' parameter or set the following:<br /> <br /> cpu_mode=none<br /> <br /> * Then restart nova-compute service:<br /> <br /> $ systemctl restart openstack-nova-compute.service<br /> <br /> * If you plan to run Virtual Machines on your Compute node, change 'images_type' parameter to 'qcow2'<br /> <br /> == Install and configure a block storage node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/mitaka/install-guide-rdo/cinder-controller-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/cinder/cinder.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> enabled_backends = lvmdriver-1,vstorage-ploop,vstorage-qcow2<br /> ...<br /> <br /> [vstorage-ploop]<br /> vzstorage_default_volume_format = ploop<br /> vzstorage_shares_config = /etc/cinder/vzstorage-shares-vstorage.conf<br /> volume_driver = cinder.volume.drivers.vzstorage.VZStorageDriver<br /> volume_backend_name = vstorage-ploop<br /> <br /> [vstorage-qcow2]<br /> vzstorage_default_volume_format = qcow2<br /> vzstorage_shares_config = /etc/cinder/vzstorage-shares-vstorage.conf<br /> volume_driver = cinder.volume.drivers.vzstorage.VZStorageDriver<br /> volume_backend_name = vstorage-qcow2<br /> <br /> * Create /etc/cinder/vzstorage-shares-vstorage.conf with the following content:<br /> <br /> YOUR-CLUSTER-NAME [&quot;-u&quot;, &quot;cinder&quot;, &quot;-g&quot;, &quot;root&quot;, &quot;-m&quot;, &quot;0770&quot;]<br /> <br /> * Create two new volume types:<br /> <br /> $ cinder type-create vstorage-qcow2<br /> $ cinder type-key vstorage-qcow2 set volume_backend_name=vstorage-qcow2<br /> <br /> $ cinder type-create vstorage-ploop<br /> $ cinder type-key vstorage-ploop set volume_backend_name=vstorage-ploop<br /> <br /> * Create directory for storage logs:<br /> <br /> $ mkdir /var/log/pstorage<br /> <br /> * Authenticate your Virtuozzo Storage client nodes in oreser to allow them to mount cluster:<br /> <br /> $ echo $CLUSTER_PASSWD | vstorage auth-node -c cc -P<br /> <br /> * Then restart cinder services:<br /> <br /> $ systemctl restart openstack-cinder-api<br /> $ systemctl restart openstack-cinder-scheduler<br /> $ systemctl restart openstack-cinder-volume<br /> <br /> == How to create a new image ploop image ready to upload to Glance == &lt;!--T:17--&gt;<br /> <br /> * Select os template. The following templates are possible: vzlinux-7, centos-7, ubuntu-16.04, ubuntu-14.04, debian-8.0, centos-6, debian-8.0-x86_64-minimal<br /> <br /> $ ct=centos-7<br /> <br /> * Create a new container based on necessary os distribution<br /> <br /> $ prlctl create glance-$ct --vmtype ct --ostemplate $ct<br /> <br /> * Set IP address and DNS to be able to connect to internet from the container<br /> <br /> $ prlctl set glance-$ct --ipadd IPADDR --nameserver DNS_IPADDR<br /> <br /> * Add additional network adapter<br /> <br /> $ prlctl set glance-$ct --device-add net --network Bridged --dhcp on<br /> <br /> * Start the container<br /> <br /> $ prlctl start glance-$ct<br /> <br /> * Install cloud-init packet<br /> <br /> $ prlctl exec glance-$ct yum install cloud-init -y<br /> <br /> * Remove the following modules from cloud.cfg<br /> <br /> $ prlctl exec glance-$ct sed -i '/- growpart/d' /etc/cloud/cloud.cfg<br /> $ prlctl exec glance-$ct sed -i '/- resizefs/d' /etc/cloud/cloud.cfg<br /> <br /> * Prepare network scripts<br /> <br /> cat &gt; /etc/sysconfig/network-scripts/ifcfg-eth0 &lt;&lt; _EOF<br /> DEVICE=eth0<br /> ONBOOT=yes<br /> NM_CONTROLLED=no<br /> BOOTPROTO=dhcp<br /> _EOF<br /> <br /> * If you need more than one network adapters withing a container, make as many copies as you need <br /> <br /> $ prlctl exec glance-$ct cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1<br /> $ prlctl exec glance-$ct sed -i '/eth0/eth1' /etc/sysconfig/network-scripts/ifcfg-eth1<br /> <br /> * Perform some cleanup<br /> <br /> $ rm -f /etc/sysconfig/network-scripts/ifcfg-venet0*<br /> $ rm -f /etc/resolv.conf<br /> <br /> * Stop the container<br /> <br /> $ prlctl stop glance-$ct<br /> <br /> * Create ploop disk and copy files<br /> <br /> $ mkdir /tmp/ploop-$ct<br /> $ ploop init -s 950M /tmp/ploop-$ct/$ct.hds<br /> $ mkdir /tmp/ploop-$ct/dst<br /> $ ploop mount -m /tmp/ploop-$ct/dst /tmp/ploop-$ct/DiskDescriptor.xml<br /> $ prlctl mount glance-$ct<br /> $ id=$(vzlist glance-$ct | awk ' NR&gt;1 { print $1 }')<br /> $ cp -Pr --preserve=all /vz/root/$id/* /tmp/ploop-$ct/dst/<br /> $ prlctl umount glance-$ct<br /> $ ploop umount -m /tmp/ploop-$ct/dst/<br /> <br /> * Now the image tmp/ploop-$ct/$ct.hds is ready to be uploaded to Glance<br /> <br /> == See also == &lt;!--T:100--&gt;<br /> * [http://docs.openstack.org/newton/install-guide-rdo/nova-controller-install.html Controller Node Installation Guide]<br /> * [http://docs.openstack.org/newton/install-guide-rdo/nova-compute-install.html Compute Node Installation Guide]<br /> * [http://docs.openstack.org/newton/install-guide-rdo/environment-packages.html OpenStack Installation Guide]<br /> * [https://docs.openvz.org/ Virtuozzo Documentation]<br /> * [[Virtuozzo ecosystem]]<br /> <br /> &lt;/translate&gt;<br /> <br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Setup_OpenStack_with_Virtuozzo_7&diff=22552 2017-03-01T14:59:08Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> This article describes how to install OpenStack on [[Virtuozzo]] 7.<br /> == Introduction ==<br /> <br /> Virtuozzo 7 supports OpenStack as cloud management solution since version 6. With Virtuozzo 7 we are going to add a lot of new capabilities to OpenStack integration. <br /> <br /> This guide describes two ways of installing OpenStack on Virtuozzo nodes. The first is for quick/development/POC needs. The second is for production. Please keep in mind that devstack allows you to install OpenStack for demo/POC/development purposes only. That means it will be reset after host reboot.<br /> <br /> You need the following infrastructure to setup OpenStack with Virtuozzo 7:<br /> #controller host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a controller and Virtuozzo containers host.<br /> #compute host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a virtual machines host.<br /> <br /> == Prerequisites ==<br /> <br /> You need to install and update your Virtuozzo nodes first. Install Virtuozzo 7 on your controller and compute hosts as usual. You can use basic (local) or Virtuozzo Storage. Update Virtuozzo hosts<br /> $ yum update -y<br /> <br /> If you have br0 bridge configured as an IP interface, then you should move an IP address assigned to it to the physical ethernet interface bridged to br0.<br /> You can check you configuration with the following command:<br /> <br /> $ if=$(brctl show | grep '^br0' | awk ' { print $4 }') &amp;&amp; addr=$(ip addr | grep -w 'br0' | grep inet | awk ' {print $2} ') &amp;&amp; gw=$(ip route | grep default | awk ' { print $3 } ') &amp;&amp; echo &quot;My interface is '$if', gateway is '$gw', IP address '$addr'&quot;<br /> <br /> For instance you have the following output after execution the above script:<br /> <br /> My interface is 'en33', gateway is '192.168.190.2', IP address '192.168.190.134/24'.<br /> <br /> Then edit your /etc/sysconfig/network-scripts/ifcfg-ens33 to have the following content and remove BRIDGE=&quot;br0&quot; string from it:<br /> ...<br /> ONBOOT=yes<br /> IPADDR=192.168.190.134<br /> GATEWAY=192.168.190.2<br /> PREFIX=24<br /> ...<br /> <br /> Remove /etc/sysconfig/network-scripts/ifcfg-br0 file.<br /> <br /> $ rm /etc/sysconfig/network-scripts/ifcfg-br0<br /> <br /> Then restart network service:<br /> <br /> $ systemctl restart network<br /> <br /> == Setup OpenStack Controller Node with Virtuozzo Containers Support (*Developer/POC Setup*) == &lt;!--T:1--&gt;<br /> <br /> &lt;!--T:3--&gt;<br /> You are able to setup OpenStack controller node together with compute node on the same server for demo or test purpose. In this case compute node with Virtuozzo Containers support will be deployed. You can add another compute node with containers or VMs anytime you want as described in Setup OpenStack Compute Node section.<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> $ yum install git -y<br /> <br /> Clone virtuozzo scripts:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Storage Cluster. <br /> <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show Virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the CONTROLLER node. Please read full script description here https://github.com/virtuozzo/virtuozzo-openstack-scripts/blob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.25 --password Virtuozzo1! --use_provider_network true --fixed_range 192.168.0.0/24 --floating_range 10.24.41.0/24 --floating_pool &quot;start=10.24.41.151,end=10.24.41.199&quot; --public_gateway 10.24.41.1 --gateway 192.168.0.1 --vzstorage vstorage1 --mode ALL <br /> <br /> Run the script on your CONTROLLER node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> Installation can take up to 30 minutes depending on your Internet connection speed. Finished!<br /> <br /> == Setup OpenStack Compute Node (*Developer/POC Setup*) ==<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> $ yum install git -y<br /> <br /> Clone Virtuozzo scripts to your COMPUTE node:<br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd /vz/virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Cluster. <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show the virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the COMPUTE node. Please read script description here https://github.com/virtuozzo/virtuozzo-openstack-scripblob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.26 --password Virtuozzo1! --use_provider_network true --mode COMPUTE --controller 10.24.41.25 <br /> <br /> Run the script on your COMPUTE node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> == How to change Virtualization Type to Virtual Machines on the Compute Node ==<br /> <br /> If you want to use virtual machines instead of containers on your compute node you need to change virtualization type to KVM on the selected compute node.<br /> <br /> Open nova configuration file:<br /> $ vi /etc/nova/nova.conf<br /> <br /> Change the following lines:<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = qcow2<br /> connection_uri = vz:///system<br /> <br /> Delete the line:<br /> inject_partition = -2<br /> <br /> Save the file.<br /> <br /> Restart nova-compute service:<br /> $ su stack<br /> $ screen -r<br /> Press Ctrl-c<br /> $ sg libvirtd '/usr/bin/nova-compute --config-file /etc/nova/nova.conf' &amp; echo $! &gt;/vz/stack/status/stack/n-cpu.pid; fg || echo &quot;n-cpu failed to start&quot; | tee &quot;/vz/stack/status/stack/n-cpu.failure&quot;<br /> <br /> To exit from screen session:<br /> Press Ctrl+a+d<br /> <br /> == How to redeploy OpenStack on the same nodes ==<br /> <br /> Your OpenStack setup will be reset after node restart. To redeploy OpenStack on the same nodes do the following:<br /> # &lt;code&gt;cd /vz/virtuozzo-openstack-scripts&lt;/code&gt;<br /> # &lt;code&gt;git pull&lt;/code&gt;<br /> # Run ./setup_devstack_vz7.sh with options you need.<br /> <br /> == Installing OpenStack with help of packstack on [[Virtuozzo]] 7 (*Production Setup*) == <br /> <br /> <br /> * Create a new repo file:<br /> <br /> cat &gt; /etc/yum.repos.d/virtuozzo-extra.repo &lt;&lt; _EOF<br /> [virtuozzo-extra]<br /> name=Virtuozzo Extra<br /> baseurl=http://repo.virtuozzo.com/openstack/newton/x86_64/os/<br /> enabled=1<br /> gpgcheck=1<br /> priority=50<br /> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-Virtuozzo-7<br /> _EOF<br /> <br /> * Add RDO repository:<br /> <br /> $ yum install https://rdoproject.org/repos/rdo-release.rpm<br /> <br /> * Install packstack package:<br /> <br /> $ yum install openstack-packstack<br /> <br /> * Download sample Vz7 packstack answer file:<br /> <br /> $ wget https://raw.githubusercontent.com/virtuozzo/virtuozzo-openstack-scripts/master/vz7-packstack-sample.txt<br /> <br /> * Edit vz7-packstack-sample.txt enabling/disabling necessary services. Also make sure you have correct IP addresses specified by the following parameters in the file:<br /> <br /> CONFIG_CONTROLLER_HOST<br /> CONFIG_COMPUTE_HOSTS<br /> CONFIG_NETWORK_HOSTS<br /> CONFIG_AMQP_HOST<br /> CONFIG_MARIADB_HOST<br /> CONFIG_REDIS_HOST<br /> <br /> * Change CONFIG_DEFAULT_PASSWORD parameter!!!<br /> * Then run packstack:<br /> <br /> $ packstack --answer-file vz7-packstack-sample.txt<br /> <br /> == Install and configure a nova controller node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:18--&gt;<br /> <br /> &lt;!--T:19--&gt;<br /> * Follow instructions on [http://docs.openstack.org/newton/install-guide-rdo/nova-controller-install.html OpenStack.org]<br /> * Change disk_formats string in /etc/glance/glance-api.conf so that it contains 'ploop'. Like this:<br /> <br /> disk_formats = ami,ari,aki,vhd,vmdk,raw,qcow2,vdi,iso,ploop<br /> <br /> * Restart glance-api service:<br /> <br /> systemctl restart openstack-glance-api.service<br /> <br /> * Download the container [http://updates.virtuozzo.com/server/virtuozzo/en_us/odin/7/techpreview-ct/centos7-exe.hds.tar.gz image]<br /> * Unpack it<br /> <br /> $ tar -xzvf centos7-exe.hds.tar.gz<br /> <br /> * Upload the image to glance:<br /> NOTE: this image was created for testing purposes only. Don't use it in production as is!<br /> <br /> $ glance image-create --name centos7-exe --disk-format ploop --container-format bare --property vm_mode=exe --property hypervisor_type=vz --property cinder_img_volume_type=vstorage-ploop --file centos7-exe.hds<br /> <br /> $ glance image-create --name centos7-hvm --disk-format qcow2 --container-format bare --property cinder_img_volume_type=vstorage-qcow2 --file CentOS-7-x86_64-GenericCloud.qcow2<br /> <br /> * CentOS image one can get from [http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.qcow2 here]<br /> <br /> == Install and configure a compute node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/newton/install-guide-rdo/nova-compute-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> force_raw_images = False<br /> pointer_model = ps2mouse<br /> <br /> [libvirt]<br /> ...<br /> vzstorage_mount_group = root<br /> virt_type = parallels<br /> images_type = ploop<br /> connection_uri = vz:///system<br /> <br /> * Remove 'cpu_mode' parameter or set the following:<br /> <br /> cpu_mode=none<br /> <br /> * Then restart nova-compute service:<br /> <br /> $ systemctl restart openstack-nova-compute.service<br /> <br /> * If you plan to run Virtual Machines on your Compute node, change 'images_type' parameter to 'qcow2'<br /> <br /> == Install and configure a block storage node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/mitaka/install-guide-rdo/cinder-controller-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/cinder/cinder.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> enabled_backends = lvmdriver-1,vstorage-ploop,vstorage-qcow2<br /> ...<br /> <br /> [vstorage-ploop]<br /> vzstorage_default_volume_format = ploop<br /> vzstorage_shares_config = /etc/cinder/vzstorage-shares-vstorage.conf<br /> volume_driver = cinder.volume.drivers.vzstorage.VZStorageDriver<br /> volume_backend_name = vstorage-ploop<br /> <br /> [vstorage-qcow2]<br /> vzstorage_default_volume_format = qcow2<br /> vzstorage_shares_config = /etc/cinder/vzstorage-shares-vstorage.conf<br /> volume_driver = cinder.volume.drivers.vzstorage.VZStorageDriver<br /> volume_backend_name = vstorage-qcow2<br /> <br /> * Create /etc/cinder/vzstorage-shares-vstorage.conf with the following content:<br /> <br /> YOUR-CLUSTER-NAME [&quot;-u&quot;, &quot;cinder&quot;, &quot;-g&quot;, &quot;root&quot;, &quot;-m&quot;, &quot;0770&quot;]<br /> <br /> * Create two new volume types:<br /> <br /> $ cinder type-create vstorage-qcow2<br /> $ cinder type-key vstorage-qcow2 set volume_backend_name=vstorage-qcow2<br /> <br /> $ cinder type-create vstorage-ploop<br /> $ cinder type-key vstorage-ploop set volume_backend_name=vstorage-ploop<br /> <br /> * Create directory for storage logs:<br /> <br /> $ mkdir /var/log/pstorage<br /> <br /> * Authenticate your Virtuozzo Storage client nodes in oreser to allow them to mount cluster:<br /> <br /> $ echo $CLUSTER_PASSWD | vstorage auth-node -c cc -P<br /> <br /> * Then restart cinder services:<br /> <br /> $ systemctl restart openstack-cinder-api<br /> $ systemctl restart openstack-cinder-scheduler<br /> $ systemctl restart openstack-cinder-volume<br /> <br /> == How to create a new image ploop image ready to upload to Glance == &lt;!--T:17--&gt;<br /> <br /> * Select os template. The following templates are possible: vzlinux-7, centos-7, ubuntu-16.04, ubuntu-14.04, debian-8.0, centos-6, debian-8.0-x86_64-minimal<br /> <br /> $ ct=centos-7<br /> <br /> * Create a new container based on necessary os distribution<br /> <br /> $ prlctl create glance-$ct --vmtype ct --ostemplate $ct<br /> <br /> * Set IP address and DNS to be able to connect to internet from the container<br /> <br /> $ prlctl set glance-$ct --ipadd IPADDR --nameserver DNS_IPADDR<br /> <br /> * Add additional network adapter<br /> <br /> $ prlctl set glance-$ct --device-add net --network Bridged --dhcp on<br /> <br /> * Start the container<br /> <br /> $ prlctl start glance-$ct<br /> <br /> * Install cloud-init packet<br /> <br /> $ prlctl exec glance-$ct yum install cloud-init -y<br /> <br /> * Remove the following modules from cloud.cfg<br /> <br /> $ prlctl exec glance-$ct sed -i '/- growpart/d' /etc/cloud/cloud.cfg<br /> $ prlctl exec glance-$ct sed -i '/- resizefs/d' /etc/cloud/cloud.cfg<br /> <br /> * Prepare network scripts<br /> <br /> cat &gt; /etc/sysconfig/network-scripts/ifcfg-eth0 &lt;&lt; _EOF<br /> DEVICE=eth0<br /> ONBOOT=yes<br /> NM_CONTROLLED=no<br /> BOOTPROTO=dhcp<br /> _EOF<br /> <br /> * If you need more than one network adapters withing a container, make as many copies as you need <br /> <br /> $ prlctl exec glance-$ct cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1<br /> $ prlctl exec glance-$ct sed -i '/eth0/eth1' /etc/sysconfig/network-scripts/ifcfg-eth1<br /> <br /> * Perform some cleanup<br /> <br /> $ rm -f /etc/sysconfig/network-scripts/ifcfg-venet0*<br /> $ rm -f /etc/resolv.conf<br /> <br /> * Stop the container<br /> <br /> $ prlctl stop glance-$ct<br /> <br /> * Create ploop disk and copy files<br /> <br /> $ mkdir /tmp/ploop-$ct<br /> $ ploop init -s 950M /tmp/ploop-$ct/$ct.hds<br /> $ mkdir /tmp/ploop-$ct/dst<br /> $ ploop mount -m /tmp/ploop-$ct/dst /tmp/ploop-$ct/DiskDescriptor.xml<br /> $ prlctl mount glance-$ct<br /> $ id=$(vzlist glance-$ct | awk ' NR&gt;1 { print $1 }')<br /> $ cp -Pr --preserve=all /vz/root/$id/* /tmp/ploop-$ct/dst/<br /> $ prlctl umount glance-$ct<br /> $ ploop umount -m /tmp/ploop-$ct/dst/<br /> <br /> * Now the image tmp/ploop-$ct/$ct.hds is ready to be uploaded to Glance<br /> <br /> == See also == &lt;!--T:100--&gt;<br /> * [http://docs.openstack.org/newton/install-guide-rdo/nova-controller-install.html Controller Node Installation Guide]<br /> * [http://docs.openstack.org/newton/install-guide-rdo/nova-compute-install.html Compute Node Installation Guide]<br /> * [http://docs.openstack.org/newton/install-guide-rdo/environment-packages.html OpenStack Installation Guide]<br /> * [https://docs.openvz.org/ Virtuozzo Documentation]<br /> * [[Virtuozzo ecosystem]]<br /> <br /> &lt;/translate&gt;<br /> <br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Setup_OpenStack_with_Virtuozzo_7&diff=22551 2017-03-01T14:58:23Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> This article describes how to install OpenStack on [[Virtuozzo]] 7.<br /> == Introduction ==<br /> <br /> Virtuozzo 7 supports OpenStack as cloud management solution since version 6. With Virtuozzo 7 we are going to add a lot of new capabilities to OpenStack integration. <br /> <br /> This guide describes two ways of installing OpenStack on Virtuozzo nodes. The first is for quick/development/POC needs. The second is for production. Please keep in mind that devstack allows you to install OpenStack for demo/POC/development purposes only. That means it will be reset after host reboot.<br /> <br /> You need the following infrastructure to setup OpenStack with Virtuozzo 7:<br /> #controller host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a controller and Virtuozzo containers host.<br /> #compute host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a virtual machines host.<br /> <br /> == Prerequisites ==<br /> <br /> You need to install and update your Virtuozzo nodes first. Install Virtuozzo 7 on your controller and compute hosts as usual. You can use basic (local) or Virtuozzo Storage. Update Virtuozzo hosts<br /> $ yum update -y<br /> <br /> If you have br0 bridge configured as an IP interface, then you should move an IP address assigned to it to the physical ethernet interface bridged to br0.<br /> You can check you configuration with the following command:<br /> <br /> $ if=$(brctl show | grep '^br0' | awk ' { print $4 }') &amp;&amp; addr=$(ip addr | grep -w 'br0' | grep inet | awk ' {print $2} ') &amp;&amp; gw=$(ip route | grep default | awk ' { print $3 } ') &amp;&amp; echo &quot;My interface is '$if', gateway is '$gw', IP address '$addr'&quot;<br /> <br /> For instance you have the following output after execution the above script:<br /> <br /> My interface is 'en33', gateway is '192.168.190.2', IP address '192.168.190.134/24'.<br /> <br /> Then edit your /etc/sysconfig/network-scripts/ifcfg-ens33 to have the following content and remove BRIDGE=&quot;br0&quot; string from it:<br /> ...<br /> ONBOOT=yes<br /> IPADDR=192.168.190.134<br /> GATEWAY=192.168.190.2<br /> PREFIX=24<br /> ...<br /> <br /> Remove /etc/sysconfig/network-scripts/ifcfg-br0 file.<br /> <br /> $ rm /etc/sysconfig/network-scripts/ifcfg-br0<br /> <br /> Then restart network service:<br /> <br /> $ systemctl restart network<br /> <br /> == Setup OpenStack Controller Node with Virtuozzo Containers Support (*Developer/POC Setup*) == &lt;!--T:1--&gt;<br /> <br /> &lt;!--T:3--&gt;<br /> You are able to setup OpenStack controller node together with compute node on the same server for demo or test purpose. In this case compute node with Virtuozzo Containers support will be deployed. You can add another compute node with containers or VMs anytime you want as described in Setup OpenStack Compute Node section.<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> $ yum install git -y<br /> <br /> Clone virtuozzo scripts:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Storage Cluster. <br /> <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show Virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the CONTROLLER node. Please read full script description here https://github.com/virtuozzo/virtuozzo-openstack-scripts/blob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.25 --password Virtuozzo1! --use_provider_network true --fixed_range 192.168.0.0/24 --floating_range 10.24.41.0/24 --floating_pool &quot;start=10.24.41.151,end=10.24.41.199&quot; --public_gateway 10.24.41.1 --gateway 192.168.0.1 --vzstorage vstorage1 --mode ALL <br /> <br /> Run the script on your CONTROLLER node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> Installation can take up to 30 minutes depending on your Internet connection speed. Finished!<br /> <br /> == Setup OpenStack Compute Node (*Developer/POC Setup*) ==<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> $ yum install git -y<br /> <br /> Clone Virtuozzo scripts to your COMPUTE node:<br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd /vz/virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Cluster. <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show the virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the COMPUTE node. Please read script description here https://github.com/virtuozzo/virtuozzo-openstack-scripblob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.26 --password Virtuozzo1! --use_provider_network true --mode COMPUTE --controller 10.24.41.25 <br /> <br /> Run the script on your COMPUTE node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> == How to change Virtualization Type to Virtual Machines on the Compute Node ==<br /> <br /> If you want to use virtual machines instead of containers on your compute node you need to change virtualization type to KVM on the selected compute node.<br /> <br /> Open nova configuration file:<br /> $ vi /etc/nova/nova.conf<br /> <br /> Change the following lines:<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = qcow2<br /> connection_uri = vz:///system<br /> <br /> Delete the line:<br /> inject_partition = -2<br /> <br /> Save the file.<br /> <br /> Restart nova-compute service:<br /> $ su stack<br /> $ screen -r<br /> Press Ctrl-c<br /> $ sg libvirtd '/usr/bin/nova-compute --config-file /etc/nova/nova.conf' &amp; echo $! &gt;/vz/stack/status/stack/n-cpu.pid; fg || echo &quot;n-cpu failed to start&quot; | tee &quot;/vz/stack/status/stack/n-cpu.failure&quot;<br /> <br /> To exit from screen session:<br /> Press Ctrl+a+d<br /> <br /> == How to redeploy OpenStack on the same nodes ==<br /> <br /> Your OpenStack setup will be reset after node restart. To redeploy OpenStack on the same nodes do the following:<br /> # &lt;code&gt;cd /vz/virtuozzo-openstack-scripts&lt;/code&gt;<br /> # &lt;code&gt;git pull&lt;/code&gt;<br /> # Run ./setup_devstack_vz7.sh with options you need.<br /> <br /> == Installing OpenStack with help of packstack on [[Virtuozzo]] 7 (*Production Setup*) == <br /> <br /> <br /> * Create a new repo file:<br /> <br /> cat &gt; /etc/yum.repos.d/virtuozzo-extra.repo &lt;&lt; _EOF<br /> [virtuozzo-extra]<br /> name=Virtuozzo Extra<br /> baseurl=http://repo.virtuozzo.com/openstack/newton/x86_64/os/<br /> enabled=1<br /> gpgcheck=1<br /> priority=50<br /> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-Virtuozzo-7<br /> _EOF<br /> <br /> * Add RDO repository:<br /> <br /> $ yum install https://rdoproject.org/repos/rdo-release.rpm<br /> <br /> * Install packstack package:<br /> <br /> $ yum install openstack-packstack<br /> <br /> * Download sample Vz7 packstack answer file:<br /> <br /> $ wget https://raw.githubusercontent.com/virtuozzo/virtuozzo-openstack-scripts/master/vz7-packstack-sample.txt<br /> <br /> * Edit vz7-packstack-sample.txt enabling/disabling necessary services. Also make sure you have correct IP addresses specified by the following parameters in the file:<br /> <br /> CONFIG_CONTROLLER_HOST<br /> CONFIG_COMPUTE_HOSTS<br /> CONFIG_NETWORK_HOSTS<br /> CONFIG_AMQP_HOST<br /> CONFIG_MARIADB_HOST<br /> CONFIG_REDIS_HOST<br /> <br /> * Change CONFIG_DEFAULT_PASSWORD parameter!!!<br /> * Then run packstack:<br /> <br /> $ packstack --answer-file vz7-packstack-sample.txt<br /> <br /> == Install and configure a nova controller node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:18--&gt;<br /> <br /> &lt;!--T:19--&gt;<br /> Please use this chapter if you are going to run containers OR virtual machines on your compute node, but not containers AND virtual machines simultaneously. If you need to run containers and VMs simultaneously, please use next chapter.<br /> <br /> * Follow instructions on [http://docs.openstack.org/newton/install-guide-rdo/nova-controller-install.html OpenStack.org]<br /> * Change disk_formats string in /etc/glance/glance-api.conf so that it contains 'ploop'. Like this:<br /> <br /> disk_formats = ami,ari,aki,vhd,vmdk,raw,qcow2,vdi,iso,ploop<br /> <br /> * Restart glance-api service:<br /> <br /> systemctl restart openstack-glance-api.service<br /> <br /> * Download the container [http://updates.virtuozzo.com/server/virtuozzo/en_us/odin/7/techpreview-ct/centos7-exe.hds.tar.gz image]<br /> * Unpack it<br /> <br /> $ tar -xzvf centos7-exe.hds.tar.gz<br /> <br /> * Upload the image to glance:<br /> NOTE: this image was created for testing purposes only. Don't use it in production as is!<br /> <br /> $ glance image-create --name centos7-exe --disk-format ploop --container-format bare --property vm_mode=exe --property hypervisor_type=vz --property cinder_img_volume_type=vstorage-ploop --file centos7-exe.hds<br /> <br /> $ glance image-create --name centos7-hvm --disk-format qcow2 --container-format bare --property cinder_img_volume_type=vstorage-qcow2 --file CentOS-7-x86_64-GenericCloud.qcow2<br /> <br /> * CentOS image one can get from [http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.qcow2 here]<br /> <br /> == Install and configure a compute node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/newton/install-guide-rdo/nova-compute-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> force_raw_images = False<br /> pointer_model = ps2mouse<br /> <br /> [libvirt]<br /> ...<br /> vzstorage_mount_group = root<br /> virt_type = parallels<br /> images_type = ploop<br /> connection_uri = vz:///system<br /> <br /> * Remove 'cpu_mode' parameter or set the following:<br /> <br /> cpu_mode=none<br /> <br /> * Then restart nova-compute service:<br /> <br /> $ systemctl restart openstack-nova-compute.service<br /> <br /> * If you plan to run Virtual Machines on your Compute node, change 'images_type' parameter to 'qcow2'<br /> <br /> == Install and configure a block storage node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/mitaka/install-guide-rdo/cinder-controller-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/cinder/cinder.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> enabled_backends = lvmdriver-1,vstorage-ploop,vstorage-qcow2<br /> ...<br /> <br /> [vstorage-ploop]<br /> vzstorage_default_volume_format = ploop<br /> vzstorage_shares_config = /etc/cinder/vzstorage-shares-vstorage.conf<br /> volume_driver = cinder.volume.drivers.vzstorage.VZStorageDriver<br /> volume_backend_name = vstorage-ploop<br /> <br /> [vstorage-qcow2]<br /> vzstorage_default_volume_format = qcow2<br /> vzstorage_shares_config = /etc/cinder/vzstorage-shares-vstorage.conf<br /> volume_driver = cinder.volume.drivers.vzstorage.VZStorageDriver<br /> volume_backend_name = vstorage-qcow2<br /> <br /> * Create /etc/cinder/vzstorage-shares-vstorage.conf with the following content:<br /> <br /> YOUR-CLUSTER-NAME [&quot;-u&quot;, &quot;cinder&quot;, &quot;-g&quot;, &quot;root&quot;, &quot;-m&quot;, &quot;0770&quot;]<br /> <br /> * Create two new volume types:<br /> <br /> $ cinder type-create vstorage-qcow2<br /> $ cinder type-key vstorage-qcow2 set volume_backend_name=vstorage-qcow2<br /> <br /> $ cinder type-create vstorage-ploop<br /> $ cinder type-key vstorage-ploop set volume_backend_name=vstorage-ploop<br /> <br /> * Create directory for storage logs:<br /> <br /> $ mkdir /var/log/pstorage<br /> <br /> * Authenticate your Virtuozzo Storage client nodes in oreser to allow them to mount cluster:<br /> <br /> $ echo $CLUSTER_PASSWD | vstorage auth-node -c cc -P<br /> <br /> * Then restart cinder services:<br /> <br /> $ systemctl restart openstack-cinder-api<br /> $ systemctl restart openstack-cinder-scheduler<br /> $ systemctl restart openstack-cinder-volume<br /> <br /> == How to create a new image ploop image ready to upload to Glance == &lt;!--T:17--&gt;<br /> <br /> * Select os template. The following templates are possible: vzlinux-7, centos-7, ubuntu-16.04, ubuntu-14.04, debian-8.0, centos-6, debian-8.0-x86_64-minimal<br /> <br /> $ ct=centos-7<br /> <br /> * Create a new container based on necessary os distribution<br /> <br /> $ prlctl create glance-$ct --vmtype ct --ostemplate $ct<br /> <br /> * Set IP address and DNS to be able to connect to internet from the container<br /> <br /> $ prlctl set glance-$ct --ipadd IPADDR --nameserver DNS_IPADDR<br /> <br /> * Add additional network adapter<br /> <br /> $ prlctl set glance-$ct --device-add net --network Bridged --dhcp on<br /> <br /> * Start the container<br /> <br /> $ prlctl start glance-$ct<br /> <br /> * Install cloud-init packet<br /> <br /> $ prlctl exec glance-$ct yum install cloud-init -y<br /> <br /> * Remove the following modules from cloud.cfg<br /> <br /> $ prlctl exec glance-$ct sed -i '/- growpart/d' /etc/cloud/cloud.cfg<br /> $ prlctl exec glance-$ct sed -i '/- resizefs/d' /etc/cloud/cloud.cfg<br /> <br /> * Prepare network scripts<br /> <br /> cat &gt; /etc/sysconfig/network-scripts/ifcfg-eth0 &lt;&lt; _EOF<br /> DEVICE=eth0<br /> ONBOOT=yes<br /> NM_CONTROLLED=no<br /> BOOTPROTO=dhcp<br /> _EOF<br /> <br /> * If you need more than one network adapters withing a container, make as many copies as you need <br /> <br /> $ prlctl exec glance-$ct cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1<br /> $ prlctl exec glance-$ct sed -i '/eth0/eth1' /etc/sysconfig/network-scripts/ifcfg-eth1<br /> <br /> * Perform some cleanup<br /> <br /> $ rm -f /etc/sysconfig/network-scripts/ifcfg-venet0*<br /> $ rm -f /etc/resolv.conf<br /> <br /> * Stop the container<br /> <br /> $ prlctl stop glance-$ct<br /> <br /> * Create ploop disk and copy files<br /> <br /> $ mkdir /tmp/ploop-$ct<br /> $ ploop init -s 950M /tmp/ploop-$ct/$ct.hds<br /> $ mkdir /tmp/ploop-$ct/dst<br /> $ ploop mount -m /tmp/ploop-$ct/dst /tmp/ploop-$ct/DiskDescriptor.xml<br /> $ prlctl mount glance-$ct<br /> $ id=$(vzlist glance-$ct | awk ' NR&gt;1 { print $1 }')<br /> $ cp -Pr --preserve=all /vz/root/$id/* /tmp/ploop-$ct/dst/<br /> $ prlctl umount glance-$ct<br /> $ ploop umount -m /tmp/ploop-$ct/dst/<br /> <br /> * Now the image tmp/ploop-$ct/$ct.hds is ready to be uploaded to Glance<br /> <br /> == See also == &lt;!--T:100--&gt;<br /> * [http://docs.openstack.org/newton/install-guide-rdo/nova-controller-install.html Controller Node Installation Guide]<br /> * [http://docs.openstack.org/newton/install-guide-rdo/nova-compute-install.html Compute Node Installation Guide]<br /> * [http://docs.openstack.org/newton/install-guide-rdo/environment-packages.html OpenStack Installation Guide]<br /> * [https://docs.openvz.org/ Virtuozzo Documentation]<br /> * [[Virtuozzo ecosystem]]<br /> <br /> &lt;/translate&gt;<br /> <br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Setup_OpenStack_with_Virtuozzo_7&diff=22550 2017-03-01T14:39:58Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> This article describes how to install OpenStack on [[Virtuozzo]] 7.<br /> == Introduction ==<br /> <br /> Virtuozzo 7 supports OpenStack as cloud management solution since version 6. With Virtuozzo 7 we are going to add a lot of new capabilities to OpenStack integration. <br /> <br /> This guide describes two ways of installing OpenStack on Virtuozzo nodes. The first is for quick/development/POC needs. The second is for production. Please keep in mind that devstack allows you to install OpenStack for demo/POC/development purposes only. That means it will be reset after host reboot.<br /> <br /> You need the following infrastructure to setup OpenStack with Virtuozzo 7:<br /> #controller host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a controller and Virtuozzo containers host.<br /> #compute host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a virtual machines host.<br /> <br /> == Prerequisites ==<br /> <br /> You need to install and update your Virtuozzo nodes first. Install Virtuozzo 7 on your controller and compute hosts as usual. You can use basic (local) or Virtuozzo Storage. Update Virtuozzo hosts<br /> $ yum update -y<br /> <br /> If you have br0 bridge configured as an IP interface, then you should move an IP address assigned to it to the physical ethernet interface bridged to br0.<br /> You can check you configuration with the following command:<br /> <br /> $ if=$(brctl show | grep '^br0' | awk ' { print $4 }') &amp;&amp; addr=$(ip addr | grep -w 'br0' | grep inet | awk ' {print $2} ') &amp;&amp; gw=$(ip route | grep default | awk ' { print $3 } ') &amp;&amp; echo &quot;My interface is '$if', gateway is '$gw', IP address '$addr'&quot;<br /> <br /> For instance you have the following output after execution the above script:<br /> <br /> My interface is 'en33', gateway is '192.168.190.2', IP address '192.168.190.134/24'.<br /> <br /> Then edit your /etc/sysconfig/network-scripts/ifcfg-ens33 to have the following content and remove BRIDGE=&quot;br0&quot; string from it:<br /> ...<br /> ONBOOT=yes<br /> IPADDR=192.168.190.134<br /> GATEWAY=192.168.190.2<br /> PREFIX=24<br /> ...<br /> <br /> Remove /etc/sysconfig/network-scripts/ifcfg-br0 file.<br /> <br /> $ rm /etc/sysconfig/network-scripts/ifcfg-br0<br /> <br /> Then restart network service:<br /> <br /> $ systemctl restart network<br /> <br /> == Setup OpenStack Controller Node with Virtuozzo Containers Support (*Developer/POC Setup*) == &lt;!--T:1--&gt;<br /> <br /> &lt;!--T:3--&gt;<br /> You are able to setup OpenStack controller node together with compute node on the same server for demo or test purpose. In this case compute node with Virtuozzo Containers support will be deployed. You can add another compute node with containers or VMs anytime you want as described in Setup OpenStack Compute Node section.<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> $ yum install git -y<br /> <br /> Clone virtuozzo scripts:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Storage Cluster. <br /> <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show Virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the CONTROLLER node. Please read full script description here https://github.com/virtuozzo/virtuozzo-openstack-scripts/blob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.25 --password Virtuozzo1! --use_provider_network true --fixed_range 192.168.0.0/24 --floating_range 10.24.41.0/24 --floating_pool &quot;start=10.24.41.151,end=10.24.41.199&quot; --public_gateway 10.24.41.1 --gateway 192.168.0.1 --vzstorage vstorage1 --mode ALL <br /> <br /> Run the script on your CONTROLLER node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> Installation can take up to 30 minutes depending on your Internet connection speed. Finished!<br /> <br /> == Setup OpenStack Compute Node (*Developer/POC Setup*) ==<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> $ yum install git -y<br /> <br /> Clone Virtuozzo scripts to your COMPUTE node:<br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd /vz/virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Cluster. <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show the virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the COMPUTE node. Please read script description here https://github.com/virtuozzo/virtuozzo-openstack-scripblob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.26 --password Virtuozzo1! --use_provider_network true --mode COMPUTE --controller 10.24.41.25 <br /> <br /> Run the script on your COMPUTE node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> == How to change Virtualization Type to Virtual Machines on the Compute Node ==<br /> <br /> If you want to use virtual machines instead of containers on your compute node you need to change virtualization type to KVM on the selected compute node.<br /> <br /> Open nova configuration file:<br /> $ vi /etc/nova/nova.conf<br /> <br /> Change the following lines:<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = qcow2<br /> connection_uri = vz:///system<br /> <br /> Delete the line:<br /> inject_partition = -2<br /> <br /> Save the file.<br /> <br /> Restart nova-compute service:<br /> $ su stack<br /> $ screen -r<br /> Press Ctrl-c<br /> $ sg libvirtd '/usr/bin/nova-compute --config-file /etc/nova/nova.conf' &amp; echo $! &gt;/vz/stack/status/stack/n-cpu.pid; fg || echo &quot;n-cpu failed to start&quot; | tee &quot;/vz/stack/status/stack/n-cpu.failure&quot;<br /> <br /> To exit from screen session:<br /> Press Ctrl+a+d<br /> <br /> == How to redeploy OpenStack on the same nodes ==<br /> <br /> Your OpenStack setup will be reset after node restart. To redeploy OpenStack on the same nodes do the following:<br /> # &lt;code&gt;cd /vz/virtuozzo-openstack-scripts&lt;/code&gt;<br /> # &lt;code&gt;git pull&lt;/code&gt;<br /> # Run ./setup_devstack_vz7.sh with options you need.<br /> <br /> == Installing OpenStack with help of packstack on [[Virtuozzo]] 7 (*Production Setup*) == <br /> <br /> <br /> * Create a new repo file:<br /> <br /> cat &gt; /etc/yum.repos.d/virtuozzo-extra.repo &lt;&lt; _EOF<br /> [virtuozzo-extra]<br /> name=Virtuozzo Extra<br /> baseurl=http://repo.virtuozzo.com/openstack/newton/x86_64/os/<br /> enabled=1<br /> gpgcheck=1<br /> priority=50<br /> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-Virtuozzo-7<br /> _EOF<br /> <br /> * Add RDO repository:<br /> <br /> $ yum install https://rdoproject.org/repos/rdo-release.rpm<br /> <br /> * Install packstack package:<br /> <br /> $ yum install openstack-packstack<br /> <br /> * Download sample Vz7 packstack answer file:<br /> <br /> $ wget https://raw.githubusercontent.com/virtuozzo/virtuozzo-openstack-scripts/master/vz7-packstack-sample.txt<br /> <br /> * Edit vz7-packstack-sample.txt enabling/disabling necessary services. Also make sure you have correct IP addresses specified by the following parameters in the file:<br /> <br /> CONFIG_CONTROLLER_HOST<br /> CONFIG_COMPUTE_HOSTS<br /> CONFIG_NETWORK_HOSTS<br /> CONFIG_AMQP_HOST<br /> CONFIG_MARIADB_HOST<br /> CONFIG_REDIS_HOST<br /> <br /> * Change CONFIG_DEFAULT_PASSWORD parameter!!!<br /> * Then run packstack:<br /> <br /> $ packstack --answer-file vz7-packstack-sample.txt<br /> <br /> == Install and configure a nova controller node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:18--&gt;<br /> <br /> &lt;!--T:19--&gt;<br /> * Follow instructions on [http://docs.openstack.org/newton/install-guide-rdo/nova-controller-install.html OpenStack.org]<br /> * Change disk_formats string in /etc/glance/glance-api.conf so that it contains 'ploop'. Like this:<br /> <br /> disk_formats = ami,ari,aki,vhd,vmdk,raw,qcow2,vdi,iso,ploop<br /> <br /> * Restart glance-api service:<br /> <br /> systemctl restart openstack-glance-api.service<br /> <br /> * Download the container [http://updates.virtuozzo.com/server/virtuozzo/en_us/odin/7/techpreview-ct/centos7-exe.hds.tar.gz image]<br /> * Unpack it<br /> <br /> $ tar -xzvf centos7-exe.hds.tar.gz<br /> <br /> * Upload the image to glance:<br /> NOTE: this image was created for testing purposes only. Don't use it in production as is!<br /> <br /> $ glance image-create --name centos7-exe --disk-format ploop --container-format bare --property vm_mode=exe --property hypervisor_type=vz --property cinder_img_volume_type=vstorage-ploop --file centos7-exe.hds<br /> <br /> $ glance image-create --name centos7-hvm --disk-format qcow2 --container-format bare --property cinder_img_volume_type=vstorage-qcow2 --file CentOS-7-x86_64-GenericCloud.qcow2<br /> <br /> * CentOS image one can get from [http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.qcow2 here]<br /> <br /> == Install and configure a compute node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/newton/install-guide-rdo/nova-compute-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> force_raw_images = False<br /> pointer_model = ps2mouse<br /> <br /> [libvirt]<br /> ...<br /> vzstorage_mount_group = root<br /> virt_type = parallels<br /> images_type = ploop<br /> connection_uri = vz:///system<br /> <br /> * Remove 'cpu_mode' parameter or set the following:<br /> <br /> cpu_mode=none<br /> <br /> * Then restart nova-compute service:<br /> <br /> $ systemctl restart openstack-nova-compute.service<br /> <br /> * If you plan to run Virtual Machines on your Compute node, change 'images_type' parameter to 'qcow2'<br /> <br /> == Install and configure a block storage node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/mitaka/install-guide-rdo/cinder-controller-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/cinder/cinder.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> enabled_backends = lvmdriver-1,vstorage-ploop,vstorage-qcow2<br /> ...<br /> <br /> [vstorage-ploop]<br /> vzstorage_default_volume_format = ploop<br /> vzstorage_shares_config = /etc/cinder/vzstorage-shares-vstorage.conf<br /> volume_driver = cinder.volume.drivers.vzstorage.VZStorageDriver<br /> volume_backend_name = vstorage-ploop<br /> <br /> [vstorage-qcow2]<br /> vzstorage_default_volume_format = qcow2<br /> vzstorage_shares_config = /etc/cinder/vzstorage-shares-vstorage.conf<br /> volume_driver = cinder.volume.drivers.vzstorage.VZStorageDriver<br /> volume_backend_name = vstorage-qcow2<br /> <br /> * Create /etc/cinder/vzstorage-shares-vstorage.conf with the following content:<br /> <br /> YOUR-CLUSTER-NAME [&quot;-u&quot;, &quot;cinder&quot;, &quot;-g&quot;, &quot;root&quot;, &quot;-m&quot;, &quot;0770&quot;]<br /> <br /> * Create two new volume types:<br /> <br /> $ cinder type-create vstorage-qcow2<br /> $ cinder type-key vstorage-qcow2 set volume_backend_name=vstorage-qcow2<br /> <br /> $ cinder type-create vstorage-ploop<br /> $ cinder type-key vstorage-ploop set volume_backend_name=vstorage-ploop<br /> <br /> * Create directory for storage logs:<br /> <br /> $ mkdir /var/log/pstorage<br /> <br /> * Authenticate your Virtuozzo Storage client nodes in oreser to allow them to mount cluster:<br /> <br /> $ echo $CLUSTER_PASSWD | vstorage auth-node -c cc -P<br /> <br /> * Then restart cinder services:<br /> <br /> $ systemctl restart openstack-cinder-api<br /> $ systemctl restart openstack-cinder-scheduler<br /> $ systemctl restart openstack-cinder-volume<br /> <br /> == How to create a new image ploop image ready to upload to Glance == &lt;!--T:17--&gt;<br /> <br /> * Select os template. The following templates are possible: vzlinux-7, centos-7, ubuntu-16.04, ubuntu-14.04, debian-8.0, centos-6, debian-8.0-x86_64-minimal<br /> <br /> $ ct=centos-7<br /> <br /> * Create a new container based on necessary os distribution<br /> <br /> $ prlctl create glance-$ct --vmtype ct --ostemplate $ct<br /> <br /> * Set IP address and DNS to be able to connect to internet from the container<br /> <br /> $ prlctl set glance-$ct --ipadd IPADDR --nameserver DNS_IPADDR<br /> <br /> * Add additional network adapter<br /> <br /> $ prlctl set glance-$ct --device-add net --network Bridged --dhcp on<br /> <br /> * Start the container<br /> <br /> $ prlctl start glance-$ct<br /> <br /> * Install cloud-init packet<br /> <br /> $ prlctl exec glance-$ct yum install cloud-init -y<br /> <br /> * Remove the following modules from cloud.cfg<br /> <br /> $ prlctl exec glance-$ct sed -i '/- growpart/d' /etc/cloud/cloud.cfg<br /> $ prlctl exec glance-$ct sed -i '/- resizefs/d' /etc/cloud/cloud.cfg<br /> <br /> * Prepare network scripts<br /> <br /> cat &gt; /etc/sysconfig/network-scripts/ifcfg-eth0 &lt;&lt; _EOF<br /> DEVICE=eth0<br /> ONBOOT=yes<br /> NM_CONTROLLED=no<br /> BOOTPROTO=dhcp<br /> _EOF<br /> <br /> * If you need more than one network adapters withing a container, make as many copies as you need <br /> <br /> $ prlctl exec glance-$ct cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1<br /> $ prlctl exec glance-$ct sed -i '/eth0/eth1' /etc/sysconfig/network-scripts/ifcfg-eth1<br /> <br /> * Perform some cleanup<br /> <br /> $ rm -f /etc/sysconfig/network-scripts/ifcfg-venet0*<br /> $ rm -f /etc/resolv.conf<br /> <br /> * Stop the container<br /> <br /> $ prlctl stop glance-$ct<br /> <br /> * Create ploop disk and copy files<br /> <br /> $ mkdir /tmp/ploop-$ct<br /> $ ploop init -s 950M /tmp/ploop-$ct/$ct.hds<br /> $ mkdir /tmp/ploop-$ct/dst<br /> $ ploop mount -m /tmp/ploop-$ct/dst /tmp/ploop-$ct/DiskDescriptor.xml<br /> $ prlctl mount glance-$ct<br /> $ id=$(vzlist glance-$ct | awk ' NR&gt;1 { print $1 }')<br /> $ cp -Pr --preserve=all /vz/root/$id/* /tmp/ploop-$ct/dst/<br /> $ prlctl umount glance-$ct<br /> $ ploop umount -m /tmp/ploop-$ct/dst/<br /> <br /> * Now the image tmp/ploop-$ct/$ct.hds is ready to be uploaded to Glance<br /> <br /> == See also == &lt;!--T:100--&gt;<br /> * [http://docs.openstack.org/newton/install-guide-rdo/nova-controller-install.html Controller Node Installation Guide]<br /> * [http://docs.openstack.org/newton/install-guide-rdo/nova-compute-install.html Compute Node Installation Guide]<br /> * [http://docs.openstack.org/newton/install-guide-rdo/environment-packages.html OpenStack Installation Guide]<br /> * [https://docs.openvz.org/ Virtuozzo Documentation]<br /> * [[Virtuozzo ecosystem]]<br /> <br /> &lt;/translate&gt;<br /> <br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Setup_OpenStack_with_Virtuozzo_7&diff=22549 2017-03-01T14:36:48Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> This article describes how to install OpenStack on [[Virtuozzo]] 7.<br /> == Introduction ==<br /> <br /> Virtuozzo 7 supports OpenStack as cloud management solution since version 6. With Virtuozzo 7 we are going to add a lot of new capabilities to OpenStack integration. <br /> <br /> This guide describes two ways of installing OpenStack on Virtuozzo nodes. The first is for quick/development/POC needs. The second is for production. Please keep in mind that devstack allows you to install OpenStack for demo/POC/development purposes only. That means it will be reset after host reboot.<br /> <br /> You need the following infrastructure to setup OpenStack with Virtuozzo 7:<br /> #controller host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a controller and Virtuozzo containers host.<br /> #compute host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a virtual machines host.<br /> <br /> == Prerequisites ==<br /> <br /> You need to install and update your Virtuozzo nodes first. Install Virtuozzo 7 on your controller and compute hosts as usual. You can use basic (local) or Virtuozzo Storage. Update Virtuozzo hosts<br /> $ yum update -y<br /> <br /> If you have br0 bridge configured as an IP interface, then you should move an IP address assigned to it to the physical ethernet interface bridged to br0.<br /> You can check you configuration with the following command:<br /> <br /> $ if=$(brctl show | grep '^br0' | awk ' { print $4 }') &amp;&amp; addr=$(ip addr | grep -w 'br0' | grep inet | awk ' {print $2} ') &amp;&amp; gw=$(ip route | grep default | awk ' { print $3 } ') &amp;&amp; echo &quot;My interface is '$if', gateway is '$gw', IP address '$addr'&quot;<br /> <br /> For instance you have the following output after execution the above script:<br /> <br /> My interface is 'en33', gateway is '192.168.190.2', IP address '192.168.190.134/24'.<br /> <br /> Then edit your /etc/sysconfig/network-scripts/ifcfg-ens33 to have the following content and remove BRIDGE=&quot;br0&quot; string from it:<br /> ...<br /> ONBOOT=yes<br /> IPADDR=192.168.190.134<br /> GATEWAY=192.168.190.2<br /> PREFIX=24<br /> ...<br /> <br /> Remove /etc/sysconfig/network-scripts/ifcfg-br0 file.<br /> <br /> $ rm /etc/sysconfig/network-scripts/ifcfg-br0<br /> <br /> Then restart network service:<br /> <br /> $ systemctl restart network<br /> <br /> == Setup OpenStack Controller Node with Virtuozzo Containers Support (*Developer/POC Setup*) == &lt;!--T:1--&gt;<br /> <br /> &lt;!--T:3--&gt;<br /> You are able to setup OpenStack controller node together with compute node on the same server for demo or test purpose. In this case compute node with Virtuozzo Containers support will be deployed. You can add another compute node with containers or VMs anytime you want as described in Setup OpenStack Compute Node section.<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> $ yum install git -y<br /> <br /> Clone virtuozzo scripts:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Storage Cluster. <br /> <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show Virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the CONTROLLER node. Please read full script description here https://github.com/virtuozzo/virtuozzo-openstack-scripts/blob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.25 --password Virtuozzo1! --use_provider_network true --fixed_range 192.168.0.0/24 --floating_range 10.24.41.0/24 --floating_pool &quot;start=10.24.41.151,end=10.24.41.199&quot; --public_gateway 10.24.41.1 --gateway 192.168.0.1 --vzstorage vstorage1 --mode ALL <br /> <br /> Run the script on your CONTROLLER node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> Installation can take up to 30 minutes depending on your Internet connection speed. Finished!<br /> <br /> == Setup OpenStack Compute Node (*Developer/POC Setup*) ==<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> $ yum install git -y<br /> <br /> Clone Virtuozzo scripts to your COMPUTE node:<br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd /vz/virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Cluster. <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show the virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the COMPUTE node. Please read script description here https://github.com/virtuozzo/virtuozzo-openstack-scripblob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.26 --password Virtuozzo1! --use_provider_network true --mode COMPUTE --controller 10.24.41.25 <br /> <br /> Run the script on your COMPUTE node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> == How to change Virtualization Type to Virtual Machines on the Compute Node ==<br /> <br /> If you want to use virtual machines instead of containers on your compute node you need to change virtualization type to KVM on the selected compute node.<br /> <br /> Open nova configuration file:<br /> $ vi /etc/nova/nova.conf<br /> <br /> Change the following lines:<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = qcow2<br /> connection_uri = parallels:///system<br /> <br /> Delete the line:<br /> inject_partition = -2<br /> <br /> Save the file.<br /> <br /> Restart nova-compute service:<br /> $ su stack<br /> $ screen -r<br /> Press Ctrl-c<br /> $ sg libvirtd '/usr/bin/nova-compute --config-file /etc/nova/nova.conf' &amp; echo $! &gt;/vz/stack/status/stack/n-cpu.pid; fg || echo &quot;n-cpu failed to start&quot; | tee &quot;/vz/stack/status/stack/n-cpu.failure&quot;<br /> <br /> To exit from screen session:<br /> Press Ctrl+a+d<br /> <br /> == How to redeploy OpenStack on the same nodes ==<br /> <br /> Your OpenStack setup will be reset after node restart. To redeploy OpenStack on the same nodes do the following:<br /> # &lt;code&gt;cd /vz/virtuozzo-openstack-scripts&lt;/code&gt;<br /> # &lt;code&gt;git pull&lt;/code&gt;<br /> # Run ./setup_devstack_vz7.sh with options you need.<br /> <br /> == Installing OpenStack with help of packstack on [[Virtuozzo]] 7 (*Production Setup*) == <br /> <br /> <br /> * Create a new repo file:<br /> <br /> cat &gt; /etc/yum.repos.d/virtuozzo-extra.repo &lt;&lt; _EOF<br /> [virtuozzo-extra]<br /> name=Virtuozzo Extra<br /> baseurl=http://repo.virtuozzo.com/openstack/newton/x86_64/os/<br /> enabled=1<br /> gpgcheck=1<br /> priority=50<br /> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-Virtuozzo-7<br /> _EOF<br /> <br /> * Add RDO repository:<br /> <br /> $ yum install https://rdoproject.org/repos/rdo-release.rpm<br /> <br /> * Install packstack package:<br /> <br /> $ yum install openstack-packstack<br /> <br /> * Download sample Vz7 packstack answer file:<br /> <br /> $ wget https://raw.githubusercontent.com/virtuozzo/virtuozzo-openstack-scripts/master/vz7-packstack-sample.txt<br /> <br /> * Edit vz7-packstack-sample.txt enabling/disabling necessary services. Also make sure you have correct IP addresses specified by the following parameters in the file:<br /> <br /> CONFIG_CONTROLLER_HOST<br /> CONFIG_COMPUTE_HOSTS<br /> CONFIG_NETWORK_HOSTS<br /> CONFIG_AMQP_HOST<br /> CONFIG_MARIADB_HOST<br /> CONFIG_REDIS_HOST<br /> <br /> * Change CONFIG_DEFAULT_PASSWORD parameter!!!<br /> * Then run packstack:<br /> <br /> $ packstack --answer-file vz7-packstack-sample.txt<br /> <br /> == Install and configure a nova controller node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:18--&gt;<br /> <br /> &lt;!--T:19--&gt;<br /> * Follow instructions on [http://docs.openstack.org/newton/install-guide-rdo/nova-controller-install.html OpenStack.org]<br /> * Change disk_formats string in /etc/glance/glance-api.conf so that it contains 'ploop'. Like this:<br /> <br /> disk_formats = ami,ari,aki,vhd,vmdk,raw,qcow2,vdi,iso,ploop<br /> <br /> * Restart glance-api service:<br /> <br /> systemctl restart openstack-glance-api.service<br /> <br /> * Download the container [http://updates.virtuozzo.com/server/virtuozzo/en_us/odin/7/techpreview-ct/centos7-exe.hds.tar.gz image]<br /> * Unpack it<br /> <br /> $ tar -xzvf centos7-exe.hds.tar.gz<br /> <br /> * Upload the image to glance:<br /> NOTE: this image was created for testing purposes only. Don't use it in production as is!<br /> <br /> $ glance image-create --name centos7-exe --disk-format ploop --container-format bare --property vm_mode=exe --property hypervisor_type=vz --property cinder_img_volume_type=vstorage-ploop --file centos7-exe.hds<br /> <br /> $ glance image-create --name centos7-hvm --disk-format qcow2 --container-format bare --property cinder_img_volume_type=vstorage-qcow2 --file CentOS-7-x86_64-GenericCloud.qcow2<br /> <br /> * CentOS image one can get from [http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.qcow2 here]<br /> <br /> == Install and configure a compute node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/newton/install-guide-rdo/nova-compute-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> force_raw_images = False<br /> pointer_model = ps2mouse<br /> <br /> [libvirt]<br /> ...<br /> vzstorage_mount_group = root<br /> virt_type = parallels<br /> images_type = ploop<br /> connection_uri = parallels:///system<br /> <br /> * Remove 'cpu_mode' parameter or set the following:<br /> <br /> cpu_mode=none<br /> <br /> * Then restart nova-compute service:<br /> <br /> $ systemctl restart openstack-nova-compute.service<br /> <br /> * If you plan to run Virtual Machines on your Compute node, change 'images_type' parameter to 'qcow2'<br /> <br /> == Install and configure a block storage node on [[Virtuozzo]] 7 (*Production Setup*) == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/mitaka/install-guide-rdo/cinder-controller-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/cinder/cinder.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> enabled_backends = lvmdriver-1,vstorage-ploop,vstorage-qcow2<br /> ...<br /> <br /> [vstorage-ploop]<br /> vzstorage_default_volume_format = ploop<br /> vzstorage_shares_config = /etc/cinder/vzstorage-shares-vstorage.conf<br /> volume_driver = cinder.volume.drivers.vzstorage.VZStorageDriver<br /> volume_backend_name = vstorage-ploop<br /> <br /> [vstorage-qcow2]<br /> vzstorage_default_volume_format = qcow2<br /> vzstorage_shares_config = /etc/cinder/vzstorage-shares-vstorage.conf<br /> volume_driver = cinder.volume.drivers.vzstorage.VZStorageDriver<br /> volume_backend_name = vstorage-qcow2<br /> <br /> * Create /etc/cinder/vzstorage-shares-vstorage.conf with the following content:<br /> <br /> YOUR-CLUSTER-NAME [&quot;-u&quot;, &quot;cinder&quot;, &quot;-g&quot;, &quot;root&quot;, &quot;-m&quot;, &quot;0770&quot;]<br /> <br /> * Create two new volume types:<br /> <br /> $ cinder type-create vstorage-qcow2<br /> $ cinder type-key vstorage-qcow2 set volume_backend_name=vstorage-qcow2<br /> <br /> $ cinder type-create vstorage-ploop<br /> $ cinder type-key vstorage-ploop set volume_backend_name=vstorage-ploop<br /> <br /> * Create directory for storage logs:<br /> <br /> $ mkdir /var/log/pstorage<br /> <br /> * Authenticate your Virtuozzo Storage client nodes in oreser to allow them to mount cluster:<br /> <br /> $ echo $CLUSTER_PASSWD | vstorage auth-node -c cc -P<br /> <br /> * Then restart cinder services:<br /> <br /> $ systemctl restart openstack-cinder-api<br /> $ systemctl restart openstack-cinder-scheduler<br /> $ systemctl restart openstack-cinder-volume<br /> <br /> == How to create a new image ploop image ready to upload to Glance == &lt;!--T:17--&gt;<br /> <br /> * Select os template. The following templates are possible: vzlinux-7, centos-7, ubuntu-16.04, ubuntu-14.04, debian-8.0, centos-6, debian-8.0-x86_64-minimal<br /> <br /> $ ct=centos-7<br /> <br /> * Create a new container based on necessary os distribution<br /> <br /> $ prlctl create glance-$ct --vmtype ct --ostemplate $ct<br /> <br /> * Set IP address and DNS to be able to connect to internet from the container<br /> <br /> $ prlctl set glance-$ct --ipadd IPADDR --nameserver DNS_IPADDR<br /> <br /> * Add additional network adapter<br /> <br /> $ prlctl set glance-$ct --device-add net --network Bridged --dhcp on<br /> <br /> * Start the container<br /> <br /> $ prlctl start glance-$ct<br /> <br /> * Install cloud-init packet<br /> <br /> $ prlctl exec glance-$ct yum install cloud-init -y<br /> <br /> * Remove the following modules from cloud.cfg<br /> <br /> $ prlctl exec glance-$ct sed -i '/- growpart/d' /etc/cloud/cloud.cfg<br /> $ prlctl exec glance-$ct sed -i '/- resizefs/d' /etc/cloud/cloud.cfg<br /> <br /> * Prepare network scripts<br /> <br /> cat &gt; /etc/sysconfig/network-scripts/ifcfg-eth0 &lt;&lt; _EOF<br /> DEVICE=eth0<br /> ONBOOT=yes<br /> NM_CONTROLLED=no<br /> BOOTPROTO=dhcp<br /> _EOF<br /> <br /> * If you need more than one network adapters withing a container, make as many copies as you need <br /> <br /> $ prlctl exec glance-$ct cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1<br /> $ prlctl exec glance-$ct sed -i '/eth0/eth1' /etc/sysconfig/network-scripts/ifcfg-eth1<br /> <br /> * Perform some cleanup<br /> <br /> $ rm -f /etc/sysconfig/network-scripts/ifcfg-venet0*<br /> $ rm -f /etc/resolv.conf<br /> <br /> * Stop the container<br /> <br /> $ prlctl stop glance-$ct<br /> <br /> * Create ploop disk and copy files<br /> <br /> $ mkdir /tmp/ploop-$ct<br /> $ ploop init -s 950M /tmp/ploop-$ct/$ct.hds<br /> $ mkdir /tmp/ploop-$ct/dst<br /> $ ploop mount -m /tmp/ploop-$ct/dst /tmp/ploop-$ct/DiskDescriptor.xml<br /> $ prlctl mount glance-$ct<br /> $ id=$(vzlist glance-$ct | awk ' NR&gt;1 { print $1 }')<br /> $ cp -Pr --preserve=all /vz/root/$id/* /tmp/ploop-$ct/dst/<br /> $ prlctl umount glance-$ct<br /> $ ploop umount -m /tmp/ploop-$ct/dst/<br /> <br /> * Now the image tmp/ploop-$ct/$ct.hds is ready to be uploaded to Glance<br /> <br /> == See also == &lt;!--T:100--&gt;<br /> * [http://docs.openstack.org/newton/install-guide-rdo/nova-controller-install.html Controller Node Installation Guide]<br /> * [http://docs.openstack.org/newton/install-guide-rdo/nova-compute-install.html Compute Node Installation Guide]<br /> * [http://docs.openstack.org/newton/install-guide-rdo/environment-packages.html OpenStack Installation Guide]<br /> * [https://docs.openvz.org/ Virtuozzo Documentation]<br /> * [[Virtuozzo ecosystem]]<br /> <br /> &lt;/translate&gt;<br /> <br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Comparison&diff=22467 2016-12-01T11:55:06Z

<p>Vporokhov: </p> <hr /> <div>{{Note|This comparison doesn't include Docker, because Docker is not a virtualization solution. It automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of operating-system-level virtualization.&lt;ref&gt;[https://en.wikipedia.org/wiki/Docker_(software) Wikipedia article about Docker]&lt;/ref&gt;}}<br /> <br /> <br /> == Disclaimer ==<br /> <br /> The information regarding Virtuozzo 7 is provided by [http://www.virtuozzo.com Virtuozzo]. Here is the Virtuozzo's statement regarding this information:<br /> <br /> :#The information contained herein is intended to outline general product direction and should not be relied upon in making purchasing decisions.<br /> :#The content is for informational purposes only and may not be incorporated into any contract.<br /> :#The information presented is not a commitment, promise, or legal obligation to deliver any material, code or functionality.<br /> :#Any references to the development, release, and timing of any features or functionality described for these products remains at Virtuozzo’s sole discretion.<br /> :#Product capabilities, timeframes and features are subject to change and should not be viewed as Virtuozzo commitments.<br /> <br /> The information regarding all other solutions are taken by authors from public sources only. This information can be changed by any OpenVZ Wiki user without any notice and author's review or approval.<br /> <br /> <br /> == Feature comparison of different virtualization solutions ==<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> ! Feature<br /> ! Description<br /> ! OpenVZ<br /> ! Virtuozzo&amp;nbsp;6 (PCS 6)<br /> ! OpenVZ&amp;nbsp;7<br /> ! [https://virtuozzo.com/products/virtuozzo-containers/ Virtuozzo&amp;nbsp;7]<br /> ! LXC<br /> ! Proxmox VE<br /> ! Microsoft Hyper-V 2012 R2<br /> ! RHEV 3.5<br /> ! Citrix XenServer 6.5<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|1. Virtualization platform<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.1. Overview<br /> |-<br /> |'''HW virtualization support (Hypervisor)'''<br /> |Full emulation of underneath hardware level: full isolation guest environment, no dependencies from host OS, overhead for hypervisor layer.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''OS-level virtualization (Containers)'''<br /> |Sharing the same instance of host OS: high density, high performance, high dependencies from host OS.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Hypervisor technology'''<br /> |Technology that enables to run Virtual Machines.<br /> |{{No}}<br /> |Parallels Desktop Monitor<br /> |KVM<br /> |KVM<br /> |None<br /> |KVM<br /> |Hyper-V<br /> |KVM<br /> |Xen<br /> |-<br /> |'''Windows guest OS additional support'''<br /> |WHQL-signed drivers, SVVP certification<br /> |N/A<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Containers technology'''<br /> |Technology that enables to run Containers.<br /> |Virtuozzo Containers<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Linux containers<br /> |LXC (moved from OpenVZ since 4.0)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.2. Memory<br /> |-<br /> |'''Memory Overcommit'''<br /> |Ability to present more memory to virtual machines than physically available <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, with new VCMMD memory management<br /> |{{Yes}}, with new VCMMD memory management<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Page sharing'''<br /> |Memory (RAM) savings through sharing identical memory pages across virtual machines<br /> |{{Yes}}<br /> |{{Yes}}, only for CTs<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> |'''Online Memory Management for VM'''<br /> |Ability to change amount of RAM for CT and VM without reboot<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |N/A<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|2. Management<br /> |-<br /> !colspan=&quot;11&quot;|2.1. General<br /> |-<br /> |'''Unified management tool for CTs and VMs'''<br /> |Single tool for managing both containers and virtual machines (if applicable)<br /> |N/A<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''OpenStack integration'''<br /> |Integration with OpenStack components ([http://docs.openstack.org/developer/nova/support-matrix.html see details])<br /> |{{Yes}}, only Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated GUI'''<br /> |Centralized multi-server management<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}, Parallels Virtual Automation (PVA)<br /> |{{No}}<br /> |{{Yes}}, [https://virtuozzo.com/support/pva/ Virtual Automator]<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}<br /> |{{Yes}}, System Center Virtual Machine Manager<br /> |{{Yes}}, RHEV Manager<br /> |{{Yes}}, XenCenter<br /> |-<br /> !colspan=&quot;11&quot;|2.2. Upgrade &amp; Backup<br /> |-<br /> |'''Live VE snapshot'''<br /> |Ability to take a snapshot of a virtual environment while the guest OS is running (e.g. for roll-back or backup purposes)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated Backup'''<br /> |Are backup plugins/tools provided to backup virtual environments (over and above the ability to perform classic backup using agents in the guests)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Backup Integration API'''<br /> |Integration with 3rd party backup applications for backup of the virtual environment.<br /> |{{No}} (only through snapshots)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}} (only through snapshots)<br /> |{{Yes}} (vzdump)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot;|2.3. Others<br /> |-<br /> |'''VEs Templates (VM, CT)'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |{{Yes}} (CT only)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}} <br /> |{{Yes}} (OpenVZ templates)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''P2V migration'''<br /> |Integrated or added P2V (or V2V) capability in order to convert physical systems to virtual environment.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}, 3rd party tools<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|3. VE Mobility and HA<br /> |-<br /> !colspan=&quot;11&quot;|3.1. VE Mobility<br /> |-<br /> |'''Live Migration'''<br /> |Ability to migrate virtual machines between hosts without perceived downtime<br /> |{{Yes}}, but with no zero downtime<br /> |{{Yes}}, Kernel-Level Migration<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''DRS/Host Maintenance Mode'''<br /> |Ability to put host into maintenance mode which will automatically live migrate all VEs onto other available hosts so that the host can be brought shut down safely<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Distributed Power Management'''<br /> |Distributed Power Management features Ability to automatically migrate VEs onto fewer hosts and power off unused capacity (hosts), wake systems back up when required <br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|3.2. HA / DR<br /> |-<br /> |'''Integrated HA'''<br /> |Recover virtual environment in case of host failures through restart on alternative hosts (downtime = restart time)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|4. Network and Storage<br /> |-<br /> !colspan=&quot;11&quot;|4.1. Storage<br /> |-<br /> |'''Supported Storage'''<br /> |Supported types of Storage (DAS, NAS or SAN)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS, NAS (NFS, ZFS), SAN (iSCSI), Ceph <br /> |DAS, NAS (SMB), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |-<br /> |'''Virtual Disk Format'''<br /> |Supported format(s) of the virtual disks for the virtual machines<br /> |CT - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |Any<br /> |Qcow2, vmdk, raw<br /> |vhdx, vhd, pass-though (raw)<br /> |Qcow2, raw disk<br /> |vhd, raw disk<br /> |-<br /> |'''Thin Disk Provisioning'''<br /> |Ability to over-commit overall disk space by dynamically growing the size of virtual disks based on actual usage rather than pre-allocating full size.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, depends on disk format (dm-thin)<br /> |{{Yes}}, depends on underlying storage driver<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Virtual SAN'''<br /> |Enhanced storage capability e.g. providing a virtual SAN through virtualized 'local' storage <br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS, sheepdog)<br /> |{{Yes}}, Storage Spaces<br /> |{{Yes}}, Red Hat Storage<br /> |{{No}}<br /> |-<br /> |'''Storage QoS'''<br /> |Ability to control Quality of Service for Storage I/O or Throughput for CT/VM<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}, VMs only<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|4.2. Network<br /> |-<br /> |'''Network QoS'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |{{Yes}}, with Open vSwitch <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|5. Others – most of features are relevant only for Virtuozzo editions<br /> |-<br /> |'''Memory deduplication for binary files'''<br /> |Memory and IOPS deduplication management that enables/disables caching for Container directories and files, verifies cache integrity, checks Containers for cache errors, and purges the cache if needed<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{No}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''Completely isolated disk subsystem for CTs'''<br /> |<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, with LVM<br /> |{{Yes}}, LVM, ZFS, or loop devices<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''API\SDK'''<br /> |<br /> |OpenVZ API for Ruby, LibVirt<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |LibLXC, API for Ruby, Python 2, Haskell, Go<br /> |Proxmox VE uses a REST like API (JSON data format)<br /> |Windows SDK<br /> |RHEV-M API: REST API, SDKs<br /> |XenAPI, XenServer SDKs<br /> |-<br /> |'''Image Catalog integration'''<br /> |Integration with 3rd-party image catalog services of popular server applications and development environments that can be installed with one click.<br /> |{{No}}<br /> |{{Yes}} Application Image Catalog [https://virtuozzo.com/introducing-the-virtuozzo-application-catalog/ Virtuozzo Application Catalog]<br /> |{{No}}<br /> |{{Yes}} Application Image Catalog [https://virtuozzo.com/introducing-the-virtuozzo-application-catalog/ Virtuozzo Application Catalog]<br /> |{{No}}<br /> |{{Yes}} (Turnkey)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Kernel update without reboot'''<br /> |Integrated ability to upgrade kernel or install security patches without downtime.<br /> |{{No}}, only 3d party tools<br /> |{{Yes}}, Rebootless Kernel Update<br /> |{{No}}<br /> |{{Yes}} [https://readykernel.com/ ReadyKernel Service]<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |N/A<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |-<br /> |'''Power Panel'''<br /> |A tool used for managing particular virtual machines and containers by their end users.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Secure for using in public networks'''<br /> |<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|6. Commercial<br /> |-<br /> |'''Open Source'''<br /> |<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}} (but there is Open Source edition(oVirt))<br /> |{{No}} (but there is Open Source edition)<br /> |-<br /> |'''License\Subscription'''<br /> |<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, Enterprise Edition<br /> |-<br /> |'''Support'''<br /> |<br /> |Both community and commercial support<br /> |Commercial support<br /> |Community support<br /> |Commercial Support<br /> |Yes, Canonical Ltd.<br /> |Both community and commercial support<br /> |Commercial support<br /> |Commercial support<br /> |Both community and commercial support<br /> |-<br /> |'''EOL policy'''<br /> |<br /> |[[Releases|5 years of support]]<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |TBD<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |<br /> |<br /> |[https://support.microsoft.com/en-us/lifecycle/search/default.aspx?alpha=hyper-v 11 years of support]]<br /> |<br /> |<br /> |-<br /> |}</div>

Vporokhov https://wiki.openvz.org/index.php?title=Comparison&diff=22466 2016-12-01T11:51:19Z

<p>Vporokhov: </p> <hr /> <div>{{Note|This comparison doesn't include Docker, because Docker is not a virtualization solution. It automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of operating-system-level virtualization.&lt;ref&gt;[https://en.wikipedia.org/wiki/Docker_(software) Wikipedia article about Docker]&lt;/ref&gt;}}<br /> <br /> <br /> == Disclaimer ==<br /> <br /> The information regarding Virtuozzo 7 is provided by [http://www.virtuozzo.com Virtuozzo]. Here is the Virtuozzo's statement regarding this information:<br /> <br /> :#The information contained herein is intended to outline general product direction and should not be relied upon in making purchasing decisions.<br /> :#The content is for informational purposes only and may not be incorporated into any contract.<br /> :#The information presented is not a commitment, promise, or legal obligation to deliver any material, code or functionality.<br /> :#Any references to the development, release, and timing of any features or functionality described for these products remains at Virtuozzo’s sole discretion.<br /> :#Product capabilities, timeframes and features are subject to change and should not be viewed as Virtuozzo commitments.<br /> <br /> The information regarding all other solutions are taken by authors from public sources only. This information can be changed by any OpenVZ Wiki user without any notice and author's review or approval.<br /> <br /> <br /> == Feature comparison of different virtualization solutions ==<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> ! Feature<br /> ! Description<br /> ! OpenVZ<br /> ! Virtuozzo&amp;nbsp;6 (PCS 6)<br /> ! OpenVZ&amp;nbsp;7<br /> ! [https://virtuozzo.com/products/virtuozzo-containers/ Virtuozzo&amp;nbsp;7]<br /> ! LXC<br /> ! Proxmox VE<br /> ! Microsoft Hyper-V 2012 R2<br /> ! RHEV 3.5<br /> ! Citrix XenServer 6.5<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|1. Virtualization platform<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.1. Overview<br /> |-<br /> |'''HW virtualization support (Hypervisor)'''<br /> |Full emulation of underneath hardware level: full isolation guest environment, no dependencies from host OS, overhead for hypervisor layer.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''OS-level virtualization (Containers)'''<br /> |Sharing the same instance of host OS: high density, high performance, high dependencies from host OS.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Hypervisor technology'''<br /> |Technology that enables to run Virtual Machines.<br /> |{{No}}<br /> |Parallels Desktop Monitor<br /> |KVM<br /> |KVM<br /> |None<br /> |KVM<br /> |Hyper-V<br /> |KVM<br /> |Xen<br /> |-<br /> |'''Windows guest OS additional support'''<br /> |WHQL-signed drivers, SVVP certification<br /> |N/A<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Containers technology'''<br /> |Technology that enables to run Containers.<br /> |Virtuozzo Containers<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Linux containers<br /> |LXC (moved from OpenVZ since 4.0)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.2. Memory<br /> |-<br /> |'''Memory Overcommit'''<br /> |Ability to present more memory to virtual machines than physically available <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, with new VCMMD memory management<br /> |{{Yes}}, with new VCMMD memory management<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Page sharing'''<br /> |Memory (RAM) savings through sharing identical memory pages across virtual machines<br /> |{{Yes}}<br /> |{{Yes}}, only for CTs<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> |'''Online Memory Management for VM'''<br /> |Ability to change amount of RAM for CT and VM without reboot<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |N/A<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|2. Management<br /> |-<br /> !colspan=&quot;11&quot;|2.1. General<br /> |-<br /> |'''Unified management tool for CTs and VMs'''<br /> |Single tool for managing both containers and virtual machines (if applicable)<br /> |N/A<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''OpenStack integration'''<br /> |Integration with OpenStack components ([http://docs.openstack.org/developer/nova/support-matrix.html see details])<br /> |{{Yes}}, only Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated GUI'''<br /> |Centralized multi-server management<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}, Parallels Virtual Automation (PVA)<br /> |{{No}}<br /> |{{Yes}}, [https://virtuozzo.com/support/pva/ Virtual Automator]<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}<br /> |{{Yes}}, System Center Virtual Machine Manager<br /> |{{Yes}}, RHEV Manager<br /> |{{Yes}}, XenCenter<br /> |-<br /> !colspan=&quot;11&quot;|2.2. Upgrade &amp; Backup<br /> |-<br /> |'''Live VE snapshot'''<br /> |Ability to take a snapshot of a virtual environment while the guest OS is running (e.g. for roll-back or backup purposes)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated Backup'''<br /> |Are backup plugins/tools provided to backup virtual environments (over and above the ability to perform classic backup using agents in the guests)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Backup Integration API'''<br /> |Integration with 3rd party backup applications for backup of the virtual environment.<br /> |{{No}} (only through snapshots)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}} (only through snapshots)<br /> |{{Yes}} (vzdump)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot;|2.3. Others<br /> |-<br /> |'''VEs Templates (VM, CT)'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |{{Yes}} (CT only)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}} <br /> |{{Yes}} (OpenVZ templates)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''P2V migration'''<br /> |Integrated or added P2V (or V2V) capability in order to convert physical systems to virtual environment.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}, 3rd party tools<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|3. VE Mobility and HA<br /> |-<br /> !colspan=&quot;11&quot;|3.1. VE Mobility<br /> |-<br /> |'''Live Migration'''<br /> |Ability to migrate virtual machines between hosts without perceived downtime<br /> |{{Yes}}, but with no zero downtime<br /> |{{Yes}}, Kernel-Level Migration<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''DRS/Host Maintenance Mode'''<br /> |Ability to put host into maintenance mode which will automatically live migrate all VEs onto other available hosts so that the host can be brought shut down safely<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Distributed Power Management'''<br /> |Distributed Power Management features Ability to automatically migrate VEs onto fewer hosts and power off unused capacity (hosts), wake systems back up when required <br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|3.2. HA / DR<br /> |-<br /> |'''Cluster size'''<br /> |Maximum number of hosts in the cluster/pool relationship and maximum number VEs per cluster/pool (if specified)<br /> |None<br /> |32 hosts/cluster validated (100 hosts/cluster maximum) - PStorage limitation<br /> |Not tested yet<br /> |Not tested yet<br /> |None<br /> |32 nodes<br /> |64 nodes<br /> |200 nodes<br /> |16 nodes<br /> |-<br /> |'''Integrated HA'''<br /> |Recover virtual environment in case of host failures through restart on alternative hosts (downtime = restart time)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Site Failover'''<br /> |Integrated ability to (ideally live) migrate virtual machine data (virtual disk files) to different storage e.g. for array upgrades/migration and I/O management<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |Manual<br /> |{{No}}<br /> |Integrated Disaster Recovery - manual<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|4. Network and Storage<br /> |-<br /> !colspan=&quot;11&quot;|4.1. Storage<br /> |-<br /> |'''Supported Storage'''<br /> |Supported types of Storage (DAS, NAS or SAN)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS, NAS (NFS, ZFS), SAN (iSCSI), Ceph <br /> |DAS, NAS (SMB), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |-<br /> |'''Virtual Disk Format'''<br /> |Supported format(s) of the virtual disks for the virtual machines<br /> |CT - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |Any<br /> |Qcow2, vmdk, raw<br /> |vhdx, vhd, pass-though (raw)<br /> |Qcow2, raw disk<br /> |vhd, raw disk<br /> |-<br /> |'''Thin Disk Provisioning'''<br /> |Ability to over-commit overall disk space by dynamically growing the size of virtual disks based on actual usage rather than pre-allocating full size.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, depends on disk format (dm-thin)<br /> |{{Yes}}, depends on underlying storage driver<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Virtual SAN'''<br /> |Enhanced storage capability e.g. providing a virtual SAN through virtualized 'local' storage <br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS, sheepdog)<br /> |{{Yes}}, Storage Spaces<br /> |{{Yes}}, Red Hat Storage<br /> |{{No}}<br /> |-<br /> |'''Storage QoS'''<br /> |Ability to control Quality of Service for Storage I/O or Throughput for CT/VM<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}, VMs only<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|4.2. Network<br /> |-<br /> |'''Advanced Network Switch'''<br /> |Centralized virtual network configuration (rather than managing virtual switches on individual hosts), typically with enhanced networking capabilities<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}, Open vSwitch support<br /> |{{Yes}}<br /> |OpenStack Neutron Integration<br /> |Open vSwitch integration<br /> |-<br /> |'''Network QoS'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |{{Yes}}, with Open vSwitch <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|5. Others – most of features are relevant only for Virtuozzo editions<br /> |-<br /> |'''Memory deduplication for binary files'''<br /> |Memory and IOPS deduplication management that enables/disables caching for Container directories and files, verifies cache integrity, checks Containers for cache errors, and purges the cache if needed<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{No}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''Completely isolated disk subsystem for CTs'''<br /> |<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, with LVM<br /> |{{Yes}}, LVM, ZFS, or loop devices<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''API\SDK'''<br /> |<br /> |OpenVZ API for Ruby, LibVirt<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |LibLXC, API for Ruby, Python 2, Haskell, Go<br /> |Proxmox VE uses a REST like API (JSON data format)<br /> |Windows SDK<br /> |RHEV-M API: REST API, SDKs<br /> |XenAPI, XenServer SDKs<br /> |-<br /> |'''Image Catalog integration'''<br /> |Integration with 3rd-party image catalog services of popular server applications and development environments that can be installed with one click.<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}} Application Image Catalog [https://virtuozzo.com/introducing-the-virtuozzo-application-catalog/ Virtuozzo Application Catalog]<br /> |{{No}}<br /> |{{Yes}} (Turnkey)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Kernel update without reboot'''<br /> |Integrated ability to upgrade kernel or install security patches without downtime.<br /> |{{No}}, only 3d party tools<br /> |{{Yes}}, Rebootless Kernel Update<br /> |{{No}}<br /> |{{Yes}} [https://readykernel.com/ ReadyKernel Service]<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |N/A<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |-<br /> |'''Power Panel'''<br /> |A tool used for managing particular virtual machines and containers by their end users.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Secure for using in public networks'''<br /> |<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|6. Commercial<br /> |-<br /> |'''Open Source'''<br /> |<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}} (but there is Open Source edition(oVirt))<br /> |{{No}} (but there is Open Source edition)<br /> |-<br /> |'''License\Subscription'''<br /> |<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, Enterprise Edition<br /> |-<br /> |'''Support'''<br /> |<br /> |Both community and commercial support<br /> |Commercial support<br /> |Community support<br /> |Commercial Support<br /> |Yes, Canonical Ltd.<br /> |Both community and commercial support<br /> |Commercial support<br /> |Commercial support<br /> |Both community and commercial support<br /> |-<br /> |'''EOL policy'''<br /> |<br /> |[[Releases|5 years of support]]<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |TBD<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |<br /> |<br /> |[https://support.microsoft.com/en-us/lifecycle/search/default.aspx?alpha=hyper-v 11 years of support]]<br /> |<br /> |<br /> |-<br /> |}</div>

Vporokhov https://wiki.openvz.org/index.php?title=Comparison&diff=22465 2016-12-01T11:49:08Z

<p>Vporokhov: </p> <hr /> <div>{{Note|This comparison doesn't include Docker, because Docker is not a virtualization solution. It automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of operating-system-level virtualization.&lt;ref&gt;[https://en.wikipedia.org/wiki/Docker_(software) Wikipedia article about Docker]&lt;/ref&gt;}}<br /> <br /> <br /> == Disclaimer ==<br /> <br /> The information regarding Virtuozzo 7 is provided by [http://www.virtuozzo.com Virtuozzo]. Here is the Virtuozzo's statement regarding this information:<br /> <br /> :#The information contained herein is intended to outline general product direction and should not be relied upon in making purchasing decisions.<br /> :#The content is for informational purposes only and may not be incorporated into any contract.<br /> :#The information presented is not a commitment, promise, or legal obligation to deliver any material, code or functionality.<br /> :#Any references to the development, release, and timing of any features or functionality described for these products remains at Virtuozzo’s sole discretion.<br /> :#Product capabilities, timeframes and features are subject to change and should not be viewed as Virtuozzo commitments.<br /> <br /> The information regarding all other solutions are taken by authors from public sources only. This information can be changed by any OpenVZ Wiki user without any notice and author's review or approval.<br /> <br /> <br /> == Feature comparison of different virtualization solutions ==<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> ! Feature<br /> ! Description<br /> ! OpenVZ<br /> ! Virtuozzo&amp;nbsp;6 (PCS 6)<br /> ! OpenVZ&amp;nbsp;7<br /> ! [https://virtuozzo.com/products/virtuozzo-containers/ Virtuozzo&amp;nbsp;7]<br /> ! LXC<br /> ! Proxmox VE<br /> ! Microsoft Hyper-V 2012 R2<br /> ! RHEV 3.5<br /> ! Citrix XenServer 6.5<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|1. Virtualization platform<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.1. Overview<br /> |-<br /> |'''HW virtualization support (Hypervisor)'''<br /> |Full emulation of underneath hardware level: full isolation guest environment, no dependencies from host OS, overhead for hypervisor layer.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''OS-level virtualization (Containers)'''<br /> |Sharing the same instance of host OS: high density, high performance, high dependencies from host OS.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Hypervisor technology'''<br /> |Technology that enables to run Virtual Machines.<br /> |{{No}}<br /> |Parallels Desktop Monitor<br /> |KVM<br /> |KVM<br /> |None<br /> |KVM<br /> |Hyper-V<br /> |KVM<br /> |Xen<br /> |-<br /> |'''Windows guest OS additional support'''<br /> |WHQL-signed drivers, SVVP certification<br /> |N/A<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Containers technology'''<br /> |Technology that enables to run Containers.<br /> |Virtuozzo Containers<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Linux containers<br /> |LXC (moved from OpenVZ since 4.0)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.2. Memory<br /> |-<br /> |'''Memory Overcommit'''<br /> |Ability to present more memory to virtual machines than physically available <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, with new VCMMD memory management<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Page sharing'''<br /> |Memory (RAM) savings through sharing identical memory pages across virtual machines<br /> |{{Yes}}<br /> |{{Yes}}, only for CTs<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> |'''Online Memory Management for VM'''<br /> |Ability to change amount of RAM for CT and VM without reboot<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |N/A<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|2. Management<br /> |-<br /> !colspan=&quot;11&quot;|2.1. General<br /> |-<br /> |'''Unified management tool for CTs and VMs'''<br /> |Single tool for managing both containers and virtual machines (if applicable)<br /> |N/A<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''OpenStack integration'''<br /> |Integration with OpenStack components ([http://docs.openstack.org/developer/nova/support-matrix.html see details])<br /> |{{Yes}}, only Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated GUI'''<br /> |Centralized multi-server management<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}, Parallels Virtual Automation (PVA)<br /> |{{No}}<br /> |{{Yes}}, [https://virtuozzo.com/support/pva/ Virtual Automator]<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}<br /> |{{Yes}}, System Center Virtual Machine Manager<br /> |{{Yes}}, RHEV Manager<br /> |{{Yes}}, XenCenter<br /> |-<br /> !colspan=&quot;11&quot;|2.2. Upgrade &amp; Backup<br /> |-<br /> |'''Live VE snapshot'''<br /> |Ability to take a snapshot of a virtual environment while the guest OS is running (e.g. for roll-back or backup purposes)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated Backup'''<br /> |Are backup plugins/tools provided to backup virtual environments (over and above the ability to perform classic backup using agents in the guests)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Backup Integration API'''<br /> |Integration with 3rd party backup applications for backup of the virtual environment.<br /> |{{No}} (only through snapshots)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}} (only through snapshots)<br /> |{{Yes}} (vzdump)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot;|2.3. Others<br /> |-<br /> |'''VEs Templates (VM, CT)'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |{{Yes}} (CT only)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}} <br /> |{{Yes}} (OpenVZ templates)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''P2V migration'''<br /> |Integrated or added P2V (or V2V) capability in order to convert physical systems to virtual environment.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}, 3rd party tools<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|3. VE Mobility and HA<br /> |-<br /> !colspan=&quot;11&quot;|3.1. VE Mobility<br /> |-<br /> |'''Live Migration'''<br /> |Ability to migrate virtual machines between hosts without perceived downtime<br /> |{{Yes}}, but with no zero downtime<br /> |{{Yes}}, Kernel-Level Migration<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''DRS/Host Maintenance Mode'''<br /> |Ability to put host into maintenance mode which will automatically live migrate all VEs onto other available hosts so that the host can be brought shut down safely<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Distributed Power Management'''<br /> |Distributed Power Management features Ability to automatically migrate VEs onto fewer hosts and power off unused capacity (hosts), wake systems back up when required <br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|3.2. HA / DR<br /> |-<br /> |'''Cluster size'''<br /> |Maximum number of hosts in the cluster/pool relationship and maximum number VEs per cluster/pool (if specified)<br /> |None<br /> |32 hosts/cluster validated (100 hosts/cluster maximum) - PStorage limitation<br /> |Not tested yet<br /> |Not tested yet<br /> |None<br /> |32 nodes<br /> |64 nodes<br /> |200 nodes<br /> |16 nodes<br /> |-<br /> |'''Integrated HA'''<br /> |Recover virtual environment in case of host failures through restart on alternative hosts (downtime = restart time)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Site Failover'''<br /> |Integrated ability to (ideally live) migrate virtual machine data (virtual disk files) to different storage e.g. for array upgrades/migration and I/O management<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |Manual<br /> |{{No}}<br /> |Integrated Disaster Recovery - manual<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|4. Network and Storage<br /> |-<br /> !colspan=&quot;11&quot;|4.1. Storage<br /> |-<br /> |'''Supported Storage'''<br /> |Supported types of Storage (DAS, NAS or SAN)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS, NAS (NFS, ZFS), SAN (iSCSI), Ceph <br /> |DAS, NAS (SMB), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |-<br /> |'''Virtual Disk Format'''<br /> |Supported format(s) of the virtual disks for the virtual machines<br /> |CT - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |Any<br /> |Qcow2, vmdk, raw<br /> |vhdx, vhd, pass-though (raw)<br /> |Qcow2, raw disk<br /> |vhd, raw disk<br /> |-<br /> |'''Thin Disk Provisioning'''<br /> |Ability to over-commit overall disk space by dynamically growing the size of virtual disks based on actual usage rather than pre-allocating full size.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, depends on disk format (dm-thin)<br /> |{{Yes}}, depends on underlying storage driver<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Virtual SAN'''<br /> |Enhanced storage capability e.g. providing a virtual SAN through virtualized 'local' storage <br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS, sheepdog)<br /> |{{Yes}}, Storage Spaces<br /> |{{Yes}}, Red Hat Storage<br /> |{{No}}<br /> |-<br /> |'''Storage QoS'''<br /> |Ability to control Quality of Service for Storage I/O or Throughput for CT/VM<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}, VMs only<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|4.2. Network<br /> |-<br /> |'''Advanced Network Switch'''<br /> |Centralized virtual network configuration (rather than managing virtual switches on individual hosts), typically with enhanced networking capabilities<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}, Open vSwitch support<br /> |{{Yes}}<br /> |OpenStack Neutron Integration<br /> |Open vSwitch integration<br /> |-<br /> |'''Network QoS'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |{{Yes}}, with Open vSwitch <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|5. Others – most of features are relevant only for Virtuozzo editions<br /> |-<br /> |'''Memory deduplication for binary files'''<br /> |Memory and IOPS deduplication management that enables/disables caching for Container directories and files, verifies cache integrity, checks Containers for cache errors, and purges the cache if needed<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{No}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''Completely isolated disk subsystem for CTs'''<br /> |<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, with LVM<br /> |{{Yes}}, LVM, ZFS, or loop devices<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''API\SDK'''<br /> |<br /> |OpenVZ API for Ruby, LibVirt<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |LibLXC, API for Ruby, Python 2, Haskell, Go<br /> |Proxmox VE uses a REST like API (JSON data format)<br /> |Windows SDK<br /> |RHEV-M API: REST API, SDKs<br /> |XenAPI, XenServer SDKs<br /> |-<br /> |'''Image Catalog integration'''<br /> |Integration with 3rd-party image catalog services of popular server applications and development environments that can be installed with one click.<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}} Application Image Catalog [https://virtuozzo.com/introducing-the-virtuozzo-application-catalog/ Virtuozzo Application Catalog]<br /> |{{No}}<br /> |{{Yes}} (Turnkey)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Kernel update without reboot'''<br /> |Integrated ability to upgrade kernel or install security patches without downtime.<br /> |{{No}}, only 3d party tools<br /> |{{Yes}}, Rebootless Kernel Update<br /> |{{No}}<br /> |{{Yes}} [https://readykernel.com/ ReadyKernel Service]<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |N/A<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |-<br /> |'''Power Panel'''<br /> |A tool used for managing particular virtual machines and containers by their end users.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Secure for using in public networks'''<br /> |<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|6. Commercial<br /> |-<br /> |'''Open Source'''<br /> |<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}} (but there is Open Source edition(oVirt))<br /> |{{No}} (but there is Open Source edition)<br /> |-<br /> |'''License\Subscription'''<br /> |<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, Enterprise Edition<br /> |-<br /> |'''Support'''<br /> |<br /> |Both community and commercial support<br /> |Commercial support<br /> |Community support<br /> |Commercial Support<br /> |Yes, Canonical Ltd.<br /> |Both community and commercial support<br /> |Commercial support<br /> |Commercial support<br /> |Both community and commercial support<br /> |-<br /> |'''EOL policy'''<br /> |<br /> |[[Releases|5 years of support]]<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |TBD<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |<br /> |<br /> |[https://support.microsoft.com/en-us/lifecycle/search/default.aspx?alpha=hyper-v 11 years of support]]<br /> |<br /> |<br /> |-<br /> |}</div>

Vporokhov https://wiki.openvz.org/index.php?title=Comparison&diff=22464 2016-12-01T11:40:32Z

<p>Vporokhov: </p> <hr /> <div>{{Note|This comparison doesn't include Docker, because Docker is not a virtualization solution. It automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of operating-system-level virtualization.&lt;ref&gt;[https://en.wikipedia.org/wiki/Docker_(software) Wikipedia article about Docker]&lt;/ref&gt;}}<br /> <br /> <br /> == Disclaimer ==<br /> <br /> The information regarding Virtuozzo 7 is provided by [http://www.virtuozzo.com Virtuozzo]. Here is the Virtuozzo's statement regarding this information:<br /> <br /> :#The information contained herein is intended to outline general product direction and should not be relied upon in making purchasing decisions.<br /> :#The content is for informational purposes only and may not be incorporated into any contract.<br /> :#The information presented is not a commitment, promise, or legal obligation to deliver any material, code or functionality.<br /> :#Any references to the development, release, and timing of any features or functionality described for these products remains at Virtuozzo’s sole discretion.<br /> :#Product capabilities, timeframes and features are subject to change and should not be viewed as Virtuozzo commitments.<br /> <br /> The information regarding all other solutions are taken by authors from public sources only. This information can be changed by any OpenVZ Wiki user without any notice and author's review or approval.<br /> <br /> <br /> == Feature comparison of different virtualization solutions ==<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> ! Feature<br /> ! Description<br /> ! OpenVZ<br /> ! Virtuozzo&amp;nbsp;6 (PCS 6)<br /> ! OpenVZ&amp;nbsp;7<br /> ! [https://virtuozzo.com/products/virtuozzo-containers/ Virtuozzo&amp;nbsp;7]<br /> ! LXC<br /> ! Proxmox VE<br /> ! Microsoft Hyper-V 2012 R2<br /> ! RHEV 3.5<br /> ! Citrix XenServer 6.5<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|1. Virtualization platform<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.1. Overview<br /> |-<br /> |'''HW virtualization support (Hypervisor)'''<br /> |Full emulation of underneath hardware level: full isolation guest environment, no dependencies from host OS, overhead for hypervisor layer.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''OS-level virtualization (Containers)'''<br /> |Sharing the same instance of host OS: high density, high performance, high dependencies from host OS.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Hypervisor technology'''<br /> |Technology that enables to run Virtual Machines.<br /> |{{No}}<br /> |Parallels Desktop Monitor<br /> |KVM<br /> |KVM<br /> |None<br /> |KVM<br /> |Hyper-V<br /> |KVM<br /> |Xen<br /> |-<br /> |'''Windows guest OS additional support'''<br /> |WHQL-signed drivers, SVVP certification<br /> |None<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Containers technology'''<br /> |Technology that enables to run Containers.<br /> |Virtuozzo Containers<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Linux containers<br /> |LXC (moved from OpenVZ since 4.0)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.2. Memory<br /> |-<br /> |'''Memory Overcommit'''<br /> |Ability to present more memory to virtual machines than physically available <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, with new VCMMD memory management<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Page sharing'''<br /> |Memory (RAM) savings through sharing identical memory pages across virtual machines<br /> |{{Yes}}<br /> |{{Yes}}, only for CTs<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> |'''Online Memory Management for VM'''<br /> |Ability to change amount of RAM for CT and VM without reboot<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |N/A<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|2. Management<br /> |-<br /> !colspan=&quot;11&quot;|2.1. General<br /> |-<br /> |'''Unified management tool for CTs and VMs'''<br /> |Single tool for managing both containers and virtual machines (if applicable)<br /> |None<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''OpenStack integration'''<br /> |Integration with OpenStack components ([http://docs.openstack.org/developer/nova/support-matrix.html see details])<br /> |{{Yes}}, only Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Central Management tool'''<br /> |Is centralized multi-server management available for this edition?<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}, Parallels Virtual Automation (PVA)<br /> |{{No}}<br /> |{{Yes}}, [https://virtuozzo.com/support/pva/ Virtual Automator]<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}<br /> |{{Yes}}, System Center Virtual Machine Manager<br /> |{{Yes}}, RHEV Manager<br /> |{{Yes}}, XenCenter<br /> |-<br /> !colspan=&quot;11&quot;|2.2. Upgrade &amp; Backup<br /> |-<br /> |'''Update Management'''<br /> |Integrated patching mechanism for the virtual environments (Guest OS) / guest tools / templates<br /> |No integrated update, YUM (Linux)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, APT (Linux)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |Yes (WSUS, SCCM, Virtual Machine Servicing Tool 2012 for offline VM update)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |-<br /> |'''Live VE snapshot'''<br /> |Ability to take a snapshot of a virtual environment while the guest OS is running (e.g. for roll-back or backup purposes)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated Backup'''<br /> |Are backup plugins/tools provided to backup virtual environments (over and above the ability to perform classic backup using agents in the guests)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Backup Integration API'''<br /> |Integration with 3rd party backup applications for backup of the virtual environment.<br /> |{{No}} (only through snapshots)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}} (only through snapshots)<br /> |{{Yes}} (vzdump)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot;|2.3. Others<br /> |-<br /> |'''VEs Templates (VM, CT)'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |{{Yes}} (CT only)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}} <br /> |{{Yes}} (OpenVZ templates)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''P2V migration'''<br /> |Integrated or added P2V (or V2V) capability in order to convert physical systems to virtual environment.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}, 3rd party tools<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|3. VE Mobility and HA<br /> |-<br /> !colspan=&quot;11&quot;|3.1. VE Mobility<br /> |-<br /> |'''Live Migration'''<br /> |Ability to migrate virtual machines between hosts without perceived downtime<br /> |{{Yes}}, but with no zero downtime<br /> |{{Yes}}, Kernel-Level Migration<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''DRS/Host Maintenance Mode'''<br /> |Ability to put host into maintenance mode which will automatically live migrate all VEs onto other available hosts so that the host can be brought shut down safely<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Distributed Power Management'''<br /> |Distributed Power Management features Ability to automatically migrate VEs onto fewer hosts and power off unused capacity (hosts), wake systems back up when required <br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|3.2. HA / DR<br /> |-<br /> |'''Cluster size'''<br /> |Maximum number of hosts in the cluster/pool relationship and maximum number VEs per cluster/pool (if specified)<br /> |None<br /> |32 hosts/cluster validated (100 hosts/cluster maximum) - PStorage limitation<br /> |Not tested yet<br /> |Not tested yet<br /> |None<br /> |32 nodes<br /> |64 nodes<br /> |200 nodes<br /> |16 nodes<br /> |-<br /> |'''Integrated HA'''<br /> |Recover virtual environment in case of host failures through restart on alternative hosts (downtime = restart time)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Site Failover'''<br /> |Integrated ability to (ideally live) migrate virtual machine data (virtual disk files) to different storage e.g. for array upgrades/migration and I/O management<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |Manual<br /> |{{No}}<br /> |Integrated Disaster Recovery - manual<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|4. Network and Storage<br /> |-<br /> !colspan=&quot;11&quot;|4.1. Storage<br /> |-<br /> |'''Supported Storage'''<br /> |Supported types of Storage (DAS, NAS or SAN)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS, NAS (NFS, ZFS), SAN (iSCSI), Ceph <br /> |DAS, NAS (SMB), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |-<br /> |'''Virtual Disk Format'''<br /> |Supported format(s) of the virtual disks for the virtual machines<br /> |CT - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |Any<br /> |qcow2, vmdk, raw<br /> |vhdx, vhd, pass-though (raw)<br /> |Qcow2, raw disk<br /> |vhd, raw disk<br /> |-<br /> |'''Thin Disk Provisioning'''<br /> |Ability to over-commit overall disk space by dynamically growing the size of virtual disks based on actual usage rather than pre-allocating full size.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, depends on disk format (dm-thin)<br /> |{{Yes}} (depends on underlying storage driver)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Virtual SAN'''<br /> |Enhanced storage capability e.g. providing a virtual SAN through virtualized 'local' storage <br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS, sheepdog)<br /> |{{Yes}}, Storage Spaces<br /> |{{Yes}}, Red Hat Storage<br /> |{{No}}<br /> |-<br /> |'''Storage QoS'''<br /> |Ability to control Quality of Service for Storage I/O or Throughput for CT/VM<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}, VMs only<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|4.2. Network<br /> |-<br /> |'''Advanced Network Switch'''<br /> |Centralized virtual network configuration (rather than managing virtual switches on individual hosts), typically with enhanced networking capabilities<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}, Open vSwitch support<br /> |{{Yes}}<br /> |OpenStack Neutron Integration<br /> |Open vSwitch integration<br /> |-<br /> |'''Network QoS'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |{{Yes}}, with Open vSwitch <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|5. Others – most of features are relevant only for Virtuozzo editions<br /> |-<br /> |'''Memory deduplication for binary files'''<br /> |Memory and IOPS deduplication management that enables/disables caching for Container directories and files, verifies cache integrity, checks Containers for cache errors, and purges the cache if needed<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{No}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''Completely isolated disk subsystem for CTs'''<br /> |<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, with LVM<br /> |{{Yes}}, LVM, ZFS, or loop devices<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''API\SDK'''<br /> |<br /> |OpenVZ API for Ruby, LibVirt<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |LibLXC, API for Ruby, Python 2, Haskell, Go<br /> |Proxmox VE uses a REST like API (JSON data format)<br /> |Windows SDK<br /> |RHEV-M API: REST API, SDKs<br /> |XenAPI, XenServer SDKs<br /> |-<br /> |'''Image Catalog integration'''<br /> |Integration with 3rd-party image catalog services of popular server applications and development environments that can be installed with one click.<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}} Application Image Catalog [https://virtuozzo.com/introducing-the-virtuozzo-application-catalog/ Virtuozzo Application Catalog]<br /> |{{No}}<br /> |{{Yes}} (Turnkey)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Kernel update without reboot'''<br /> |Integrated ability to upgrade kernel or install security patches without downtime.<br /> |{{No}}, only 3d party tools<br /> |{{Yes}}, Rebootless Kernel Update<br /> |{{No}}<br /> |{{Yes}} [https://readykernel.com/ ReadyKernel Service]<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |N/A<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |-<br /> |'''Power Panel'''<br /> |A tool used for managing particular virtual machines and containers by their end users.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Secure for using in public networks'''<br /> |<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|6. Commercial<br /> |-<br /> |'''Open Source'''<br /> |<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}} (but there is Open Source edition(oVirt))<br /> |{{No}} (but there is Open Source edition)<br /> |-<br /> |'''License\Subscription'''<br /> |<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, Enterprise Edition<br /> |-<br /> |'''Support'''<br /> |<br /> |Both community and commercial support<br /> |Commercial support<br /> |Community support<br /> |Commercial Support<br /> |Yes, Canonical Ltd.<br /> |Both community and commercial support<br /> |Commercial support<br /> |Commercial support<br /> |Both community and commercial support<br /> |-<br /> |'''EOL policy'''<br /> |<br /> |[[Releases|5 years of support]]<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |TBD<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |<br /> |<br /> |[https://support.microsoft.com/en-us/lifecycle/search/default.aspx?alpha=hyper-v 11 years of support]]<br /> |<br /> |<br /> |-<br /> |}</div>

Vporokhov https://wiki.openvz.org/index.php?title=Comparison&diff=22463 2016-12-01T11:39:52Z

<p>Vporokhov: </p> <hr /> <div>{{Note|This comparison doesn't include Docker, because Docker is not a virtualization solution. It automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of operating-system-level virtualization.&lt;ref&gt;[https://en.wikipedia.org/wiki/Docker_(software) Wikipedia article about Docker]&lt;/ref&gt;}}<br /> <br /> <br /> == Disclaimer ==<br /> <br /> The information regarding Virtuozzo 7 is provided by [http://www.virtuozzo.com Virtuozzo]. Here is the Virtuozzo's statement regarding this information:<br /> <br /> :#The information contained herein is intended to outline general product direction and should not be relied upon in making purchasing decisions.<br /> :#The content is for informational purposes only and may not be incorporated into any contract.<br /> :#The information presented is not a commitment, promise, or legal obligation to deliver any material, code or functionality.<br /> :#Any references to the development, release, and timing of any features or functionality described for these products remains at Virtuozzo’s sole discretion.<br /> :#Product capabilities, timeframes and features are subject to change and should not be viewed as Virtuozzo commitments.<br /> <br /> The information regarding all other solutions are taken by authors from public sources only. This information can be changed by any OpenVZ Wiki user without any notice and author's review or approval.<br /> <br /> <br /> == Feature comparison of different virtualization solutions ==<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> ! Feature<br /> ! Description<br /> ! OpenVZ<br /> ! Virtuozzo&amp;nbsp;6 (PCS 6)<br /> ! OpenVZ&amp;nbsp;7<br /> ! [https://virtuozzo.com/products/virtuozzo-containers/ Virtuozzo&amp;nbsp;7]<br /> ! LXC<br /> ! Proxmox VE<br /> ! Microsoft Hyper-V 2012 R2<br /> ! RHEV 3.5<br /> ! Citrix XenServer 6.5<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|1. Virtualization platform<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.1. Overview<br /> |-<br /> |'''HW virtualization support (Hypervisor)'''<br /> |Full emulation of underneath hardware level: full isolation guest environment, no dependencies from host OS, overhead for hypervisor layer.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''OS-level virtualization (Containers)'''<br /> |Sharing the same instance of host OS: high density, high performance, high dependencies from host OS.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Hypervisor technology'''<br /> |Technology that enables to run Virtual Machines.<br /> |{{No}}<br /> |Parallels Desktop Monitor<br /> |KVM<br /> |KVM<br /> |None<br /> |KVM<br /> |Hyper-V<br /> |KVM<br /> |Xen<br /> |-<br /> |'''Windows guest OS additional support'''<br /> |WHQL-signed drivers, SVVP certification<br /> |None<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Containers technology'''<br /> |Technology that enables to run Containers.<br /> |Virtuozzo Containers<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Linux containers<br /> |LXC (moved from OpenVZ since 4.0)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.2. Memory<br /> |-<br /> |'''Memory Overcommit'''<br /> |Ability to present more memory to virtual machines than physically available <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, with new VCMMD memory management<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Page sharing'''<br /> |Memory (RAM) savings through sharing identical memory pages across virtual machines<br /> |{{Yes}}<br /> |{{Yes}}, only for CTs<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> |'''Online Memory Management for VM'''<br /> |Ability to change amount of RAM for CT and VM without reboot<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |N/A<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|2. Management<br /> |-<br /> !colspan=&quot;11&quot;|2.1. General<br /> |-<br /> |'''Unified management tool for CTs and VMs'''<br /> |Single tool for managing both containers and virtual machines (if applicable)<br /> |None<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''OpenStack integration'''<br /> |Integration with OpenStack components ([http://docs.openstack.org/developer/nova/support-matrix.html see details])<br /> |{{Yes}}, only Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Central Management tool'''<br /> |Is centralized multi-server management available for this edition?<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}, Parallels Virtual Automation (PVA)<br /> |{{No}}<br /> |{{Yes}}, [https://virtuozzo.com/support/pva/ Virtual Automator]<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}<br /> |{{Yes}}, System Center Virtual Machine Manager<br /> |{{Yes}}, RHEV Manager<br /> |{{Yes}}, XenCenter<br /> |-<br /> !colspan=&quot;11&quot;|2.2. Upgrade &amp; Backup<br /> |-<br /> |'''Update Management'''<br /> |Integrated patching mechanism for the virtual environments (Guest OS) / guest tools / templates<br /> |No integrated update, YUM (Linux)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, APT (Linux)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |Yes (WSUS, SCCM, Virtual Machine Servicing Tool 2012 for offline VM update)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |-<br /> |'''Live VE snapshot'''<br /> |Ability to take a snapshot of a virtual environment while the guest OS is running (e.g. for roll-back or backup purposes)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated Backup'''<br /> |Are backup plugins/tools provided to backup virtual environments (over and above the ability to perform classic backup using agents in the guests)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Backup Integration API'''<br /> |Integration with 3rd party backup applications for backup of the virtual environment.<br /> |{{No}} (only through snapshots)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}} (only through snapshots)<br /> |{{Yes}} (vzdump)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot;|2.3. Others<br /> |-<br /> |'''VEs Templates (VM, CT)'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |{{Yes}} (CT only)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}} <br /> |{{Yes}} (OpenVZ templates)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''P2V migration'''<br /> |Integrated or added P2V (or V2V) capability in order to convert physical systems to virtual environment.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}, 3rd party tools<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|3. VE Mobility and HA<br /> |-<br /> !colspan=&quot;11&quot;|3.1. VE Mobility<br /> |-<br /> |'''Live Migration'''<br /> |Ability to migrate virtual machines between hosts without perceived downtime<br /> |{{Yes}}, but with no zero downtime<br /> |{{Yes}}, Kernel-Level Migration<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''DRS/Host Maintenance Mode'''<br /> |Ability to put host into maintenance mode which will automatically live migrate all VEs onto other available hosts so that the host can be brought shut down safely<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Distributed Power Management'''<br /> |Distributed Power Management features Ability to automatically migrate VEs onto fewer hosts and power off unused capacity (hosts), wake systems back up when required <br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|3.2. HA / DR<br /> |-<br /> |'''Cluster size'''<br /> |Maximum number of hosts in the cluster/pool relationship and maximum number VEs per cluster/pool (if specified)<br /> |None<br /> |32 hosts/cluster validated (100 hosts/cluster maximum) - PStorage limitation<br /> |Not tested yet<br /> |Not tested yet<br /> |None<br /> |32 nodes<br /> |64 nodes<br /> |200 nodes<br /> |16 nodes<br /> |-<br /> |'''Integrated HA'''<br /> |Recover virtual environment in case of host failures through restart on alternative hosts (downtime = restart time)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Site Failover'''<br /> |Integrated ability to (ideally live) migrate virtual machine data (virtual disk files) to different storage e.g. for array upgrades/migration and I/O management<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |Manual<br /> |{{No}}<br /> |Integrated Disaster Recovery - manual<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|4. Network and Storage<br /> |-<br /> !colspan=&quot;11&quot;|4.1. Storage<br /> |-<br /> |'''Supported Storage'''<br /> |Supported types of Storage (DAS, NAS or SAN)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS, NAS (NFS, ZFS), SAN (iSCSI), Ceph <br /> |DAS, NAS (SMB), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |-<br /> |'''Virtual Disk Format'''<br /> |Supported format(s) of the virtual disks for the virtual machines<br /> |CT - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |Any<br /> |qcow2, vmdk, raw<br /> |vhdx, vhd, pass-though (raw)<br /> |Qcow2, raw disk<br /> |vhd, raw disk<br /> |-<br /> |'''Thin Disk Provisioning'''<br /> |Ability to over-commit overall disk space by dynamically growing the size of virtual disks based on actual usage rather than pre-allocating full size.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, depends on disk format (dm-thin)<br /> |{{Yes}} (depends on underlying storage driver)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Virtual SAN'''<br /> |Enhanced storage capability e.g. providing a virtual SAN through virtualized 'local' storage <br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS, sheepdog)<br /> |{{Yes}}, Storage Spaces<br /> |{{Yes}}, Red Hat Storage<br /> |{{No}}<br /> |-<br /> |'''Storage QoS'''<br /> |Ability to control Quality of Service for Storage I/O or Throughput for CT/VM<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}, VMs only<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|4.2. Network<br /> |-<br /> |'''Advanced Network Switch'''<br /> |Centralized virtual network configuration (rather than managing virtual switches on individual hosts), typically with enhanced networking capabilities<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}, Open vSwitch support<br /> |{{Yes}}<br /> |OpenStack Neutron Integration<br /> |Open vSwitch integration<br /> |-<br /> |'''Network QoS'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |{{Yes}}, with Open vSwitch <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|5. Others – most of features are relevant only for Virtuozzo editions<br /> |-<br /> |'''Memory deduplication for binary files'''<br /> |Memory and IOPS deduplication management that enables/disables caching for Container directories and files, verifies cache integrity, checks Containers for cache errors, and purges the cache if needed<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{No}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''Completely isolated disk subsystem for CTs'''<br /> |<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, with LVM<br /> |{{Yes}}, LVM, ZFS, or loop devices<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''API\SDK'''<br /> |<br /> |OpenVZ API for Ruby, LibVirt<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |LibLXC, API for Ruby, Python 2, Haskell, Go<br /> |Proxmox VE uses a REST like API (JSON data format)<br /> |Windows SDK<br /> |RHEV-M API: REST API, SDKs<br /> |XenAPI, XenServer SDKs<br /> |-<br /> |'''Image Catalog integration'''<br /> |Integration with 3rd-party image catalog services of popular server applications and development environments that can be installed with one click.<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}} Application Image Catalog [https://virtuozzo.com/introducing-the-virtuozzo-application-catalog/ Virtuozzo Application Catalog]<br /> |{{No}}<br /> |{{Yes}} (Turnkey)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Kernel update without reboot'''<br /> |Integrated ability to upgrade kernel or install security patches without downtime.<br /> |{{No}}, only 3d party tools<br /> |{{Yes}}, Rebootless Kernel Update<br /> |{{No}}<br /> |{{Yes}} [https://readykernel.com/ ReadyKernel Service]<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |N/A<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |-<br /> |'''Power Panel'''<br /> |A tool used for managing particular virtual machines and containers by their end users.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Secure for using in public networks'''<br /> |<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|6. Commercial<br /> |-<br /> |'''Open Source'''<br /> |<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}} (but there is Open Source edition(oVirt))<br /> |{{No}} (but there is Open Source edition)<br /> |-<br /> |'''License\Subscription'''<br /> |<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, Enterprise Edition<br /> |-<br /> |'''Support'''<br /> |<br /> |Both community and commercial support<br /> |Commercial support<br /> |Community support<br /> |Commercial Support<br /> |Yes, Canonical Ltd.<br /> |Both community and commercial support<br /> |Commercial support<br /> |Commercial support<br /> |Both community and commercial support<br /> |-<br /> |'''EOL policy'''<br /> |<br /> |[[Releases|5 years of support]]<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |TBD<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |<br /> |<br /> |[https://support.microsoft.com/en-us/lifecycle/search/default.aspx?alpha=hyper-v 11 years of support]]<br /> |<br /> |<br /> |-<br /> |}</div>

Vporokhov https://wiki.openvz.org/index.php?title=Comparison&diff=22462 2016-12-01T11:37:15Z

<p>Vporokhov: </p> <hr /> <div>{{Note|This comparison doesn't include Docker, because Docker is not a virtualization solution. It automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of operating-system-level virtualization.&lt;ref&gt;[https://en.wikipedia.org/wiki/Docker_(software) Wikipedia article about Docker]&lt;/ref&gt;}}<br /> <br /> <br /> == Disclaimer ==<br /> <br /> The information regarding Virtuozzo 7 is provided by [http://www.virtuozzo.com Virtuozzo]. Here is the Virtuozzo's statement regarding this information:<br /> <br /> :#The information contained herein is intended to outline general product direction and should not be relied upon in making purchasing decisions.<br /> :#The content is for informational purposes only and may not be incorporated into any contract.<br /> :#The information presented is not a commitment, promise, or legal obligation to deliver any material, code or functionality.<br /> :#Any references to the development, release, and timing of any features or functionality described for these products remains at Virtuozzo’s sole discretion.<br /> :#Product capabilities, timeframes and features are subject to change and should not be viewed as Virtuozzo commitments.<br /> <br /> The information regarding all other solutions are taken by authors from public sources only. This information can be changed by any OpenVZ Wiki user without any notice and author's review or approval.<br /> <br /> <br /> == Feature comparison of different virtualization solutions ==<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> ! Feature<br /> ! Description<br /> ! OpenVZ<br /> ! Virtuozzo&amp;nbsp;6 (PCS 6)<br /> ! OpenVZ&amp;nbsp;7<br /> ! [https://virtuozzo.com/products/virtuozzo-containers/ Virtuozzo&amp;nbsp;7]<br /> ! LXC<br /> ! Proxmox VE<br /> ! Microsoft Hyper-V 2012 R2<br /> ! RHEV 3.5<br /> ! Citrix XenServer 6.5<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|1. Virtualization platform<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.1. Overview<br /> |-<br /> |'''HW virtualization support (Hypervisor)'''<br /> |Full emulation of underneath hardware level: full isolation guest environment, no dependencies from host OS, overhead for hypervisor layer.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''OS-level virtualization (Containers)'''<br /> |Sharing the same instance of host OS: high density, high performance, high dependencies from host OS.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Hypervisor technology'''<br /> |Technology that enables to run Virtual Machines.<br /> |{{No}}<br /> |Parallels Desktop Monitor<br /> |KVM<br /> |KVM<br /> |None<br /> |KVM<br /> |Hyper-V<br /> |KVM<br /> |Xen<br /> |-<br /> |'''Windows guest OS additional support'''<br /> |WHQL-signed drivers, SVVP certification<br /> |None<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Containers technology'''<br /> |Technology that enables to run Containers.<br /> |Virtuozzo Containers<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Linux containers<br /> |LXC (moved from OpenVZ since 4.0)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.2. Memory<br /> |-<br /> |'''Memory Overcommit'''<br /> |Ability to present more memory to virtual machines than physically available <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, with new VCMMD memory management<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Page sharing'''<br /> |Memory (RAM) savings through sharing identical memory pages across virtual machines<br /> |{{Yes}}<br /> |{{Yes}}, only for CTs<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> |'''Online Memory Management for VM'''<br /> |Ability to change amount of RAM for CT and VM without reboot<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |N/A<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|2. Management<br /> |-<br /> !colspan=&quot;11&quot;|2.1. General<br /> |-<br /> |'''Unified management tool for CTs and VMs'''<br /> |Single tool for managing both containers and virtual machines (if applicable)<br /> |None<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''OpenStack integration'''<br /> |Integration with OpenStack components ([http://docs.openstack.org/developer/nova/support-matrix.html see details])<br /> |{{Yes}}, only Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Central Management tool'''<br /> |Is centralized multi-server management available for this edition?<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}, Parallels Virtual Automation (PVA)<br /> |{{No}}<br /> |{{Yes}}, [https://virtuozzo.com/support/pva/ Virtual Automator]<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}<br /> |{{Yes}}, System Center Virtual Machine Manager<br /> |{{Yes}}, RHEV Manager<br /> |{{Yes}}, XenCenter<br /> |-<br /> !colspan=&quot;11&quot;|2.2. Upgrade &amp; Backup<br /> |-<br /> |'''Update Management'''<br /> |Integrated patching mechanism for the virtual environments (Guest OS) / guest tools / templates<br /> |No integrated update, YUM (Linux)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, APT (Linux)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |Yes (WSUS, SCCM, Virtual Machine Servicing Tool 2012 for offline VM update)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |-<br /> |'''Kernel Updates without reboot'''<br /> |Ability to update Linux kernel or install security patches without reboot<br /> |{{Yes}}, only Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Live VE snapshot'''<br /> |Ability to take a snapshot of a virtual environment while the guest OS is running (e.g. for roll-back or backup purposes)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated Backup'''<br /> |Are backup plugins/tools provided to backup virtual environments (over and above the ability to perform classic backup using agents in the guests)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Backup Integration API'''<br /> |Integration with 3rd party backup applications for backup of the virtual environment.<br /> |{{No}} (only through snapshots)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}} (only through snapshots)<br /> |{{Yes}} (vzdump)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot;|2.3. Others<br /> |-<br /> |'''VEs Templates (VM, CT)'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |{{Yes}} (CT only)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}} <br /> |{{Yes}} (OpenVZ templates)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''P2V migration'''<br /> |Integrated or added P2V (or V2V) capability in order to convert physical systems to virtual environment.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}, 3rd party tools<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|3. VE Mobility and HA<br /> |-<br /> !colspan=&quot;11&quot;|3.1. VE Mobility<br /> |-<br /> |'''Live Migration'''<br /> |Ability to migrate virtual machines between hosts without perceived downtime<br /> |{{Yes}}, but with no zero downtime<br /> |{{Yes}}, Kernel-Level Migration<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''DRS/Host Maintenance Mode'''<br /> |Ability to put host into maintenance mode which will automatically live migrate all VEs onto other available hosts so that the host can be brought shut down safely<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Distributed Power Management'''<br /> |Distributed Power Management features Ability to automatically migrate VEs onto fewer hosts and power off unused capacity (hosts), wake systems back up when required <br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|3.2. HA / DR<br /> |-<br /> |'''Cluster size'''<br /> |Maximum number of hosts in the cluster/pool relationship and maximum number VEs per cluster/pool (if specified)<br /> |None<br /> |32 hosts/cluster validated (100 hosts/cluster maximum) - PStorage limitation<br /> |Not tested yet<br /> |Not tested yet<br /> |None<br /> |32 nodes<br /> |64 nodes<br /> |200 nodes<br /> |16 nodes<br /> |-<br /> |'''Integrated HA'''<br /> |Recover virtual environment in case of host failures through restart on alternative hosts (downtime = restart time)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Site Failover'''<br /> |Integrated ability to (ideally live) migrate virtual machine data (virtual disk files) to different storage e.g. for array upgrades/migration and I/O management<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |Manual<br /> |{{No}}<br /> |Integrated Disaster Recovery - manual<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|4. Network and Storage<br /> |-<br /> !colspan=&quot;11&quot;|4.1. Storage<br /> |-<br /> |'''Supported Storage'''<br /> |Supported types of Storage (DAS, NAS or SAN)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS, NAS (NFS, ZFS), SAN (iSCSI), Ceph <br /> |DAS, NAS (SMB), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |-<br /> |'''Virtual Disk Format'''<br /> |Supported format(s) of the virtual disks for the virtual machines<br /> |CT - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |Any<br /> |qcow2, vmdk, raw<br /> |vhdx, vhd, pass-though (raw)<br /> |Qcow2, raw disk<br /> |vhd, raw disk<br /> |-<br /> |'''Thin Disk Provisioning'''<br /> |Ability to over-commit overall disk space by dynamically growing the size of virtual disks based on actual usage rather than pre-allocating full size.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, depends on disk format (dm-thin)<br /> |{{Yes}} (depends on underlying storage driver)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Virtual SAN'''<br /> |Enhanced storage capability e.g. providing a virtual SAN through virtualized 'local' storage <br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS, sheepdog)<br /> |{{Yes}}, Storage Spaces<br /> |{{Yes}}, Red Hat Storage<br /> |{{No}}<br /> |-<br /> |'''Storage QoS'''<br /> |Ability to control Quality of Service for Storage I/O or Throughput for CT/VM<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}, VMs only<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|4.2. Network<br /> |-<br /> |'''Advanced Network Switch'''<br /> |Centralized virtual network configuration (rather than managing virtual switches on individual hosts), typically with enhanced networking capabilities<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}, Open vSwitch support<br /> |{{Yes}}<br /> |OpenStack Neutron Integration<br /> |Open vSwitch integration<br /> |-<br /> |'''Network QoS'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |{{Yes}}, with Open vSwitch <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|5. Others – most of features are relevant only for Virtuozzo editions<br /> |-<br /> |'''Memory deduplication for binary files'''<br /> |Memory and IOPS deduplication management that enables/disables caching for Container directories and files, verifies cache integrity, checks Containers for cache errors, and purges the cache if needed<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{No}}<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''Completely isolated disk subsystem for CTs'''<br /> |<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, with LVM<br /> |{{Yes}}, LVM, ZFS, or loop devices<br /> |N/A<br /> |N/A<br /> |N/A<br /> |-<br /> |'''API\SDK'''<br /> |<br /> |OpenVZ API for Ruby, LibVirt<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |LibLXC, API for Ruby, Python 2, Haskell, Go<br /> |Proxmox VE uses a REST like API (JSON data format)<br /> |Windows SDK<br /> |RHEV-M API: REST API, SDKs<br /> |XenAPI, XenServer SDKs<br /> |-<br /> |'''Image Catalog integration'''<br /> |Integration with 3rd-party image catalog services of popular server applications and development environments that can be installed with one click.<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}} Application Image Catalog [https://virtuozzo.com/introducing-the-virtuozzo-application-catalog/ Virtuozzo Application Catalog]<br /> |{{No}}<br /> |{{Yes}} (Turnkey)<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Kernel maintenance'''<br /> |Integrated ability to upgrade kernel with minimal downtime.<br /> |{{No}}, only 3d party tools<br /> |{{Yes}}, kernel rebootless update (vzreboot)<br /> |{{No}}<br /> |{{Yes}} [https://readykernel.com/ ReadyKernel Service]<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |N/A<br /> |{{No}}, only 3d party tools<br /> |{{No}}, only 3d party tools<br /> |-<br /> |'''Power Panel'''<br /> |A tool used for managing particular virtual machines and containers by their end users.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Secure for using in public networks'''<br /> |<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|6. Commercial<br /> |-<br /> |'''Open Source'''<br /> |<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}} (but there is Open Source edition(oVirt))<br /> |{{No}} (but there is Open Source edition)<br /> |-<br /> |'''License\Subscription'''<br /> |<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, Enterprise Edition<br /> |-<br /> |'''Support'''<br /> |<br /> |Both community and commercial support<br /> |Commercial support<br /> |Community support<br /> |Commercial Support<br /> |Yes, Canonical Ltd.<br /> |Both community and commercial support<br /> |Commercial support<br /> |Commercial support<br /> |Both community and commercial support<br /> |-<br /> |'''EOL policy'''<br /> |<br /> |[[Releases|5 years of support]]<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |TBD<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |<br /> |<br /> |[https://support.microsoft.com/en-us/lifecycle/search/default.aspx?alpha=hyper-v 11 years of support]]<br /> |<br /> |<br /> |-<br /> |}</div>

Vporokhov https://wiki.openvz.org/index.php?title=Comparison&diff=22461 2016-12-01T11:32:47Z

<p>Vporokhov: </p> <hr /> <div>{{Note|This comparison doesn't include Docker, because Docker is not a virtualization solution. It automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of operating-system-level virtualization.&lt;ref&gt;[https://en.wikipedia.org/wiki/Docker_(software) Wikipedia article about Docker]&lt;/ref&gt;}}<br /> <br /> <br /> == Disclaimer ==<br /> <br /> The information regarding Virtuozzo 7 is provided by [http://www.virtuozzo.com Virtuozzo]. Here is the Virtuozzo's statement regarding this information:<br /> <br /> :#The information contained herein is intended to outline general product direction and should not be relied upon in making purchasing decisions.<br /> :#The content is for informational purposes only and may not be incorporated into any contract.<br /> :#The information presented is not a commitment, promise, or legal obligation to deliver any material, code or functionality.<br /> :#Any references to the development, release, and timing of any features or functionality described for these products remains at Virtuozzo’s sole discretion.<br /> :#Product capabilities, timeframes and features are subject to change and should not be viewed as Virtuozzo commitments.<br /> <br /> The information regarding all other solutions are taken by authors from public sources only. This information can be changed by any OpenVZ Wiki user without any notice and author's review or approval.<br /> <br /> <br /> == Feature comparison of different virtualization solutions ==<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> ! Feature<br /> ! Description<br /> ! OpenVZ<br /> ! Virtuozzo&amp;nbsp;6 (PCS 6)<br /> ! OpenVZ&amp;nbsp;7<br /> ! [https://virtuozzo.com/products/virtuozzo-containers/ Virtuozzo&amp;nbsp;7]<br /> ! LXC<br /> ! Proxmox VE<br /> ! Microsoft Hyper-V 2012 R2<br /> ! RHEV 3.5<br /> ! Citrix XenServer 6.5<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|1. Virtualization platform<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.1. Overview<br /> |-<br /> |'''HW virtualization support (Hypervisor)'''<br /> |Full emulation of underneath hardware level: full isolation guest environment, no dependencies from host OS, overhead for hypervisor layer.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''OS-level virtualization (Containers)'''<br /> |Sharing the same instance of host OS: high density, high performance, high dependencies from host OS.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Hypervisor technology'''<br /> |Technology that enables to run Virtual Machines.<br /> |None<br /> |Parallels Desktop Monitor<br /> |KVM<br /> |KVM<br /> |None<br /> |KVM<br /> |Hyper-V<br /> |KVM<br /> |Xen<br /> |-<br /> |'''Windows guest OS additional support'''<br /> |WHQL-signed drivers, SVVP certification<br /> |None<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Containers technology'''<br /> |Technology that enables to run Containers.<br /> |Virtuozzo Containers<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Linux containers<br /> |LXC (moved from OpenVZ since 4.0)<br /> |None<br /> |None<br /> |None<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.2. Memory<br /> |-<br /> |'''Memory Overcommit'''<br /> |Ability to present more memory to virtual machines than physically available <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, with new VCMMD memory management<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Page sharing'''<br /> |Memory (RAM) savings through sharing identical memory pages across virtual machines<br /> |{{Yes}}<br /> |{{Yes}}, only for CTs<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> |'''Online Memory Management for VM'''<br /> |Ability to change amount of RAM for CT and VM without reboot<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |N/A<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|2. Management<br /> |-<br /> !colspan=&quot;11&quot;|2.1. General<br /> |-<br /> |'''Unified management tool for CTs and VMs'''<br /> |Single tool for managing both containers and virtual machines (if applicable)<br /> |None<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''OpenStack integration'''<br /> |Integration with OpenStack components ([http://docs.openstack.org/developer/nova/support-matrix.html see details])<br /> |{{Yes}}, only Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Central Management tool'''<br /> |Is centralized multi-server management available for this edition?<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}, Parallels Virtual Automation (PVA)<br /> |{{No}}<br /> |{{Yes}}, [https://virtuozzo.com/support/pva/ Virtual Automator]<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}<br /> |{{Yes}}, System Center Virtual Machine Manager<br /> |{{Yes}}, RHEV Manager<br /> |{{Yes}}, XenCenter<br /> |-<br /> !colspan=&quot;11&quot;|2.2. Upgrade &amp; Backup<br /> |-<br /> |'''Update Management'''<br /> |Integrated patching mechanism for the virtual environments (Guest OS) / guest tools / templates<br /> |No integrated update, YUM (Linux)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, APT (Linux)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |Yes (WSUS, SCCM, Virtual Machine Servicing Tool 2012 for offline VM update)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |-<br /> |'''Kernel Updates without reboot'''<br /> |Ability to update Linux kernel or install security patches without reboot<br /> |{{Yes}}, only Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Live VE snapshot'''<br /> |Ability to take a snapshot of a virtual environment while the guest OS is running (e.g. for roll-back or backup purposes)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |Offline, CRIU support is planned<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated Backup'''<br /> |Are backup plugins/tools provided to backup virtual environments (over and above the ability to perform classic backup using agents in the guests)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Backup Integration API'''<br /> |Integration with 3rd party backup applications for backup of the virtual environment.<br /> |{{No}} (only through snapshots)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}} (only through snapshots)<br /> |{{Yes}} (vzdump)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot;|2.3. Others<br /> |-<br /> |'''VEs Templates (VM, CT)'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |{{Yes}} (CT only)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}} <br /> |{{Yes}} (OpenVZ templates)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''P2V migration'''<br /> |Integrated or added P2V (or V2V) capability in order to convert physical systems to virtual environment.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}, 3rd party tools<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|3. VE Mobility and HA<br /> |-<br /> !colspan=&quot;11&quot;|3.1. VE Mobility<br /> |-<br /> |'''Live Migration'''<br /> |Ability to migrate virtual machines between hosts without perceived downtime<br /> |{{Yes}}, but with no zero downtime<br /> |{{Yes}}, Kernel-Level Migration<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}, CRIU for containers<br /> |Offline, CRIU support is planned<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''DRS/Host Maintenance Mode'''<br /> |Ability to put host into maintenance mode which will automatically live migrate all VEs onto other available hosts so that the host can be brought shut down safely<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Distributed Power Management'''<br /> |Distributed Power Management features Ability to automatically migrate VEs onto fewer hosts and power off unused capacity (hosts), wake systems back up when required <br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|3.2. HA / DR<br /> |-<br /> |'''Cluster size'''<br /> |Maximum number of hosts in the cluster/pool relationship and maximum number VEs per cluster/pool (if specified)<br /> |None<br /> |32 hosts/cluster validated (100 hosts/cluster maximum) - PStorage limitation<br /> |Not tested yet<br /> |Not tested yet<br /> |None<br /> |32 nodes<br /> |64 nodes<br /> |200 nodes<br /> |16 nodes<br /> |-<br /> |'''Integrated HA'''<br /> |Recover virtual environment in case of host failures through restart on alternative hosts (downtime = restart time)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Site Failover'''<br /> |Integrated ability to (ideally live) migrate virtual machine data (virtual disk files) to different storage e.g. for array upgrades/migration and I/O management<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |Manual<br /> |{{No}}<br /> |Integrated Disaster Recovery - manual<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|4. Network and Storage<br /> |-<br /> !colspan=&quot;11&quot;|4.1. Storage<br /> |-<br /> |'''Supported Storage'''<br /> |Supported types of Storage (DAS, NAS or SAN)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS, NAS (NFS, ZFS), SAN (iSCSI), Ceph <br /> |DAS, NAS (SMB), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |-<br /> |'''Virtual Disk Format'''<br /> |Supported format(s) of the virtual disks for the virtual machines<br /> |CT - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |Any<br /> |qcow2, vmdk, raw<br /> |vhdx, vhd, pass-though (raw)<br /> |Qcow2, raw disk<br /> |vhd, raw disk<br /> |-<br /> |'''Thin Disk Provisioning'''<br /> |Ability to over-commit overall disk space by dynamically growing the size of virtual disks based on actual usage rather than pre-allocating full size.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, depends on disk format (dm-thin)<br /> |{{Yes}} (depends on underlying storage driver)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Virtual SAN'''<br /> |Enhanced storage capability e.g. providing a virtual SAN through virtualized 'local' storage <br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS, sheepdog)<br /> |{{Yes}}, Storage Spaces<br /> |{{Yes}}, Red Hat Storage<br /> |{{No}}<br /> |-<br /> |'''Storage QoS'''<br /> |Ability to control Quality of Service for Storage I/O or Throughput for CT/VM<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}, VMs only<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|4.2. Network<br /> |-<br /> |'''Advanced Network Switch'''<br /> |Centralized virtual network configuration (rather than managing virtual switches on individual hosts), typically with enhanced networking capabilities<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}, Open vSwitch support<br /> |{{Yes}}<br /> |OpenStack Neutron Integration<br /> |Open vSwitch integration<br /> |-<br /> |'''Network QoS'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |{{Yes}}, with Open vSwitch <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|5. Others – most of features are relevant only for Virtuozzo editions<br /> |-<br /> |'''Memory deduplication for binary files'''<br /> |Memory and IOPS deduplication management that enables/disables caching for Container directories and files, verifies cache integrity, checks Containers for cache errors, and purges the cache if needed<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{No}}<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Completely isolated disk subsystem for CTs'''<br /> |<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, with LVM<br /> |{{Yes}}, LVM, ZFS, or loop devices<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''API\SDK'''<br /> |<br /> |OpenVZ API for Ruby, LibVirt<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |LibLXC, API for Ruby, Python 2, Haskell, Go<br /> |Proxmox VE uses a REST like API (JSON data format)<br /> |Windows SDK<br /> |RHEV-M API: REST API, SDKs<br /> |XenAPI, XenServer SDKs<br /> |-<br /> |'''Image Catalog integration'''<br /> |Integration with 3rd-party image catalog services of popular server applications and development environments that can be installed with one click.<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}} Application Image Catalog [https://virtuozzo.com/introducing-the-virtuozzo-application-catalog/ Virtuozzo Application Catalog]<br /> |{{No}}<br /> |{{Yes}} (Turnkey)<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Kernel maintenance'''<br /> |Ability to upgrade kernel with minimal downtime.<br /> |KernelCare service integration<br /> |kernel rebootless update (vzreboot)<br /> |{{No}}<br /> |{{Yes}} [https://readykernel.com/ ReadyKernel Service]<br /> |KernelCare service integration<br /> |KernelCare service integration<br /> |None<br /> |KernelCare service integration<br /> |KernelCare service integration<br /> |-<br /> |'''Power Panel'''<br /> |A tool used for managing particular virtual machines and containers by their end users.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Secure for using in public networks'''<br /> |<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|6. Commercial<br /> |-<br /> |'''Open Source'''<br /> |<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}} (but there is Open Source edition(oVirt))<br /> |{{No}} (but there is Open Source edition)<br /> |-<br /> |'''License\Subscription'''<br /> |<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, Enterprise Edition<br /> |-<br /> |'''Support'''<br /> |<br /> |Both community and commercial support<br /> |Commercial support<br /> |Community support<br /> |Commercial Support<br /> |Yes, Canonical Ltd.<br /> |Both community and commercial support<br /> |Commercial support<br /> |Commercial support<br /> |Both community and commercial support<br /> |-<br /> |'''EOL policy'''<br /> |<br /> |[[Releases|5 years of support]]<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |TBD<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |<br /> |<br /> |[https://support.microsoft.com/en-us/lifecycle/search/default.aspx?alpha=hyper-v 11 years of support]]<br /> |<br /> |<br /> |-<br /> |}</div>

Vporokhov https://wiki.openvz.org/index.php?title=Comparison&diff=22460 2016-12-01T11:30:42Z

<p>Vporokhov: </p> <hr /> <div>{{Note|This comparison doesn't include Docker, because Docker is not a virtualization solution. It automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of operating-system-level virtualization.&lt;ref&gt;[https://en.wikipedia.org/wiki/Docker_(software) Wikipedia article about Docker]&lt;/ref&gt;}}<br /> <br /> <br /> == Disclaimer ==<br /> <br /> The information regarding Virtuozzo 7 is provided by [http://www.virtuozzo.com Virtuozzo]. Here is the Virtuozzo's statement regarding this information:<br /> <br /> :#The information contained herein is intended to outline general product direction and should not be relied upon in making purchasing decisions.<br /> :#The content is for informational purposes only and may not be incorporated into any contract.<br /> :#The information presented is not a commitment, promise, or legal obligation to deliver any material, code or functionality.<br /> :#Any references to the development, release, and timing of any features or functionality described for these products remains at Virtuozzo’s sole discretion.<br /> :#Product capabilities, timeframes and features are subject to change and should not be viewed as Virtuozzo commitments.<br /> <br /> The information regarding all other solutions are taken by authors from public sources only. This information can be changed by any OpenVZ Wiki user without any notice and author's review or approval.<br /> <br /> <br /> == Feature comparison of different virtualization solutions ==<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> ! Feature<br /> ! Description<br /> ! OpenVZ<br /> ! Virtuozzo&amp;nbsp;6 (PCS 6)<br /> ! OpenVZ&amp;nbsp;7<br /> ! [https://virtuozzo.com/products/virtuozzo-containers/ Virtuozzo&amp;nbsp;7]<br /> ! LXC<br /> ! Proxmox VE<br /> ! Microsoft Hyper-V 2012 R2<br /> ! RHEV 3.5<br /> ! Citrix XenServer 6.5<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|1. Virtualization platform<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.1. Overview<br /> |-<br /> |'''HW virtualization support (Hypervisor)'''<br /> |Full emulation of underneath hardware level: full isolation guest environment, no dependencies from host OS, overhead for hypervisor layer.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''OS-level virtualization (Containers)'''<br /> |Sharing the same instance of host OS: high density, high performance, high dependencies from host OS.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Hypervisor technology'''<br /> |Technology that enables to run Virtual Machines.<br /> |None<br /> |Parallels Desktop Monitor<br /> |KVM<br /> |KVM<br /> |None<br /> |KVM<br /> |Hyper-V<br /> |KVM<br /> |Xen<br /> |-<br /> |'''Windows guest OS additional support'''<br /> |WHQL-signed drivers, SVVP certification<br /> |None<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Containers technology'''<br /> |Technology that enables to run Containers.<br /> |Virtuozzo Containers<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Linux containers<br /> |LXC (moved from OpenVZ since 4.0)<br /> |None<br /> |None<br /> |None<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.2. Memory<br /> |-<br /> |'''Memory Overcommit'''<br /> |Ability to present more memory to virtual machines than physically available <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, with new VCMMD memory management<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Page sharing'''<br /> |Memory (RAM) savings through sharing identical memory pages across virtual machines<br /> |{{Yes}}<br /> |{{Yes}}, only for CTs<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> |'''Online Memory Management for CT/VM'''<br /> |Ability to change amount of RAM for CT and VM without reboot<br /> |{{Yes}}<br /> |{{Yes}}, only for CTs<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|2. Management<br /> |-<br /> !colspan=&quot;11&quot;|2.1. General<br /> |-<br /> |'''Unified management tool for CTs and VMs'''<br /> |Single tool for managing both containers and virtual machines (if applicable)<br /> |None<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''OpenStack integration'''<br /> |Integration with OpenStack components ([http://docs.openstack.org/developer/nova/support-matrix.html see details])<br /> |{{Yes}}, only Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Central Management tool'''<br /> |Is centralized multi-server management available for this edition?<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}, Parallels Virtual Automation (PVA)<br /> |{{No}}<br /> |{{Yes}}, [https://virtuozzo.com/support/pva/ Virtual Automator]<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}<br /> |{{Yes}}, System Center Virtual Machine Manager<br /> |{{Yes}}, RHEV Manager<br /> |{{Yes}}, XenCenter<br /> |-<br /> !colspan=&quot;11&quot;|2.2. Upgrade &amp; Backup<br /> |-<br /> |'''Update Management'''<br /> |Integrated patching mechanism for the virtual environments (Guest OS) / guest tools / templates<br /> |No integrated update, YUM (Linux)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, APT (Linux)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |Yes (WSUS, SCCM, Virtual Machine Servicing Tool 2012 for offline VM update)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |-<br /> |'''Kernel Updates without reboot'''<br /> |Ability to update Linux kernel or install security patches without reboot<br /> |{{Yes}}, only Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Live VE snapshot'''<br /> |Ability to take a snapshot of a virtual environment while the guest OS is running (e.g. for roll-back or backup purposes)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |Offline, CRIU support is planned<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated Backup'''<br /> |Are backup plugins/tools provided to backup virtual environments (over and above the ability to perform classic backup using agents in the guests)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Backup Integration API'''<br /> |Integration with 3rd party backup applications for backup of the virtual environment.<br /> |{{No}} (only through snapshots)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}} (only through snapshots)<br /> |{{Yes}} (vzdump)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot;|2.3. Others<br /> |-<br /> |'''VEs Templates (VM, CT)'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |{{Yes}} (CT only)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}} <br /> |{{Yes}} (OpenVZ templates)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''P2V migration'''<br /> |Integrated or added P2V (or V2V) capability in order to convert physical systems to virtual environment.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}, 3rd party tools<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|3. VE Mobility and HA<br /> |-<br /> !colspan=&quot;11&quot;|3.1. VE Mobility<br /> |-<br /> |'''Live Migration'''<br /> |Ability to migrate virtual machines between hosts without perceived downtime<br /> |{{Yes}}, but with no zero downtime<br /> |{{Yes}}, Kernel-Level Migration<br /> |{{Yes}}, CRIU for containers<br /> |{{Yes}}, CRIU for containers<br /> |Offline, CRIU support is planned<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''DRS/Host Maintenance Mode'''<br /> |Ability to put host into maintenance mode which will automatically live migrate all VEs onto other available hosts so that the host can be brought shut down safely<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Distributed Power Management'''<br /> |Distributed Power Management features Ability to automatically migrate VEs onto fewer hosts and power off unused capacity (hosts), wake systems back up when required <br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|3.2. HA / DR<br /> |-<br /> |'''Cluster size'''<br /> |Maximum number of hosts in the cluster/pool relationship and maximum number VEs per cluster/pool (if specified)<br /> |None<br /> |32 hosts/cluster validated (100 hosts/cluster maximum) - PStorage limitation<br /> |Not tested yet<br /> |Not tested yet<br /> |None<br /> |32 nodes<br /> |64 nodes<br /> |200 nodes<br /> |16 nodes<br /> |-<br /> |'''Integrated HA'''<br /> |Recover virtual environment in case of host failures through restart on alternative hosts (downtime = restart time)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Site Failover'''<br /> |Integrated ability to (ideally live) migrate virtual machine data (virtual disk files) to different storage e.g. for array upgrades/migration and I/O management<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |Manual<br /> |{{No}}<br /> |Integrated Disaster Recovery - manual<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|4. Network and Storage<br /> |-<br /> !colspan=&quot;11&quot;|4.1. Storage<br /> |-<br /> |'''Supported Storage'''<br /> |Supported types of Storage (DAS, NAS or SAN)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS, NAS (NFS, ZFS), SAN (iSCSI), Ceph <br /> |DAS, NAS (SMB), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |-<br /> |'''Virtual Disk Format'''<br /> |Supported format(s) of the virtual disks for the virtual machines<br /> |CT - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |Any<br /> |qcow2, vmdk, raw<br /> |vhdx, vhd, pass-though (raw)<br /> |Qcow2, raw disk<br /> |vhd, raw disk<br /> |-<br /> |'''Thin Disk Provisioning'''<br /> |Ability to over-commit overall disk space by dynamically growing the size of virtual disks based on actual usage rather than pre-allocating full size.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, depends on disk format (dm-thin)<br /> |{{Yes}} (depends on underlying storage driver)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Virtual SAN'''<br /> |Enhanced storage capability e.g. providing a virtual SAN through virtualized 'local' storage <br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS, sheepdog)<br /> |{{Yes}}, Storage Spaces<br /> |{{Yes}}, Red Hat Storage<br /> |{{No}}<br /> |-<br /> |'''Storage QoS'''<br /> |Ability to control Quality of Service for Storage I/O or Throughput for CT/VM<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}, VMs only<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|4.2. Network<br /> |-<br /> |'''Advanced Network Switch'''<br /> |Centralized virtual network configuration (rather than managing virtual switches on individual hosts), typically with enhanced networking capabilities<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}, Open vSwitch support<br /> |{{Yes}}<br /> |OpenStack Neutron Integration<br /> |Open vSwitch integration<br /> |-<br /> |'''Network QoS'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |{{Yes}}, with Open vSwitch <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|5. Others – most of features are relevant only for Virtuozzo editions<br /> |-<br /> |'''Memory deduplication for binary files'''<br /> |Memory and IOPS deduplication management that enables/disables caching for Container directories and files, verifies cache integrity, checks Containers for cache errors, and purges the cache if needed<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{No}}<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Completely isolated disk subsystem for CTs'''<br /> |<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, with LVM<br /> |{{Yes}}, LVM, ZFS, or loop devices<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''API\SDK'''<br /> |<br /> |OpenVZ API for Ruby, LibVirt<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |LibLXC, API for Ruby, Python 2, Haskell, Go<br /> |Proxmox VE uses a REST like API (JSON data format)<br /> |Windows SDK<br /> |RHEV-M API: REST API, SDKs<br /> |XenAPI, XenServer SDKs<br /> |-<br /> |'''Image Catalog integration'''<br /> |Integration with 3rd-party image catalog services of popular server applications and development environments that can be installed with one click.<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}} Application Image Catalog [https://virtuozzo.com/introducing-the-virtuozzo-application-catalog/ Virtuozzo Application Catalog]<br /> |{{No}}<br /> |{{Yes}} (Turnkey)<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Kernel maintenance'''<br /> |Ability to upgrade kernel with minimal downtime.<br /> |KernelCare service integration<br /> |kernel rebootless update (vzreboot)<br /> |{{No}}<br /> |{{Yes}} [https://readykernel.com/ ReadyKernel Service]<br /> |KernelCare service integration<br /> |KernelCare service integration<br /> |None<br /> |KernelCare service integration<br /> |KernelCare service integration<br /> |-<br /> |'''Power Panel'''<br /> |A tool used for managing particular virtual machines and containers by their end users.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Secure for using in public networks'''<br /> |<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|6. Commercial<br /> |-<br /> |'''Open Source'''<br /> |<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}} (but there is Open Source edition(oVirt))<br /> |{{No}} (but there is Open Source edition)<br /> |-<br /> |'''License\Subscription'''<br /> |<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, Enterprise Edition<br /> |-<br /> |'''Support'''<br /> |<br /> |Both community and commercial support<br /> |Commercial support<br /> |Community support<br /> |Commercial Support<br /> |Yes, Canonical Ltd.<br /> |Both community and commercial support<br /> |Commercial support<br /> |Commercial support<br /> |Both community and commercial support<br /> |-<br /> |'''EOL policy'''<br /> |<br /> |[[Releases|5 years of support]]<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |TBD<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |<br /> |<br /> |[https://support.microsoft.com/en-us/lifecycle/search/default.aspx?alpha=hyper-v 11 years of support]]<br /> |<br /> |<br /> |-<br /> |}</div>

Vporokhov https://wiki.openvz.org/index.php?title=Comparison&diff=22459 2016-12-01T11:23:07Z

<p>Vporokhov: </p> <hr /> <div>{{Note|This comparison doesn't include Docker, because Docker is not a virtualization solution. It automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of operating-system-level virtualization.&lt;ref&gt;[https://en.wikipedia.org/wiki/Docker_(software) Wikipedia article about Docker]&lt;/ref&gt;}}<br /> <br /> <br /> == Disclaimer ==<br /> <br /> The information regarding Virtuozzo 7 is provided by [http://www.virtuozzo.com Virtuozzo]. Here is the Virtuozzo's statement regarding this information:<br /> <br /> :#The information contained herein is intended to outline general product direction and should not be relied upon in making purchasing decisions.<br /> :#The content is for informational purposes only and may not be incorporated into any contract.<br /> :#The information presented is not a commitment, promise, or legal obligation to deliver any material, code or functionality.<br /> :#Any references to the development, release, and timing of any features or functionality described for these products remains at Virtuozzo’s sole discretion.<br /> :#Product capabilities, timeframes and features are subject to change and should not be viewed as Virtuozzo commitments.<br /> <br /> The information regarding all other solutions are taken by authors from public sources only. This information can be changed by any OpenVZ Wiki user without any notice and author's review or approval.<br /> <br /> <br /> == Feature comparison of different virtualization solutions ==<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> ! Feature<br /> ! Description<br /> ! OpenVZ<br /> ! Virtuozzo&amp;nbsp;6 (PCS 6)<br /> ! OpenVZ&amp;nbsp;7<br /> ! [https://virtuozzo.com/products/virtuozzo-containers/ Virtuozzo&amp;nbsp;7]<br /> ! LXC<br /> ! Proxmox VE<br /> ! Microsoft Hyper-V 2012 R2<br /> ! RHEV 3.5<br /> ! Citrix XenServer 6.5<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|1. Virtualization platform<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.1. Overview<br /> |-<br /> |'''HW virtualization support (Hypervisor)'''<br /> |Full emulation of underneath hardware level: full isolation guest environment, no dependencies from host OS, overhead for hypervisor layer.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''OS-level virtualization (Containers)'''<br /> |Sharing the same instance of host OS: high density, high performance, high dependencies from host OS.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Hypervisor technology'''<br /> |Technology that enables to run Virtual Machines.<br /> |None<br /> |Parallels Desktop Monitor<br /> |KVM<br /> |KVM<br /> |None<br /> |KVM<br /> |Hyper-V<br /> |KVM<br /> |Xen<br /> |-<br /> |'''Windows guest OS additional support'''<br /> |WHQL-signed drivers, SVVP certification<br /> |None<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Containers technology'''<br /> |Technology that enables to run Containers.<br /> |Virtuozzo Containers<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Linux containers<br /> |LXC (moved from OpenVZ since 4.0)<br /> |None<br /> |None<br /> |None<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.2. Memory<br /> |-<br /> |'''Memory Overcommit'''<br /> |Ability to present more memory to virtual machines than physically available <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Page sharing'''<br /> |Memory (RAM) savings through sharing identical memory pages across virtual machines<br /> |{{Yes}}<br /> |{{Yes}}, only for CTs<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|2. Management<br /> |-<br /> !colspan=&quot;11&quot;|2.1. General<br /> |-<br /> |'''Unified management tool for CTs and VMs'''<br /> |Single tool for managing both containers and virtual machines (if applicable)<br /> |None<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |None<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''OpenStack integration'''<br /> |Integration with OpenStack components ([http://docs.openstack.org/developer/nova/support-matrix.html see details])<br /> |{{Yes}}, only Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Central Management tool'''<br /> |Is centralized multi-server management available for this edition?<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}, Parallels Virtual Automation (PVA)<br /> |{{No}}<br /> |{{Yes}}, [https://virtuozzo.com/support/pva/ Virtual Automator]<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}<br /> |{{Yes}}, System Center Virtual Machine Manager<br /> |{{Yes}}, RHEV Manager<br /> |{{Yes}}, XenCenter<br /> |-<br /> !colspan=&quot;11&quot;|2.2. Upgrade &amp; Backup<br /> |-<br /> |'''Update Management'''<br /> |Integrated patching mechanism for the virtual environments (Guest OS) / guest tools / templates<br /> |No integrated update, YUM (Linux)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, APT (Linux)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |Yes (WSUS, SCCM, Virtual Machine Servicing Tool 2012 for offline VM update)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |-<br /> |'''Live VE snapshot'''<br /> |Ability to take a snapshot of a virtual environment while the guest OS is running (e.g. for roll-back or backup purposes)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |Offline, CRIU support is planned<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated Backup'''<br /> |Are backup plugins/tools provided to backup virtual environments (over and above the ability to perform classic backup using agents in the guests)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Backup Integration API'''<br /> |Integration with 3rd party backup applications for backup of the virtual environment.<br /> |{{No}} (only through snapshots)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}} (only through snapshots)<br /> |{{Yes}} (vzdump)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot;|2.3. Others<br /> |-<br /> |'''VEs Templates (VM, CT)'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |{{Yes}} (CT only)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}} (OpenVZ templates)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''P2V migration'''<br /> |Integrated or added P2V (or V2V) capability in order to convert physical systems to virtual environment.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}, 3rd party tools<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|3. VE Mobility and HA<br /> |-<br /> !colspan=&quot;11&quot;|3.1. VE Mobility<br /> |-<br /> |'''Live Migration'''<br /> |Ability to migrate virtual machines between hosts without perceived downtime<br /> |{{Yes}}, but with no zero downtime<br /> |{{Yes}}, Kernel-Level Migration<br /> |{{Yes}}, CRIU<br /> |{{Yes}}, CRIU<br /> |Offline, CRIU support is planned<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''DRS/Host Maintenance Mode'''<br /> |Ability to put host into maintenance mode which will automatically live migrate all VEs onto other available hosts so that the host can be brought shut down safely<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Distributed Power Management'''<br /> |Distributed Power Management features Ability to automatically migrate VEs onto fewer hosts and power off unused capacity (hosts), wake systems back up when required <br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|3.2. HA / DR<br /> |-<br /> |'''Cluster size'''<br /> |Maximum number of hosts in the cluster/pool relationship and maximum number VEs per cluster/pool (if specified)<br /> |None<br /> |32 hosts/cluster validated (100 hosts/cluster maximum) - PStorage limitation<br /> |Not tested yet<br /> |Not tested yet<br /> |None<br /> |32 nodes<br /> |64 nodes<br /> |200 nodes<br /> |16 nodes<br /> |-<br /> |'''Integrated HA'''<br /> |Recover virtual environment in case of host failures through restart on alternative hosts (downtime = restart time)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Site Failover'''<br /> |Integrated ability to (ideally live) migrate virtual machine data (virtual disk files) to different storage e.g. for array upgrades/migration and I/O management<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |Manual<br /> |{{No}}<br /> |Integrated Disaster Recovery - manual<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|4. Network and Storage<br /> |-<br /> !colspan=&quot;11&quot;|4.1. Storage<br /> |-<br /> |'''Supported Storage'''<br /> |Supported types of Storage (DAS, NAS or SAN)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS, NAS (NFS, ZFS), SAN (iSCSI), Ceph <br /> |DAS, NAS (SMB), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |-<br /> |'''Virtual Disk Format'''<br /> |Supported format(s) of the virtual disks for the virtual machines<br /> |CT - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |Any<br /> |qcow2, vmdk, raw<br /> |vhdx, vhd, pass-though (raw)<br /> |Qcow2, raw disk<br /> |vhd, raw disk<br /> |-<br /> |'''Thin Disk Provisioning'''<br /> |Ability to over-commit overall disk space by dynamically growing the size of virtual disks based on actual usage rather than pre-allocating full size.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, depends on disk format (dm-thin)<br /> |{{Yes}} (depends on underlying storage driver)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Virtual SAN'''<br /> |Enhanced storage capability e.g. providing a virtual SAN through virtualized 'local' storage <br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS, sheepdog)<br /> |{{Yes}}, Storage Spaces<br /> |{{Yes}}, Red Hat Storage<br /> |{{No}}<br /> |-<br /> |'''Storage QoS'''<br /> |Ability to control Quality of Service for Storage I/O or Throughput for CT/VM<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}, VMs only<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|4.2. Network<br /> |-<br /> |'''Advanced Network Switch'''<br /> |Centralized virtual network configuration (rather than managing virtual switches on individual hosts), typically with enhanced networking capabilities<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}, Open vSwitch support<br /> |{{Yes}}<br /> |OpenStack Neutron Integration<br /> |Open vSwitch integration<br /> |-<br /> |'''Network QoS'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |{{Yes}}, with Open vSwitch <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|5. Others – most of features are relevant only for Virtuozzo editions<br /> |-<br /> |'''Memory deduplication for binary files'''<br /> |Memory and IOPS deduplication management that enables/disables caching for Container directories and files, verifies cache integrity, checks Containers for cache errors, and purges the cache if needed<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{No}}<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Completely isolated disk subsystem for CTs'''<br /> |<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, with LVM<br /> |{{Yes}}, LVM, ZFS, or loop devices<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''API\SDK'''<br /> |<br /> |OpenVZ API for Ruby, LibVirt<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |LibLXC, API for Ruby, Python 2, Haskell, Go<br /> |Proxmox VE uses a REST like API (JSON data format)<br /> |Windows SDK<br /> |RHEV-M API: REST API, SDKs<br /> |XenAPI, XenServer SDKs<br /> |-<br /> |'''Image Catalog integration'''<br /> |Integration with 3rd-party image catalog services of popular server applications and development environments that can be installed with one click.<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}} [https://virtuozzo.com/introducing-the-virtuozzo-application-catalog/ Virtuozzo Application Catalog]<br /> |{{No}}<br /> |{{Yes}} (Turnkey)<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Kernel maintenance'''<br /> |Ability to upgrade kernel with minimal downtime.<br /> |KernelCare service integration<br /> |kernel rebootless update (vzreboot)<br /> |{{No}}<br /> |{{Yes}} [https://readykernel.com/ ReadyKernel Service]<br /> |KernelCare service integration<br /> |KernelCare service integration<br /> |None<br /> |KernelCare service integration<br /> |KernelCare service integration<br /> |-<br /> |'''Power Panel'''<br /> |A tool used for managing particular virtual machines and containers by their end users.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Secure for using in public networks'''<br /> |<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|6. Commercial<br /> |-<br /> |'''Open Source'''<br /> |<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}} (but there is Open Source edition(oVirt))<br /> |{{No}} (but there is Open Source edition)<br /> |-<br /> |'''License\Subscription'''<br /> |<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, Enterprise Edition<br /> |-<br /> |'''Support'''<br /> |<br /> |Both community and commercial support<br /> |Commercial support<br /> |Community support<br /> |Commercial Support<br /> |Yes, Canonical Ltd.<br /> |Both community and commercial support<br /> |Commercial support<br /> |Commercial support<br /> |Both community and commercial support<br /> |-<br /> |'''EOL policy'''<br /> |<br /> |[[Releases|5 years of support]]<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |TBD<br /> |[https://virtuozzo.com/support/server-lifecycle/ 7 years of support]<br /> |<br /> |<br /> |[https://support.microsoft.com/en-us/lifecycle/search/default.aspx?alpha=hyper-v 11 years of support]]<br /> |<br /> |<br /> |-<br /> |}</div>

Vporokhov https://wiki.openvz.org/index.php?title=Comparison&diff=19800 2016-07-26T10:35:55Z

<p>Vporokhov: </p> <hr /> <div>{{Note|This comparison doesn't include Docker, because Docker is not a virtualization solution. It automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of operating-system-level virtualization.&lt;ref&gt;[https://en.wikipedia.org/wiki/Docker_(software) Wikipedia article about Docker]&lt;/ref&gt;}}<br /> <br /> <br /> == Disclaimer ==<br /> <br /> The information regarding [[Virtuozzo]] 7 are provided by [http://www.virtuozzo.com Virtuozzo]. Here is the Virtuozzo's statement regarding this information:<br /> <br /> :#The information contained herein is intended to outline general product direction and should not be relied upon in making purchasing decisions.<br /> :#The content is for informational purposes only and may not be incorporated into any contract.<br /> :#The information presented is not a commitment, promise, or legal obligation to deliver any material, code or functionality.<br /> :#Any references to the development, release, and timing of any features or functionality described for these products remains at Virtuozzo’s sole discretion.<br /> :#Product capabilities, timeframes and features are subject to change and should not be viewed as Virtuozzo commitments.<br /> <br /> The information regarding all other solutions are taken by authors from public sources only. This information can be changed by any OpenVZ Wiki user without any notice and author's review or approval.<br /> <br /> <br /> == Feature comparison of different virtualization solutions ==<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> ! Feature<br /> ! Description<br /> ! OpenVZ (stable)<br /> ! Virtuozzo&amp;nbsp;6 (PCS 6)<br /> ! Virtuozzo&amp;nbsp;7<br /> ! Virtuozzo&amp;nbsp;7 Plus<br /> ! LXC<br /> ! Proxmox VE<br /> ! Microsoft Hyper-V 2012 R2<br /> ! RHEV 3.5<br /> ! Citrix XenServer 6.5<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|1. Virtualization platform<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.1. Overview<br /> |-<br /> |'''HW virtualization support (Hypervisor)'''<br /> |Full emulation of underneath hardware level: full isolation guest environment, no dependencies from host OS, overhead for hypervisor layer.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''OS-level virtualization (Containers)'''<br /> |Sharing the same instance of host OS: high density, high performance, high dependencies from host OS.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Hypervisor technology'''<br /> |Technology that enables to run Virtual Machines.<br /> |None<br /> |Parallels Desktop Monitor<br /> |KVM<br /> |KVM<br /> |None<br /> |KVM<br /> |Hyper-V<br /> |KVM<br /> |Xen<br /> |-<br /> |'''Windows guest OS additional support'''<br /> |WHQL-signed drivers, SVVP certification<br /> |None<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Containers technology'''<br /> |Technology that enables to run Containers.<br /> |Virtuozzo Containers<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Linux containers<br /> |LXC (moved from OpenVZ since 4.0)<br /> |None<br /> |None<br /> |None<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.2. Memory<br /> |-<br /> |'''Memory Overcommit'''<br /> |Ability to present more memory to virtual machines than physically available <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Page sharing'''<br /> |Memory (RAM) savings through sharing identical memory pages across virtual machines<br /> |{{Yes}}<br /> |{{Yes}}, only for CTs<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|2. Management<br /> |-<br /> !colspan=&quot;11&quot;|2.1. General<br /> |-<br /> |'''Unified management tool for CTs and VMs'''<br /> |Single tool for managing both containers and virtual machines (if applicable)<br /> |None<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |None<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''OpenStack integration'''<br /> |Integration with OpenStack components ([http://docs.openstack.org/developer/nova/support-matrix.html see details])<br /> |{{Yes}}, only Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Central Management tool'''<br /> |Is centralized multi-server management available for this edition?<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}, Parallels Virtual Automation (PVA)<br /> |{{No}}<br /> |{{Yes}}, PVA<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}<br /> |{{Yes}}, System Center Virtual Machine Manager<br /> |{{Yes}}, RHEV Manager<br /> |{{Yes}}, XenCenter<br /> |-<br /> !colspan=&quot;11&quot;|2.2. Upgrade &amp; Backup<br /> |-<br /> |'''Update Management'''<br /> |Integrated patching mechanism for the virtual environments (Guest OS) / guest tools / templates<br /> |No integrated update, YUM (Linux)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, APT (Linux)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |Yes (WSUS, SCCM, Virtual Machine Servicing Tool 2012 for offline VM update)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |-<br /> |'''Live VE snapshot'''<br /> |Ability to take a snapshot of a virtual environment while the guest OS is running (e.g. for roll-back or backup purposes)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |Offline, CRIU support is planned<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated Backup'''<br /> |Are backup plugins/tools provided to backup virtual environments (over and above the ability to perform classic backup using agents in the guests)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Backup Integration API'''<br /> |Integration with 3rd party backup applications for backup of the virtual environment.<br /> |{{No}} (only through snapshots)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}} (only through snapshots)<br /> |{{Yes}} (vzdump)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot;|2.3. Others<br /> |-<br /> |'''VEs Templates (VM, CT)'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |{{Yes}} (CT only)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}} (OpenVZ templates)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''P2V migration'''<br /> |Integrated or added P2V (or V2V) capability in order to convert physical systems to virtual environment.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}, 3rd party tools<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|3. VE Mobility and HA<br /> |-<br /> !colspan=&quot;11&quot;|3.1. VE Mobility<br /> |-<br /> |'''Live Migration'''<br /> |Ability to migrate virtual machines between hosts without perceived downtime<br /> |{{Yes}}, but with no zero downtime<br /> |{{Yes}}, Kernal-Level Migration<br /> |{{Yes}}, CRIU<br /> |{{Yes}}, CRIU<br /> |Offline, CRIU support is planned<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''DRS/Host Maintenance Mode'''<br /> |Ability to put host into maintenance mode which will automatically live migrate all VEs onto other available hosts so that the host can be brought shut down safely<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Distributed Power Management'''<br /> |Distributed Power Management features Ability to automatically migrate VEs onto fewer hosts and power off unused capacity (hosts), wake systems back up when required <br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|3.2. HA / DR<br /> |-<br /> |'''Cluster size'''<br /> |Maximum number of hosts in the cluster/pool relationship and maximum number VEs per cluster/pool (if specified)<br /> |None<br /> |32 hosts/cluster validated (100 hosts/cluster maximum) - PStorage limitation<br /> |Not tested yet<br /> |Not tested yet<br /> |None<br /> |32 nodes<br /> |64 nodes<br /> |200 nodes<br /> |16 nodes<br /> |-<br /> |'''Integrated HA'''<br /> |Recover virtual environment in case of host failures through restart on alternative hosts (downtime = restart time)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Site Failover'''<br /> |Integrated ability to (ideally live) migrate virtual machine data (virtual disk files) to different storage e.g. for array upgrades/migration and I/O management<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |Manual<br /> |{{No}}<br /> |Integrated Disaster Recovery - manual<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|4. Network and Storage<br /> |-<br /> !colspan=&quot;11&quot;|4.1. Storage<br /> |-<br /> |'''Supported Storage'''<br /> |Supported types of Storage (DAS, NAS or SAN)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS, NAS (NFS, ZFS), SAN (iSCSI), Ceph <br /> |DAS, NAS (SMB), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |-<br /> |'''Virtual Disk Format'''<br /> |Supported format(s) of the virtual disks for the virtual machines<br /> |CT - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |CT - [[ploop]], VM - [[ploop]]\Qcow2<br /> |Any<br /> |qcow2, vmdk, raw<br /> |vhdx, vhd, pass-though (raw)<br /> |Qcow2, raw disk<br /> |vhd, raw disk<br /> |-<br /> |'''Thin Disk Provisioning'''<br /> |Ability to over-commit overall disk space by dynamically growing the size of virtual disks based on actual usage rather than pre-allocating full size.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, depends on disk format (dm-thin)<br /> |{{Yes}} (depends on underlying storage driver)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Virtual SAN'''<br /> |Enhanced storage capability e.g. providing a virtual SAN through virtualized 'local' storage <br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS, sheepdog)<br /> |{{Yes}}, Storage Spaces<br /> |{{Yes}}, Red Hat Storage<br /> |{{No}}<br /> |-<br /> |'''Storage QoS'''<br /> |Ability to control Quality of Service for Storage I/O or Throughput for CT/VM<br /> |{{Yes}}<br /> |{{Yes}}<br /> |TBD<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}, VMs only<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|4.2. Network<br /> |-<br /> |'''Advanced Network Switch'''<br /> |Centralized virtual network configuration (rather than managing virtual switches on individual hosts), typically with enhanced networking capabilities<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}, Open vSwitch support<br /> |{{Yes}}<br /> |OpenStack Neutron Integration<br /> |Open vSwitch integration<br /> |-<br /> |'''Network QoS'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |{{Yes}}, with Open vSwitch <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|5. Others – most of features are relevant only for Virtuozzo editions<br /> |-<br /> |'''Memory deduplication for binary files'''<br /> |Memory and IOPS deduplication management that enables/disables caching for Container directories and files, verifies cache integrity, checks Containers for cache errors, and purges the cache if needed<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{No}}<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Completely isolated disk subsystem for CTs'''<br /> |<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, with LVM<br /> |{{Yes}}, LVM, ZFS, or loop devices<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''API\SDK'''<br /> |<br /> |OpenVZ API for Ruby, LibVirt<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |LibLXC, API for Ruby, Python 2, Haskell, Go<br /> |Proxmox VE uses a REST like API (JSON data format)<br /> |Windows SDK<br /> |RHEV-M API: REST API, SDKs<br /> |XenAPI, XenServer SDKs<br /> |-<br /> |'''Image Catalog integration'''<br /> |Integration with 3rd-party image catalog services of popular server applications and development environments that can be installed with one click.<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}} (Bitnami)&lt;ref&gt;[http://www.odin.com/fileadmin/media/hcap/virtuozzo/documents/Virtuozzo-app-catalog-Whitepaper_Ltr_20151015.pdf Image Management Using the Virtuozzo Application Catalog]&lt;/ref&gt;<br /> |{{No}}<br /> |{{Yes}} (Turnkey)<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Kernel maintenance'''<br /> |Ability to upgrade kernel with minimal downtime.<br /> |KernelCare service integration<br /> |kernel rebootless update (vzreboot)<br /> |KernelCare service integration<br /> |kernel rebootless update (vzreboot)<br /> |KernelCare service integration<br /> |KernelCare service integration<br /> |None<br /> |KernelCare service integration<br /> |KernelCare service integration<br /> |-<br /> |'''Power Panel'''<br /> |A tool used for managing particular virtual machines and containers by their end users.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Secure for using in public networks'''<br /> |<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{No}}&lt;ref name=&quot;LXC security&quot;&gt;[https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.txt LXC Security Analysis]&lt;/ref&gt;, &lt;ref name=&quot;Security issues and mitigations with lxc&quot;&gt;[https://wiki.ubuntu.com/LxcSecurity Security issues and mitigations with LXC]&lt;/ref&gt;<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|6. Commercial<br /> |-<br /> |'''Open Source'''<br /> |<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}} (but there is Open Source edition(oVirt))<br /> |{{No}} (but there is Open Source edition)<br /> |-<br /> |'''License\Subscription'''<br /> |<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, Enterprise Edition<br /> |-<br /> |'''Support'''<br /> |<br /> |Both community and commercial support<br /> |Commercial support<br /> |Community support<br /> |Commercial Support<br /> |Yes, Canonical Ltd.<br /> |Both community and commercial support<br /> |Commercial support<br /> |Commercial support<br /> |Both community and commercial support<br /> |-<br /> |'''EOL policy'''<br /> |<br /> |[[Releases|5 years of support]]<br /> |[http://www.odin.com/support/policies/server-lifecycle/ 7 years of support]<br /> |TBD<br /> |5 years of support<br /> |<br /> |<br /> |[https://support.microsoft.com/en-us/lifecycle/search/default.aspx?alpha=hyper-v 11 years of support]]<br /> |<br /> |<br /> |-<br /> |}</div>

Vporokhov https://wiki.openvz.org/index.php?title=Docker_inside_CT_vz7&diff=19788 2016-07-25T08:49:32Z

<p>Vporokhov: </p> <hr /> <div>Since Virtuozzo 7 kernel 3.10.0-327.18.2.vz7.14.7 it is possible to run Docker inside containers.<br /> <br /> '''Please be aware that this feature is experimental and is not supported in production! We plan to make it production in the upcoming updates.'''<br /> <br /> '''This page is applicable for Virtuozzo 7''' (for Virtuozzo 6 see [[Docker inside CT | '''here''']]).<br /> <br /> == Prerequisites ==<br /> <br /> * Kernel 3.10.0-327.18.2.vz7.14.7 or later version<br /> * Kernel modules '''veth''' and '''overlay''' loaded on host<br /> <br /> To enable '''veth''' and '''overlay''' modules please run:<br /> modprobe veth<br /> modprobe overlay <br /> <br /> '''Note:''' if you use kernel &gt;= 3.10.0-327.18.2.vz7.14.25, you need to allow using &quot;overlayfs&quot; inside a Virtuozzo Container:<br /> echo 1 &gt; /proc/sys/fs/experimental_fs_enable<br /> This is a temporary step, it will be dropped once overlayfs is proved to be absolutely safe to run in any vz7 Container.<br /> <br /> == Limitations ==<br /> <br /> * Only '''overlay''' and '''vfs''' Docker graph drivers are currently supported. Recommended driver is '''overlay'''. To enable '''overlayfs''' Storage Driver for docker engine inside CT please read here https://docs.docker.com/engine/userguide/storagedriver/selectadriver/<br /> * [[Checkpointing and live migration]] of a container with Docker containers inside is not supported yet (to be done)<br /> <br /> == Container tuning ==<br /> <br /> * Turn on '''bridge''' feature to allow docker creating bridged network inside container:<br /> prlctl set $veid --features bridge:on<br /> * Setup Container veth-based network (Container must be '''veth'''-based, not '''venet'''-based):<br /> prlctl set $veid --device-add net --network Bridged --dhcp yes<br /> * Allow all iptables modules to be used in containers:<br /> prlctl set $veid --netfilter=full<br /> <br /> == Docker install ==<br /> <br /> To install docker inside container please use Docker Installation Guide for your OS<br /> https://docs.docker.com/v1.11/engine/installation/<br /> <br /> [[Category:HOWTO]]<br /> [[Category: TRD]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Docker_inside_CT_vz7&diff=19787 2016-07-25T08:22:35Z

<p>Vporokhov: </p> <hr /> <div>Since Virtuozzo 7 kernel 3.10.0-327.18.2.vz7.14.7 it is possible to run Docker inside containers.<br /> <br /> '''Please be aware that this feature is experimental and is not supported in production!'''<br /> <br /> '''This page is applicable for Virtuozzo 7''' (for Virtuozzo 6 see [[Docker inside CT | '''here''']]).<br /> <br /> == Prerequisites ==<br /> <br /> * Kernel 3.10.0-327.18.2.vz7.14.7 or later version<br /> * Kernel modules '''veth''' and '''overlay''' loaded on host<br /> <br /> To enable '''veth''' and '''overlay''' modules please run:<br /> modprobe veth<br /> modprobe overlay <br /> <br /> '''Note:''' if you use kernel &gt;= 3.10.0-327.18.2.vz7.14.25, you need to allow using &quot;overlayfs&quot; inside a Virtuozzo Container:<br /> echo 1 &gt; /proc/sys/fs/experimental_fs_enable<br /> This is a temporary step, it will be dropped once overlayfs is proved to be absolutely safe to run in any vz7 Container.<br /> <br /> == Limitations ==<br /> <br /> * Only '''overlay''' and '''vfs''' Docker graph drivers are currently supported. Recommended driver is '''overlay'''. To enable '''overlayfs''' Storage Driver for docker engine inside CT please read here https://docs.docker.com/engine/userguide/storagedriver/selectadriver/<br /> * [[Checkpointing and live migration]] of a container with Docker containers inside is not supported yet (to be done)<br /> <br /> == Container tuning ==<br /> <br /> * Turn on '''bridge''' feature to allow docker creating bridged network inside container:<br /> prlctl set $veid --features bridge:on<br /> * Setup Container veth-based network (Container must be '''veth'''-based, not '''venet'''-based):<br /> prlctl set $veid --device-add net --network Bridged --dhcp yes<br /> * Allow all iptables modules to be used in containers:<br /> prlctl set $veid --netfilter=full<br /> <br /> == Docker install ==<br /> <br /> To install docker inside container please use Docker Installation Guide for your OS<br /> https://docs.docker.com/v1.11/engine/installation/<br /> <br /> [[Category:HOWTO]]<br /> [[Category: TRD]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Docker_inside_CT_vz7&diff=19786 2016-07-25T08:22:01Z

<p>Vporokhov: </p> <hr /> <div>Since Virtuozzo 7 kernel 3.10.0-327.18.2.vz7.14.7 it is possible to run Docker inside containers.<br /> <br /> '''Please be aware that this feature is experimental and is not supported in production!'''<br /> <br /> '''This page is applicable for Virtuozzo 7''' (for OpenVZ 6 see [[Docker inside CT | '''here''']]).<br /> <br /> == Prerequisites ==<br /> <br /> * Kernel 3.10.0-327.18.2.vz7.14.7 or later version<br /> * Kernel modules '''veth''' and '''overlay''' loaded on host<br /> <br /> To enable '''veth''' and '''overlay''' modules please run:<br /> modprobe veth<br /> modprobe overlay <br /> <br /> '''Note:''' if you use kernel &gt;= 3.10.0-327.18.2.vz7.14.25, you need to allow using &quot;overlayfs&quot; inside a Virtuozzo Container:<br /> echo 1 &gt; /proc/sys/fs/experimental_fs_enable<br /> This is a temporary step, it will be dropped once overlayfs is proved to be absolutely safe to run in any vz7 Container.<br /> <br /> == Limitations ==<br /> <br /> * Only '''overlay''' and '''vfs''' Docker graph drivers are currently supported. Recommended driver is '''overlay'''. To enable '''overlayfs''' Storage Driver for docker engine inside CT please read here https://docs.docker.com/engine/userguide/storagedriver/selectadriver/<br /> * [[Checkpointing and live migration]] of a container with Docker containers inside is not supported yet (to be done)<br /> <br /> == Container tuning ==<br /> <br /> * Turn on '''bridge''' feature to allow docker creating bridged network inside container:<br /> prlctl set $veid --features bridge:on<br /> * Setup Container veth-based network (Container must be '''veth'''-based, not '''venet'''-based):<br /> prlctl set $veid --device-add net --network Bridged --dhcp yes<br /> * Allow all iptables modules to be used in containers:<br /> prlctl set $veid --netfilter=full<br /> <br /> == Docker install ==<br /> <br /> To install docker inside container please use Docker Installation Guide for your OS<br /> https://docs.docker.com/v1.11/engine/installation/<br /> <br /> [[Category:HOWTO]]<br /> [[Category: TRD]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Docker_inside_CT_vz7&diff=19785 2016-07-22T12:00:42Z

<p>Vporokhov: </p> <hr /> <div>Since Virtuozzo 7 kernel 3.10.0-327.18.2.vz7.14.7 it is possible to run Docker inside containers. This article describes how.<br /> &lt;br&gt;'''This page is applicable for Virtuozzo 7''' (for OpenVZ 6 see [[Docker inside CT | '''here''']]).<br /> <br /> == Prerequisites ==<br /> <br /> * Kernel 3.10.0-327.18.2.vz7.14.7 or later version<br /> * Kernel modules '''veth''' and '''overlay''' loaded on host<br /> <br /> To enable '''veth''' and '''overlay''' modules please run:<br /> modprobe veth<br /> modprobe overlay <br /> <br /> '''Note:''' if you use kernel &gt;= 3.10.0-327.18.2.vz7.14.25, you need to allow using &quot;overlayfs&quot; inside a Virtuozzo Container:<br /> echo 1 &gt; /proc/sys/fs/experimental_fs_enable<br /> This is a temporary step, it will be dropped once overlayfs is proved to be absolutely safe to run in any vz7 Container.<br /> <br /> == Limitations ==<br /> <br /> * Only '''overlay''' and '''vfs''' Docker graph drivers are currently supported. Recommended driver is '''overlay'''. To enable '''overlayfs''' Storage Driver for docker engine inside CT please read here https://docs.docker.com/engine/userguide/storagedriver/selectadriver/<br /> * [[Checkpointing and live migration]] of a container with Docker containers inside is not supported yet (to be done)<br /> <br /> == Container tuning ==<br /> <br /> * Turn on '''bridge''' feature to allow docker creating bridged network inside container:<br /> prlctl set $veid --features bridge:on<br /> * Setup Container veth-based network (Container must be '''veth'''-based, not '''venet'''-based):<br /> prlctl set $veid --device-add net --network Bridged --dhcp yes<br /> * Allow all iptables modules to be used in containers:<br /> prlctl set $veid --netfilter=full<br /> <br /> == Docker install ==<br /> <br /> To install docker inside container please use Docker Installation Guide for your OS<br /> https://docs.docker.com/v1.11/engine/installation/<br /> <br /> [[Category:HOWTO]]<br /> [[Category: TRD]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Setup_OpenStack_with_Virtuozzo_7&diff=19775 2016-07-15T11:50:03Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> This article describes how to install OpenStack on [[Virtuozzo]] 7.<br /> == Introduction ==<br /> <br /> Virtuozzo 7 supports OpenStack as cloud management solution since version 6. With Virtuozzo 7 we are going to add a lot of new capabilities to OpenStack integration. <br /> Current limitations (bugs, not implemented or by design):<br /> #HA does not work.<br /> #Virtuozzo Storage is not supported for containers and VMs in cinder. <br /> <br /> This guide allows you to install OpenStack with Virtuozzo nodes with a help of Devstack tools. Devstack allows you to install stateless OpenStack for demo purpose that means it will be reset after host reboot. So, the best platform to setup OpenStack in this case is virtual machines.<br /> <br /> Please note that OpenStack now does not support containers and virtual machines on the same node, thus you need at least two nodes to try containers and VMs management.<br /> <br /> You need the following infrastructure to setup OpenStack with Virtuozzo 7:<br /> #controller host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a controller and Virtuozzo containers host.<br /> #compute host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a virtual machines host.<br /> <br /> == Prerequisites ==<br /> <br /> You need to install and update your Virtuozzo nodes first. Install Virtuozzo 7 on your controller and compute hosts as usual. You can use basic (local) or Virtuozzo Storage. Update Virtuozzo hosts<br /> $ yum update -y<br /> <br /> IP connection tracking should be enabled for CT0. Please do the following:<br /> #Open the file /etc/modprobe.d/vz.conf<br /> #Change the line &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=1&lt;/code&gt; to &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=0&lt;/code&gt;<br /> #Reboot the system<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> $ yum install git -y<br /> <br /> == Setup OpenStack Controller Node with Virtuozzo Containers Support == &lt;!--T:1--&gt;<br /> <br /> &lt;!--T:3--&gt;<br /> You are able to setup OpenStack controller node together with compute node on the same server for demo or test purpose. In this case compute node with Virtuozzo Containers support will be deployed. You can add another compute node with containers or VMs anytime you want as described in Setup OpenStack Compute Node section.<br /> <br /> Clone virtuozzo scripts:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Storage Cluster. <br /> <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node -P<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show Virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the CONTROLLER node. Please read full script description here https://github.com/virtuozzo/virtuozzo-openstack-scripts/blob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.25 --password Virtuozzo1! --use_provider_network true --fixed_range 192.168.1.0/24 --floating_range 10.24.41.0/24 --floating_pool &quot;start=10.24.41.151,end=10.24.41.199&quot; --public_gateway 10.24.41.1 --gateway 192.168.0.1 --vzstorage vstorage1 --mode ALL <br /> <br /> Run the script on your CONTROLLER node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> Installation can take up to 30 minutes depending on your Internet connection speed. Finished!<br /> <br /> == Setup OpenStack Compute Node ==<br /> <br /> Clone Virtuozzo scripts to your COMPUTE node:<br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd /vz/virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Cluster. <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node -P<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show the virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the COMPUTE node. Please read script description here https://github.com/virtuozzo/virtuozzo-openstack-scripblob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.26 --password Virtuozzo1! --use_provider_network true --mode COMPUTE --controller 10.24.41.25 <br /> <br /> Run the script on your COMPUTE node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> == How to change Virtualiztion Type to Virtual Machines on the Compute Node ==<br /> <br /> If you want to use virtual machines instead of containers on your compute node you need to change virtualization type to KVM on the selected compute node.<br /> <br /> Open nova configuration file:<br /> $ vi /etc/nova/nova.conf<br /> <br /> Change the following lines:<br /> <br /> [libvirt]<br /> ...<br /> virt_type = kvm<br /> images_type = qcow2<br /> connection_uri = qemu:///system<br /> <br /> Delete the line:<br /> inject_partition = -2<br /> <br /> Save the file.<br /> <br /> Restart nova-compute service:<br /> $ su stack<br /> $ screen -r<br /> Press Ctrl-c<br /> $ sg libvirtd '/usr/bin/nova-compute --config-file /etc/nova/nova.conf' &amp; echo $! &gt;/vz/stack/status/stack/n-cpu.pid; fg || echo &quot;n-cpu failed to start&quot; | tee &quot;/vz/stack/status/stack/n-cpu.failure&quot;<br /> <br /> To exit from screen session:<br /> Press Ctrl+a+d<br /> <br /> == How to redeploy OpenStack on the same nodes ==<br /> <br /> Your OpenStack setup will be reset after node restart. To redeploy OpenStack on the same nodes do the following:<br /> # &lt;code&gt;cd /vz/virtuozzo-openstack-scripts&lt;/code&gt;<br /> # &lt;code&gt;git pull&lt;/code&gt;<br /> # Run ./setup_devstack_vz7.sh with options you need.<br /> <br /> == Install and configure a nova controller node on [[Virtuozzo]] 7 == &lt;!--T:18--&gt;<br /> <br /> &lt;!--T:19--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-controller-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> <br /> * Change disk_formats string in /etc/glance/glance-api.conf so that it contains 'ploop'. Like this:<br /> <br /> disk_formats = ami,ari,aki,vhd,vmdk,raw,qcow2,vdi,iso,ploop<br /> <br /> * Restart glance-api service:<br /> <br /> systemctl restart openstack-glance-api.service<br /> <br /> * Download the container [http://updates.pvs.parallels.com/server/virtuozzo/en_us/odin/7/techpreview-ct/centos7-exe.hds.tar.gz image]<br /> * Unpack it<br /> <br /> $ tar -xzvf centos7-exe.hds.tar.gz<br /> <br /> * Upload the image to glance:<br /> NOTE: this image was created for testing purposes only. Don't use it in production as is!<br /> <br /> glance image-create --name centos7-exe --disk-format ploop --container-format bare --property vm_mode=exe --file centos7-exe.hds<br /> <br /> * Restart nova services:<br /> <br /> systemctl restart openstack-nova-api.service \<br /> openstack-nova-cert.service openstack-nova-consoleauth.service \<br /> openstack-nova-scheduler.service openstack-nova-conductor.service \<br /> openstack-nova-novncproxy.service<br /> <br /> == Install and configure a compute node on [[Virtuozzo]] 7 == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-compute-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> force_raw_images = False<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> connection_uri = parallels+unix:///system<br /> inject_partition = -2<br /> <br /> * Then restart nova-compute service:<br /> <br /> systemctl restart openstack-nova-compute.service<br /> <br /> == See also == &lt;!--T:100--&gt;<br /> * [http://docs.openstack.org/liberty/install-guide-rdo/environment-packages.html OpenStack installation guide]<br /> * [https://docs.openvz.org/ Virtuozzo documentation]<br /> * [[Virtuozzo ecosystem]]<br /> <br /> &lt;/translate&gt;<br /> <br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Setup_OpenStack_with_Virtuozzo_7&diff=19774 2016-07-15T11:46:11Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> This article describes how to install OpenStack on [[Virtuozzo]] 7.<br /> == Introduction ==<br /> <br /> Virtuozzo 7 supports OpenStack as cloud management solution since version 6. With Virtuozzo 7 we are going to add a lot of new capabilities to OpenStack integration. <br /> Current limitations (bugs, not implemented or by design):<br /> #HA does not work.<br /> #Virtuozzo Storage is not supported for containers and VMs in cinder. <br /> <br /> This guide allows you to install OpenStack with Virtuozzo nodes with a help of Devstack tools. Devstack allows you to install stateless OpenStack for demo purpose that means it will be reset after host reboot. So, the best platform to setup OpenStack in this case is virtual machines.<br /> <br /> Please note that OpenStack now does not support containers and virtual machines on the same node, thus you need at least two nodes to try containers and VMs management.<br /> <br /> You need the following infrastructure to setup OpenStack with Virtuozzo 7:<br /> #controller host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a controller and Virtuozzo containers host.<br /> #compute host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a virtual machines host.<br /> <br /> == Prerequisites ==<br /> <br /> You need to install and update your Virtuozzo nodes first. Install Virtuozzo 7 on your controller and compute hosts as usual. You can use basic (local) or Virtuozzo Storage. Update Virtuozzo hosts<br /> $ yum update -y<br /> <br /> IP connection tracking should be enabled for CT0. Please do the following:<br /> #Open the file /etc/modprobe.d/vz.conf<br /> #Change the line &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=1&lt;/code&gt; to &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=0&lt;/code&gt;<br /> #Reboot the system<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> $ yum install git -y<br /> <br /> == Setup OpenStack Controller Node with Virtuozzo Containers Support == &lt;!--T:1--&gt;<br /> <br /> &lt;!--T:3--&gt;<br /> You are able to setup OpenStack controller node together with compute node on the same server for demo or test purpose. In this case compute node with Virtuozzo Containers support will be deployed. You can add another compute node with containers or VMs anytime you want as described in Setup OpenStack Compute Node section.<br /> <br /> Clone virtuozzo scripts:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Storage Cluster. <br /> <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node -P<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show Virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the CONTROLLER node. Please read full script description here https://github.com/virtuozzo/virtuozzo-openstack-scripts/blob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.25 --password Virtuozzo1! --use_provider_network true --fixed_range 192.168.1.0/24 --floating_range 10.24.41.0/24 --floating_pool &quot;start=10.24.41.151,end=10.24.41.199&quot; --public_gateway 10.24.41.1 --gateway 192.168.0.1 --vzstorage vstorage1 --mode ALL <br /> <br /> Run the script on your CONTROLLER node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> Installation can take up to 30 minutes depending on your Internet connection speed. Finished!<br /> <br /> == Setup OpenStack Compute Node ==<br /> <br /> Clone Virtuozzo scripts to your COMPUTE node:<br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd /vz/virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Cluster. <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node -P<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show the virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the COMPUTE node. Please read script description here https://github.com/virtuozzo/virtuozzo-openstack-scripblob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.26 --password Virtuozzo1! --use_provider_network true --mode COMPUTE --controller 10.24.41.25 <br /> <br /> Run the script on your COMPUTE node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> == How to change Virtualiztion Type to Virtual Machines on the Compute Node ==<br /> <br /> If you want to use virtual machines instead of containers on your compute node you need to change virtualization type to KVM on the selected compute node.<br /> <br /> Open nova configuration file:<br /> $ vi /etc/nova/nova.conf<br /> <br /> Change the following lines:<br /> [libvirt]<br /> ...<br /> virt_type = kvm<br /> images_type = qcow2<br /> connection_uri = qemu:///system<br /> <br /> Delete the line:<br /> inject_partition = -2<br /> <br /> Save the file.<br /> <br /> Restart nova-compute service:<br /> $ su stack<br /> $ screen -r<br /> Press Ctrl-c<br /> $ sg libvirtd '/usr/bin/nova-compute --config-file /etc/nova/nova.conf' &amp; echo $! &gt;/vz/stack/status/stack/n-cpu.pid; fg || echo &quot;n-cpu failed to start&quot; | tee &quot;/vz/stack/status/stack/n-cpu.failure&quot;<br /> <br /> To exit from screen session:<br /> Press Ctrl+a+d<br /> <br /> == How to redeploy OpenStack on the same nodes ==<br /> <br /> Your OpenStack setup will be reset after node restart. To redeploy OpenStack on the same nodes do the following:<br /> # &lt;code&gt;cd /vz/virtuozzo-openstack-scripts&lt;/code&gt;<br /> # &lt;code&gt;git pull&lt;/code&gt;<br /> # Run ./setup_devstack_vz7.sh with options you need.<br /> <br /> == Install and configure a nova controller node on [[Virtuozzo]] 7 == &lt;!--T:18--&gt;<br /> <br /> &lt;!--T:19--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-controller-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> <br /> * Change disk_formats string in /etc/glance/glance-api.conf so that it contains 'ploop'. Like this:<br /> <br /> disk_formats = ami,ari,aki,vhd,vmdk,raw,qcow2,vdi,iso,ploop<br /> <br /> * Restart glance-api service:<br /> <br /> systemctl restart openstack-glance-api.service<br /> <br /> * Download the container [http://updates.pvs.parallels.com/server/virtuozzo/en_us/odin/7/techpreview-ct/centos7-exe.hds.tar.gz image]<br /> * Unpack it<br /> <br /> $ tar -xzvf centos7-exe.hds.tar.gz<br /> <br /> * Upload the image to glance:<br /> NOTE: this image was created for testing purposes only. Don't use it in production as is!<br /> <br /> glance image-create --name centos7-exe --disk-format ploop --container-format bare --property vm_mode=exe --file centos7-exe.hds<br /> <br /> * Restart nova services:<br /> <br /> systemctl restart openstack-nova-api.service \<br /> openstack-nova-cert.service openstack-nova-consoleauth.service \<br /> openstack-nova-scheduler.service openstack-nova-conductor.service \<br /> openstack-nova-novncproxy.service<br /> <br /> == Install and configure a compute node on [[Virtuozzo]] 7 == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-compute-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> force_raw_images = False<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> connection_uri = parallels+unix:///system<br /> inject_partition = -2<br /> <br /> * Then restart nova-compute service:<br /> <br /> systemctl restart openstack-nova-compute.service<br /> <br /> == See also == &lt;!--T:100--&gt;<br /> * [http://docs.openstack.org/liberty/install-guide-rdo/environment-packages.html OpenStack installation guide]<br /> * [https://docs.openvz.org/ Virtuozzo documentation]<br /> * [[Virtuozzo ecosystem]]<br /> <br /> &lt;/translate&gt;<br /> <br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Setup_OpenStack_with_Virtuozzo_7&diff=19773 2016-07-15T11:45:36Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> This article describes how to install OpenStack on [[Virtuozzo]] 7.<br /> == Introduction ==<br /> <br /> Virtuozzo 7 supports OpenStack as cloud management solution since version 6. With Virtuozzo 7 we are going to add a lot of new capabilities to OpenStack integration. <br /> Current limitations (bugs, not implemented or by design):<br /> #HA does not work.<br /> #Virtuozzo Storage is not supported for containers and VMs in cinder. <br /> <br /> This guide allows you to install OpenStack with Virtuozzo nodes with a help of Devstack tools. Devstack allows you to install stateless OpenStack for demo purpose that means it will be reset after host reboot. So, the best platform to setup OpenStack in this case is virtual machines.<br /> <br /> Please note that OpenStack now does not support containers and virtual machines on the same node, thus you need at least two nodes to try containers and VMs management.<br /> <br /> You need the following infrastructure to setup OpenStack with Virtuozzo 7:<br /> #controller host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a controller and Virtuozzo containers host.<br /> #compute host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a virtual machines host.<br /> <br /> == Prerequisites ==<br /> <br /> You need to install and update your Virtuozzo nodes first. Install Virtuozzo 7 on your controller and compute hosts as usual. You can use basic (local) or Virtuozzo Storage. Update Virtuozzo hosts<br /> $ yum update -y<br /> <br /> IP connection tracking should be enabled for CT0. Please do the following:<br /> #Open the file /etc/modprobe.d/vz.conf<br /> #Change the line &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=1&lt;/code&gt; to &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=0&lt;/code&gt;<br /> #Reboot the system<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> $ yum install git -y<br /> <br /> == Setup OpenStack Controller Node with Virtuozzo Containers Support == &lt;!--T:1--&gt;<br /> <br /> &lt;!--T:3--&gt;<br /> You are able to setup OpenStack controller node together with compute node on the same server for demo or test purpose. In this case compute node with Virtuozzo Containers support will be deployed. You can add another compute node with containers or VMs anytime you want as described in Setup OpenStack Compute Node section.<br /> <br /> Clone virtuozzo scripts:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Storage Cluster. <br /> <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node -P<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show Virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the CONTROLLER node. Please read full script description here [http://www.example.com link title]https://github.com/virtuozzo/virtuozzo-openstack-scripts/blob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.25 --password Virtuozzo1! --use_provider_network true --fixed_range 192.168.1.0/24 --floating_range 10.24.41.0/24 --floating_pool &quot;start=10.24.41.151,end=10.24.41.199&quot; --public_gateway 10.24.41.1 --gateway 192.168.0.1 --vzstorage vstorage1 --mode ALL <br /> <br /> Run the script on your CONTROLLER node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> Installation can take up to 30 minutes depending on your Internet connection speed. Finished!<br /> <br /> == Setup OpenStack Compute Node ==<br /> <br /> Clone Virtuozzo scripts to your COMPUTE node:<br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd /vz/virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Cluster. <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node -P<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show the virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the COMPUTE node. Please read script description here https://github.com/virtuozzo/virtuozzo-openstack-scripblob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.26 --password Virtuozzo1! --use_provider_network true --mode COMPUTE --controller 10.24.41.25 <br /> <br /> Run the script on your COMPUTE node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> == How to change Virtualiztion Type to Virtual Machines on the Compute Node ==<br /> <br /> If you want to use virtual machines instead of containers on your compute node you need to change virtualization type to KVM on the selected compute node.<br /> <br /> Open nova configuration file:<br /> $ vi /etc/nova/nova.conf<br /> <br /> Change the following lines:<br /> [libvirt]<br /> ...<br /> virt_type = kvm<br /> images_type = qcow2<br /> connection_uri = qemu:///system<br /> <br /> Delete the line:<br /> inject_partition = -2<br /> <br /> Save the file.<br /> <br /> Restart nova-compute service:<br /> $ su stack<br /> $ screen -r<br /> Press Ctrl-c<br /> $ sg libvirtd '/usr/bin/nova-compute --config-file /etc/nova/nova.conf' &amp; echo $! &gt;/vz/stack/status/stack/n-cpu.pid; fg || echo &quot;n-cpu failed to start&quot; | tee &quot;/vz/stack/status/stack/n-cpu.failure&quot;<br /> <br /> To exit from screen session:<br /> Press Ctrl+a+d<br /> <br /> == How to redeploy OpenStack on the same nodes ==<br /> <br /> Your OpenStack setup will be reset after node restart. To redeploy OpenStack on the same nodes do the following:<br /> # &lt;code&gt;cd /vz/virtuozzo-openstack-scripts&lt;/code&gt;<br /> # &lt;code&gt;git pull&lt;/code&gt;<br /> # Run ./setup_devstack_vz7.sh with options you need.<br /> <br /> == Install and configure a nova controller node on [[Virtuozzo]] 7 == &lt;!--T:18--&gt;<br /> <br /> &lt;!--T:19--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-controller-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> <br /> * Change disk_formats string in /etc/glance/glance-api.conf so that it contains 'ploop'. Like this:<br /> <br /> disk_formats = ami,ari,aki,vhd,vmdk,raw,qcow2,vdi,iso,ploop<br /> <br /> * Restart glance-api service:<br /> <br /> systemctl restart openstack-glance-api.service<br /> <br /> * Download the container [http://updates.pvs.parallels.com/server/virtuozzo/en_us/odin/7/techpreview-ct/centos7-exe.hds.tar.gz image]<br /> * Unpack it<br /> <br /> $ tar -xzvf centos7-exe.hds.tar.gz<br /> <br /> * Upload the image to glance:<br /> NOTE: this image was created for testing purposes only. Don't use it in production as is!<br /> <br /> glance image-create --name centos7-exe --disk-format ploop --container-format bare --property vm_mode=exe --file centos7-exe.hds<br /> <br /> * Restart nova services:<br /> <br /> systemctl restart openstack-nova-api.service \<br /> openstack-nova-cert.service openstack-nova-consoleauth.service \<br /> openstack-nova-scheduler.service openstack-nova-conductor.service \<br /> openstack-nova-novncproxy.service<br /> <br /> == Install and configure a compute node on [[Virtuozzo]] 7 == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-compute-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> force_raw_images = False<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> connection_uri = parallels+unix:///system<br /> inject_partition = -2<br /> <br /> * Then restart nova-compute service:<br /> <br /> systemctl restart openstack-nova-compute.service<br /> <br /> == See also == &lt;!--T:100--&gt;<br /> * [http://docs.openstack.org/liberty/install-guide-rdo/environment-packages.html OpenStack installation guide]<br /> * [https://docs.openvz.org/ Virtuozzo documentation]<br /> * [[Virtuozzo ecosystem]]<br /> <br /> &lt;/translate&gt;<br /> <br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Setup_OpenStack_with_Virtuozzo_7&diff=19772 2016-07-15T11:44:17Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> This article describes how to install OpenStack on [[Virtuozzo]] 7.<br /> == Introduction ==<br /> <br /> Virtuozzo 7 supports OpenStack as cloud management solution since version 6. With Virtuozzo 7 we are going to add a lot of new capabilities to OpenStack integration. <br /> Current limitations (bugs, not implemented or by design):<br /> #HA does not work.<br /> #Virtuozzo Storage is not supported for containers and VMs in cinder. <br /> <br /> This guide allows you to install OpenStack with Virtuozzo nodes with a help of Devstack tools. Devstack allows you to install stateless OpenStack for demo purpose that means it will be reset after host reboot. So, the best platform to setup OpenStack in this case is virtual machines.<br /> <br /> Please note that OpenStack now does not support containers and virtual machines on the same node, thus you need at least two nodes to try containers and VMs management.<br /> <br /> You need the following infrastructure to setup OpenStack with Virtuozzo 7:<br /> #controller host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a controller and Virtuozzo containers host.<br /> #compute host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a virtual machines host.<br /> <br /> == Prerequisites ==<br /> <br /> You need to install and update your Virtuozzo nodes first. Install Virtuozzo 7 on your controller and compute hosts as usual. You can use basic (local) or Virtuozzo Storage. Update Virtuozzo hosts<br /> $ yum update -y<br /> <br /> IP connection tracking should be enabled for CT0. Please do the following:<br /> #Open the file /etc/modprobe.d/vz.conf<br /> #Change the line &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=1&lt;/code&gt; to &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=0&lt;/code&gt;<br /> #Reboot the system<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> $ yum install git -y<br /> <br /> == Setup OpenStack Controller Node with Virtuozzo Containers Support == &lt;!--T:1--&gt;<br /> <br /> &lt;!--T:3--&gt;<br /> You are able to setup OpenStack controller node together with compute node on the same server for demo or test purpose. In this case compute node with Virtuozzo Containers support will be deployed. You can add another compute node with containers or VMs anytime you want as described in Setup OpenStack Compute Node section.<br /> <br /> Clone virtuozzo scripts:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Storage Cluster. <br /> <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node -P<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show Virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the CONTROLLER node. Please read full script description here https://github.com/virtuozzo/virtuozzo-openstack-scripts/blob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.25 --password Virtuozzo1! --use_provider_network true --fixed_range 192.168.1.0/24 --floating_range 10.24.41.0/24 --floating_pool &quot;start=10.24.41.151,end=10.24.41.199&quot; --public_gateway 10.24.41.1 --gateway 192.168.0.1 --vzstorage vstorage1 --mode ALL <br /> <br /> Run the script on your CONTROLLER node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> Installation can take up to 30 minutes depending on your Internet connection speed. Finished!<br /> <br /> == Setup OpenStack Compute Node ==<br /> <br /> Clone Virtuozzo scripts to your COMPUTE node:<br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd /vz/virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Cluster. <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node -P<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show the virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the COMPUTE node. Please read script description here https://github.com/virtuozzo/virtuozzo-openstack-scripts/blob/master/README.md<br /> <br /> Example:<br /> source vzrc --host_ip 10.24.41.26 --password Virtuozzo1! --use_provider_network true --mode COMPUTE --controller 10.24.41.25 <br /> <br /> Run the script on your COMPUTE node and follow instructions (if any):<br /> $ ./setup_devstack_vz7.sh<br /> <br /> == How to change Virtualiztion Type to Virtual Machines on the Compute Node ==<br /> <br /> If you want to use virtual machines instead of containers on your compute node you need to change virtualization type to KVM on the selected compute node.<br /> <br /> Open nova configuration file:<br /> $ vi /etc/nova/nova.conf<br /> <br /> Change the following lines:<br /> [libvirt]<br /> ...<br /> virt_type = kvm<br /> images_type = qcow2<br /> connection_uri = qemu:///system<br /> <br /> Delete the line:<br /> inject_partition = -2<br /> <br /> Save the file.<br /> <br /> Restart nova-compute service:<br /> $ su stack<br /> $ screen -r<br /> Press Ctrl-c<br /> $ sg libvirtd '/usr/bin/nova-compute --config-file /etc/nova/nova.conf' &amp; echo $! &gt;/vz/stack/status/stack/n-cpu.pid; fg || echo &quot;n-cpu failed to start&quot; | tee &quot;/vz/stack/status/stack/n-cpu.failure&quot;<br /> <br /> To exit from screen session:<br /> Press Ctrl+a+d<br /> <br /> == How to redeploy OpenStack on the same nodes ==<br /> <br /> Your OpenStack setup will be reset after node restart. To redeploy OpenStack on the same nodes do the following:<br /> # &lt;code&gt;cd /vz/virtuozzo-openstack-scripts&lt;/code&gt;<br /> # &lt;code&gt;git pull&lt;/code&gt;<br /> # Run ./setup_devstack_vz7.sh with options you need.<br /> <br /> == Install and configure a nova controller node on [[Virtuozzo]] 7 == &lt;!--T:18--&gt;<br /> <br /> &lt;!--T:19--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-controller-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> <br /> * Change disk_formats string in /etc/glance/glance-api.conf so that it contains 'ploop'. Like this:<br /> <br /> disk_formats = ami,ari,aki,vhd,vmdk,raw,qcow2,vdi,iso,ploop<br /> <br /> * Restart glance-api service:<br /> <br /> systemctl restart openstack-glance-api.service<br /> <br /> * Download the container [http://updates.pvs.parallels.com/server/virtuozzo/en_us/odin/7/techpreview-ct/centos7-exe.hds.tar.gz image]<br /> * Unpack it<br /> <br /> $ tar -xzvf centos7-exe.hds.tar.gz<br /> <br /> * Upload the image to glance:<br /> NOTE: this image was created for testing purposes only. Don't use it in production as is!<br /> <br /> glance image-create --name centos7-exe --disk-format ploop --container-format bare --property vm_mode=exe --file centos7-exe.hds<br /> <br /> * Restart nova services:<br /> <br /> systemctl restart openstack-nova-api.service \<br /> openstack-nova-cert.service openstack-nova-consoleauth.service \<br /> openstack-nova-scheduler.service openstack-nova-conductor.service \<br /> openstack-nova-novncproxy.service<br /> <br /> == Install and configure a compute node on [[Virtuozzo]] 7 == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-compute-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> force_raw_images = False<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> connection_uri = parallels+unix:///system<br /> inject_partition = -2<br /> <br /> * Then restart nova-compute service:<br /> <br /> systemctl restart openstack-nova-compute.service<br /> <br /> == See also == &lt;!--T:100--&gt;<br /> * [http://docs.openstack.org/liberty/install-guide-rdo/environment-packages.html OpenStack installation guide]<br /> * [https://docs.openvz.org/ Virtuozzo documentation]<br /> * [[Virtuozzo ecosystem]]<br /> <br /> &lt;/translate&gt;<br /> <br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Setup_OpenStack_with_Virtuozzo_7&diff=19771 2016-07-15T11:37:14Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> This article describes how to install OpenStack on [[Virtuozzo]] 7.<br /> == Introduction ==<br /> <br /> Virtuozzo 7 supports OpenStack as cloud management solution since version 6. With Virtuozzo 7 we are going to add a lot of new capabilities to OpenStack integration. <br /> Current limitations (bugs, not implemented or by design):<br /> #HA does not work.<br /> #Virtuozzo Storage is not supported for containers and VMs in cinder. <br /> <br /> This guide allows you to install OpenStack with Virtuozzo nodes with a help of Devstack tools. Devstack allows you to install stateless OpenStack for demo purpose that means it will be reset after host reboot. So, the best platform to setup OpenStack in this case is virtual machines.<br /> <br /> Please note that OpenStack now does not support containers and virtual machines on the same node, thus you need at least two nodes to try containers and VMs management.<br /> <br /> You need the following infrastructure to setup OpenStack with Virtuozzo 7:<br /> #controller host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a controller and Virtuozzo containers host.<br /> #compute host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a virtual machines host.<br /> <br /> == Prerequisites ==<br /> <br /> You need to install and update your Virtuozzo nodes first. Install Virtuozzo 7 on your controller and compute hosts as usual. You can use basic (local) or Virtuozzo Storage. Update Virtuozzo hosts<br /> $ yum update -y<br /> <br /> IP connection tracking should be enabled for CT0. Please do the following:<br /> #Open the file /etc/modprobe.d/vz.conf<br /> #Change the line &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=1&lt;/code&gt; to &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=0&lt;/code&gt;<br /> #Reboot the system<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> $ yum install git -y<br /> <br /> == Setup OpenStack Controller Node with Virtuozzo Containers Support == &lt;!--T:1--&gt;<br /> <br /> &lt;!--T:3--&gt;<br /> You are able to setup OpenStack controller node together with compute node on the same server for demo or test purpose. In this case compute node with Virtuozzo Containers support will be deployed. You can add another compute node with containers or VMs anytime you want as described in Setup OpenStack Compute Node section.<br /> <br /> Clone virtuozzo scripts:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> If you want to use Virtuozzo Storage with OpenStack and your Virtuozzo Storage is running on another node and not on the compute you need to setup Virtuozzo Storage client and authorize compute node in the Virtuozzo Storage Cluster. <br /> <br /> Setup Virtuozzo Storage client:<br /> $ yum install vstorage-client -y<br /> Check cluster discovery is working fine first: <br /> $ vstorage discover<br /> Output will show the discovered clusters.<br /> Now you need to authenticate controller node on the Virtuozzo Storage cluster:<br /> $ vstorage -c $CLUSTER_NAME auth-node -P<br /> Enter the virtuozzo storage cluster password and press Enter. <br /> Check the cluster properties:<br /> $ vstorage -c $CLUSTER_NAME top<br /> Output will show Virtuozzo storage cluster properties and state.<br /> <br /> Configure the script on the CONTROLLER node. Please read full script description here https://github.com/virtuozzo/virtuozzo-openstack-scripts/blob/master/README.md<br /> <br /> Example:<br /> $ source vzrc --host_ip 10.24.41.25 --password Virtuozzo1! --use_provider_network true --fixed_range 192.168.1.0/24 --floating_range 10.24.41.0/24 --floating_pool &quot;start=10.24.41.151,end=10.24.41.199&quot; --public_gateway 10.24.41.1 --gateway 192.168.0.1 --vzstorage vstorage1 --mode ALL <br /> <br /> Run the script on your CONTROLLER node and follow instructions (if any):<br /> $./setup_devstack_vz7.sh<br /> <br /> Installation can take up to 30 minutes depending on your Internet connection speed. Finished!<br /> <br /> == Setup OpenStack Compute Node ==<br /> <br /> Clone Virtuozzo scripts to your COMPUTE node:<br /> # cd /vz<br /> # git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> # cd /vz/virtuozzo-openstack-scripts<br /> <br /> == How to redeploy OpenStack on the same nodes ==<br /> <br /> Your OpenStack setup will be reset after node restart. To redeploy OpenStack on the same nodes do the following:<br /> # &lt;code&gt;cd /vz/virtuozzo-openstack-scripts&lt;/code&gt;<br /> # &lt;code&gt;git pull&lt;/code&gt;<br /> # Run ./setup_devstack_vz7.sh with options you need.<br /> <br /> == Install and configure a nova controller node on [[Virtuozzo]] 7 == &lt;!--T:18--&gt;<br /> <br /> &lt;!--T:19--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-controller-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> <br /> * Change disk_formats string in /etc/glance/glance-api.conf so that it contains 'ploop'. Like this:<br /> <br /> disk_formats = ami,ari,aki,vhd,vmdk,raw,qcow2,vdi,iso,ploop<br /> <br /> * Restart glance-api service:<br /> <br /> systemctl restart openstack-glance-api.service<br /> <br /> * Download the container [http://updates.pvs.parallels.com/server/virtuozzo/en_us/odin/7/techpreview-ct/centos7-exe.hds.tar.gz image]<br /> * Unpack it<br /> <br /> $ tar -xzvf centos7-exe.hds.tar.gz<br /> <br /> * Upload the image to glance:<br /> NOTE: this image was created for testing purposes only. Don't use it in production as is!<br /> <br /> glance image-create --name centos7-exe --disk-format ploop --container-format bare --property vm_mode=exe --file centos7-exe.hds<br /> <br /> * Restart nova services:<br /> <br /> systemctl restart openstack-nova-api.service \<br /> openstack-nova-cert.service openstack-nova-consoleauth.service \<br /> openstack-nova-scheduler.service openstack-nova-conductor.service \<br /> openstack-nova-novncproxy.service<br /> <br /> == Install and configure a compute node on [[Virtuozzo]] 7 == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-compute-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> force_raw_images = False<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> connection_uri = parallels+unix:///system<br /> inject_partition = -2<br /> <br /> * Then restart nova-compute service:<br /> <br /> systemctl restart openstack-nova-compute.service<br /> <br /> == See also == &lt;!--T:100--&gt;<br /> * [http://docs.openstack.org/liberty/install-guide-rdo/environment-packages.html OpenStack installation guide]<br /> * [https://docs.openvz.org/ Virtuozzo documentation]<br /> * [[Virtuozzo ecosystem]]<br /> <br /> &lt;/translate&gt;<br /> <br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Setup_OpenStack_with_Virtuozzo_7&diff=19770 2016-07-15T11:29:00Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> This article describes how to install OpenStack on [[Virtuozzo]] 7.<br /> == Introduction ==<br /> <br /> Virtuozzo 7 supports OpenStack as cloud management solution since version 6. With Virtuozzo 7 we are going to add a lot of new capabilities to OpenStack integration. <br /> Current limitations (bugs, not implemented or by design):<br /> #HA does not work.<br /> #Virtuozzo Storage is not supported for containers and VMs in cinder. <br /> <br /> This guide allows you to install OpenStack with Virtuozzo nodes with a help of Devstack tools. Devstack allows you to install stateless OpenStack for demo purpose that means it will be reset after host reboot. So, the best platform to setup OpenStack in this case is virtual machines.<br /> <br /> You need the following infrastructure to setup OpenStack with Virtuozzo 7:<br /> #controller host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a controller and Virtuozzo containers host.<br /> #compute host: physical host or virtual machine with at least 4CPU, 8GB RAM, 150GB disk. This host will act as a virtual machines host.<br /> <br /> == Prerequisites ==<br /> <br /> You need to install and update your Virtuozzo nodes first. Install Virtuozzo 7 on your controller and compute hosts as usual. You can use basic (local) or Virtuozzo Storage. Update Virtuozzo hosts<br /> $ yum update -y<br /> <br /> IP connection tracking should be enabled for CT0. Please do the following:<br /> #Open the file /etc/modprobe.d/vz.conf<br /> #Change the line &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=1&lt;/code&gt; to &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=0&lt;/code&gt;<br /> #Reboot the system<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> yum install git<br /> <br /> == Devstack all-in-one installation == &lt;!--T:1--&gt;<br /> <br /> &lt;!--T:3--&gt;<br /> You are able to setup OpenStack controller node together with compute node on the same server for demo or test purpose. In this case compute node with Virtuozzo Containers supported will be deployed. You can add another compute node with containers or VMs anytime you want as described in Devstack Multi-node Installation section.<br /> <br /> Please note that OpenStack now does not support containers and virtual machines on the same node.<br /> <br /> Clone virtuozzo scripts:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> <br /> <br /> <br /> Run the script and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh YOUR_HOST_IP YOUR_PASSWORD<br /> <br /> == Devstack multi node installation == &lt;!--T:11--&gt;<br /> <br /> &lt;!--T:12--&gt;<br /> Clone virtuozzo scripts on your CONTROLLER node:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:13--&gt;<br /> Run the script on your CONTROLLER node and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh YOUR_HOST_IP YOUR_PASSWORD CONTROLLER<br /> <br /> &lt;!--T:14--&gt;<br /> Clone virtuozzo scripts on your COMPUTE node:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:15--&gt;<br /> Run the script on your COMPUTE node and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh YOUR_COMPUTE_HOST_IP YOUR_PASSWORD COMPUTE YOUR_CONTROLLER_HOST_IP<br /> <br /> == How to redeploy OpenStack on the same nodes ==<br /> <br /> Your OpenStack setup will be reset after node restart. To redeploy OpenStack on the same nodes do the following:<br /> # &lt;code&gt;cd /vz/virtuozzo-openstack-scripts&lt;/code&gt;<br /> # &lt;code&gt;git pull&lt;/code&gt;<br /> # Run ./setup_devstack_vz7.sh with options you need.<br /> <br /> == Install and configure a nova controller node on [[Virtuozzo]] 7 == &lt;!--T:18--&gt;<br /> <br /> &lt;!--T:19--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-controller-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> <br /> * Change disk_formats string in /etc/glance/glance-api.conf so that it contains 'ploop'. Like this:<br /> <br /> disk_formats = ami,ari,aki,vhd,vmdk,raw,qcow2,vdi,iso,ploop<br /> <br /> * Restart glance-api service:<br /> <br /> systemctl restart openstack-glance-api.service<br /> <br /> * Download the container [http://updates.pvs.parallels.com/server/virtuozzo/en_us/odin/7/techpreview-ct/centos7-exe.hds.tar.gz image]<br /> * Unpack it<br /> <br /> $ tar -xzvf centos7-exe.hds.tar.gz<br /> <br /> * Upload the image to glance:<br /> NOTE: this image was created for testing purposes only. Don't use it in production as is!<br /> <br /> glance image-create --name centos7-exe --disk-format ploop --container-format bare --property vm_mode=exe --file centos7-exe.hds<br /> <br /> * Restart nova services:<br /> <br /> systemctl restart openstack-nova-api.service \<br /> openstack-nova-cert.service openstack-nova-consoleauth.service \<br /> openstack-nova-scheduler.service openstack-nova-conductor.service \<br /> openstack-nova-novncproxy.service<br /> <br /> == Install and configure a compute node on [[Virtuozzo]] 7 == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-compute-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> force_raw_images = False<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> connection_uri = parallels+unix:///system<br /> inject_partition = -2<br /> <br /> * Then restart nova-compute service:<br /> <br /> systemctl restart openstack-nova-compute.service<br /> <br /> == See also == &lt;!--T:100--&gt;<br /> * [http://docs.openstack.org/liberty/install-guide-rdo/environment-packages.html OpenStack installation guide]<br /> * [https://docs.openvz.org/ Virtuozzo documentation]<br /> * [[Virtuozzo ecosystem]]<br /> <br /> &lt;/translate&gt;<br /> <br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Setup_OpenStack_with_Virtuozzo_7&diff=19769 2016-07-15T11:22:06Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> This article describes how to install OpenStack on [[Virtuozzo]] 7.<br /> == Prerequisites ==<br /> <br /> You need to install and update your Virtuozzo or OpenVZ nodes first.<br /> <br /> IP connection tracking should be enabled for CT0. Please do the following:<br /> #Open the file /etc/modprobe.d/vz.conf<br /> #Change the line &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=1&lt;/code&gt; to &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=0&lt;/code&gt;<br /> #Reboot the system<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> yum install git<br /> <br /> == Devstack all-in-one installation == &lt;!--T:1--&gt;<br /> <br /> &lt;!--T:3--&gt;<br /> You are able to setup OpenStack controller node together with compute node on the same server for demo or test purpose. In this case compute node with Virtuozzo Containers supported will be deployed. You can add another compute node with containers or VMs anytime you want as described in Devstack Multi-node Installation section.<br /> <br /> Please note that OpenStack now does not support containers and virtual machines on the same node.<br /> <br /> Clone virtuozzo scripts:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:4--&gt;<br /> Run the script and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh YOUR_HOST_IP YOUR_PASSWORD<br /> <br /> == Devstack multi node installation == &lt;!--T:11--&gt;<br /> <br /> &lt;!--T:12--&gt;<br /> Clone virtuozzo scripts on your CONTROLLER node:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:13--&gt;<br /> Run the script on your CONTROLLER node and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh YOUR_HOST_IP YOUR_PASSWORD CONTROLLER<br /> <br /> &lt;!--T:14--&gt;<br /> Clone virtuozzo scripts on your COMPUTE node:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:15--&gt;<br /> Run the script on your COMPUTE node and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh YOUR_COMPUTE_HOST_IP YOUR_PASSWORD COMPUTE YOUR_CONTROLLER_HOST_IP<br /> <br /> == How to redeploy OpenStack on the same nodes ==<br /> <br /> Your OpenStack setup will be reset after node restart. To redeploy OpenStack on the same nodes do the following:<br /> # &lt;code&gt;cd /vz/virtuozzo-openstack-scripts&lt;/code&gt;<br /> # &lt;code&gt;git pull&lt;/code&gt;<br /> # Run ./setup_devstack_vz7.sh with options you need.<br /> <br /> == Install and configure a nova controller node on [[Virtuozzo]] 7 == &lt;!--T:18--&gt;<br /> <br /> &lt;!--T:19--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-controller-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> <br /> * Change disk_formats string in /etc/glance/glance-api.conf so that it contains 'ploop'. Like this:<br /> <br /> disk_formats = ami,ari,aki,vhd,vmdk,raw,qcow2,vdi,iso,ploop<br /> <br /> * Restart glance-api service:<br /> <br /> systemctl restart openstack-glance-api.service<br /> <br /> * Download the container [http://updates.pvs.parallels.com/server/virtuozzo/en_us/odin/7/techpreview-ct/centos7-exe.hds.tar.gz image]<br /> * Unpack it<br /> <br /> $ tar -xzvf centos7-exe.hds.tar.gz<br /> <br /> * Upload the image to glance:<br /> NOTE: this image was created for testing purposes only. Don't use it in production as is!<br /> <br /> glance image-create --name centos7-exe --disk-format ploop --container-format bare --property vm_mode=exe --file centos7-exe.hds<br /> <br /> * Restart nova services:<br /> <br /> systemctl restart openstack-nova-api.service \<br /> openstack-nova-cert.service openstack-nova-consoleauth.service \<br /> openstack-nova-scheduler.service openstack-nova-conductor.service \<br /> openstack-nova-novncproxy.service<br /> <br /> == Install and configure a compute node on [[Virtuozzo]] 7 == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-compute-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> force_raw_images = False<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> connection_uri = parallels+unix:///system<br /> inject_partition = -2<br /> <br /> * Then restart nova-compute service:<br /> <br /> systemctl restart openstack-nova-compute.service<br /> <br /> == See also == &lt;!--T:100--&gt;<br /> * [http://docs.openstack.org/liberty/install-guide-rdo/environment-packages.html OpenStack installation guide]<br /> * [https://docs.openvz.org/ Virtuozzo documentation]<br /> * [[Virtuozzo ecosystem]]<br /> <br /> &lt;/translate&gt;<br /> <br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Setup_OpenStack_with_Virtuozzo_7&diff=19756 2016-06-28T15:26:40Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> This article describes how to install OpenStack on [[Virtuozzo]] 7.<br /> == Prerequisites ==<br /> <br /> IP connection tracking should be enabled for CT0. Please do the following:<br /> #Open the file /etc/modprobe.d/vz.conf<br /> #Change the line &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=1&lt;/code&gt; to &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=0&lt;/code&gt;<br /> #Reboot the system<br /> <br /> Git must be installed on all your Virtuozzo nodes:<br /> yum install git<br /> <br /> == Devstack all-in-one installation == &lt;!--T:1--&gt;<br /> <br /> &lt;!--T:3--&gt;<br /> You are able to setup OpenStack controller node together with compute node on the same server for demo or test purpose. In this case compute node with Virtuozzo Containers supported will be deployed. You can add another compute node with containers or VMs anytime you want as described in Devstack Multi-node Installation section.<br /> <br /> Please note that OpenStack now does not support containers and virtual machines on the same node.<br /> <br /> Clone virtuozzo scripts:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:4--&gt;<br /> Run the script and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh YOUR_HOST_IP YOUR_PASSWORD<br /> <br /> == Devstack multi node installation == &lt;!--T:11--&gt;<br /> <br /> &lt;!--T:12--&gt;<br /> Clone virtuozzo scripts on your CONTROLLER node:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:13--&gt;<br /> Run the script on your CONTROLLER node and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh YOUR_HOST_IP YOUR_PASSWORD CONTROLLER<br /> <br /> &lt;!--T:14--&gt;<br /> Clone virtuozzo scripts on your COMPUTE node:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:15--&gt;<br /> Run the script on your COMPUTE node and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh YOUR_COMPUTE_HOST_IP YOUR_PASSWORD COMPUTE YOUR_CONTROLLER_HOST_IP<br /> <br /> == Change iptables rules to allow access to Horizon Dashboard ==<br /> <br /> Remove the reject rule in iptables:<br /> iptables -D INPUT -j REJECT --reject-with icmp-host-prohibited<br /> <br /> == How to redeploy OpenStack on the same nodes ==<br /> <br /> Your OpenStack setup will be reset after node restart. To redeploy OpenStack on the same nodes do the following:<br /> # &lt;code&gt;cd /vz/virtuozzo-openstack-scripts&lt;/code&gt;<br /> # &lt;code&gt;git pull&lt;/code&gt;<br /> # Run ./setup_devstack_vz7.sh with options you need.<br /> <br /> == Install and configure a nova controller node on [[Virtuozzo]] 7 == &lt;!--T:18--&gt;<br /> <br /> &lt;!--T:19--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-controller-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> <br /> * Change disk_formats string in /etc/glance/glance-api.conf so that it contains 'ploop'. Like this:<br /> <br /> disk_formats = ami,ari,aki,vhd,vmdk,raw,qcow2,vdi,iso,ploop<br /> <br /> * Restart glance-api service:<br /> <br /> systemctl restart openstack-glance-api.service<br /> <br /> * Download the container [http://updates.pvs.parallels.com/server/virtuozzo/en_us/odin/7/techpreview-ct/centos7-exe.hds.tar.gz image]<br /> * Unpack it<br /> <br /> $ tar -xzvf centos7-exe.hds.tar.gz<br /> <br /> * Upload the image to glance:<br /> NOTE: this image was created for testing purposes only. Don't use it in production as is!<br /> <br /> glance image-create --name centos7-exe --disk-format ploop --container-format bare --property vm_mode=exe --file centos7-exe.hds<br /> <br /> * Restart nova services:<br /> <br /> systemctl restart openstack-nova-api.service \<br /> openstack-nova-cert.service openstack-nova-consoleauth.service \<br /> openstack-nova-scheduler.service openstack-nova-conductor.service \<br /> openstack-nova-novncproxy.service<br /> <br /> == Install and configure a compute node on [[Virtuozzo]] 7 == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-compute-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> force_raw_images = False<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> connection_uri = parallels+unix:///system<br /> inject_partition = -2<br /> <br /> * Then restart nova-compute service:<br /> <br /> systemctl restart openstack-nova-compute.service<br /> <br /> == See also == &lt;!--T:100--&gt;<br /> * [http://docs.openstack.org/liberty/install-guide-rdo/environment-packages.html OpenStack installation guide]<br /> * [https://docs.openvz.org/ Virtuozzo documentation]<br /> * [[Virtuozzo ecosystem]]<br /> <br /> &lt;/translate&gt;<br /> <br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Setup_OpenStack_with_Virtuozzo_7&diff=19755 2016-06-28T15:26:10Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> This article describes how to install OpenStack on [[Virtuozzo]] 7.<br /> == Prerequisites ==<br /> <br /> IP connection tracking should be enabled for CT0. Please do the following:<br /> #Open the file /etc/modprobe.d/vz.conf<br /> #Change the line &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=1&lt;/code&gt; to &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=0&lt;/code&gt;<br /> #Reboot the system<br /> <br /> Git must be installed on your Virtuozzo node:<br /> yum install git<br /> <br /> == Devstack all-in-one installation == &lt;!--T:1--&gt;<br /> <br /> &lt;!--T:3--&gt;<br /> You are able to setup OpenStack controller node together with compute node on the same server for demo or test purpose. In this case compute node with Virtuozzo Containers supported will be deployed. You can add another compute node with containers or VMs anytime you want as described in Devstack Multi-node Installation section.<br /> <br /> Please note that OpenStack now does not support containers and virtual machines on the same node.<br /> <br /> Clone virtuozzo scripts:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:4--&gt;<br /> Run the script and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh YOUR_HOST_IP YOUR_PASSWORD<br /> <br /> == Devstack multi node installation == &lt;!--T:11--&gt;<br /> <br /> &lt;!--T:12--&gt;<br /> Clone virtuozzo scripts on your CONTROLLER node:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:13--&gt;<br /> Run the script on your CONTROLLER node and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh YOUR_HOST_IP YOUR_PASSWORD CONTROLLER<br /> <br /> &lt;!--T:14--&gt;<br /> Clone virtuozzo scripts on your COMPUTE node:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:15--&gt;<br /> Run the script on your COMPUTE node and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh YOUR_COMPUTE_HOST_IP YOUR_PASSWORD COMPUTE YOUR_CONTROLLER_HOST_IP<br /> <br /> == Change iptables rules to allow access to Horizon Dashboard ==<br /> <br /> Remove the reject rule in iptables:<br /> iptables -D INPUT -j REJECT --reject-with icmp-host-prohibited<br /> <br /> == How to redeploy OpenStack on the same nodes ==<br /> <br /> Your OpenStack setup will be reset after node restart. To redeploy OpenStack on the same nodes do the following:<br /> # &lt;code&gt;cd /vz/virtuozzo-openstack-scripts&lt;/code&gt;<br /> # &lt;code&gt;git pull&lt;/code&gt;<br /> # Run ./setup_devstack_vz7.sh with options you need.<br /> <br /> == Install and configure a nova controller node on [[Virtuozzo]] 7 == &lt;!--T:18--&gt;<br /> <br /> &lt;!--T:19--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-controller-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> <br /> * Change disk_formats string in /etc/glance/glance-api.conf so that it contains 'ploop'. Like this:<br /> <br /> disk_formats = ami,ari,aki,vhd,vmdk,raw,qcow2,vdi,iso,ploop<br /> <br /> * Restart glance-api service:<br /> <br /> systemctl restart openstack-glance-api.service<br /> <br /> * Download the container [http://updates.pvs.parallels.com/server/virtuozzo/en_us/odin/7/techpreview-ct/centos7-exe.hds.tar.gz image]<br /> * Unpack it<br /> <br /> $ tar -xzvf centos7-exe.hds.tar.gz<br /> <br /> * Upload the image to glance:<br /> NOTE: this image was created for testing purposes only. Don't use it in production as is!<br /> <br /> glance image-create --name centos7-exe --disk-format ploop --container-format bare --property vm_mode=exe --file centos7-exe.hds<br /> <br /> * Restart nova services:<br /> <br /> systemctl restart openstack-nova-api.service \<br /> openstack-nova-cert.service openstack-nova-consoleauth.service \<br /> openstack-nova-scheduler.service openstack-nova-conductor.service \<br /> openstack-nova-novncproxy.service<br /> <br /> == Install and configure a compute node on [[Virtuozzo]] 7 == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-compute-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> force_raw_images = False<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> connection_uri = parallels+unix:///system<br /> inject_partition = -2<br /> <br /> * Then restart nova-compute service:<br /> <br /> systemctl restart openstack-nova-compute.service<br /> <br /> == See also == &lt;!--T:100--&gt;<br /> * [http://docs.openstack.org/liberty/install-guide-rdo/environment-packages.html OpenStack installation guide]<br /> * [https://docs.openvz.org/ Virtuozzo documentation]<br /> * [[Virtuozzo ecosystem]]<br /> <br /> &lt;/translate&gt;<br /> <br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Setup_OpenStack_with_Virtuozzo_7&diff=19647 2016-06-07T13:45:40Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> This article describes how to install OpenStack on [[Virtuozzo]] 7.<br /> == Prerequisites ==<br /> <br /> IP connection tracking should be enabled for CT0. Please do the following:<br /> #Open the file /etc/modprobe.d/parallels.conf<br /> #Change the line &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=1&lt;/code&gt; to &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=0&lt;/code&gt;<br /> #Reboot the system<br /> <br /> Git must be installed on your Virtuozzo node:<br /> yum install git<br /> <br /> == Devstack all-in-one installation == &lt;!--T:1--&gt;<br /> <br /> &lt;!--T:3--&gt;<br /> You are able to setup OpenStack controller node together with compute node on the same server for demo or test purpose. In this case compute node with Virtuozzo Containers supported will be deployed. You can add another compute node with containers or VMs anytime you want as described in Devstack Multi-node Installation section.<br /> <br /> Please note that OpenStack now does not support containers and virtual machines on the same node.<br /> <br /> Clone virtuozzo scripts:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:4--&gt;<br /> Run the script and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh YOUR_HOST_IP YOUR_PASSWORD<br /> <br /> == Devstack multi node installation == &lt;!--T:11--&gt;<br /> <br /> &lt;!--T:12--&gt;<br /> Clone virtuozzo scripts on your CONTROLLER node:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:13--&gt;<br /> Run the script on your CONTROLLER node and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh YOUR_HOST_IP YOUR_PASSWORD CONTROLLER<br /> <br /> &lt;!--T:14--&gt;<br /> Clone virtuozzo scripts on your COMPUTE node:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:15--&gt;<br /> Run the script on your COMPUTE node and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh YOUR_COMPUTE_HOST_IP YOUR_PASSWORD COMPUTE YOUR_CONTROLLER_HOST_IP<br /> <br /> == Change iptables rules to allow access to Horizon Dashboard ==<br /> <br /> Remove the reject rule in iptables:<br /> iptables -D INPUT -j REJECT --reject-with icmp-host-prohibited<br /> <br /> == How to redeploy OpenStack on the same nodes ==<br /> <br /> Your OpenStack setup will be reset after node restart. To redeploy OpenStack on the same nodes do the following:<br /> # &lt;code&gt;cd /vz/virtuozzo-openstack-scripts&lt;/code&gt;<br /> # &lt;code&gt;git pull&lt;/code&gt;<br /> # Run ./setup_devstack_vz7.sh with options you need.<br /> <br /> == Install and configure a nova controller node on [[Virtuozzo]] 7 == &lt;!--T:18--&gt;<br /> <br /> &lt;!--T:19--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-controller-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> <br /> * Change disk_formats string in /etc/glance/glance-api.conf so that it contains 'ploop'. Like this:<br /> <br /> disk_formats = ami,ari,aki,vhd,vmdk,raw,qcow2,vdi,iso,ploop<br /> <br /> * Restart glance-api service:<br /> <br /> systemctl restart openstack-glance-api.service<br /> <br /> * Download the container [http://updates.pvs.parallels.com/server/virtuozzo/en_us/odin/7/techpreview-ct/centos7-exe.hds.tar.gz image]<br /> * Unpack it<br /> <br /> $ tar -xzvf centos7-exe.hds.tar.gz<br /> <br /> * Upload the image to glance:<br /> NOTE: this image was created for testing purposes only. Don't use it in production as is!<br /> <br /> glance image-create --name centos7-exe --disk-format ploop --container-format bare --property vm_mode=exe --file centos7-exe.hds<br /> <br /> * Restart nova services:<br /> <br /> systemctl restart openstack-nova-api.service \<br /> openstack-nova-cert.service openstack-nova-consoleauth.service \<br /> openstack-nova-scheduler.service openstack-nova-conductor.service \<br /> openstack-nova-novncproxy.service<br /> <br /> == Install and configure a compute node on [[Virtuozzo]] 7 == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-compute-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> force_raw_images = False<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> connection_uri = parallels+unix:///system<br /> inject_partition = -2<br /> <br /> * Then restart nova-compute service:<br /> <br /> systemctl restart openstack-nova-compute.service<br /> <br /> == See also == &lt;!--T:100--&gt;<br /> * [http://docs.openstack.org/liberty/install-guide-rdo/environment-packages.html OpenStack installation guide]<br /> * [https://docs.openvz.org/ Virtuozzo documentation]<br /> * [[Virtuozzo ecosystem]]<br /> <br /> &lt;/translate&gt;<br /> <br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Setup_OpenStack_with_Virtuozzo_7&diff=19641 2016-06-06T14:06:37Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> This article describes how to install OpenStack on [[Virtuozzo]] 7.<br /> == Prerequisites ==<br /> <br /> IP connection tracking should be enabled for CT0. Please do the following:<br /> #Open the file /etc/modprobe.d/parallels.conf<br /> #Change the line &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=1&lt;/code&gt; to &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=0&lt;/code&gt;<br /> #Reboot the system<br /> <br /> Git must be installed on your Virtuozzo node:<br /> yum install git<br /> <br /> == Devstack all-in-one installation == &lt;!--T:1--&gt;<br /> <br /> &lt;!--T:3--&gt;<br /> You are able to setup OpenStack controller node together with compute node on the same server for demo or test purpose. In this case compute node with Virtuozzo Containers supported will be deployed. You can add another compute node with containers or VMs anytime you want as described in Devstack Multi-node Installation section.<br /> <br /> Please note that OpenStack now does not support containers and virtual machines on the same node.<br /> <br /> Clone virtuozzo scripts:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:4--&gt;<br /> Run the script and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh YOUR_HOST_IP YOUR_PASSWORD<br /> <br /> == Devstack multi node installation == &lt;!--T:11--&gt;<br /> <br /> &lt;!--T:12--&gt;<br /> Clone virtuozzo scripts on your CONTROLLER node:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:13--&gt;<br /> Run the script on your CONTROLLER node and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh YOUR_HOST_IP YOUR_PASSWORD CONTROLLER<br /> <br /> &lt;!--T:14--&gt;<br /> Clone virtuozzo scripts on your COMPUTE node:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:15--&gt;<br /> Run the script on your COMPUTE node and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh YOUR_COMPUTE_HOST_IP YOUR_PASSWORD COMPUTE YOUR_CONTROLLER_HOST_IP<br /> <br /> == How to redeploy OpenStack on the same nodes ==<br /> <br /> Your OpenStack setup will be reset after node restart. To redeploy OpenStack on the same nodes do the following:<br /> # &lt;code&gt;cd /vz/virtuozzo-openstack-scripts&lt;/code&gt;<br /> # &lt;code&gt;git pull&lt;/code&gt;<br /> # Run ./setup_devstack_vz7.sh with options you need.<br /> <br /> == Install and configure a nova controller node on [[Virtuozzo]] 7 == &lt;!--T:18--&gt;<br /> <br /> &lt;!--T:19--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-controller-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> <br /> * Change disk_formats string in /etc/glance/glance-api.conf so that it contains 'ploop'. Like this:<br /> <br /> disk_formats = ami,ari,aki,vhd,vmdk,raw,qcow2,vdi,iso,ploop<br /> <br /> * Restart glance-api service:<br /> <br /> systemctl restart openstack-glance-api.service<br /> <br /> * Download the container [http://updates.pvs.parallels.com/server/virtuozzo/en_us/odin/7/techpreview-ct/centos7-exe.hds.tar.gz image]<br /> * Unpack it<br /> <br /> $ tar -xzvf centos7-exe.hds.tar.gz<br /> <br /> * Upload the image to glance:<br /> NOTE: this image was created for testing purposes only. Don't use it in production as is!<br /> <br /> glance image-create --name centos7-exe --disk-format ploop --container-format bare --property vm_mode=exe --file centos7-exe.hds<br /> <br /> * Restart nova services:<br /> <br /> systemctl restart openstack-nova-api.service \<br /> openstack-nova-cert.service openstack-nova-consoleauth.service \<br /> openstack-nova-scheduler.service openstack-nova-conductor.service \<br /> openstack-nova-novncproxy.service<br /> <br /> == Install and configure a compute node on [[Virtuozzo]] 7 == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-compute-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> force_raw_images = False<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> connection_uri = parallels+unix:///system<br /> inject_partition = -2<br /> <br /> * Then restart nova-compute service:<br /> <br /> systemctl restart openstack-nova-compute.service<br /> <br /> == See also == &lt;!--T:100--&gt;<br /> * [http://docs.openstack.org/liberty/install-guide-rdo/environment-packages.html OpenStack installation guide]<br /> * [https://docs.openvz.org/ Virtuozzo documentation]<br /> * [[Virtuozzo ecosystem]]<br /> <br /> &lt;/translate&gt;<br /> <br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Setup_OpenStack_with_Virtuozzo_7&diff=19598 2016-05-25T23:36:19Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> This article describes how to install OpenStack on [[Virtuozzo]] 7.<br /> == Prerequisites ==<br /> <br /> IP connection tracking should be enabled for CT0. Please do the following:<br /> #Open the file /etc/modprobe.d/parallels.conf<br /> #Change the line &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=1&lt;/code&gt; to &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=0&lt;/code&gt;<br /> #Reboot the system<br /> <br /> Git must be installed on your Virtuozzo node:<br /> yum install git<br /> <br /> == Devstack all-in-one installation == &lt;!--T:1--&gt;<br /> <br /> &lt;!--T:3--&gt;<br /> Clone virtuozzo scripts:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:4--&gt;<br /> Run the script and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh HOST_IP PASSWORD<br /> <br /> == Devstack multi node installation == &lt;!--T:11--&gt;<br /> <br /> &lt;!--T:12--&gt;<br /> Clone virtuozzo scripts on your CONTROLLER node:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:13--&gt;<br /> Run the script on your CONTROLLER node and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh HOST_IP PASSWORD true<br /> <br /> &lt;!--T:14--&gt;<br /> Clone virtuozzo scripts on your COMPUTE node:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:15--&gt;<br /> Run the script on your COMPUTE node and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7_compute.sh COMPUTE_HOST_IP PASSWORD CONTROLLER_HOST_IP<br /> <br /> == How to redeploy OpenStack on the same nodes ==<br /> <br /> Your OpenStack setup will be reset after node restart. To redeploy OpenStack on the same nodes do the following:<br /> # &lt;code&gt;cd /vz/virtuozzo-openstack-scripts&lt;/code&gt;<br /> # &lt;code&gt;git pull&lt;/code&gt;<br /> # Run ./setup_devstack_vz7.sh with options you need.<br /> <br /> == Install and configure a nova controller node on [[Virtuozzo]] 7 == &lt;!--T:18--&gt;<br /> <br /> &lt;!--T:19--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-controller-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> <br /> * Change disk_formats string in /etc/glance/glance-api.conf so that it contains 'ploop'. Like this:<br /> <br /> disk_formats = ami,ari,aki,vhd,vmdk,raw,qcow2,vdi,iso,ploop<br /> <br /> * Restart glance-api service:<br /> <br /> systemctl restart openstack-glance-api.service<br /> <br /> * Download the container [http://updates.pvs.parallels.com/server/virtuozzo/en_us/odin/7/techpreview-ct/centos7-exe.hds.tar.gz image]<br /> * Unpack it<br /> <br /> $ tar -xzvf centos7-exe.hds.tar.gz<br /> <br /> * Upload the image to glance:<br /> NOTE: this image was created for testing purposes only. Don't use it in production as is!<br /> <br /> glance image-create --name centos7-exe --disk-format ploop --container-format bare --property vm_mode=exe --file centos7-exe.hds<br /> <br /> * Restart nova services:<br /> <br /> systemctl restart openstack-nova-api.service \<br /> openstack-nova-cert.service openstack-nova-consoleauth.service \<br /> openstack-nova-scheduler.service openstack-nova-conductor.service \<br /> openstack-nova-novncproxy.service<br /> <br /> == Install and configure a compute node on [[Virtuozzo]] 7 == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-compute-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> force_raw_images = False<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> connection_uri = parallels+unix:///system<br /> inject_partition = -2<br /> <br /> * Then restart nova-compute service:<br /> <br /> systemctl restart openstack-nova-compute.service<br /> <br /> == See also == &lt;!--T:100--&gt;<br /> * [http://docs.openstack.org/liberty/install-guide-rdo/environment-packages.html OpenStack installation guide]<br /> * [https://docs.openvz.org/ Virtuozzo documentation]<br /> * [[Virtuozzo ecosystem]]<br /> <br /> &lt;/translate&gt;<br /> <br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Using_Virtuozzo_in_the_Amazon_EC2&diff=19597 2016-05-25T13:40:52Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> <br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> To allow customers to familiarize themselves with improved containers technology of Virtuozzo and to maximize AWS instance utilization along with security and isolation we introduce Virtuozzo image for Amazon EC2.<br /> <br /> &lt;!--T:2--&gt;<br /> Please note that:<br /> * Virtuozzo only supports containers then deployed on Amazon EC2.<br /> * Virtuozzo 7 image is shipped for only one version: Virtuozzo 7.<br /> <br /> == Steps to provisioning == &lt;!--T:3--&gt;<br /> <br /> &lt;!--T:4--&gt;<br /> * Log into the [https://aws.amazon.com/marketplace AWS Marketplace], search for the AMI from Odin as the publisher, then click the selected product.<br /> * Check the product description to verify it suits your needs. Then click the &quot;Continue&quot; button.<br /> * You can choose the ''Manual Launch'' with EC2 console by the pressing corresponding tab, or continue with the 1-Click Launch using predefined settings (the 1-Click Launch option does not allow you to modify the default storage size and type when creating the instance: 30 GB magnetic storage. To change disk storage after deployment, see the Amazon AWS documentation -[http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-expand-volume.html Expanding the Storage Space of a Volume].<br /> <br /> === 1-Click Launch (predefined settings) === &lt;!--T:5--&gt;<br /> <br /> &lt;!--T:6--&gt;<br /> * Select the &quot;Region&quot; to deploy the instance and the EC2 Instance Type depending on your needs (Note: the price is different for different regions).<br /> * In VPC settings, select where your instance will be deployed: EC2 classic (recommended) or your personal Virtual Private Cloud. If the VPC network is selected, please make sure that your virtual network is configured to provide internet access to the instance is being deployed. The main differences between EC2-classic and VPC are described in [http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html Amazon EC2 and Amazon Virtual Private Cloud (VPC)]. Find more information about VPC in the [http://aws.amazon.com/documentation/vpc/ Amazon VPC documentation].<br /> * Select the default options or create a new Security Group based on seller settings. Pay special attention to the ports that are required for Plesk - see Knowledgebase article [http://kb.odin.com/en/391 KB391: Which ports need to be opened for all Plesk services to work with a firewall?]<br /> * Select the Key Pair to be used for connection to the instance (an existing Key Pair is required for connection to the OpenVZ instance). A Key Pair can be generated in the [https://console.aws.amazon.com/ec AWS Management Console].<br /> * Click the Launch with 1-Click button.<br /> By default, instances are deployed with small root storage (30 GB). It allows you deploy around 10 containers depends on container OS and installed packages. To deploy instances with bigger storage, use Manual Launch with EC2 console.<br /> To change the disk storage after deployment, check the Amazon AWS documentation: [http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-expand-volume.html Expanding the Storage Space of a Volume].<br /> <br /> === Manual Launch with EC2 console === &lt;!--T:7--&gt;<br /> <br /> &lt;!--T:8--&gt;<br /> Adjust additional settings such as disk space before launch.<br /> <br /> &lt;!--T:9--&gt;<br /> * Click on the Manual Launch tab.<br /> * Click the Launch with EC2 Console button in the Region the instance is to be deployed.<br /> * In the opened EC2 Console, choose an Instance Type depending on your requirements. Then, click the Next: Configure Instance Details button.<br /> * Set instance details. Here, you can select how many instances to deploy and select a Network (EC2-classic or VPC).If the VPC network is selected, please make sure that your virtual network is configured to provide internet access to the instance is being deployed. The main differences between EC2-classic and VPC are described in [http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html Amazon EC2 and Amazon Virtual Private Cloud (VPC)]. Find more information about VPC in the [http://aws.amazon.com/documentation/vpc/ Amazon VPC documentation].<br /> * Change other options if required, then click Next: Add Storage<br /> * Add storage to your instance. It is recommended that you increase your disk storage from the default values - your disk will be automatically resized when the instance is deployed. To change disk storage after deployment, check the Amazon AWS documentation: [http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-expand-volume.html Expanding the Storage Space of a Volume]. You can also add more storages to your instance and change the storage volume types to increase performance. Find more information about the storage type and pricing in the Amazon AWS documentaion: [http://aws.amazon.com/ebs/details/ Amazon EBS Product Details]. Click Next: Tag Instance<br /> * Add Tags for the instance. For example, you can define a tag with key = Name and value = openvz. Learn more about tagging your Amazon EC2 resources. Click Next: Configure Security Group<br /> * Configure the security group. A security group is a set of firewall rules that control the traffic for your instance. It is recommended that you configure the security group depending on services you are going to server, follow [[Setting_up_an_iptables_firewall|steps to setup iptables]]. Click Next: Review Instance Launch<br /> * Review your instance launch details. You can go back to edit changes for each section. Click Launch to assign a key pair to your instance and complete the launch process.<br /> * When the instance is deployed, click the Visit Your Software link. The page with your subscription will be opened.<br /> * Select [https://console.aws.amazon.com/ec2/v2/ Manage in the AWS console]. In the opened AWS Management Console, open your instances list (using the Instances link in the left menu) and select the instance.<br /> * (Recommended) After every stop/start, your instance changes the external and internal IP pair. Thus we recommend to attach special Elastic IP to the instance. In the left menu, select Elastic IPs and Allocate New Address or select any existing unassociated address to be allocated to your instance. After Elastic IP attachment, reboot the instance and perform additional actions to configure Plesk (see the Changing IP Address section). Please find more information about Elastic IP on Amazon AWS documentation: [http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html Elastic IP Addresses].<br /> * To connect your instance please use connection via SSH as ec2user with the private key of the Keys Pair you deployed the instance with. For example:<br /> <br /> # ssh -i &lt;path to private key&gt; ec2user@&lt;elastic or public IP&gt;<br /> <br /> &lt;!--T:10--&gt;<br /> * To operate with OpenVZ you need to enter sudo mode:<br /> <br /> &lt;!--T:11--&gt;<br /> # sudo -i<br /> <br /> == Configure the external IP address for the container == &lt;!--T:12--&gt;<br /> <br /> &lt;!--T:13--&gt;<br /> To access to your container through the Internet you can attach additional Private IPs and Elastic IPs to the instance and then attach every Private IP to the specific container.<br /> <br /> &lt;!--T:14--&gt;<br /> Please review this article to learn how to assign additional Elastic IPs to the instance http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/MultipleIP.html. If you need additional information on IP addressing in Amazon EC2 please see this article http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html<br /> <br /> &lt;!--T:15--&gt;<br /> Login to the Amazon EC2 Management Console.<br /> <br /> &lt;!--T:16--&gt;<br /> Assign new Private IP to your Instance:<br /> <br /> &lt;!--T:17--&gt;<br /> * Choose your instance;<br /> * Click Actions &gt; Networking &gt; Manage Private IP Addresses;<br /> * Click Assigh New IP;<br /> * Click Yes, Update.<br /> <br /> &lt;!--T:18--&gt;<br /> Assign new Elastic IP to corresponding Private IP of your instance:<br /> <br /> &lt;!--T:19--&gt;<br /> * Choose Elastic IP section in the menu;<br /> * Click Allocate New Addresses;<br /> * Choose just created Elastic IP and click Actions &gt; Associate Address;<br /> * Choose your instance;<br /> * Choose corresponding Private IP of your instance;<br /> * Click Associate.<br /> <br /> &lt;!--T:20--&gt;<br /> Connect to your OpenVZ instance via SSH.<br /> <br /> &lt;!--T:21--&gt;<br /> Create example container:<br /> <br /> &lt;!--T:22--&gt;<br /> # prlctl create 100700 --vmtype ct<br /> <br /> &lt;!--T:23--&gt;<br /> Assign Private IP and DNS server to the container:<br /> <br /> &lt;!--T:24--&gt;<br /> # prlctl set 100700 --ipadd &lt;Private IP address&gt;/24<br /> # prlctl set 100700 --nameserver 8.8.8.8<br /> <br /> &lt;!--T:25--&gt;<br /> Start the container:<br /> <br /> &lt;!--T:26--&gt;<br /> # prlctl start 100700<br /> <br /> &lt;!--T:27--&gt;<br /> Enter the container and set root password:<br /> <br /> &lt;!--T:28--&gt;<br /> # prlctl enter 100700<br /> # passwd<br /> <br /> &lt;!--T:29--&gt;<br /> Connect to the container via SSH:<br /> <br /> &lt;!--T:30--&gt;<br /> # ssh root@&lt;Elastic IP Address&gt;<br /> <br /> == Configure NAT on the instance == &lt;!--T:31--&gt;<br /> <br /> &lt;!--T:32--&gt;<br /> If you do not want to attach multiple Elastic IPs to your instance you may also to [[Using_NAT_for_container_with_private_IPs|configure internal NAT]] on your OpenVZ instance.<br /> <br /> == See also == &lt;!--T:33--&gt;<br /> <br /> &lt;!--T:34--&gt;<br /> * [http://www.slideshare.net/kentaroebisawa/quick-start-guide-using-virtuozzo-7-on-aws-ec2 Quick Start Guide using Virtuozzo 7 (β) on AWS EC2]<br /> &lt;/translate&gt;<br /> <br /> [[Category: Installation]]<br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Setup_OpenStack_with_Virtuozzo_7&diff=19580 2016-05-24T18:40:59Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> This article describes how to install OpenStack on [[Virtuozzo]] 7.<br /> == Prerequisites ==<br /> <br /> IP connection tracking should be enabled for CT0. Please do the following:<br /> #Open the file /etc/modprobe.d/parallels.conf<br /> #Change the line &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=1&lt;/code&gt; to &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=0&lt;/code&gt;<br /> #Reboot the system<br /> <br /> == Devstack all-in-one installation == &lt;!--T:1--&gt;<br /> <br /> &lt;!--T:3--&gt;<br /> Clone virtuozzo scripts:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:4--&gt;<br /> Run the script and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh HOST_IP PASSWORD<br /> <br /> == Devstack multi node installation == &lt;!--T:11--&gt;<br /> <br /> &lt;!--T:12--&gt;<br /> Clone virtuozzo scripts on your CONTROLLER node:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:13--&gt;<br /> Run the script on your CONTROLLER node and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh HOST_IP PASSWORD true<br /> <br /> &lt;!--T:14--&gt;<br /> Clone virtuozzo scripts on your COMPUTE node:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:15--&gt;<br /> Run the script on your COMPUTE node and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7_compute.sh COMPUTE_HOST_IP PASSWORD CONTROLLER_HOST_IP<br /> <br /> == How to redeploy OpenStack on the same nodes ==<br /> <br /> Your OpenStack setup will be reset after node restart. To redeploy OpenStack on the same nodes do the following:<br /> # &lt;code&gt;cd /vz/virtuozzo-openstack-scripts&lt;/code&gt;<br /> # &lt;code&gt;git pull&lt;/code&gt;<br /> # Run ./setup_devstack_vz7.sh with options you need.<br /> <br /> == Install and configure a nova controller node on [[Virtuozzo]] 7 == &lt;!--T:18--&gt;<br /> <br /> &lt;!--T:19--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-controller-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> <br /> * Change disk_formats string in /etc/glance/glance-api.conf so that it contains 'ploop'. Like this:<br /> <br /> disk_formats = ami,ari,aki,vhd,vmdk,raw,qcow2,vdi,iso,ploop<br /> <br /> * Restart glance-api service:<br /> <br /> systemctl restart openstack-glance-api.service<br /> <br /> * Download the container [http://updates.pvs.parallels.com/server/virtuozzo/en_us/odin/7/techpreview-ct/centos7-exe.hds.tar.gz image]<br /> * Unpack it<br /> <br /> $ tar -xzvf centos7-exe.hds.tar.gz<br /> <br /> * Upload the image to glance:<br /> NOTE: this image was created for testing purposes only. Don't use it in production as is!<br /> <br /> glance image-create --name centos7-exe --disk-format ploop --container-format bare --property vm_mode=exe --file centos7-exe.hds<br /> <br /> * Restart nova services:<br /> <br /> systemctl restart openstack-nova-api.service \<br /> openstack-nova-cert.service openstack-nova-consoleauth.service \<br /> openstack-nova-scheduler.service openstack-nova-conductor.service \<br /> openstack-nova-novncproxy.service<br /> <br /> == Install and configure a compute node on [[Virtuozzo]] 7 == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-compute-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> force_raw_images = False<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> connection_uri = parallels+unix:///system<br /> inject_partition = -2<br /> <br /> * Then restart nova-compute service:<br /> <br /> systemctl restart openstack-nova-compute.service<br /> <br /> == See also == &lt;!--T:100--&gt;<br /> * [http://docs.openstack.org/liberty/install-guide-rdo/environment-packages.html OpenStack installation guide]<br /> * [https://docs.openvz.org/ Virtuozzo documentation]<br /> * [[Virtuozzo ecosystem]]<br /> <br /> &lt;/translate&gt;<br /> <br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Setup_OpenStack_with_Virtuozzo_7&diff=19579 2016-05-24T18:30:06Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> This article describes how to install OpenStack on [[Virtuozzo]] 7.<br /> == Prerequisites ==<br /> <br /> IP connection tracking should be enabled for CT0. Please do the following:<br /> #Open the file /etc/modprobe.d/parallels.conf<br /> #Change the line &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=1&lt;/code&gt; to &lt;code&gt;options nf_conntrack ip_conntrack_disable_ve0=0&lt;/code&gt;<br /> #Reboot the system<br /> <br /> == Devstack all-in-one installation == &lt;!--T:1--&gt;<br /> <br /> &lt;!--T:3--&gt;<br /> Clone virtuozzo scripts:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:4--&gt;<br /> Run the script and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh HOST_IP PASSWORD<br /> <br /> == Devstack multi node installation == &lt;!--T:11--&gt;<br /> <br /> &lt;!--T:12--&gt;<br /> Clone virtuozzo scripts on your CONTROLLER node:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:13--&gt;<br /> Run the script on your CONTROLLER node and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7.sh HOST_IP PASSWORD true<br /> <br /> &lt;!--T:14--&gt;<br /> Clone virtuozzo scripts on your COMPUTE node:<br /> <br /> $ cd /vz<br /> $ git clone https://github.com/virtuozzo/virtuozzo-openstack-scripts<br /> $ cd virtuozzo-openstack-scripts<br /> <br /> &lt;!--T:15--&gt;<br /> Run the script on your COMPUTE node and follow instructions (if any):<br /> <br /> $ ./setup_devstack_vz7_compute.sh COMPUTE_HOST_IP PASSWORD CONTROLLER_HOST_IP<br /> <br /> == Install and configure a nova controller node on [[Virtuozzo]] 7 == &lt;!--T:18--&gt;<br /> <br /> &lt;!--T:19--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-controller-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> <br /> * Change disk_formats string in /etc/glance/glance-api.conf so that it contains 'ploop'. Like this:<br /> <br /> disk_formats = ami,ari,aki,vhd,vmdk,raw,qcow2,vdi,iso,ploop<br /> <br /> * Restart glance-api service:<br /> <br /> systemctl restart openstack-glance-api.service<br /> <br /> * Download the container [http://updates.pvs.parallels.com/server/virtuozzo/en_us/odin/7/techpreview-ct/centos7-exe.hds.tar.gz image]<br /> * Unpack it<br /> <br /> $ tar -xzvf centos7-exe.hds.tar.gz<br /> <br /> * Upload the image to glance:<br /> NOTE: this image was created for testing purposes only. Don't use it in production as is!<br /> <br /> glance image-create --name centos7-exe --disk-format ploop --container-format bare --property vm_mode=exe --file centos7-exe.hds<br /> <br /> * Restart nova services:<br /> <br /> systemctl restart openstack-nova-api.service \<br /> openstack-nova-cert.service openstack-nova-consoleauth.service \<br /> openstack-nova-scheduler.service openstack-nova-conductor.service \<br /> openstack-nova-novncproxy.service<br /> <br /> == Install and configure a compute node on [[Virtuozzo]] 7 == &lt;!--T:16--&gt;<br /> <br /> &lt;!--T:17--&gt;<br /> * Follow instructions on [http://docs.openstack.org/liberty/install-guide-rdo/nova-compute-install.html OpenStack.org]<br /> * In addition to above instructions change /etc/nova/nova.conf:<br /> <br /> [DEFAULT]<br /> ...<br /> vnc_keymap =<br /> force_raw_images = False<br /> <br /> [libvirt]<br /> ...<br /> virt_type = parallels<br /> images_type = ploop<br /> connection_uri = parallels+unix:///system<br /> inject_partition = -2<br /> <br /> * Then restart nova-compute service:<br /> <br /> systemctl restart openstack-nova-compute.service<br /> <br /> == See also == &lt;!--T:100--&gt;<br /> * [http://docs.openstack.org/liberty/install-guide-rdo/environment-packages.html OpenStack installation guide]<br /> * [https://docs.openvz.org/ Virtuozzo documentation]<br /> * [[Virtuozzo ecosystem]]<br /> <br /> &lt;/translate&gt;<br /> <br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Quick_installation&diff=19496 2016-04-29T10:49:56Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> <br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> {{Note|See [[Quick installation]] if you are looking to install the current stable version of OpenVZ.}}<br /> <br /> &lt;!--T:2--&gt;<br /> This document briefly describes the steps needed to install Virtuozzo Linux distribution on your machine.<br /> <br /> &lt;!--T:3--&gt;<br /> There are a few ways to install Virtuozzo:<br /> <br /> === Bare-metal installation === &lt;!--T:4--&gt;<br /> <br /> &lt;!--T:5--&gt;<br /> OpenVZ project builds its own Linux distribution with both hypervisor and container virtualization.<br /> It is based on our own Linux distribution, with the additions of [[Download/kernel/rhel7-testing|our custom kernel]], OpenVZ management utilities, [[QEMU]] and Virtuozzo installer. It is highly recommended to use OpenVZ containers and virtual machines with this Virtuozzo installation image. See [[Virtuozzo]].<br /> [https://download.openvz.org/virtuozzo/releases/7.0-beta3/x86_64/iso/ Download] installation ISO image.<br /> <br /> === Using Virtuozzo in the Vagrant box === &lt;!--T:6--&gt;<br /> <br /> &lt;!--T:7--&gt;<br /> [https://www.vagrantup.com/ Vagrant] is a tool for creating reproducible and portable development environments.<br /> It is easy to run environment with Virtuozzo using Vagrant:<br /> <br /> &lt;!--T:8--&gt;<br /> * Download and [https://docs.vagrantup.com/v2/installation/ install Vagrant]<br /> * Download and install [https://www.virtualbox.org/wiki/Downloads Virtualbox], Parallels Desktop, VMware Fusion or VMware Workstation. Please note that you need to enable nested virtualization support in your hypervisor to run virtual machines on Virtuozzo 7. VirtualBox does not officially support nested virtualization now.<br /> * Download [https://atlas.hashicorp.com/OpenVZ/boxes/Virtuozzo-7.0 Virtuozzo box]:<br /> <br /> &lt;!--T:9--&gt;<br /> $ vagrant init OpenVZ/Virtuozzo-7.0<br /> <br /> &lt;!--T:10--&gt;<br /> * Run box:<br /> <br /> &lt;!--T:11--&gt;<br /> $ vagrant up --provider virtualbox<br /> <br /> &lt;!--T:12--&gt;<br /> and in case of VMware hypervisor:<br /> <br /> &lt;!--T:13--&gt;<br /> $ vagrant up --provider vmware_desktop<br /> <br /> &lt;!--T:14--&gt;<br /> and in case of Parallels hypervisor:<br /> <br /> &lt;!--T:15--&gt;<br /> $ vagrant up --provider parallels<br /> <br /> &lt;!--T:16--&gt;<br /> * Attach to console:<br /> <br /> &lt;!--T:17--&gt;<br /> $ vagrant ssh<br /> <br /> &lt;!--T:18--&gt;<br /> * Use ''vagrant/vagrant'' to login inside box<br /> <br /> === Using Virtuozzo in the Amazon EC2 === &lt;!--T:19--&gt;<br /> <br /> &lt;!--T:20--&gt;<br /> Follow steps in [[Using Virtuozzo in the Amazon EC2]].<br /> <br /> === Setup on pre-installed Linux distribution === &lt;!--T:21--&gt;<br /> <br /> &lt;!--T:22--&gt;<br /> {{Note|Pay attention, this installation method currently blocked by broken network after installation - {{OVZ|6454}}.}}<br /> <br /> &lt;!--T:23--&gt;<br /> Alternatively, one can install OpenVZ on a pre-installed RPM based Linux distribution.<br /> Supported Linux distributions: Cloud Linux 7.*, CentOS 7.*, Scientific Linux 7.* etc<br /> <br /> &lt;!--T:24--&gt;<br /> Follow step-by-step instruction below:<br /> <br /> &lt;!--T:25--&gt;<br /> Package ''virtuozzo-release'' will bring meta information and YUM repositories:<br /> <br /> &lt;!--T:26--&gt;<br /> # yum localinstall http://download.openvz.org/virtuozzo/releases/7.0/x86_64/os/Packages/v/virtuozzo-release-7.0.0-10.vz7.x86_64.rpm<br /> <br /> &lt;!--T:27--&gt;<br /> EPEL is a requisite:<br /> <br /> &lt;!--T:28--&gt;<br /> # yum install -y epel-release<br /> <br /> &lt;!--T:29--&gt;<br /> Then install mandatory Virtuozzo RPM packages:<br /> <br /> &lt;!--T:30--&gt;<br /> # yum install -y prlctl prl-disp-service vzkernel<br /> <br /> &lt;!--T:31--&gt;<br /> See OpenVZ [[Packages]] available in various Linux distributions.<br /> <br /> === OpenVZ with upstream Linux kernel === &lt;!--T:32--&gt;<br /> <br /> &lt;!--T:33--&gt;<br /> See article [[OpenVZ with upstream kernel]] if you want more details about support of upstream kernel.<br /> <br /> <br /> == Using Virtuozzo == &lt;!--T:34--&gt;<br /> <br /> &lt;!--T:35--&gt;<br /> Page with [[screencasts]] shows demo with a few Virtuozzo commands. Feel free to add more.<br /> <br /> == See also == &lt;!--T:36--&gt;<br /> <br /> &lt;!--T:37--&gt;<br /> * [https://docs.openvz.org/ Official Virtuozzo documentation]<br /> &lt;/translate&gt;<br /> <br /> [[Category: Installation]]<br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Quick_installation&diff=19370 2016-03-01T16:13:36Z

<p>Vporokhov: </p> <hr /> <div>{{Virtuozzo}}<br /> <br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> {{Note|See [[Quick installation]] if you are looking to install the current stable version of OpenVZ.}}<br /> <br /> &lt;!--T:2--&gt;<br /> This document briefly describes the steps needed to install Virtuozzo Linux distribution on your machine.<br /> <br /> &lt;!--T:3--&gt;<br /> There are a few ways to install Virtuozzo:<br /> <br /> === Bare-metal installation === &lt;!--T:4--&gt;<br /> <br /> &lt;!--T:5--&gt;<br /> OpenVZ project builds its own Linux distribution with both hypervisor and container virtualization.<br /> It is based on our own Linux distribution, with the additions of [[Download/kernel/rhel7-testing|our custom kernel]], OpenVZ management utilities, [[QEMU]] and Virtuozzo installer. It is highly recommended to use OpenVZ containers and virtual machines with this Virtuozzo installation image. See [[Virtuozzo]].<br /> [https://download.openvz.org/virtuozzo/releases/7.0-beta3/x86_64/iso/ Download] installation ISO image.<br /> <br /> === Using Virtuozzo in the Vagrant box === &lt;!--T:6--&gt;<br /> <br /> &lt;!--T:7--&gt;<br /> [https://www.vagrantup.com/ Vagrant] is a tool for creating reproducible and portable development environments.<br /> It is easy to run environment with Virtuozzo using Vagrant:<br /> <br /> &lt;!--T:8--&gt;<br /> * Download and [https://docs.vagrantup.com/v2/installation/ install Vagrant]<br /> * Download and install [https://www.virtualbox.org/wiki/Downloads Virtualbox], VMware Fusion or VMware Workstation<br /> * Download [https://atlas.hashicorp.com/OpenVZ/boxes/Virtuozzo-7.0 Virtuozzo box]:<br /> <br /> &lt;!--T:9--&gt;<br /> $ vagrant init OpenVZ/Virtuozzo-7.0<br /> <br /> &lt;!--T:10--&gt;<br /> * Run box:<br /> <br /> &lt;!--T:11--&gt;<br /> $ vagrant up --provider virtualbox<br /> <br /> &lt;!--T:12--&gt;<br /> and in case of VMware hypervisor:<br /> <br /> &lt;!--T:13--&gt;<br /> $ vagrant up --provider vmware_desktop<br /> <br /> &lt;!--T:14--&gt;<br /> and in case of Parallels hypervisor:<br /> <br /> &lt;!--T:15--&gt;<br /> $ vagrant up --provider parallels<br /> <br /> &lt;!--T:16--&gt;<br /> * Attach to console:<br /> <br /> &lt;!--T:17--&gt;<br /> $ vagrant ssh<br /> <br /> &lt;!--T:18--&gt;<br /> * Use ''vagrant/vagrant'' to login inside box<br /> <br /> === Using Virtuozzo in the Amazon EC2 === &lt;!--T:19--&gt;<br /> <br /> &lt;!--T:20--&gt;<br /> Follow steps in [[Using Virtuozzo in the Amazon EC2]].<br /> <br /> === Setup on pre-installed Linux distribution === &lt;!--T:21--&gt;<br /> <br /> &lt;!--T:22--&gt;<br /> {{Note|Pay attention, this installation method currently blocked by broken network after installation - {{OVZ|6454}}.}}<br /> <br /> &lt;!--T:23--&gt;<br /> Alternatively, one can install OpenVZ on a pre-installed RPM based Linux distribution.<br /> Supported Linux distributions: Cloud Linux 7.*, CentOS 7.*, Scientific Linux 7.* etc<br /> <br /> &lt;!--T:24--&gt;<br /> Follow step-by-step instruction below:<br /> <br /> &lt;!--T:25--&gt;<br /> Package ''virtuozzo-release'' will bring meta information and YUM repositories:<br /> <br /> &lt;!--T:26--&gt;<br /> # yum localinstall http://download.openvz.org/virtuozzo/releases/7.0/x86_64/os/Packages/v/virtuozzo-release-7.0.0-10.vz7.x86_64.rpm<br /> <br /> &lt;!--T:27--&gt;<br /> EPEL is a requisite:<br /> <br /> &lt;!--T:28--&gt;<br /> # yum install -y epel-release<br /> <br /> &lt;!--T:29--&gt;<br /> Then install mandatory Virtuozzo RPM packages:<br /> <br /> &lt;!--T:30--&gt;<br /> # yum install -y prlctl prl-disp-service vzkernel<br /> <br /> &lt;!--T:31--&gt;<br /> See OpenVZ [[Packages]] available in various Linux distributions.<br /> <br /> === OpenVZ with upstream Linux kernel === &lt;!--T:32--&gt;<br /> <br /> &lt;!--T:33--&gt;<br /> See article [[OpenVZ with upstream kernel]] if you want more details about support of upstream kernel.<br /> <br /> <br /> == Using Virtuozzo == &lt;!--T:34--&gt;<br /> <br /> &lt;!--T:35--&gt;<br /> Page with [[screencasts]] shows demo with a few Virtuozzo commands. Feel free to add more.<br /> <br /> == See also == &lt;!--T:36--&gt;<br /> <br /> &lt;!--T:37--&gt;<br /> * [https://docs.openvz.org/ Official Virtuozzo documentation]<br /> &lt;/translate&gt;<br /> <br /> [[Category: Installation]]<br /> [[Category: HOWTO]]</div>

Vporokhov https://wiki.openvz.org/index.php?title=Comparison&diff=17751 2015-09-28T11:48:52Z

<p>Vporokhov: </p> <hr /> <div>== Disclaimer ==<br /> <br /> The information regarding [[Virtuozzo]] 7 are provided by Odin. Here is the Odin's statement regarding this information:<br /> <br /> :#The information contained herein is intended to outline general product direction and should not be relied upon in making purchasing decisions.<br /> :#The content is for informational purposes only and may not be incorporated into any contract.<br /> :#The information presented is not a commitment, promise, or legal obligation to deliver any material, code or functionality.<br /> :#Any references to the development, release, and timing of any features or functionality described for these products remains at Odin’s sole discretion.<br /> :#Product capabilities, timeframes and features are subject to change and should not be viewed as Odin commitments.<br /> <br /> The information regarding all other solutions are taken by authors from public sources only. This information can be changed by any OpenVZ Wiki user without any notice and author's review or approval.<br /> <br /> <br /> == Feature comparison of different virtualization solutions ==<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> ! Feature<br /> ! Description<br /> ! OpenVZ (stable)<br /> ! Virtuozzo&amp;nbsp;6 (PCS 6)<br /> ! Virtuozzo&amp;nbsp;7<br /> ! Virtuozzo&amp;nbsp;7 Plus<br /> ! LXC<br /> ! Proxmox VE<br /> ! Microsoft Hyper-V 2012 R2<br /> ! RHEV 3.5<br /> ! Citrix XenServer 6.5<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|1. Virtualization platform<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.1. Overview<br /> |-<br /> |'''HW virtualization support (Hypervisor)'''<br /> |Full emulation of underneath hardware level: full isolation guest environment, no dependencies from host OS, overhead for hypervisor layer.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''OS-level virtualization (Containers)'''<br /> |Sharing the same instance of host OS: high density, high performance, high dependencies from host OS.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Hypervisor technology'''<br /> |Technology that enables to run Virtual Machines.<br /> |None<br /> |Parallels Desktop Monitor<br /> |KVM<br /> |KVM<br /> |None<br /> |KVM<br /> |Hyper-V<br /> |KVM<br /> |Xen<br /> |-<br /> |'''Containers technology'''<br /> |Technology that enables to run Containers.<br /> |Virtuozzo Containers<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Linux containers<br /> |LXC (moved from OpenVZ since 4.0)<br /> |None<br /> |None<br /> |None<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.2. Memory<br /> |-<br /> |'''Memory Overcommit'''<br /> |Ability to present more memory to virtual machines than physically available <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Page sharing'''<br /> |Memory (RAM) savings through sharing identical memory pages across virtual machines<br /> |{{Yes}}<br /> |{{Yes}}, only for CTs<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|2. Management<br /> |-<br /> !colspan=&quot;11&quot;|2.1. General<br /> |-<br /> |'''Unified management tool for CTs and VMs'''<br /> |Single tool for managing both containers and virtual machines (if applicable)<br /> |None<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |None<br /> |{{No}}<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Central Management tool'''<br /> |Is centralized multi-server management available for this edition?<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}, Parallels Virtual Automation (PVA)<br /> |{{No}}<br /> |{{Yes}}, PVA<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}<br /> |{{Yes}}, System Center Virtual Machine Manager<br /> |{{Yes}}, RHEV Manager<br /> |{{Yes}}, XenCenter<br /> |-<br /> !colspan=&quot;11&quot;|2.2. Upgrade &amp; Backup<br /> |-<br /> |'''Update Management'''<br /> |Integrated patching mechanism for the virtual environments (Guest OS) / guest tools / templates<br /> |No integrated update, YUM (Linux)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, APT (Linux)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |Yes (WSUS, SCCM, Virtual Machine Servicing Tool 2012 for offline VM update)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |-<br /> |'''Live VE snapshot'''<br /> |Ability to take a snapshot of a virtual environment while the guest OS is running (e.g. for roll-back or backup purposes)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |Offline, CRIU support is planned<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated Backup'''<br /> |Are backup plugins/tools provided to backup virtual environments (over and above the ability to perform classic backup using agents in the guests)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Backup Integration API'''<br /> |Integration with 3rd party backup applications for backup of the virtual environment.<br /> |{{No}} (only through snapshots)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}} (only through snapshots)<br /> |{{Yes}} (vzdump)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot;|2.3. Others<br /> |-<br /> |'''VEs Templates (VM, CT)'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |{{Yes}} (CT only)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}} (OpenVZ templates)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''P2V migration'''<br /> |Integrated or added P2V (or V2V) capability in order to convert physical systems to virtual environment.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}, 3rd party tools<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|3. VE Mobility and HA<br /> |-<br /> !colspan=&quot;11&quot;|3.1. VE Mobility<br /> |-<br /> |'''Live Migration'''<br /> |Ability to migrate virtual machines between hosts without perceived downtime<br /> |{{Yes}}, but with no zero downtime<br /> |{{Yes}}, Kernal-Level Migration<br /> |{{Yes}}, CRIU<br /> |{{Yes}}, CRIU<br /> |Offline, CRIU support is planned<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''DRS/Host Maintenance Mode'''<br /> |Ability to put host into maintenance mode which will automatically live migrate all VEs onto other available hosts so that the host can be brought shut down safely<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Distributed Power Management'''<br /> |Distributed Power Management features Ability to automatically migrate VEs onto fewer hosts and power off unused capacity (hosts), wake systems back up when required <br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|3.2. HA / DR<br /> |-<br /> |'''Cluster size'''<br /> |Maximum number of hosts in the cluster/pool relationship and maximum number VEs per cluster/pool (if specified)<br /> |None<br /> |32 hosts/cluster validated (100 hosts/cluster maximum) - PStorage limitation<br /> |Not tested yet<br /> |Not tested yet<br /> |None<br /> |32 nodes<br /> |64 nodes<br /> |200 nodes<br /> |16 nodes<br /> |-<br /> |'''Integrated HA'''<br /> |Recover virtual environment in case of host failures through restart on alternative hosts (downtime = restart time)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Site Failover'''<br /> |Integrated ability to (ideally live) migrate virtual machine data (virtual disk files) to different storage e.g. for array upgrades/migration and I/O management<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |Manual<br /> |{{No}}<br /> |Integrated Disaster Recovery - manual<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|4. Network and Storage<br /> |-<br /> !colspan=&quot;11&quot;|4.1. Storage<br /> |-<br /> |'''Supported Storage'''<br /> |Supported types of Storage (DAS, NAS or SAN)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |SAN, NAS (NFS, ZFS), Ceph <br /> |DAS, NAS (SMB), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |-<br /> |'''Virtual Disk Format'''<br /> |Supported format(s) of the virtual disks for the virtual machines<br /> |CT - ploop<br /> |CT - ploop, VM - ploop<br /> |CT - ploop, VM - ploop\Qcow2<br /> |CT - ploop, VM - ploop\Qcow2<br /> |Any<br /> |qcow2, vmdk, raw<br /> |vhdx, vhd, pass-though (raw)<br /> |Qcow2, raw disk<br /> |vhd, raw disk<br /> |-<br /> |'''Thin Disk Provisioning'''<br /> |Ability to over-commit overall disk space by dynamically growing the size of virtual disks based on actual usage rather than pre-allocating full size.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, depends on disk format (dm-thin)<br /> |{{Yes}} (depends on underlying storage driver)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Virtual SAN'''<br /> |Enhanced storage capability e.g. providing a virtual SAN through virtualized 'local' storage <br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{No}}<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, Storage Spaces<br /> |{{Yes}}, Red Hat Storage<br /> |{{No}}<br /> |-<br /> |'''Storage QoS'''<br /> |Ability to control Quality of Service for Storage I/O or Throughput for CT/VM<br /> |{{Yes}}<br /> |{{Yes}}<br /> |TBD<br /> |{{Yes}}<br /> |{{No}}<br /> |{{VMs only}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|4.2. Network<br /> |-<br /> |'''Advanced Network Switch'''<br /> |Centralized virtual network configuration (rather than managing virtual switches on individual hosts), typically with enhanced networking capabilities<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}, Open vSwitch support<br /> |{{Yes}}<br /> |OpenStack Neutron Integration<br /> |Open vSwitch integration<br /> |-<br /> |'''Network QoS'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |{{Yes}}, with Open vSwitch <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|5. Others – most of features are relevant only for Odin Virtuozzo editions<br /> |-<br /> |'''Memory deduplication for binary files'''<br /> |Memory and IOPS deduplication management that enables/disables caching for Container directories and files, verifies cache integrity, checks Containers for cache errors, and purges the cache if needed<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{Yes}}, pfcache<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{No}}<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Completely isolated disk subsystem for CTs'''<br /> |<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, with LVM<br /> |{{No}}<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''API\SDK'''<br /> |<br /> |OpenVZ API for Ruby, LibVirt<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |LibLXC, API for Ruby, Python 2, Haskell, Go<br /> |Proxmox VE uses a REST like API (JSON data format)<br /> |Windows SDK<br /> |RHEV-M API: REST API, SDKs<br /> |XenAPI, XenServer SDKs<br /> |-<br /> |'''Image Catalog integration'''<br /> |Integration with 3rd-party image catalog services of popular server applications and development environments that can be installed with one click.<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}} (Bitnami)<br /> |{{No}}<br /> |{{Yes}} (Turnkey)<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Open Stack integration'''<br /> |Driver for Open Stack Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |(LXC and KVM supported through libvirt)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Kernel maintenance'''<br /> |Ability to upgrade kernel with minimal downtime.<br /> |KernelCare service integration<br /> |kernel rebootless update (vzreboot)<br /> |KernelCare service integration<br /> |kernel rebootless update (vzreboot)<br /> |KernelCare service integration<br /> |KernelCare service integration<br /> |None<br /> |KernelCare service integration<br /> |KernelCare service integration<br /> |-<br /> |'''Power Panel'''<br /> |A tool used for managing particular virtual machines and containers by their end users.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |None<br /> |None<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|6. Commercial<br /> |-<br /> |'''Open Source'''<br /> |<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}} (but there is Open Source edition)<br /> |-<br /> |'''License\Subscription'''<br /> |<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, Enterprise Edition<br /> |-<br /> |'''Support'''<br /> |<br /> |Both community and commercial support<br /> |Commercial support<br /> |Community support<br /> |Commercial Support<br /> |Yes, Canonical Ltd.<br /> |Both community and commercial support<br /> |Commercial support<br /> |Commercial support<br /> |Both community and commercial support<br /> |-<br /> |}</div>

Vporokhov https://wiki.openvz.org/index.php?title=Comparison&diff=17750 2015-09-28T11:47:05Z

<p>Vporokhov: </p> <hr /> <div>== Disclaimer ==<br /> <br /> The information regarding [[Virtuozzo]] 7 are provided by Odin. Here is the Odin's statement regarding this information:<br /> <br /> :#The information contained herein is intended to outline general product direction and should not be relied upon in making purchasing decisions.<br /> :#The content is for informational purposes only and may not be incorporated into any contract.<br /> :#The information presented is not a commitment, promise, or legal obligation to deliver any material, code or functionality.<br /> :#Any references to the development, release, and timing of any features or functionality described for these products remains at Odin’s sole discretion.<br /> :#Product capabilities, timeframes and features are subject to change and should not be viewed as Odin commitments.<br /> <br /> The information regarding all other solutions are taken by authors from public sources only. This information can be changed by any OpenVZ Wiki user without any notice and author's review or approval.<br /> <br /> <br /> == Feature comparison of different virtualization solutions ==<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> ! Feature<br /> ! Description<br /> ! OpenVZ (stable)<br /> ! Virtuozzo&amp;nbsp;6 (PCS 6)<br /> ! Virtuozzo&amp;nbsp;7<br /> ! Virtuozzo&amp;nbsp;7 Plus<br /> ! LXC<br /> ! Proxmox VE<br /> ! Microsoft Hyper-V 2012 R2<br /> ! RHEV 3.5<br /> ! Citrix XenServer 6.5<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|1. Virtualization platform<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.1. Overview<br /> |-<br /> |'''HW virtualization support (Hypervisor)'''<br /> |Full emulation of underneath hardware level: full isolation guest environment, no dependencies from host OS, overhead for hypervisor layer.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''OS-level virtualization (Containers)'''<br /> |Sharing the same instance of host OS: high density, high performance, high dependencies from host OS.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Hypervisor technology'''<br /> |Technology that enables to run Virtual Machines.<br /> |None<br /> |Parallels Desktop Monitor<br /> |KVM<br /> |KVM<br /> |None<br /> |KVM<br /> |Hyper-V<br /> |KVM<br /> |Xen<br /> |-<br /> |'''Containers technology'''<br /> |Technology that enables to run Containers.<br /> |Virtuozzo Containers<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Linux containers<br /> |LXC (moved from OpenVZ since 4.0)<br /> |None<br /> |None<br /> |None<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.2. Memory<br /> |-<br /> |'''Memory Overcommit'''<br /> |Ability to present more memory to virtual machines than physically available <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Page sharing'''<br /> |Memory (RAM) savings through sharing identical memory pages across virtual machines<br /> |{{Yes}}<br /> |{{Yes}}, only for CTs<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|2. Management<br /> |-<br /> !colspan=&quot;11&quot;|2.1. General<br /> |-<br /> |'''Unified management tool for CTs and VMs'''<br /> |Single tool for managing both containers and virtual machines (if applicable)<br /> |None<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |None<br /> |{{No}}<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Central Management tool'''<br /> |Is centralized multi-server management available for this edition?<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}, Parallels Virtual Automation (PVA)<br /> |{{No}}<br /> |{{Yes}}, PVA<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}<br /> |{{Yes}}, System Center Virtual Machine Manager<br /> |{{Yes}}, RHEV Manager<br /> |{{Yes}}, XenCenter<br /> |-<br /> !colspan=&quot;11&quot;|2.2. Upgrade &amp; Backup<br /> |-<br /> |'''Update Management'''<br /> |Integrated patching mechanism for the virtual environments (Guest OS) / guest tools / templates<br /> |No integrated update, YUM (Linux)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, APT (Linux)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |Yes (WSUS, SCCM, Virtual Machine Servicing Tool 2012 for offline VM update)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |-<br /> |'''Live VE snapshot'''<br /> |Ability to take a snapshot of a virtual environment while the guest OS is running (e.g. for roll-back or backup purposes)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |Offline, CRIU support is planned<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated Backup'''<br /> |Are backup plugins/tools provided to backup virtual environments (over and above the ability to perform classic backup using agents in the guests)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Backup Integration API'''<br /> |Integration with 3rd party backup applications for backup of the virtual environment.<br /> |{{No}} (only through snapshots)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}} (only through snapshots)<br /> |{{Yes}} (vzdump)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot;|2.3. Others<br /> |-<br /> |'''VEs Templates (VM, CT)'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |{{Yes}} (CT only)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}} (OpenVZ templates)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''P2V migration'''<br /> |Integrated or added P2V (or V2V) capability in order to convert physical systems to virtual environment.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}, 3rd party tools<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|3. VE Mobility and HA<br /> |-<br /> !colspan=&quot;11&quot;|3.1. VE Mobility<br /> |-<br /> |'''Live Migration'''<br /> |Ability to migrate virtual machines between hosts without perceived downtime<br /> |{{Yes}}, but with no zero downtime<br /> |{{Yes}}, Kernal-Level Migration<br /> |{{Yes}}, CRIU<br /> |{{Yes}}, CRIU<br /> |Offline, CRIU support is planned<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''DRS/Host Maintenance Mode'''<br /> |Ability to put host into maintenance mode which will automatically live migrate all VEs onto other available hosts so that the host can be brought shut down safely<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Distributed Power Management'''<br /> |Distributed Power Management features Ability to automatically migrate VEs onto fewer hosts and power off unused capacity (hosts), wake systems back up when required <br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|3.2. HA / DR<br /> |-<br /> |'''Cluster size'''<br /> |Maximum number of hosts in the cluster/pool relationship and maximum number VEs per cluster/pool (if specified)<br /> |None<br /> |32 hosts/cluster validated (100 hosts/cluster maximum) - PStorage limitation<br /> |Not tested yet<br /> |Not tested yet<br /> |None<br /> |32 nodes<br /> |64 nodes<br /> |200 nodes<br /> |16 nodes<br /> |-<br /> |'''Integrated HA'''<br /> |Recover virtual environment in case of host failures through restart on alternative hosts (downtime = restart time)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Site Failover'''<br /> |Integrated ability to (ideally live) migrate virtual machine data (virtual disk files) to different storage e.g. for array upgrades/migration and I/O management<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |Manual<br /> |{{No}}<br /> |Integrated Disaster Recovery - manual<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|4. Network and Storage<br /> |-<br /> !colspan=&quot;11&quot;|4.1. Storage<br /> |-<br /> |'''Supported Storage'''<br /> |Supported types of Storage (DAS, NAS or SAN)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |SAN, NAS (NFS, ZFS), Ceph <br /> |DAS, NAS (SMB), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |-<br /> |'''Virtual Disk Format'''<br /> |Supported format(s) of the virtual disks for the virtual machines<br /> |CT - ploop<br /> |CT - ploop, VM - ploop<br /> |CT - ploop, VM - ploop\Qcow2<br /> |CT - ploop, VM - ploop\Qcow2<br /> |Any<br /> |qcow2, vmdk, raw<br /> |vhdx, vhd, pass-though (raw)<br /> |Qcow2, raw disk<br /> |vhd, raw disk<br /> |-<br /> |'''Thin Disk Provisioning'''<br /> |Ability to over-commit overall disk space by dynamically growing the size of virtual disks based on actual usage rather than pre-allocating full size.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, depends on disk format (dm-thin)<br /> |{{Yes}} (depends on underlying storage driver)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Virtual SAN'''<br /> |Enhanced storage capability e.g. providing a virtual SAN through virtualized 'local' storage <br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, Storage Spaces<br /> |{{Yes}}, Red Hat Storage<br /> |{{No}}<br /> |-<br /> |'''Storage QoS'''<br /> |Ability to control Quality of Service for Storage I/O or Throughput for CT/VM<br /> |{{Yes}}<br /> |{{Yes}}<br /> |TBD<br /> |{{Yes}}<br /> |{{No}}<br /> |{{VMs only}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|4.2. Network<br /> |-<br /> |'''Advanced Network Switch'''<br /> |Centralized virtual network configuration (rather than managing virtual switches on individual hosts), typically with enhanced networking capabilities<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}, Open vSwitch support<br /> |{{Yes}}<br /> |OpenStack Neutron Integration<br /> |Open vSwitch integration<br /> |-<br /> |'''Network QoS'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |{{Yes}}, with Open vSwitch <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|5. Others – most of features are relevant only for Odin Virtuozzo editions<br /> |-<br /> |'''Memory deduplication for binary files'''<br /> |Memory and IOPS deduplication management that enables/disables caching for Container directories and files, verifies cache integrity, checks Containers for cache errors, and purges the cache if needed<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{Yes}}, pfcache<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{No}}<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Completely isolated disk subsystem for CTs'''<br /> |<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, with LVM<br /> |{{No}}<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''API\SDK'''<br /> |<br /> |OpenVZ API for Ruby, LibVirt<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |LibLXC, API for Ruby, Python 2, Haskell, Go<br /> |Proxmox VE uses a REST like API (JSON data format)<br /> |Windows SDK<br /> |RHEV-M API: REST API, SDKs<br /> |XenAPI, XenServer SDKs<br /> |-<br /> |'''Image Catalog integration'''<br /> |Integration with 3rd-party image catalog services of popular server applications and development environments that can be installed with one click.<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}} (Bitnami)<br /> |{{No}}<br /> |{{Yes}} (Turnkey)<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Open Stack integration'''<br /> |Driver for Open Stack Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |(LXC and KVM supported through libvirt)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Kernel maintenance'''<br /> |Ability to upgrade kernel with minimal downtime.<br /> |KernelCare service integration<br /> |kernel rebootless update (vzreboot)<br /> |KernelCare service integration<br /> |kernel rebootless update (vzreboot)<br /> |KernelCare service integration<br /> |KernelCare service integration<br /> |None<br /> |KernelCare service integration<br /> |KernelCare service integration<br /> |-<br /> |'''Power Panel'''<br /> |A tool used for managing particular virtual machines and containers by their end users.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |None<br /> |None<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|6. Commercial<br /> |-<br /> |'''Open Source'''<br /> |<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}} (but there is Open Source edition)<br /> |-<br /> |'''License\Subscription'''<br /> |<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, Enterprise Edition<br /> |-<br /> |'''Support'''<br /> |<br /> |Both community and commercial support<br /> |Commercial support<br /> |Community support<br /> |Commercial Support<br /> |Yes, Canonical Ltd.<br /> |Both community and commercial support<br /> |Commercial support<br /> |Commercial support<br /> |Both community and commercial support<br /> |-<br /> |}</div>

Vporokhov https://wiki.openvz.org/index.php?title=Comparison&diff=17749 2015-09-28T11:43:44Z

<p>Vporokhov: </p> <hr /> <div>== Disclaimer ==<br /> <br /> The information regarding [[Virtuozzo]] 7 are provided by Odin. Here is the Odin's statement regarding this information:<br /> <br /> :#The information contained herein is intended to outline general product direction and should not be relied upon in making purchasing decisions.<br /> :#The content is for informational purposes only and may not be incorporated into any contract.<br /> :#The information presented is not a commitment, promise, or legal obligation to deliver any material, code or functionality.<br /> :#Any references to the development, release, and timing of any features or functionality described for these products remains at Odin’s sole discretion.<br /> :#Product capabilities, timeframes and features are subject to change and should not be viewed as Odin commitments.<br /> <br /> The information regarding all other solutions are taken by authors from public sources only. This information can be changed by any OpenVZ Wiki user without any notice and author's review or approval.<br /> <br /> <br /> == Feature comparison of different virtualization solutions ==<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> ! Feature<br /> ! Description<br /> ! OpenVZ (stable)<br /> ! Virtuozzo&amp;nbsp;6 (PCS 6)<br /> ! Virtuozzo&amp;nbsp;7<br /> ! Virtuozzo&amp;nbsp;7 Plus<br /> ! LXC<br /> ! Proxmox VE<br /> ! Microsoft Hyper-V 2012 R2<br /> ! RHEV 3.5<br /> ! Citrix XenServer 6.5<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|1. Virtualization platform<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.1. Overview<br /> |-<br /> |'''HW virtualization support (Hypervisor)'''<br /> |Full emulation of underneath hardware level: full isolation guest environment, no dependencies from host OS, overhead for hypervisor layer.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''OS-level virtualization (Containers)'''<br /> |Sharing the same instance of host OS: high density, high performance, high dependencies from host OS.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Hypervisor technology'''<br /> |Technology that enables to run Virtual Machines.<br /> |None<br /> |Parallels Desktop Monitor<br /> |KVM<br /> |KVM<br /> |None<br /> |KVM<br /> |Hyper-V<br /> |KVM<br /> |Xen<br /> |-<br /> |'''Containers technology'''<br /> |Technology that enables to run Containers.<br /> |Virtuozzo Containers<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Virtuozzo Containers with enhancements<br /> |Linux containers<br /> |LXC (moved from OpenVZ since 4.0)<br /> |None<br /> |None<br /> |None<br /> |-<br /> !colspan=&quot;11&quot; align=&quot;left&quot;|1.2. Memory<br /> |-<br /> |'''Memory Overcommit'''<br /> |Ability to present more memory to virtual machines than physically available <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Page sharing'''<br /> |Memory (RAM) savings through sharing identical memory pages across virtual machines<br /> |{{Yes}}<br /> |{{Yes}}, only for CTs<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|2. Management<br /> |-<br /> !colspan=&quot;11&quot;|2.1. General<br /> |-<br /> |'''Unified management tool for CTs and VMs'''<br /> |Single tool for managing both containers and virtual machines (if applicable)<br /> |None<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |None<br /> |{{No}}<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Central Management tool'''<br /> |Is centralized multi-server management available for this edition?<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}, Parallels Virtual Automation (PVA)<br /> |{{No}}<br /> |{{Yes}}, PVA<br /> |{{Yes}}, 3rd party<br /> |{{Yes}}<br /> |{{Yes}}, System Center Virtual Machine Manager<br /> |{{Yes}}, RHEV Manager<br /> |{{Yes}}, XenCenter<br /> |-<br /> !colspan=&quot;11&quot;|2.2. Upgrade &amp; Backup<br /> |-<br /> |'''Update Management'''<br /> |Integrated patching mechanism for the virtual environments (Guest OS) / guest tools / templates<br /> |No integrated update, YUM (Linux)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, APT (Linux)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |Yes (WSUS, SCCM, Virtual Machine Servicing Tool 2012 for offline VM update)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |No integrated update, YUM (Linux), WSUS (Windows)<br /> |-<br /> |'''Live VE snapshot'''<br /> |Ability to take a snapshot of a virtual environment while the guest OS is running (e.g. for roll-back or backup purposes)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |Offline, CRIU support is planned<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Integrated Backup'''<br /> |Are backup plugins/tools provided to backup virtual environments (over and above the ability to perform classic backup using agents in the guests)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> |'''Backup Integration API'''<br /> |Integration with 3rd party backup applications for backup of the virtual environment.<br /> |{{No}} (only through snapshots)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}} (only through snapshots)<br /> |{{Yes}} (vzdump)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot;|2.3. Others<br /> |-<br /> |'''VEs Templates (VM, CT)'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |{{Yes}} (CT only)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}} (OpenVZ templates)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''P2V migration'''<br /> |Integrated or added P2V (or V2V) capability in order to convert physical systems to virtual environment.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}, 3rd party tools<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|3. VE Mobility and HA<br /> |-<br /> !colspan=&quot;11&quot;|3.1. VE Mobility<br /> |-<br /> |'''Live Migration of VEs'''<br /> |Ability to migrate virtual machines between hosts without perceived downtime<br /> |{{Yes}}, but with no zero downtime<br /> |{{Yes}}, Kernal-Level Migration<br /> |{{Yes}}, CRIU<br /> |{{Yes}}, CRIU<br /> |Offline, CRIU support is planned<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Automated Live Migration (DRS)'''<br /> |Ability to put host into maintenance mode which will automatically live migrate all virtual machines onto other available hosts so that the host can be brought shut down safely<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Storage Migration'''<br /> |Integrated Power Management features Ability to automatically migrate vms onto fewer hosts and power off unused capacity (hosts), wake systems back up when required <br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|3.2. HA / DR<br /> |-<br /> |'''Cluster size'''<br /> |Maximum number of hosts in the cluster/pool relationship and maximum number vms per cluster/pool (if specified)<br /> |None<br /> |32 hosts/cluster validated (100 hosts/cluster maximum) - PStorage limitation<br /> |Not tested yet<br /> |Not tested yet<br /> |None<br /> |32 nodes<br /> |64 nodes<br /> |200 nodes<br /> |16 nodes<br /> |-<br /> |'''Integrated HA'''<br /> |Recover virtual environment in case of host failures through restart on alternative hosts (downtime = restart time)<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Site Failover'''<br /> |Integrated ability to (ideally live) migrate virtual machine data (virtual disk files) to different storage e.g. for array upgrades/migration and I/O management<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |Manual<br /> |{{No}}<br /> |Integrated Disaster Recovery - manual<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|4. Network and Storage<br /> |-<br /> !colspan=&quot;11&quot;|4.1. Storage<br /> |-<br /> |'''Supported Storage'''<br /> |Supported types of Storage (DAS, NAS or SAN)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |NAS (NFS), DAS (EXT4)<br /> |SAN, NAS (NFS, ZFS), Ceph <br /> |DAS, NAS (SMB), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)<br /> |-<br /> |'''Virtual Disk Format'''<br /> |Supported format(s) of the virtual disks for the virtual machines<br /> |CT - ploop<br /> |CT - ploop, VM - ploop<br /> |CT - ploop, VM - ploop\Qcow2<br /> |CT - ploop, VM - ploop\Qcow2<br /> |Any<br /> |qcow2, vmdk, raw<br /> |vhdx, vhd, pass-though (raw)<br /> |Qcow2, raw disk<br /> |vhd, raw disk<br /> |-<br /> |'''Thin Disk Provisioning'''<br /> |Ability to over-commit overall disk space by dynamically growing the size of virtual disks based on actual usage rather than pre-allocating full size.<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, depends on disk format (dm-thin)<br /> |{{Yes}} (depends on underlying storage driver)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Virtual SAN'''<br /> |Enhanced storage capability e.g. providing a virtual SAN through virtualized 'local' storage <br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, Virtuozzo Storage<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, but 3rd party (DRBD 9, Ceph, GlusterFS)<br /> |{{Yes}}, Storage Spaces<br /> |{{Yes}}, Red Hat Storage<br /> |{{No}}<br /> |-<br /> |'''Storage QoS'''<br /> |Ability to control Quality of Service for Storage I/O or Throughput for CT/VM<br /> |{{Yes}}<br /> |{{Yes}}<br /> |TBD<br /> |{{Yes}}<br /> |{{No}}<br /> |{{VMs only}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot;|4.2. Network<br /> |-<br /> |'''Advanced Network Switch'''<br /> |Centralized virtual network configuration (rather than managing virtual switches on individual hosts), typically with enhanced networking capabilities<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}, Open vSwitch support<br /> |{{Yes}}<br /> |OpenStack Neutron Integration<br /> |Open vSwitch integration<br /> |-<br /> |'''Network QoS'''<br /> |Ability to create and store master images and deploy virtual machines from them<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |Only bandwidth limits<br /> |{{Yes}}, with Open vSwitch <br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|5. Others – most of features are relevant only for Odin Virtuozzo editions<br /> |-<br /> |'''Memory deduplication for binary files'''<br /> |Memory and IOPS deduplication management that enables/disables caching for Container directories and files, verifies cache integrity, checks Containers for cache errors, and purges the cache if needed<br /> |{{No}}<br /> |{{Yes}}, pfcache<br /> |{{Yes}}, pfcache<br /> |{{Yes}}, pfcache<br /> |{{No}}<br /> |{{No}}<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Completely isolated disk subsystem for CTs'''<br /> |<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, ploop<br /> |{{Yes}}, with LVM<br /> |{{No}}<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''API\SDK'''<br /> |<br /> |OpenVZ API for Ruby, LibVirt<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |Virtuozzo SDK, [[LibVirt]]<br /> |LibLXC, API for Ruby, Python 2, Haskell, Go<br /> |Proxmox VE uses a REST like API (JSON data format)<br /> |Windows SDK<br /> |RHEV-M API: REST API, SDKs<br /> |XenAPI, XenServer SDKs<br /> |-<br /> |'''Image Catalog integration'''<br /> |Integration with 3rd-party image catalog services of popular server applications and development environments that can be installed with one click.<br /> |{{No}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}} (Bitnami)<br /> |{{No}}<br /> |{{Yes}} (Turnkey)<br /> |None<br /> |None<br /> |None<br /> |-<br /> |'''Open Stack integration'''<br /> |Driver for Open Stack Nova<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |(LXC and KVM supported through libvirt)<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |-<br /> |'''Kernel maintenance'''<br /> |Ability to upgrade kernel with minimal downtime.<br /> |KernelCare service integration<br /> |kernel rebootless update (vzreboot)<br /> |KernelCare service integration<br /> |kernel rebootless update (vzreboot)<br /> |KernelCare service integration<br /> |KernelCare service integration<br /> |None<br /> |KernelCare service integration<br /> |KernelCare service integration<br /> |-<br /> |'''Power Panel'''<br /> |A tool used for managing particular virtual machines and containers by their end users.<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |None<br /> |None<br /> |None<br /> |None<br /> |None<br /> |-<br /> !colspan=&quot;11&quot; style=&quot;font-style:bold;background-color:gold;&quot;|6. Commercial<br /> |-<br /> |'''Open Source'''<br /> |<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{No}} (but there is Open Source edition)<br /> |-<br /> |'''License\Subscription'''<br /> |<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{No}}<br /> |{{No}}<br /> |{{Yes}}<br /> |{{Yes}}<br /> |{{Yes}}, Enterprise Edition<br /> |-<br /> |'''Support'''<br /> |<br /> |Both community and commercial support<br /> |Commercial support<br /> |Community support<br /> |Commercial Support<br /> |Yes, Canonical Ltd.<br /> |Both community and commercial support<br /> |Commercial support<br /> |Commercial support<br /> |Both community and commercial support<br /> |-<br /> |}</div>

Vporokhov