openshift · adellape · May 8, 2024 · Apr 24, 2024
diff --git a/modules/lvms-about-scaling-storage-of-clusters.adoc b/modules/lvms-about-scaling-storage-of-clusters.adoc
@@ -0,0 +1,18 @@
+// Module included in the following assemblies:
+//
+// storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc
+
+:_mod-docs-content-type: CONCEPT
+[id="lvms-about-scaling-storage-of-cluster_{context}"]
+= Ways to scale up the storage of a {sno} cluster
+
+You can scale up the storage of a {sno} cluster by adding new devices to the existing node. 
+
+To add a new device to the existing node on a {sno} cluster, you must add the path to the new device in the `deviceSelector` field of the `LVMCluster` custom resource (CR).
+
+[IMPORTANT]
+====
+You can add the `deviceSelector` field in the `LVMCluster` CR only while creating the `LVMCluster` CR. If you have not added the `deviceSelector` field while creating the `LVMCluster` CR, you must delete the `LVMCluster` CR and create a new `LVMCluster` CR containing the `deviceSelector` field.
+====
+
+If you do not add the `deviceSelector` field in the `LVMCluster` CR, {lvms} automatically adds the new devices when the devices are available.
diff --git a/modules/lvms-scaling-storage-of-clusters-using-cli.adoc b/modules/lvms-scaling-storage-of-clusters-using-cli.adoc
@@ -0,0 +1,30 @@
+// Module included in the following assemblies:
+//
+// storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="lvms-scaling-storage-of-clusters-using-cli_{context}"]
+= Scaling up the storage of a {sno} cluster by using the CLI
+
+You can scale up the storage capacity of the existing node on a {sno} cluster by using the OpenShift CLI (`oc`).
+
+.Prerequisites
+
+* You have additional unused devices on the {sno} cluster to be used by {lvms-first}.
+* You have installed the OpenShift CLI (`oc`).
+* You have created an `LVMCluster` custom resource (CR).
+
+.Procedure
+
+. Edit the `LVMCluster` CR by running the following command:
++
+[source, terminal]
+----
+$ oc edit <lvmcluster_file_name> -n <namespace>
+----
+
+. Add the path to the new device in the `deviceSelector` field:
++
+include::snippets/lvms-scaling-up-storage-lvmcluster-cr-snippet.adoc[]
+
+. Save the `LVMCluster` CR.
diff --git a/modules/lvms-scaling-storage-of-clusters-using-web-console.adoc b/modules/lvms-scaling-storage-of-clusters-using-web-console.adoc
@@ -0,0 +1,27 @@
+// Module included in the following assemblies:
+//
+// storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="lvms-scaling-storage-of-clusters-using-web-console_{context}"]
+= Scaling up the storage of a {sno} cluster by using the web console
+
+You can scale up the storage capacity of the existing node on a {sno} cluster by using the {product-title} web console.
+
+.Prerequisites
+
+* You have additional unused devices on the {sno} cluster to be used by {lvms-first}.
+* You have created an `LVMCluster` custom resource (CR).
+
+.Procedure
+
+. Log in to the {product-title} web console.
+. Click *Operators* -> *Installed Operators*. 
+. Click *LVM Storage* in the `openshift-storage` namespace.
+. Click the *LVMCluster* tab to view the `LVMCluster` CR created on the cluster.
+. From the *Actions* menu, select *Edit LVMCluster*.
+. Click the *YAML* tab.
+. Edit the `LVMCluster` CR to add the new device path in the `deviceSelector` field:
++
+include::snippets/lvms-scaling-up-storage-lvmcluster-cr-snippet.adoc[]
+. Click *Save*.
diff --git a/modules/lvms-scaling-storage-of-single-node-open-concept.adoc b/modules/lvms-scaling-storage-of-single-node-open-concept.adoc
diff --git a/modules/lvms-scaling-storage-of-single-node-openshift-cluster.adoc b/modules/lvms-scaling-storage-of-single-node-openshift-cluster.adoc
diff --git a/snippets/lvms-scaling-up-storage-lvmcluster-cr-snippet.adoc b/snippets/lvms-scaling-up-storage-lvmcluster-cr-snippet.adoc
@@ -0,0 +1,32 @@
+:_mod-docs-content-type: SNIPPET
+.Example `LVMCluster` CR
+[source,yaml]
+----
+apiVersion: lvm.topolvm.io/v1alpha1
+kind: LVMCluster
+metadata:
+  name: my-lvmcluster
+spec:
+  storage:
+    deviceClasses:
+# ...
+      deviceSelector: <1>
+        paths: <2>
+        - /dev/disk/by-path/pci-0000:87:00.0-nvme-1
+        - /dev/disk/by-path/pci-0000:88:00.0-nvme-1
+        optionalPaths: <3>
+        - /dev/disk/by-path/pci-0000:89:00.0-nvme-1
+        - /dev/disk/by-path/pci-0000:90:00.0-nvme-1
+# ...
+----
+<1> Contains the configuration to specify the paths to the devices that you want to add to the Logical Volume Manager (LVM) volume group.
+You can specify the device paths in the `paths` field, the `optionalPaths` field, or both. If you do not specify the device paths in both `paths` and `optionalPaths`, {lvms} adds the supported unused devices to the LVM volume group. {lvms} adds the devices to the LVM volume group only if the device path exists.
+<2> Specify the device paths. If the device path specified in this field does not exist, the `LVMCluster` CR moves to the `Failed` state.
+<3> Specify the optional device paths. If the device path specified in this field does not exist, {lvms} ignores the device without causing an error. 
++
+[IMPORTANT]
+====
+After a device is added to the LVM volume group, it cannot be removed.
+====
+
+
diff --git a/.../persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc b/.../persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc
@@ -73,14 +73,21 @@ include::modules/lvms-adding-a-storage-class.adoc[leveloffset=+1]
 include::modules/lvms-provisioning-storage-using-logical-volume-manager-operator.adoc[leveloffset=+1]
 
 //Scaling
