Niels de Vos b132696e54 rbd: note that thick-provisioning is deprecated ... 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>		2021-10-27 06:54:07 +00:00
..
cephfs	cleanup: move mount functions to new pkg	2021-09-23 06:39:37 +00:00
controller	cleanup: simplify checkStaticVolume function and remove unwanted vars	2021-09-07 12:51:30 +00:00
csi-common	util: NodeGetVolumeStatsResponse.Usage may not contain negative values	2021-10-20 07:18:48 +00:00
journal	cleanup: replace parentName to snapParentName in checkReservation	2021-09-14 05:32:54 +00:00
kms	rbd: set vaultAuthNamespace to vaultNamespace if empty	2021-09-08 11:18:03 +00:00
liveness	cleanup: move log functions to new internal/util/log package	2021-08-26 09:34:05 +00:00
rbd	rbd: note that thick-provisioning is deprecated	2021-10-27 06:54:07 +00:00
util	rbd: use clusterID from volumeContext at nodestage	2021-10-11 10:06:30 +00:00