Editing Ploop/Why
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 17: | Line 17: | ||
<ol> | <ol> | ||
<li>Since containers are living on one same file system, they all | <li>Since containers are living on one same file system, they all | ||
− | share common properties of that file system ( | + | share common properties of that file system (it's type, block size, |
− | and other options). That means we | + | and other options). That means we can not configure the above properties |
on a per-container basis.</li> | on a per-container basis.</li> | ||
Line 30: | Line 30: | ||
file truncates), all the other containers I/O will block waiting | file truncates), all the other containers I/O will block waiting | ||
for the journal to be written to disk. In some extreme cases we saw | for the journal to be written to disk. In some extreme cases we saw | ||
− | up to 15 seconds of such blockage | + | up to 15 seconds of such blockage.</li> |
− | |||
<!--T:7--> | <!--T:7--> | ||
Line 40: | Line 39: | ||
<!--T:8--> | <!--T:8--> | ||
<li>Since many containers share the same file system, and the number | <li>Since many containers share the same file system, and the number | ||
− | of inodes on a file system is limited [ | + | of inodes on a file system is limited [for most file systems], vzquota |
should also be able to limit inodes on a per container (per directory) | should also be able to limit inodes on a per container (per directory) | ||
basis.</li> | basis.</li> | ||
Line 134: | Line 133: | ||
<!--T:27--> | <!--T:27--> | ||
− | * File system journal is not bottleneck anymore | + | * File system journal is not bottleneck anymore |
* Large-size image files I/O instead of lots of small-size files I/O on management operations | * Large-size image files I/O instead of lots of small-size files I/O on management operations | ||
* Disk space quota can be implemented based on virtual device sizes; no need for per-directory quotas | * Disk space quota can be implemented based on virtual device sizes; no need for per-directory quotas | ||
− | * Number of inodes doesn't have to be limited because this is not a shared resource anymore (each CT has its own file system) | + | * Number of inodes doesn't have to be limited because this is not a shared resource anymore (each CT has its own file system) |
* Live backup is easy and consistent | * Live backup is easy and consistent | ||
* Live migration is reliable and efficient | * Live migration is reliable and efficient | ||
Line 144: | Line 143: | ||
<!--T:28--> | <!--T:28--> | ||
In addition: | In addition: | ||
+ | * Efficient container creation | ||
* [Potential] support for QCOW2 and other image formats | * [Potential] support for QCOW2 and other image formats | ||
* Support for different storage types | * Support for different storage types | ||
− | + | == See also == <!--T:29--> | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | == See also == <!--T: | ||
* [[Ploop]] | * [[Ploop]] | ||
</translate> | </translate> | ||
[[Category: Storage]] | [[Category: Storage]] |