-include::modules/lvms-scaling-storage-of-single-node-open-concept.adoc[leveloffset=+1]
+include::modules/lvms-about-scaling-storage-of-clusters.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../nodes/nodes/nodes-sno-worker-nodes.adoc[Adding worker nodes to {sno} clusters]
 
-include::modules/lvms-scaling-storage-of-single-node-openshift-cluster.adoc[leveloffset=+2]
+include::modules/lvms-scaling-storage-of-clusters-using-cli.adoc[leveloffset=+2]
+
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../../../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#lvms-reference-file_logical-volume-manager-storage[{lvms} reference YAML file]
+
+include::modules/lvms-scaling-storage-of-clusters-using-web-console.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
 .Additional resources
@@ -96,14 +103,14 @@ include::modules/lvms-scaling-storage-of-single-node-openshift-cluster-using-rha
 
 * xref:../../../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#lvms-reference-file_logical-volume-manager-storage[{lvms} reference YAML file]
 
-include::modules/lvms-scaling-storage-expand-pvc.adoc[leveloffset=+2]
+//Expanding PVCs
+
+include::modules/lvms-scaling-storage-expand-pvc.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../../../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#lvms-scaling-storage-of-single-node-openshift-cluster_logical-volume-manager-storage[Scaling up storage by adding capacity to your {sno} cluster]
-
-* xref:../../../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#lvms-scaling-storage-of-single-node-openshift-cluster-using-rhacm_logical-volume-manager-storage[Scaling up storage by adding capacity to your single-node OpenShift cluster using RHACM]
+* xref:../../../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#lvms-about-scaling-storage-of-cluster_logical-volume-manager-storage[Ways to scale up the storage of clusters]
 
 * xref:../../../storage/expanding-persistent-volumes.adoc#add-volume-expansion_expanding-persistent-volumes[Enabling volume expansion support]