Merge pull request #75965 from sr1kar99/10568-deleting-int-raid-arrays-proc

skopacz1 · web-flow · commit d884ddd81ea5 · 2024-06-06T09:20:00.000-04:00
OSDOCS#10568: Deleted "Integrating RAID arrays with LVMS" proc
diff --git a/modules/lvms-about-adding-devices-to-a-vg.adoc b/modules/lvms-about-adding-devices-to-a-vg.adoc
@@ -6,11 +6,21 @@
 [id="about-adding-devices-to-a-vg_{context}"]
 = About adding devices to a volume group
 
-The `deviceSelector` field in the `LVMCluster` CR contains the configuration to specify the paths to the devices that you want to add to the LVM volume group (VG).
+The `deviceSelector` field in the `LVMCluster` CR 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 `deviceSelector.paths` field, the `deviceSelector.optionalPaths` field, or both. If you do not specify the device paths in both the `deviceSelector.paths` field and the `deviceSelector.optionalPaths` field, {lvms} adds the supported unused devices to the VG. 
+You can specify the device paths in the `deviceSelector.paths` field, the `deviceSelector.optionalPaths` field, or both. If you do not specify the device paths in both the `deviceSelector.paths` field and the `deviceSelector.optionalPaths` field, {lvms} adds the supported unused devices to the volume group (VG). 
 
-You can also add the path to the RAID arrays to integrate the RAID arrays with {lvms}. For more information, see "Integrating RAID arrays with {lvms}".
+You can add the path to the Redundant Array of Independent Disks (RAID) arrays in the `deviceSelector` field to integrate the RAID arrays with {lvms}. You can create the RAID array by using the `mdadm` utility. {lvms} does not support creating a software RAID.
+
+[NOTE]
+====
+You can create a RAID array only during an {product-title} installation. For information on creating a RAID array, see the following sections:
+
+* "Configuring a RAID-enabled data volume" in "Additional resources".
+* link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/managing_storage_devices/managing-raid_managing-storage-devices#creating-a-software-raid-on-an-installed-system_managing-raid[Creating a software RAID on an installed system]
+* link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/managing_storage_devices/managing-raid_managing-storage-devices#replacing-a-failed-disk-in-raid_managing-raid[Replacing a failed disk in RAID]
+* link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/managing_storage_devices/managing-raid_managing-storage-devices#repairing-raid-disks_managing-raid[Repairing RAID disks]
+====
 
 You can also add encrypted devices to the volume group. You can enable disk encryption on the cluster nodes during an {product-title} installation. After encrypting a device, you can specify the path to the LUKS encrypted device in the `deviceSelector` field. For information on disk encryption, see "About disk encryption" and "Configuring disk encryption and mirroring".
 
diff --git a/modules/lvms-about-lvmcluster-cr.adoc b/modules/lvms-about-lvmcluster-cr.adoc
@@ -38,7 +38,7 @@ LVM Storage creates a storage class and volume snapshot class for each device cl
 |`string`
 |Specify a name for the LVM volume group (VG). 
 
-You can also configure this field to reuse a volume group that you created in the previous installation. For more information, see "Reusing a volume group from the previous LVM Storage installation" in the "Additional resources" section.
+You can also configure this field to reuse a volume group that you created in the previous installation. For more information, see "Reusing a volume group from the previous LVM Storage installation".
 
 |`deviceClasses.fstype`
 |`string`
@@ -65,7 +65,7 @@ On the control-plane node, {lvms} detects and uses the additional worker nodes w
 * Specify the paths to the devices that you want to add to the LVM volume group.
 * Force wipe the devices that are added to the LVM volume group.
 
-For more information, see "About adding devices to a volume group" in the "Additional resources" section.
+For more information, see "About adding devices to a volume group".
 
 |`deviceSelector.paths`
 |`array`
diff --git a/modules/lvms-about-scaling-storage-of-clusters.adoc b/modules/lvms-about-scaling-storage-of-clusters.adoc
@@ -20,5 +20,5 @@ You can add the `deviceSelector` field in the `LVMCluster` CR only while creatin
 If you do not add the `deviceSelector` field in the `LVMCluster` CR, {lvms} automatically adds the new devices when the devices are available.
 [NOTE]
 ====
