Changes

Jump to: navigation, search

CT storage backends

216 bytes added, 11:09, 7 June 2016
return back row with 'Shared storage support', merge three tables to single table
{{stub}}
<translate>
= Comparison tables =
=Comparison table == Solidity in front of failures and security === 
<!--T:1-->
{| class="wikitable sortable" style="text-align: center;"
|-
! Feature
! OVZ Ploop
! OVZ SimFS (ext4)
! LVM (ext4)
! ZFS (~simfs)|-!colspan="11" style="font-style:bold;background-color:gold;"|1. Solidity in front of failures and security
|-
|'''I/O isolation'''
|{{Yes|Good}}
|{{No|Bad}}: Some bug could be exploited to escape CT and access HN Possibility of "no inodes" issues (when file systemjournal become a bottleneck).|{{Yes|Good}}: [https://bugs.openvz.org/browse/OVZ-6296 CVE-2015-2925], [http://www.openwall.com/lists/oss-security/2014/06/24/16 CVE-2014-3519]
|{{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'''
|{{Yes|Excellent}}: no write hole, checksumming and COW
|-
|'''Risk to be using filesystem Filesystem over filesystem'''|{{No|Yes}}|{{Yes|No}}|{{Yes|No}}
|?
|-
|'''Effect of HN filesystem corruption at /vz'''
|{{Yes|No effectcorruption}}|{{No|Same FSPossible corruption}}
|?
|?
|{{No|Since 2014}}
|-
|'''Incremental backup support on filesystem level'''|{{Yes}}, through snapshots|{{No}}|{{No}}|{{Yes}}|-|} === Performance and design features ===<!--T:1-->{| classcolspan="wikitable sortable11" style="textfont-alignstyle: centerbold;background-color:gold;"! Feature! OVZ Ploop! OVZ SimFS (ext4)! LVM (ext4)! ZFS (~simfs)|2. Performance and design features
|-
|'''Maximum container volume space'''
|4 TiB <ref>[[Ploop/Limits]]</ref>
|1 EiB<ref>[https://en.wikipedia.org/wiki/Ext4 Ext4]</ref>|1 EiB?
|256 ZiB
|-
|'''Wasted Disk space due to architectureoverhead'''|{{No|up Up to 20%}}|{{Yes|No}}|{{No|up Up to 20%}}
|?
|-
|'''Disk iI/o O speed'''|Fast in any case|Very fast Fast only with small amount of containersper node, slowdown in case of big number of small files.|Fast in any case|Fast in any case
|-
|'''Disk space overcommit (provide more space for containers than available on server now)'''
|No
|-
|'''Incremental backup support on filesystem level'''|{{Yes}}, through snapshots|{{No}}=== Administrator operations ===|{{No}}|{{Yes}}<!|--T:1-->|'''Shared storage support (Virtuozzo storage, NFS)'''|{{Yes|Yes}}|{{No|No}}|{{Yes| classYes}}|?|-!colspan="wikitable sortable11" style="textfont-alignstyle: centerbold;background-color:gold;"|3. Maintenance! Feature|-|'''vzctl integration'''! OVZ Ploop|{{Yes|Complete}}! OVZ SimFS (ext4)|{{Yes|Complete}}! LVM (ext4)|{{No}}, many manual operations! ZFS (~simfs)|{{No}}, some manual operations
|-
|'''External compaction for container volumes'''
|-
|'''Live backup'''
|{{Yes|Easy, fast and consistent}}<ref name="ploop backup">[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|Fast}}
|-
|'''Snapshot support'''
|{{Yes}}<ref name="ploop backup">[http://openvz.livejournal.com/44508.html ploop snapshots and backups]</ref>
|{{No}} theoretically, because of much/small files to be copied
|{{Yes}}

Navigation menu