Merge pull request #69310 from sr1kar99/removing-instances-of-single-node

jeana-redhat · web-flow · commit 32fc114c6728 · 2024-01-12T09:41:01.000-05:00
TELCODOCS#1255: Removed all instances of single-node
diff --git a/modules/deploying-lvms-on-sno-cluster.adoc b/modules/deploying-lvms-on-sno-cluster.adoc
@@ -4,9 +4,9 @@
 
 :_mod-docs-content-type: CONCEPT
 [id="lvms-preface-sno-ran_{context}"]
-= Deploying {lvms} on {sno} clusters
+= Deploying {lvms}
 
-You can deploy {lvms} on a {sno} bare-metal or user-provisioned infrastructure cluster and configure it to dynamically provision storage for your workloads.
+You can deploy {lvms} on a bare-metal or user-provisioned infrastructure cluster and configure it to dynamically provision storage for your workloads.
 
 {lvms} creates a volume group using all the available unused disks and creates a single thin pool with a size of 90% of the volume group.
 The remaining 10% of the volume group is left free to enable data recovery by expanding the thin pool when required.
@@ -15,30 +15,30 @@ You might need to manually perform such recovery.
 You can use persistent volume claims (PVCs) and volume snapshots provisioned by {lvms} to request storage and create volume snapshots.
 
 {lvms} configures a default overprovisioning limit of 10 to take advantage of the thin-provisioning feature.
-The total size of the volumes and volume snapshots that can be created on the {sno} clusters is 10 times the size of the thin pool.
+The total size of the volumes and volume snapshots that can be created on the clusters is 10 times the size of the thin pool.
 
-You can deploy {lvms} on {sno} clusters using one of the following:
+You can deploy {lvms} using one of the following:
 
 * {rh-rhacm-first}
 * {product-title} Web Console
 
 [id="lvms-deployment-requirements-for-sno-ran_{context}"]
 == Requirements
 
-Before you begin deploying {lvms} on {sno} clusters, ensure that the following requirements are met:
+Before you begin deploying {lvms}, ensure that the following requirements are met:
 
 * You have installed {rh-rhacm-first} on an {product-title} cluster.
-* Every managed {sno} cluster has dedicated disks that are used to provision storage.
+* Every managed cluster has dedicated disks that are used to provision storage.
 
-Before you deploy {lvms} on {sno} clusters, be aware of the following limitations:
+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
 
-For deploying {sno}, LVM Storage has the following limitations:
+For deploying {product-title}, LVM Storage has the following limitations:
 
 * The total storage size is limited by the size of the underlying Logical Volume Manager (LVM) thin pool and the overprovisioning factor.
 * The size of the logical volume depends on the size of the Physical Extent (PE) and the Logical Extent (LE).
diff --git a/modules/lvms-creating-logical-volume-manager-cluster.adoc b/modules/lvms-creating-logical-volume-manager-cluster.adoc
@@ -4,10 +4,10 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="lvms-creating-lvms-cluster_{context}"]
-= Creating a Logical Volume Manager cluster on a {sno} worker node
+= Creating a Logical Volume Manager cluster on a worker node
 
-You can configure a {sno} worker node as a Logical Volume Manager cluster.
-On the control-plane {sno} node, {lvms} detects and uses the additional worker nodes when the new nodes become active in the cluster.
+You can configure a worker node as a Logical Volume Manager cluster.
+On the control-plane node, {lvms} detects and uses the additional worker nodes when the new nodes become active in the cluster.
 
 [NOTE]
 ====
@@ -17,7 +17,7 @@ When you create a Logical Volume Manager cluster, `StorageClass` and `LVMVolumeG
 `LVMVolumeGroup` CRs provide the back-end storage for the persistent volumes that you create.
 ====
 
-Perform the following procedure to create a Logical Volume Manager cluster on a {sno} worker node.
+Perform the following procedure to create a Logical Volume Manager cluster on a worker node.
 
 [NOTE]
 ====
@@ -30,7 +30,7 @@ You also can perform the same task by using the {product-title} web console.
 
 * You have logged in as a user with `cluster-admin` privileges.
 
-* You installed {lvms} in a {sno} cluster and have installed a worker node for use in the {sno} cluster.
+* You installed {lvms} in a cluster and have installed a worker node for use in the cluster.
 
 .Procedure
 
@@ -74,7 +74,7 @@ Configure the local device paths of the disks as an array of values in the `devi
 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 upgrading the `LVMCluster` resource from a previous version, you must specify a single default device class.