-{lvms} adds only the supported devices. For information about unsupported devices, see "Devices not supported by LVM Storage" in the "Additional resources" section.
+{lvms} adds only the supported devices. For information about unsupported devices, see "Devices not supported by LVM Storage".
 ====
diff --git a/modules/lvms-about-volume-snapshots.adoc b/modules/lvms-about-volume-snapshots.adoc
@@ -14,7 +14,7 @@ You can perform the following actions using the volume snapshots:
 +
 [IMPORTANT]
 ====
-Volume snapshots are located on the same devices as the original data. To use the volume snapshots as backups, you must move the snapshots to a secure location. You can use OpenShift API for Data Protection (OADP) backup and restore solutions. For information about OADP, see "OADP features" in the "Additional resources" section.
+Volume snapshots are located on the same devices as the original data. To use the volume snapshots as backups, you must move the snapshots to a secure location. You can use OpenShift API for Data Protection (OADP) backup and restore solutions. For information about OADP, see "OADP features".
 ====
 
 * Revert to a state at which the volume snapshot was taken.
diff --git a/modules/lvms-creating-lvmcluster-using-rhacm.adoc b/modules/lvms-creating-lvmcluster-using-rhacm.adoc
@@ -12,7 +12,7 @@ After you have installed {lvms} by using {rh-rhacm}, you must create an `LVMClus
 
 * You have installed {lvms} by using {rh-rhacm}.
 * You have access to the {rh-rhacm} cluster using an account with `cluster-admin` permissions.
-* You read the "About the LVMCluster custom resource" section. See the "Additional resources" section.
+* You read the "About the LVMCluster custom resource" section.
 
 .Procedure
 
diff --git a/modules/lvms-creating-lvms-cluster-using-cli.adoc b/modules/lvms-creating-lvms-cluster-using-cli.adoc
@@ -23,7 +23,7 @@ You can only create a single instance of the `LVMCluster` custom resource (CR) o
 
 * You have installed a worker node in the cluster.
 
-* You read the "About the LVMCluster custom resource" section. See the "Additional resources" section.
+* You read the "About the LVMCluster custom resource" section.
 
 .Procedure
 
diff --git a/modules/lvms-creating-lvms-cluster-using-web-console.adoc b/modules/lvms-creating-lvms-cluster-using-web-console.adoc
@@ -21,7 +21,7 @@ You can only create a single instance of the `LVMCluster` custom resource (CR) o
 
 * You have installed a worker node in the cluster.
 
-* You read the "About the LVMCluster custom resource" section. See the "Additional resources" section.
+* You read the "About the LVMCluster custom resource" section.
 
 .Procedure
 
diff --git a/modules/lvms-integrating-software-raid-arrays.adoc b/modules/lvms-integrating-software-raid-arrays.adoc
diff --git a/modules/lvms-scaling-storage-of-clusters-using-rhacm.adoc b/modules/lvms-scaling-storage-of-clusters-using-rhacm.adoc
@@ -57,7 +57,7 @@ apiVersion: policy.open-cluster-management.io/v1
 <1> Contains the configuration to specify the paths to the devices that you want to add to the 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-first} adds the supported unused devices to the LVM volume group. {lvms} adds the devices to the LVM volume group only if the following conditions are met:
 * The device path exists.
-* The device is supported by {lvms}. For information about unsupported devices, see "Devices not supported by {lvms}" in the "Additional resources" section.
+* The device is supported by {lvms}. For information about unsupported devices, see "Devices not supported by {lvms}".
 <2> Specify the device paths. If the device path specified in this field does not exist, or the device is not supported by {lvms}, 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, or the device is not supported by {lvms}, {lvms} ignores the device without causing an error. 
 +
diff --git a/snippets/lvms-scaling-up-storage-lvmcluster-cr-snippet.adoc b/snippets/lvms-scaling-up-storage-lvmcluster-cr-snippet.adoc
@@ -22,7 +22,7 @@ spec:
 <1> Contains the configuration to specify the paths to the devices that you want to add to the 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-first} adds the supported unused devices to the LVM volume group. {lvms} adds the devices to the LVM volume group only if the following conditions are met:
 * The device path exists.
-* The device is supported by {lvms}. For information about unsupported devices, see "Devices not supported by {lvms}" in the "Additional resources" section.
+* The device is supported by {lvms}. For information about unsupported devices, see "Devices not supported by {lvms}".
 <2> Specify the device paths. If the device path specified in this field does not exist, or the device is not supported by {lvms}, 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, or the device is not supported by {lvms}, {lvms} ignores the device without causing an error. 
 +
diff --git a/storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc b/storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc
@@ -69,13 +69,9 @@ include::modules/lvms-about-adding-devices-to-a-vg.adoc[leveloffset=+2]
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../../../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#lvms-unsupported-devices_logical-volume-manager-storage[Devices not supported by {lvms}]
-
-* xref:../../../installing/install_config/installing-customizing.adoc#installation-special-config-encrypt-disk_installing-customizing[About disk encryption]
-
-* xref:../../../installing/install_config/installing-customizing.adoc#installation-special-config-storage-procedure_installing-customizing[Configuring disk encryption and mirroring]
+* xref:../../../installing/install_config/installing-customizing.adoc#installation-special-config-raid_installing-customizing[Configuring a RAID-enabled data volume]
 
-* xref:../../../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#lvms-integrating-software-raid-arrays_logical-volume-manager-storage[Integrating software RAID arrays with {lvms}]
+* xref:../../../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#lvms-unsupported-devices_logical-volume-manager-storage[Devices not supported by {lvms}]
 
 // Devices not supported by LVMS
 include::modules/lvms-unsupported-devices.adoc[leveloffset=+2]
@@ -87,17 +83,6 @@ include::modules/lvms-about-creating-lvmcluster-cr.adoc[leveloffset=+1]
 // Reusing a volume group from the previous LVM Storage installation
 include::modules/lvms-reusing-vg-from-prev-installation.adoc[leveloffset=+2]
 
-//Integrating software RAID arrays
-include::modules/lvms-integrating-software-raid-arrays.adoc[leveloffset=+2]
-
-[role="_additional-resources"]
-.Additional resources
-
-* xref:../../../installing/install_config/installing-customizing.adoc#installation-special-config-raid_installing-customizing[Configuring a RAID-enabled data volume]
-* link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/managing_storage_devices/managing-raid_managing-storage-devices#creating-a-software-raid-on-an-installed-system_managing-raid[Creating a software RAID on an installed system]
-* link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/managing_storage_devices/managing-raid_managing-storage-devices#replacing-a-failed-disk-in-raid_managing-raid[Replacing a failed disk in RAID]
-* link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/managing_storage_devices/managing-raid_managing-storage-devices#repairing-raid-disks_managing-raid[Repairing RAID disks]
-
 include::modules/lvms-creating-lvms-cluster-using-cli.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
@@ -151,18 +136,18 @@ include::modules/lvms-scaling-storage-of-clusters-using-cli.adoc[leveloffset=+2]
 
 * xref:../../../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#lvms-unsupported-devices_logical-volume-manager-storage[Devices not supported by {lvms}]
 
-* xref:../../../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#lvms-integrating-software-raid-arrays_logical-volume-manager-storage[Integrating software RAID arrays with {lvms}]
+* xref:../../../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#about-adding-devices-to-a-vg_logical-volume-manager-storage[About adding devices to a volume group]
 
 include::modules/lvms-scaling-storage-of-clusters-using-web-console.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../../../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#lvms-unsupported-devices_logical-volume-manager-storage[Devices not supported by {lvms}]
+* xref:../../../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#about-lvmcluster_logical-volume-manager-storage[About the LVMCluster custom resource]
 
-* xref:../../../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#lvms-integrating-software-raid-arrays_logical-volume-manager-storage[Integrating software RAID arrays with {lvms}]
+* xref:../../../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#lvms-unsupported-devices_logical-volume-manager-storage[Devices not supported by {lvms}]
 
-* xref:../../../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#about-lvmcluster_logical-volume-manager-storage[About the LVMCluster custom resource]
+* xref:../../../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#about-adding-devices-to-a-vg_logical-volume-manager-storage[About adding devices to a volume group]
 
 include::modules/lvms-scaling-storage-of-clusters-using-rhacm.adoc[leveloffset=+2]
 
@@ -175,7 +160,7 @@ include::modules/lvms-scaling-storage-of-clusters-using-rhacm.adoc[leveloffset=+
 
 * xref:../../../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#lvms-unsupported-devices_logical-volume-manager-storage[Devices not supported by {lvms}]
 
-* xref:../../../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#lvms-integrating-software-raid-arrays_logical-volume-manager-storage[Integrating software RAID arrays with {lvms}]
+* xref:../../../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#about-adding-devices-to-a-vg_logical-volume-manager-storage[About adding devices to a volume group]
 
 // Expanding PVCs
 include::modules/lvms-scaling-storage-expand-pvc.adoc[leveloffset=+1]

Original file line number	Diff line number	Diff line change
`@@ -14,7 +14,7 @@ You can perform the following actions using the volume snapshots:`
`14`	`14`	`+`
`15`	`15`	`[IMPORTANT]`
`16`	`16`	`====`
`17`		`-Volume snapshots are located on the same devices as the original data. To use the volume snapshots as backups, you must move the snapshots to a secure location. You can use OpenShift API for Data Protection (OADP) backup and restore solutions. For information about OADP, see "OADP features" in the "Additional resources" section.`
	`17`	`+Volume snapshots are located on the same devices as the original data. To use the volume snapshots as backups, you must move the snapshots to a secure location. You can use OpenShift API for Data Protection (OADP) backup and restore solutions. For information about OADP, see "OADP features".`
`18`	`18`	`====`
`19`	`19`
`20`	`20`	`* Revert to a state at which the volume snapshot was taken.`
Original file line number	Diff line number	Diff line change
`@@ -57,7 +57,7 @@ apiVersion: policy.open-cluster-management.io/v1`
`57`	`57`	`<1> Contains the configuration to specify the paths to the devices that you want to add to the LVM volume group.`
`58`	`58`	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-first} adds the supported unused devices to the LVM volume group. {lvms} adds the devices to the LVM volume group only if the following conditions are met:
`59`	`59`	`* The device path exists.`
`60`		`-* The device is supported by {lvms}. For information about unsupported devices, see "Devices not supported by {lvms}" in the "Additional resources" section.`
	`60`	`+* The device is supported by {lvms}. For information about unsupported devices, see "Devices not supported by {lvms}".`
`61`	`61`	<2> Specify the device paths. If the device path specified in this field does not exist, or the device is not supported by {lvms}, the `LVMCluster` CR moves to the `Failed` state.
`62`	`62`	`<3> Specify the optional device paths. If the device path specified in this field does not exist, or the device is not supported by {lvms}, {lvms} ignores the device without causing an error.`
`63`	`63`	`+`
Original file line number	Diff line number	Diff line change
`@@ -22,7 +22,7 @@ spec:`
`22`	`22`	`<1> Contains the configuration to specify the paths to the devices that you want to add to the LVM volume group.`
`23`	`23`	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-first} adds the supported unused devices to the LVM volume group. {lvms} adds the devices to the LVM volume group only if the following conditions are met:
`24`	`24`	`* The device path exists.`
`25`		`-* The device is supported by {lvms}. For information about unsupported devices, see "Devices not supported by {lvms}" in the "Additional resources" section.`
	`25`	`+* The device is supported by {lvms}. For information about unsupported devices, see "Devices not supported by {lvms}".`
`26`	`26`	<2> Specify the device paths. If the device path specified in this field does not exist, or the device is not supported by {lvms}, the `LVMCluster` CR moves to the `Failed` state.
`27`	`27`	`<3> Specify the optional device paths. If the device path specified in this field does not exist, or the device is not supported by {lvms}, {lvms} ignores the device without causing an error.`
`28`	`28`	`+`