TELCODOCS#1834: Thick provisioning documentation

Author: sr1kar99

modules/lvms-about-lvmcluster-cr.adoc

@@ -101,7 +101,16 @@ If any of these conditions are true, do not force wipe the disk. Instead, you mu
 
 |`deviceClasses.thinPoolConfig`
 |`object`
-|Contains the configuration to create a thin pool in the LVM volume group.
+|Contains the configuration to create a thin pool in the LVM volume group. 
+
+If you exclude this field, logical volumes are thick provisioned. 
+
+Using thick-provisioned storage includes the following limitations:
+
+* No copy-on-write support for volume cloning.
+* No support for snapshot class.
+* No support for over-provisioning. As a result, the provisioned capacity of `PersistentVolumeClaims` (PVCs) is immediately reduced from the volume group.
+* No support for thin metrics. Thick-provisioned devices only support volume group metrics.
 
 |`thinPoolConfig.name`
 |`string`

modules/lvms-creating-lvmcluster-using-rhacm.adoc

@@ -51,7 +51,7 @@ spec:
 ----
 <1> Contains the configuration to assign the local storage devices to the LVM volume groups.
 <2> Contains the configuration to specify the paths to the devices that you want to add to the LVM volume group, and force wipe the devices that are added to the LVM volume group. 
-<3> Contains the LVM thin pool configuration.
+<3> Contains the configuration to create a thin pool in the LVM volume group. If you exclude this field, logical volumes are thick provisioned.
 <4> Contains the configuration to choose the nodes on which you want to create the LVM volume groups. If this field is empty, then all nodes without no-schedule taints are considered.
 
 . Create the `ConfigurationPolicy` CR by running the following command:

modules/lvms-creating-lvms-cluster-using-cli.adoc

@@ -51,7 +51,7 @@ spec:
 <1> Contains the configuration to assign the local storage devices to the LVM volume groups.
 <2> Contains the configuration to choose the nodes on which you want to create the LVM volume group. If this field is empty, all nodes without no-schedule taints are considered.
 <3> Contains the configuration to specify the paths to the devices that you want to add to the LVM volume group, and force wipe the devices that are added to the LVM volume group.  
-<4> Contains the configuration to create a thin pool in the LVM volume group.
+<4> Contains the configuration to create a thin pool in the LVM volume group. If you exclude this field, logical volumes are thick provisioned.
 
 . Create the `LVMCluster` CR by running the following command:
 +

storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc

@@ -6,9 +6,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-Logical Volume Manager Storage uses the TopoLVM CSI driver to dynamically provision local storage on the {product-title} clusters.
-
-{lvms} creates thin-provisioned volumes using Logical Volume Manager and provides dynamic provisioning of block storage on a limited resources cluster.
+{lvms-first} uses LVM2 through the TopoLVM CSI driver to dynamically provision local storage on a cluster with limited resources.
 
 You can create volume groups, persistent volume claims (PVCs), volume snapshots, and volume clones by using {lvms}.