+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.
 <5> 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.
diff --git a/modules/lvms-creating-volume-clones-in-single-node-openshift.adoc b/modules/lvms-creating-volume-clones-in-single-node-openshift.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="lvms-creating-volume-clones-in-single-node-openshift_{context}"]
-= Creating volume clones in {sno}
+= Creating volume clones
 
 You create a clone of a volume to make a point-in-time copy of the data.
 A persistent volume claim (PVC) cannot be cloned with a different size.
diff --git a/modules/lvms-creating-volume-snapshots-in-single-node-openshift.adoc b/modules/lvms-creating-volume-snapshots-in-single-node-openshift.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="lvms-creating-volume-snapshots-in-single-node-openshift_{context}"]
-= Creating volume snapshots in {sno}
+= Creating volume snapshots
 
 You can create volume snapshots based on the available capacity of the thin pool and the overprovisioning limits.
 {lvms} creates a `VolumeSnapshotClass` with the `lvms-<deviceclass-name>` name.
@@ -16,7 +16,7 @@ You can create volume snapshots based on the available capacity of the thin pool
 
 .Procedure
 
-. Log in to the {sno} for which you need to run the `oc` command.
+. Log in to the {product-title} by running the `oc` command.
 . Save the following YAML to a file with a name such as `lvms-vol-snapshot.yaml`.
 +
 .Example YAML to create a volume snapshot
diff --git a/modules/lvms-deleting-cloned-volumes-in-single-node-openshift.adoc b/modules/lvms-deleting-cloned-volumes-in-single-node-openshift.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="lvms-deleting-cloned-volumes-in-single-node-openshift_{context}"]
-= Deleting cloned volumes in {sno}
+= Deleting cloned volumes
 
 You can delete cloned volumes.
 
diff --git a/modules/lvms-deleting-volume-snapshots-in-single-node-openshift.adoc b/modules/lvms-deleting-volume-snapshots-in-single-node-openshift.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="lvms-deleting-volume-snapshots-in-single-node-openshift_{context}"]
-= Deleting volume snapshots in {sno}
+= Deleting volume snapshots
 
 You can delete volume snapshots resources and persistent volume claims (PVCs).
 
diff --git a/modules/lvms-installing-logical-volume-manager-operator-using-openshift-web-console.adoc b/modules/lvms-installing-logical-volume-manager-operator-using-openshift-web-console.adoc
@@ -10,7 +10,7 @@ You can install {lvms-first} by using the Red Hat {product-title} OperatorHub.
 
 .Prerequisites
 
-* You have access to the {sno} cluster.
+* You have access to the cluster.
 * You are using an account with the `cluster-admin` and Operator installation permissions.
 
 .Procedure
@@ -26,7 +26,7 @@ You can install {lvms-first} by using the Red Hat {product-title} OperatorHub.
    If the `openshift-storage` namespace does not exist, it is created during the operator installation.
 .. *Approval Strategy* as *Automatic* or *Manual*.
 +
-If you select *Automatic* updates, then the Operator Lifecycle Manager (OLM) automatically upgrades the running instance of your Operator without any intervention.
+If you select *Automatic* updates, then the Operator Lifecycle Manager (OLM) automatically updates the running instance of your Operator without any intervention.
 +
 If you select *Manual* updates, then the OLM creates an update request.
 As a cluster administrator, you must then manually approve that update request to update the Operator to a newer version.
diff --git a/modules/lvms-installing-logical-volume-manager-operator-using-rhacm.adoc b/modules/lvms-installing-logical-volume-manager-operator-using-rhacm.adoc
@@ -6,14 +6,14 @@
 [id="lvms-installing-odf-logical-volume-manager-operator-using-rhacm_{context}"]
 = Installing {lvms} using {rh-rhacm}
 
