Merge pull request #70160 from sr1kar99/add-remove-device_class

Author: sheriff-rh

modules/deploying-lvms-on-sno-cluster.adoc

@@ -30,11 +30,6 @@ Before you begin deploying {lvms}, ensure that the following requirements are me
 * You have installed {rh-rhacm-first} on an {product-title} cluster.
 * Every managed cluster has dedicated disks that are used to provision storage.
 
-Before you deploy {lvms}, be aware of the following limitations:
-
-* You can only create a single instance of the `LVMCluster` custom resource (CR) on an {product-title} cluster.
-* When a device becomes part of the `LVMCluster` CR, it cannot be removed.
-
 [id="lvms-deployment-limitations-for-sno-ran_{context}"]
 == Limitations
 

modules/lvms-creating-logical-volume-manager-cluster.adoc

@@ -35,7 +35,12 @@ You also can perform the same task by using the {product-title} web console.
 .Procedure
 
 . Create the `LVMCluster` custom resource (CR).
-
++
+[IMPORTANT]
+=====
+You can only create a single instance of the `LVMCluster` custom resource (CR) on an {product-title} cluster.
+=====
++
 .. Save the following YAML in the `lvmcluster.yaml` file:
 +
 [source,yaml]
@@ -71,12 +76,13 @@ spec:
                 - test1
 ----
 <1> To create multiple device storage classes in the cluster, create a YAML array under `deviceClasses` for each required storage class.
+If you add or remove a `deviceClass`, then the update reflects in the cluster only after deleting and recreating the `TopoLVM-Node` pod.
 Configure the local device paths of the disks as an array of values in the `deviceSelector` field.
 When configuring multiple device classes, you must specify the device path for each device.
 <2> Set `fstype` to `ext4` or `xfs`. By default, it is set to `xfs` if the setting is not specified.
 <3> Mandatory: The `LVMCluster` resource must contain a single default storage class. Set `default: false` for secondary device storage classes.
 If you are updating the `LVMCluster` resource from a previous version, you must specify a single default device class.
-<4> Optional. To control or restrict the volume group to your preferred devices, you can manually specify the local paths of the devices in the `deviceSelector` section of the `LVMCluster` YAML. The `paths` section refers to devices the `LVMCluster` adds, which means those paths must exist. The `optionalPaths` section refers to devices the `LVMCluster` might add. You must specify at least one of `paths` or `optionalPaths` when specifying the `deviceSelector` section. If you specify `paths`, it is not mandatory to specify `optionalPaths`. If you specify `optionalPaths`, it is not mandatory to specify `paths` but at least one optional path must be present on the node. If you do not specify any paths, then the `LVMCluster` adds the unused devices on the node.
+<4> Optional. To control or restrict the volume group to your preferred devices, you can manually specify the local paths of the devices in the `deviceSelector` section of the `LVMCluster` YAML. The `paths` section refers to devices the `LVMCluster` adds, which means those paths must exist. The `optionalPaths` section refers to devices the `LVMCluster` might add. You must specify at least one of `paths` or `optionalPaths` when specifying the `deviceSelector` section. If you specify `paths`, it is not mandatory to specify `optionalPaths`. If you specify `optionalPaths`, it is not mandatory to specify `paths` but at least one optional path must be present on the node. If you do not specify any paths, then the `LVMCluster` adds the unused devices on the node. After a device is added to the `LVMCluster`, it cannot be removed.
 <5> Optional: To force wipe the selected disks, set `forceWipeDevicesAndDestroyAllData` to true. This parameter is set to `false` by default.
 <6> Optional: To control what worker nodes the `LVMCluster` CR is applied to, specify a set of node selector labels.
 The specified labels must be present on the node in order for the `LVMCluster` to be scheduled on that node.