Skip to content

[enterprise-4.13] OCPBUGS#23193: Added info on deviceClass #70613

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 22, 2024
Merged

[enterprise-4.13] OCPBUGS#23193: Added info on deviceClass #70613

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 0 additions & 5 deletions modules/deploying-lvms-on-sno-cluster.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,11 +30,6 @@ Before you begin deploying {lvms} on {sno} clusters, ensure that the following r
* You have installed {rh-rhacm-first} on an {product-title} cluster.
* Every managed {sno} cluster has dedicated disks that are used to provision storage.

Before you deploy {lvms} on {sno} clusters, 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

Expand Down
8 changes: 7 additions & 1 deletion modules/lvms-creating-logical-volume-manager-cluster.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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]
Expand Down Expand Up @@ -66,6 +71,7 @@ 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> Mandatory: The `LVMCluster` resource must contain a single default storage class. Set `default: false` for secondary device storage classes.
Expand Down