-{lvms} is deployed on {sno} clusters using {rh-rhacm-first}.
+{lvms} is deployed on the clusters using {rh-rhacm-first}.
 You create a `Policy` object on {rh-rhacm} that deploys and configures the Operator when it is applied to managed clusters which match the selector specified in the `PlacementRule` resource.
 The policy is also applied to clusters that are imported later and satisfy the placement rule.
 
 .Prerequisites
 * Access to the {rh-rhacm} cluster using an account with `cluster-admin` and Operator installation permissions.
-* Dedicated disks on each {sno} cluster to be used by {lvms}.
-* The {sno} cluster needs to be managed by {rh-rhacm}, either imported or created.
+* Dedicated disks on each cluster to be used by {lvms}.
+* The cluster needs to be managed by {rh-rhacm}, either imported or created.
 
 .Procedure
 
@@ -152,7 +152,7 @@ spec:
         remediationAction: enforce
         severity: low
 ----
-<1> Replace the key and value in `PlacementRule.spec.clusterSelector` to match the labels set on the {sno} clusters on which you want to install {lvms}.
+<1> Replace the key and value in `PlacementRule.spec.clusterSelector` to match the labels set on the clusters on which you want to install {lvms}.
 <2> 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, it will add all unused devices on the node.
 <3> To add a node filter, which is a subset of the additional worker nodes, specify the required filter in the `nodeSelector` section. {lvms} detects and uses the additional worker nodes when the new nodes show up.
 +
@@ -174,9 +174,9 @@ This `nodeSelector` node filter matching is not the same as the pod label matchi
 +
 This creates a `Policy`, a `PlacementRule`, and a `PlacementBinding` object in the `lvms-policy-ns` namespace.
 The policy creates a `Namespace`, `OperatorGroup`, `Subscription`, and `LVMCluster` resource on the clusters that match the placement rule.
-This deploys the Operator on the {sno} clusters which match the selection criteria and configures it to set up the required resources to provision storage.
+This deploys the Operator on the clusters which match the selection criteria and configures it to set up the required resources to provision storage.
 The Operator uses all the disks specified in the `LVMCluster` CR.
-If no disks are specified, the Operator uses all the unused disks on the {sno} node.
+If no disks are specified, the Operator uses all the unused disks on the node.
 +
 [IMPORTANT]
 ====
diff --git a/modules/lvms-monitoring-logical-volume-manager-operator.adoc b/modules/lvms-monitoring-logical-volume-manager-operator.adoc
@@ -6,7 +6,7 @@
 [id="lvms-monitoring-using-lvms_{context}"]
 = Monitoring {lvms}
 
-When you use {rh-rhacm} to install {lvms}, you must configure {rh-rhacm} Observability to monitor all the {sno} clusters from one place.
+When you use {rh-rhacm} to install {lvms}, you must configure {rh-rhacm} Observability to monitor all the clusters from one place.
 
 [id="lvms-monitoring-using-lvms-metrics_{context}"]
 == Metrics
diff --git a/modules/lvms-restoring-volume-snapshots-in-single-node-openshift.adoc b/modules/lvms-restoring-volume-snapshots-in-single-node-openshift.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="lvms-restoring-volume-snapshots-in-single-node-openshift_{context}"]
-= Restoring volume snapshots in {sno}
+= Restoring volume snapshots
 
 When you restore a volume snapshot, a new persistent volume claim (PVC) is created.
 The restored PVC is independent of the volume snapshot and the source PVC.
diff --git a/modules/lvms-scaling-storage-of-single-node-open-concept.adoc b/modules/lvms-scaling-storage-of-single-node-open-concept.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: CONCEPT
 [id="lvms-scaling-storage-of-single-node-openshift-cluster-con_{context}"]
-= Scaling storage of {sno} clusters
+= Scaling storage of clusters
 
-The {product-title} supports additional worker nodes for {sno} clusters on bare-metal user-provisioned infrastructure.
+The {product-title} supports additional worker nodes for clusters on bare-metal user-provisioned infrastructure.
 {lvms} detects and uses the new additional worker nodes when the nodes show up.
