Editing CT storage backends

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
 
{{stub}}
 
{{stub}}
 
<translate>
 
<translate>
 
+
= Comparison tables =
= Comparison table =
 
  
 
<!--T:1-->
 
<!--T:1-->
 +
=== Solidity in front of failures and security ===
 
{| class="wikitable sortable" style="text-align: center;"
 
{| class="wikitable sortable" style="text-align: center;"
|-
 
 
! Feature
 
! Feature
 
! OVZ Ploop
 
! OVZ Ploop
Line 12: Line 11:
 
! LVM (ext4)
 
! LVM (ext4)
 
! ZFS
 
! ZFS
|-
 
!colspan="11" style="font-style:bold;background-color:gold;"|1. Solidity in front of failures and security
 
 
|-
 
|-
 
|'''I/O isolation'''
 
|'''I/O isolation'''
 
|{{Yes|Good}}
 
|{{Yes|Good}}
|{{No|Bad}}: Possibility of "no inodes" issues (when file system journal become a bottleneck).
+
|{{No|Bad}}: Some bug could be exploited to escape CT and access HN file system <ref>[https://bugs.openvz.org/browse/OVZ-6296 CVE-2015-2925]</ref> <ref>[http://www.openwall.com/lists/oss-security/2014/06/24/16 CVE-2014-3519]</ref>
 
|{{Yes|Good}}
 
|{{Yes|Good}}
 
|{{Yes|Good}}
 
|{{Yes|Good}}
|-
 
|'''Security'''
 
|{{Yes|Good}}
 
|{{No|Bad}}: Some bug could be exploited to escape CT and access HN file system <ref>[https://bugs.openvz.org/browse/OVZ-6296 CVE-2015-2925]</ref> <ref>[http://www.openwall.com/lists/oss-security/2014/06/24/16 CVE-2014-3519]</ref>
 
|
 
|
 
 
|-
 
|-
 
|'''Reliability'''
 
|'''Reliability'''
Line 34: Line 25:
 
|-
 
|-
 
|'''Filesystem over filesystem'''
 
|'''Filesystem over filesystem'''
|Yes
+
|{{No|Yes}}
|No
+
|{{Yes|No}}
|No
+
|{{Yes|No}}
|{{Yes|Using zvol}}
+
|?
 
|-
 
|-
 
|'''Effect of HN filesystem corruption at /vz'''
 
|'''Effect of HN filesystem corruption at /vz'''
|{{Yes|No corruption}}
+
|{{Yes|No effect}}
|{{No|Possible corruption}}
+
|{{No|Same FS}}
 
|?
 
|?
 
|?
 
|?
 
|-
 
|-
 
|'''Maturity in O/VZ'''
 
|'''Maturity in O/VZ'''
|{{Yes|Since 2012}}
+
|{{No|Since 2012}}
 
|{{Yes|Since ~2005}}
 
|{{Yes|Since ~2005}}
 
|{{Yes|Since 1998}}
 
|{{Yes|Since 1998}}
|{{Yes|Since 2014}}
+
|{{No|Since 2014}}
 
|-
 
|-
!colspan="11" style="font-style:bold;background-color:gold;"|2. Performance and design features
+
|}
 +
 
 +
=== Performance and design features ===
 +
{| class="wikitable sortable" style="text-align: center;"
 +
! Feature
 +
! OVZ Ploop
 +
! OVZ SimFS (ext4)
 +
! LVM (ext4)
 +
! ZFS (~simfs)
 
|-
 
|-
 
|'''Maximum container volume space'''
 
|'''Maximum container volume space'''
Line 59: Line 58:
 
|256 ZiB
 
|256 ZiB
 
|-
 
|-
|'''Disk space overhead'''
+
|'''Wasted space due to architecture'''
|Up to 20%
+
|{{No|up to 20%}}
|No
+
|{{Yes|No}}
|Up to 20%
+
|{{No|up to 20%}}
|No, but if using zvol is up to 50% depending on volblocksize
+
|?
 
|-
 
|-
|'''Disk I/O speed'''
+
|'''Disk i/o speed'''
|Fast
+
|Fast in any case
|Fast only with small amount of containers per node, slowdown in case of big number of small files.
+
|Very fast with small amount of containers
|Fast
+
|Fast in any case
|Fast
+
|Fast in any case
 
|-
 
|-
 
|'''Disk space overcommit (provide more space for containers than available on server now)'''
 
|'''Disk space overcommit (provide more space for containers than available on server now)'''
Line 80: Line 79:
 
|{{Yes}}
 
|{{Yes}}
 
|{{No}}
 
|{{No}}
|{{Yes}}
+
|Yes
|{{Yes|Using zvol}}
+
|No
 
|-
 
|-
 
|'''Second level quotes in Linux (inside container)'''
 
|'''Second level quotes in Linux (inside container)'''
Line 87: Line 86:
 
|{{Yes}}
 
|{{Yes}}
 
|{{Yes}}
 
|{{Yes}}
|{{Yes|Using zvol}}
+
|{{No|Not implemented}}
 
|-
 
|-
 
|'''Potential support for QCOW2 and other image formats'''
 
|'''Potential support for QCOW2 and other image formats'''
Line 93: Line 92:
 
|{{No}}
 
|{{No}}
 
|{{No}}
 
|{{No}}
|{{No}}
+
|No
 
|-
 
|-
 
|'''Incremental backup support on filesystem level'''
 
|'''Incremental backup support on filesystem level'''
Line 101: Line 100:
 
|{{Yes}}
 
|{{Yes}}
 
|-
 
|-
|'''Shared storage support (Virtuozzo storage, NFS)'''
+
|}
|{{Yes|Yes}}
+
 
|{{No|No}}
+
=== Administrator operations ===
|{{Yes|Yes}}
+
{| class="wikitable sortable" style="text-align: center;"
|{{Yes|NFS only}}
+
! Feature
|-
+
! OVZ Ploop
!colspan="11" style="font-style:bold;background-color:gold;"|3. Maintenance
+
! OVZ SimFS (ext4)
 +
! LVM (ext4)
 +
! ZFS (~simfs)
 
|-
 
|-
 
|'''vzctl integration'''
 
|'''vzctl integration'''
Line 125: Line 126:
 
|{{Yes}}
 
|{{Yes}}
 
|?
 
|?
|{{Yes|Only using ZFS filesystem}}
+
|?
 
|-
 
|-
 
|'''Live backup'''
 
|'''Live backup'''
 
|{{Yes|Easy, fast and consistent}}<ref>[http://openvz.livejournal.com/44508.html ploop snapshots and backups]</ref> <ref>[[Ploop/Backup]]</ref>
 
|{{Yes|Easy, fast and consistent}}<ref>[http://openvz.livejournal.com/44508.html ploop snapshots and backups]</ref> <ref>[[Ploop/Backup]]</ref>
 
|{{No|Easy, slow, and sometimes inconsistent}} in case some application depends on inode IDs
 
|{{No|Easy, slow, and sometimes inconsistent}} in case some application depends on inode IDs
|{{No|No}}
+
|{{No|Fast}}
|{{Yes|Fast}} via ZFS Send/Receive
+
|{{Yes|Fast}} theoretically
 
|-
 
|-
 
|'''Snapshot support'''
 
|'''Snapshot support'''
Line 143: Line 144:
 
|{{No|Not reliable and slow}}, if some application depends on inode IDs
 
|{{No|Not reliable and slow}}, if some application depends on inode IDs
 
|{{No|Not implemented}}
 
|{{No|Not implemented}}
|{{Yes|Fast}} via ZFS Send/Receive
+
|{{Yes|Fast}} theoretically
 
|-
 
|-
 
|'''Continue failed CT migration'''
 
|'''Continue failed CT migration'''

Please note that all contributions to OpenVZ Virtuozzo Containers Wiki may be edited, altered, or removed by other contributors. If you don't want your writing to be edited mercilessly, then don't submit it here.
If you are going to add external links to an article, read the External links policy first!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)

Templates used on this page: