OSDOCS-12579: Updated the Installing OpenShift on a single node

Author: dfitzmau

installing/installing_sno/install-sno-installing-sno.adoc

@@ -7,7 +7,9 @@ include::_attributes/common-attributes.adoc[]
 toc::[]
 
 ifndef::openshift-origin[]
-You can install {sno} using the web-based Assisted Installer and a discovery ISO that you generate using the Assisted Installer. You can also install {sno} by using `coreos-installer` to generate the installation ISO.
+You can install {sno} by using either the web-based Assisted Installer or the `coreos-installer` tool to generate a discovery ISO image. The discovery ISO image writes the {op-system-first} system configuration to the target installation disk, so that you can run a single-cluster node to meet your needs.
+
+Consider using {sno} when you want to run a cluster in a low-resource or an isolated environment for testing, troubleshooting, training, or small-scale project purposes.
 
 [id="installing-sno-assisted-installer"]
 == Installing {sno} using the Assisted Installer
@@ -24,6 +26,7 @@ include::modules/install-sno-generating-the-discovery-iso-with-the-assisted-inst
 * xref:../../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#persistent-storage-using-lvms_logical-volume-manager-storage[Persistent storage using logical volume manager storage]
 * xref:../../virt/about_virt/about-virt.adoc#virt-what-you-can-do-with-virt_about-virt[What you can do with OpenShift Virtualization]
 
+// Installing single-node OpenShift with the Assisted Installer
 include::modules/install-sno-installing-with-the-assisted-installer.adoc[leveloffset=+2]
 endif::openshift-origin[]
 