diff --git a/modules/lvms-scaling-storage-of-single-node-openshift-cluster-using-rhacm.adoc b/modules/lvms-scaling-storage-of-single-node-openshift-cluster-using-rhacm.adoc
@@ -4,20 +4,20 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="lvms-scaling-storage-of-single-node-openshift-cluster-using-rhacm_{context}"]
-= Scaling up storage by adding capacity to your {sno} cluster using {rh-rhacm}
+= Scaling up storage by adding capacity to your cluster using {rh-rhacm}
 
-You can scale the storage capacity of your configured worker nodes on a {sno} cluster using {rh-rhacm}.
+You can scale the storage capacity of your configured worker nodes on a cluster using {rh-rhacm}.
 
 .Prerequisites
 
 * You have access to the {rh-rhacm} cluster using an account with `cluster-admin` privileges.
-* You have additional unused devices on each {sno} cluster that {lvms} can use.
+* You have additional unused devices on each cluster that {lvms} can use.
 
 .Procedure
 
 . Log in to the {rh-rhacm} CLI using your {product-title} credentials.
 . Find the device that you want to add. The device to be added needs to match with the device name and path of the existing devices.
-. To add capacity to the {sno} cluster, edit the `deviceSelector` section of the existing policy YAML, for example, `policy-lvms-operator.yaml`.
+. To add capacity to the cluster, edit the `deviceSelector` section of the existing policy YAML, for example, `policy-lvms-operator.yaml`.
 
 +
 [NOTE]
diff --git a/modules/lvms-scaling-storage-of-single-node-openshift-cluster.adoc b/modules/lvms-scaling-storage-of-single-node-openshift-cluster.adoc
@@ -4,17 +4,17 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="lvms-scaling-storage-of-single-node-openshift-cluster_{context}"]
-= Scaling up storage by adding capacity to your {sno} cluster
+= Scaling up storage by adding capacity to your cluster
 
-To scale the storage capacity of your configured worker nodes on a {sno} cluster, you can increase the capacity by adding disks.
+To scale the storage capacity of your configured worker nodes on a cluster, you can increase the capacity by adding disks.
 
 .Prerequisites
 
-* You have additional unused disks on each {sno} cluster to be used by {lvms}.
+* You have additional unused disks on each cluster to be used by {lvms}.
 
 .Procedure
 
-. Log in to {product-title} console of the {sno} cluster.
+. Log in to {product-title} console of the cluster.
 . From the *Operators* -> *Installed Operators* page, click on the *LVM Storage Operator* in the `openshift-storage` namespace.
 . Click on the *LVMCluster* tab to list the `LVMCluster` CR created on the cluster.
 . Select *Edit LVMCluster* from the *Actions* drop-down menu.
diff --git a/modules/lvms-uninstalling-logical-volume-manager-operator-using-openshift-web-console.adoc b/modules/lvms-uninstalling-logical-volume-manager-operator-using-openshift-web-console.adoc
@@ -14,7 +14,7 @@ You can unstall {lvms} using the Red Hat OpenShift Container Platform Web Consol
 * You deleted the persistent volume claims (PVCs) and persistent volumes (PVs) provisioned using {lvms}.
 * You deleted all volume snapshots provisioned by {lvms}.
 * You verified that no logical volume resources exist by using the `oc get logicalvolume` command.
-* You have access to the {sno} cluster using an account with `cluster-admin` permissions.
+* You have access to the cluster using an account with `cluster-admin` permissions.
 
 .Procedure
 
diff --git a/modules/lvms-upgrading-lvms-on-sno.adoc b/modules/lvms-upgrading-lvms-on-sno.adoc
@@ -4,13 +4,13 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="lvms-upgrading-lvms-on-sno_{context}"]
-= Upgrading {lvms} on {sno} clusters
+= Updating {lvms} on clusters
 
-You can upgrade the {lvms-first} Operator to ensure compatibility with your {sno} version.
+You can update the {lvms-first} Operator to ensure compatibility with your {product-title} version.
 
 .Prerequisites
 
