mirror of
https://github.com/ceph/ceph-csi.git
synced 2024-12-23 05:20:19 +00:00
b132696e54
Thick-provisioning was introduced to make accounting of assigned space for volumes easier. When thick-provisioned volumes are the only consumer of the Ceph cluster, this works fine. However, it is unlikely that this is the case. Instead, accounting of the requested (thin-provisioned) size of volumes is much more practical as different types of volumes can be tracked. OpenShift already provides cluster-wide quotas, which can combine accounting of requested volumes by grouping different StorageClasses. In addition to the difficult practise of allowing only thick-provisioned RBD backed volumes, the performance makes thick-provisioning troublesome. As volumes need to be completely allocated, data needs to be written to the volume. This can take a long time, depending on the size of the volume. Provisioning, cloning and snapshotting becomes very much noticeable, and because of the additional time consumption, more prone to failures. Signed-off-by: Niels de Vos <ndevos@redhat.com> |
||
|---|---|---|
| .. | ||
| block-pod-clone.yaml | ||
| exec-bash.sh | ||
| logs.sh | ||
| plugin-deploy.sh | ||
| plugin-teardown.sh | ||
| pod-clone.yaml | ||
| pod-restore.yaml | ||
| pod.yaml | ||
| pvc-block-clone.yaml | ||
| pvc-clone.yaml | ||
| pvc-restore.yaml | ||
| pvc.yaml | ||
| raw-block-pod.yaml | ||
| raw-block-pvc.yaml | ||
| secret.yaml | ||
| snapshot.yaml | ||
| snapshotclass.yaml | ||
| storageclass.yaml | ||