@@ -80,6 +83,7 @@ include::modules/install-sno-generating-the-install-iso-manually.adoc[leveloffse
 * See xref:../../installing/overview/cluster-capabilities.adoc#cluster-capabilities[Cluster capabilities] for more information about enabling cluster capabilities that were disabled before installation.
 * See xref:../../installing/overview/cluster-capabilities.adoc#explanation_of_capabilities_cluster-capabilities[Optional cluster capabilities in {product-title} {product-version}] for more information about the features provided by each capability.
 
+// Monitoring the cluster installation using openshift-install
 include::modules/install-sno-monitoring-the-installation-manually.adoc[leveloffset=+2]
 
 [role="_additional-resources"]

modules/creating-manifest-file-customized-br-ex-bridge.adoc

@@ -149,7 +149,7 @@ spec:
 endif::postinstall-bare-metal-ipi,postinstall-bare-metal-upi[]
 
 ifdef::postinstall-bare-metal-ipi,postinstall-bare-metal-upi[]
-. Create a `NodeNetworkConfigurationPolicy` (NNCP) CR and define a customized `br-ex` bridge network configuration. Depending on your needs, ensure that you set a masquerade IP for either the `ipv4.address.ip`, `ipv6.address.ip`, or both parameters. A masquerade IP address must match an in-use IP address block.
+* Create a `NodeNetworkConfigurationPolicy` (NNCP) CR and define a customized `br-ex` bridge network configuration. Depending on your needs, ensure that you set a masquerade IP for either the `ipv4.address.ip`, `ipv6.address.ip`, or both parameters. A masquerade IP address must match an in-use IP address block.
 +
 .Example of an NNCP CR that sets IPv6 and IPv4 masquerade IP addresses
 [source,yaml]

modules/install-sno-additional-requirements-for-installing-sno-on-a-cloud-provider.adoc

@@ -9,7 +9,7 @@ ifndef::openshift-origin[]
 
 The documentation for installer-provisioned installation on cloud providers is based on a high availability cluster consisting of three control plane nodes. When referring to the documentation, consider the differences between the requirements for a {sno} cluster and a high availability cluster.
 
-* A high availability cluster requires a temporary bootstrap machine, three control plane machines, and at least two compute machines. For a {sno} cluster, you need only a temporary bootstrap machine and one cloud instance for the control plane node and no worker nodes.
+* A high availability cluster requires a temporary bootstrap machine, three control plane machines, and at least two compute machines. For a {sno} cluster, you need only a temporary bootstrap machine and one cloud instance for the control plane node and no compute nodes.
 
 * The minimum resource requirements for high availability cluster installation include a control plane node with 4 vCPUs and 100GB of storage. For a {sno} cluster, you must have a minimum of 8 vCPUs and 120GB of storage.
 endif::openshift-origin[]

modules/install-sno-generating-the-discovery-iso-with-the-assisted-installer.adoc

@@ -12,7 +12,7 @@ Installing {product-title} on a single node requires a discovery ISO, which the
 
 . On the administration host, open a browser and navigate to link:https://console.redhat.com/openshift/assisted-installer/clusters[{cluster-manager-first}].
 
-. Click *Create Cluster* to create a new cluster.
+. Click *Create New Cluster* to create a new cluster.
 
 . In the *Cluster name* field, enter a name for the cluster.
 
@@ -25,7 +25,7 @@ example.com
 All DNS records must be subdomains of this base domain and include the cluster name, for example:
 +
 ----
-<cluster-name>.example.com
+<cluster_name>.example.com
 ----
 +
 [NOTE]
@@ -35,9 +35,11 @@ You cannot change the base domain or cluster name after cluster installation.
 
 . Select *Install single node OpenShift (SNO)* and complete the rest of the wizard steps. Download the discovery ISO.
 
-. Make a note of the discovery ISO URL for installing with virtual media.
-
-[NOTE]
+. Complete the remaining Assisted Installer wizard steps.
++
+[IMPORTANT]
 =====
+Ensure that you take note of the discovery ISO URL for installing with virtual media.
+
 If you enable {VirtProductName} during this process, you must have a second local storage device of at least 50GiB for your virtual machines.
 =====

modules/install-sno-generating-the-install-iso-manually.adoc

@@ -24,7 +24,7 @@ ifndef::openshift-origin[]
 +
 [source,terminal]
 ----
-$ OCP_VERSION=<ocp_version> <1>
+$ export OCP_VERSION=<ocp_version> <1>
 ----
 +
 <1> Replace `<ocp_version>` with the current version, for example, `latest-{product-version}`
@@ -44,7 +44,7 @@ endif::openshift-origin[]
 +
 [source,terminal]
 ----
-$ ARCH=<architecture> <1>
+$ export ARCH=<architecture> <1>
 ----
 <1> Replace `<architecture>` with the target host architecture, for example, `aarch64` or `x86_64`.
 
@@ -116,7 +116,7 @@ $ chmod +x openshift-install
 +
 [source,terminal]
 ----
-$ ISO_URL=$(./openshift-install coreos print-stream-json | grep location | grep $ARCH | grep iso | cut -d\" -f4)
+$ export ISO_URL=$(./openshift-install coreos print-stream-json | grep location | grep $ARCH | grep iso | cut -d\" -f4)
 ----
 
 ifndef::openshift-origin[]

modules/install-sno-installing-with-the-assisted-installer.adoc

@@ -8,18 +8,22 @@
 
 Use the Assisted Installer to install the single-node cluster.
 
+.Prerequisites
+
+* Ensure that the boot drive order in the server BIOS settings defaults to booting the server from the target installation disk.
+
 .Procedure
 
-. Attach the {op-system} discovery ISO to the target host.
+. Attach the discovery ISO image to the target host.
 
-. Configure the boot drive order in the server BIOS settings to boot from the attached discovery ISO and then reboot the server.
+. Boot the server from the discovery ISO image. The discovery ISO image writes the system configuration to the target installation disk and automatically triggers a server restart.
 
 . On the administration host, return to the browser. Wait for the host to appear in the list of discovered hosts. If necessary, reload the link:https://console.redhat.com/openshift/assisted-installer/clusters[*Assisted Clusters*] page and select the cluster name.
 
 . Complete the install wizard steps. Add networking details, including a subnet from the available subnets. Add the SSH public key if necessary.
 
 . Monitor the installation's progress. Watch the cluster events. After the installation process finishes writing the operating system image to the server's hard disk, the server restarts.
 
-. Remove the discovery ISO, and reset the server to boot from the installation drive.
+. Optional: Remove the discovery ISO image.
 +
 The server restarts several times automatically, deploying the control plane.

modules/install-sno-monitoring-the-installation-manually.adoc

@@ -8,11 +8,15 @@
 
 Use `openshift-install` to monitor the progress of the single-node cluster installation.
 
+.Prerequisites
+
+* Ensure that the boot drive order in the server BIOS settings defaults to booting the server from the target installation disk.
+
 .Procedure
 
-. Attach the modified {op-system} installation ISO to the target host.
+. Attach the discovery ISO image to the target host.
 
-. Configure the boot drive order in the server BIOS settings to boot from the attached discovery ISO and then reboot the server.
+. Boot the server from the discovery ISO image. The discovery ISO image writes the system configuration to the target installation disk and automatically triggers a server restart.
 
 . On the administration host, monitor the installation by running the following command:
 ifndef::openshift-origin[]
@@ -29,6 +33,8 @@ ifdef::openshift-origin[]
 $ ./openshift-install --dir=sno wait-for install-complete
 ----
 endif::openshift-origin[]
+
+. Optional: Remove the discovery ISO image.
 +
 The server restarts several times while deploying the control plane.