-* You have upgraded your {sno} cluster.
+* You have updated your cluster.
 
 * You have installed a previous version of the {lvms} Operator.
 
@@ -28,7 +28,7 @@ $ oc patch subscription lvms-operator -n openshift-storage --type merge --patch
 ----
 <1> Replace `<update-channel>` with the version of the {lvms} Operator that you want to install, for example `stable-{product-version}`.
 
-. View the upgrade events to check that the installation is complete by running the following command:
+. View the update events to check that the installation is complete by running the following command:
 +
 [source,terminal]
 ----
diff --git a/modules/lvms-volume-clones-in-single-node-openshift.adoc b/modules/lvms-volume-clones-in-single-node-openshift.adoc
@@ -4,6 +4,6 @@
 
 :_mod-docs-content-type: CONCEPT
 [id="lvms-volume-cloning-for-single-node-openshift-cluster_{context}"]
-= Volume cloning for {sno}
+= Volume cloning
 
 A clone is a duplicate of an existing storage volume that can be used like any standard volume.
diff --git a/modules/lvms-volume-snapshots-in-single-node-openshift.adoc b/modules/lvms-volume-snapshots-in-single-node-openshift.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: CONCEPT
 [id="lvms-volume-snapsot-for-sno_{context}"]
-= Volume snapshots for {sno}
+= Volume snapshots
 
 You can take volume snapshots of persistent volumes (PVs) that are provisioned by {lvms}.
 You can also create volume snapshots of the cloned volumes. Volume snapshots help you to do the following:
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
@@ -6,9 +6,9 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-{lvms-first} uses the TopoLVM CSI driver to dynamically provision local storage on {sno} clusters.
+{lvms-first} uses the TopoLVM CSI driver to dynamically provision local storage on the clusters.
 
-{lvms} creates thin-provisioned volumes using Logical Volume Manager and provides dynamic provisioning of block storage on a limited resources {sno} cluster.
+{lvms} creates thin-provisioned volumes using Logical Volume Manager and provides dynamic provisioning of block storage on a limited resources cluster.
 
 //deploying/requirements with RHACM
 include::modules/deploying-lvms-on-sno-cluster.adoc[leveloffset=+1]
@@ -114,9 +114,9 @@ include::modules/lvms-scaling-storage-expand-pvc.adoc[leveloffset=+2]
 [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_logical-volume-manager-storage[Scaling up storage by adding capacity to your 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-scaling-storage-of-single-node-openshift-cluster-using-rhacm_logical-volume-manager-storage[Scaling up storage by adding capacity to your cluster using {rh-rhacm}]
 
 * xref:../../../storage/expanding-persistent-volumes.adoc#add-volume-expansion_expanding-persistent-volumes[Enabling volume expansion support]
 

Original file line number	Diff line number	Diff line change
`@@ -10,7 +10,7 @@ You can install {lvms-first} by using the Red Hat {product-title} OperatorHub.`
`10`	`10`
`11`	`11`	`.Prerequisites`
`12`	`12`
`13`		`-* You have access to the {sno} cluster.`
	`13`	`+* You have access to the cluster.`
`14`	`14`	* You are using an account with the `cluster-admin` and Operator installation permissions.
`15`	`15`
`16`	`16`	`.Procedure`
`@@ -26,7 +26,7 @@ You can install {lvms-first} by using the Red Hat {product-title} OperatorHub.`
`26`	`26`	If the `openshift-storage` namespace does not exist, it is created during the operator installation.
`27`	`27`	`.. Approval Strategy as Automatic or Manual.`
`28`	`28`	`+`
`29`		`-If you select Automatic updates, then the Operator Lifecycle Manager (OLM) automatically upgrades the running instance of your Operator without any intervention.`
	`29`	`+If you select Automatic updates, then the Operator Lifecycle Manager (OLM) automatically updates the running instance of your Operator without any intervention.`
`30`	`30`	`+`
`31`	`31`	`If you select Manual updates, then the OLM creates an update request.`
`32`	`32`	`As a cluster administrator, you must then manually approve that update request to update the Operator to a newer version.`