Skip to content

Commit 573ff6c

Browse files
authored
Merge pull request #57417 from dhellmann/lvms-config-changes
OSDOCS-5562: update info about default LVMS behavior
2 parents 94fb9c2 + a40173c commit 573ff6c

File tree

2 files changed

+9
-3
lines changed

2 files changed

+9
-3
lines changed

modules/microshift-lvms-system-requirements.adoc

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,13 @@ Using LVMS in {product-title} requires the following system specifications.
1111
[id="lvms-volume-group-name_{context}"]
1212
== Volume Group Name
1313

14-
The default integration of LVMS uses a volume group named `rhel`. You can change the default name of the volume group in the configuration file. For details, read the "Configuring the LVMS" section of this document.
14+
The default integration of LVMS selects the default volume group dynamically. If there are no volume groups on the {product-title} host, LVMS is disabled.
15+
16+
If there is only one volume group on the {product-title} host, that volume group is used. If there are multiple volume groups, the group `microshift` is used. If the `microshift` group is not found, LVMS is disabled.
17+
18+
If you want to use a specific volume group, LVMS must be configured to select that volume group. You can change the default name of the volume group in the configuration file. For details, read the "Configuring the LVMS" section of this document.
19+
20+
You can change the default name of the volume group in the configuration file. For details, read the "Configuring the LVMS" section of this document.
1521

1622
Prior to launching, the `lvmd.yaml` configuration file must specify an existing volume group on the node with sufficient capacity for workload storage. If the volume group does not exist, the node controller fails to start and enters a `CrashLoopBackoff` state.
1723

@@ -24,4 +30,4 @@ The LVMS provisions storage in increments of 1 gigabyte (GB). Storage requests a
2430
----
2531
Warning ProvisioningFailed 3s (x2 over 5s) topolvm.cybozu.com_topolvm-controller-858c78d96c-xttzp_0fa83aef-2070-4ae2-bcb9-163f818dcd9f failed to provision volume with
2632
StorageClass "topolvm-provisioner": rpc error: code = ResourceExhausted desc = no enough space left on VG: free=(BYTES_INT), requested=(BYTES_INT)
27-
----
33+
----

modules/microshift-using-lvms.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Use the following procedure to provision and mount a logical volume to a pod.
1616
+
1717
[source,terminal]
1818
----
19-
$ cat <<'EOF' | oc apply -f -
19+
$ cat <<EOF | oc apply -f -
2020
kind: PersistentVolumeClaim
2121
apiVersion: v1
2222
metadata:

0 commit comments

Comments
 (0)