From 9c38d8a28d997a669514059cd4cb03e9d1ba8410 Mon Sep 17 00:00:00 2001 From: aravipra Date: Fri, 1 Mar 2024 19:13:05 +0530 Subject: [PATCH] OSDOCS-9793: Doc edits in storage vol group and getting started --- microshift_getting_started/microshift-architecture.adoc | 2 +- modules/microshift-lvms-system-requirements.adoc | 7 ++++--- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/microshift_getting_started/microshift-architecture.adoc b/microshift_getting_started/microshift-architecture.adoc index 00d06f26e0..94fe33f4b6 100644 --- a/microshift_getting_started/microshift-architecture.adoc +++ b/microshift_getting_started/microshift-architecture.adoc @@ -43,7 +43,7 @@ The following operational differences from {oke} can help you understand where { .{product-title} differences from {oke}. image::311_RHDevice_Edge_Overview_0223_2.png[<{microshift-short} is tasked with only the Kubernetes cluster capabilities of networking, ingress, storage, helm, with the additional Kubernetes functions of orchestration and security, as the following diagram illustrates.>] -Figure 2 shows that {oke} has the same cluster capabilities as {product-title}, and adds the following: +The figure "{product-title} differences from {oke}" shows that {oke} has the same cluster capabilities as {product-title}, and adds the following information: * Install * Over-the-air updates diff --git a/modules/microshift-lvms-system-requirements.adoc b/modules/microshift-lvms-system-requirements.adoc index 95a2bddc44..222d77b78f 100644 --- a/modules/microshift-lvms-system-requirements.adoc +++ b/modules/microshift-lvms-system-requirements.adoc @@ -11,9 +11,10 @@ Using LVMS in {microshift-short} requires the following system specifications. [id="lvms-volume-group-name_{context}"] == Volume group name -If you did not configure LVMS in an `lvmd.yaml` YAML file placed in the `/etc/microshift/` directory, {microshift-short} attempts to assign a default volume group (VG) dynamically by running the `vgs` command. -* {microshift-short} assigns a default VG when only one VG is found. -* If more than one VG is present, the VG named `microshift` is assigned as the default. +If you did not configure LVMS in an `lvmd.yaml` file placed in the `/etc/microshift/` directory, {microshift-short} attempts to assign a default volume group (VG) dynamically by running the `vgs` command. + +* {microshift-short} assigns a default VG when only one VG is found. +* If more than one VG is present, the VG named `microshift` is assigned as the default. * If a VG named `microshift` does not exist, LVMS is not deployed. If there are no volume groups on the {microshift-short} host, LVMS is disabled.