RedHatQuickCourses · sarveshpandit · Sep 27, 2024 · Sep 27, 2024 · Sep 27, 2024 · sarveshpandit
diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc
@@ -27,7 +27,7 @@ When ordering this catalog item in RHDP:
 
 . Select *Practice/Enablement* for the *Activity* field.
 . Select the nearest or any region in the *Region* field.
-. Select *n3.xlarge.x86* as the flavor in *Type* field.
+. Select *n3.xlarge.x86* as the flavor in the  *Type* field.
 
 === Red Hat Partners
 
@@ -45,7 +45,7 @@ For this course, you should have:
 * https://rol.redhat.com/rol/app/courses/do280-4.14[Red Hat OpenShift Administration II: Configuring a Production Cluster (DO280),window=read-later], or equivalent knowledge on configuring a production Red Hat OpenShift cluster.
 * https://rol.redhat.com/rol/app/technical-overview/do016-4.14[Red Hat OpenShift Virtualization (OCP Virt) Technical Overview (DO016),window=read-later]
 * https://rol.redhat.com/rol/app/courses/do316-4.14[Managing Virtual Machines with Red Hat OpenShift Virtualization (DO316),window=read-later], or equivalent knowledge on how to create virtual machines on Red Hat OpenShift cluster using Red Hat OpenShift Virtualization.
-* Knowledge on installing Red Hat Advanced Cluster Management (RHACM) operator
+* Knowledge of installing Red Hat Advanced Cluster Management (RHACM) operator
 
 == Objectives
 

diff --git a/modules/appendix/pages/section1.adoc b/modules/appendix/pages/section1.adoc
@@ -1,7 +1,7 @@
 = Initial Setup on Hypervisor without Automation
 
-Before proceeding the actual MCAP deployment, let's first ensure the initial setup and configuration is done on the hypervisor.
-You will need to perform few tasks before actual deployment of openshift clusters.
+Before proceeding with the actual MCAP deployment, let's first ensure the initial setup and configuration are done on the hypervisor.
+You will need to perform a few tasks before the actual deployment of openshift clusters.
 
 image::MCAP_setup_1.png[]
 
@@ -20,10 +20,10 @@ Login as `root` on the hypervisor.
 
 == Setup and Configuration without Automation
 
-=== Create SSH key for the root user
+=== Create an SSH key for the root user
 
 The public key from the following command will be used while deploying _Hub_ and _Infrastructure_ clusters.
-You will be asked for public key while building the discovery iso for the host.
+You will be asked for a public key while building the discovery iso for the host.
 
 [source,bash,role=execute]
 ----
@@ -32,8 +32,8 @@ ssh-keygen -t rsa -f /root/.ssh/id_rsa -N ''
 
 === Install the required packages
 
-The following required packages needed for DHCP server, HTTP server, DNS server, VNC server and creating virtual machines on hypervisor.
-It also include additional tools packages.
+The following required packages are needed for DHCP server, HTTP server, DNS server, VNC server, and creating virtual machines on the hypervisor.
+It also includes additional tools and packages.
 
 [source,bash,role=execute]
 ----
@@ -44,9 +44,9 @@ libguestfs-tools-c cockpit cockpit-machines unzip tigervnc tigervnc-server firef
 
 === Increase the _Swap_ space
 
-_Swap_ space is extension of physical RAM.
+_Swap_ space is an extension of physical RAM.
 It offers virtual memory in case of physical RAM is fully used.
-MCAP needs considerable amount of memory and it is recommended to have proportionate amount of _Swap_ space configured in an environment.
+MCAP needs a considerable amount of memory and it is recommended to have a proportionate amount of _Swap_ space configured in an environment.
 
 . Disable the existing _Swap_ first.
 +
@@ -55,7 +55,7 @@ MCAP needs considerable amount of memory and it is recommended to have proportio
 swapoff -a
 ----
 +
-Check the _Swap_ space using `free` command.
+Check the _Swap_ space using the `free` command.
 +
 .Sample output
 ----
@@ -93,7 +93,7 @@ Here `nvme1n1` disk can be used to create the swap space.
 The NVMe disk sequencing used as an OS partition will change, whenever you provision the catalog.
 The unused NVMe disk may vary in your environment output.
 
-. Use unused 250GB nvme disk as swap partition.
+. Use unused 250GB nvme disk as a swap partition.
 +
 [source,bash,role=execute]
 ----
@@ -111,7 +111,7 @@ The above UUID may differ in your environment.
 
 . Add swap entry in `/etc/fstab` to make it persistent throughout the reboot.
 +
-Ensure to replace the UUID in following command with UUID from previous step.
+Ensure to replace the UUID in following command with the UUID from the previous step.
 +
 [source,bash,role=execute]
 ----
@@ -147,7 +147,7 @@ Swap:          238Gi          0B       238Gi
 
 === Create LV for VM storage pool
 
-The LV created in this section will be used as storage pool for virtual machine disks and backend shared OpenShift DataFoundation using Red Hat Ceph storage for _Tenant_ cluster.
+The LV created in this section will be used as a storage pool for virtual machine disks and backend-shared OpenShift DataFoundation using Red Hat Ceph storage for the _Tenant_ cluster.
 
 . Find the 3.5TB nvme disks.
 +
@@ -229,14 +229,14 @@ The above UUID may differ in your environment.
 
 . Mount the 7TB LV on `/var/lib/libvirt/images`.
 +
-Ensure to replace the UUID in following command with UUID from previous step.
+Ensure to replace the UUID in the following command with UUID from the previous step.
 +
 [source,bash,role=execute]
 ----
 echo "UUID=195dc91e-58be-4671-bbf5-b4fdf70945e2	/var/lib/libvirt/images	ext4	errors=remount-ro	0	1" >> /etc/fstab
 ----
 +
-Run `mount` command to mount the LV on `/var/lib/libvirt/images`.
+Run the `mount` command to mount the LV on `/var/lib/libvirt/images`.
 +
 [source,bash,role=execute]
 ----
@@ -273,7 +273,7 @@ After enabling and starting the libvirt services, `virbr0` bridge will be create
 You can verify it by running the `ip addr` command.
 
 After enabling and starting the cockpit services, it creates cockpit web console access.
-You can login to cockpit web console with `lab-user's` credentials.
+You can log in to the cockpit web console with the `lab-user's` credentials.
 
 [source,bash,role=execute]
 ----
@@ -300,7 +300,7 @@ You can use the cockpit web console (https://<your_hypervisor_IP>:9090/) to moni
 
 === Configure DHCP
 
-It is recommended to have DHCP server.
+It is recommended to have the DHCP server.
 In this section, you will be configuring the DHCP server.
 
 . Create the `/etc/dhcp/dhcpd.conf` file.
@@ -393,7 +393,7 @@ systemctl start dhcpd
 
 === Configure DNS
 
-To have name resolution, DNS server is needed.
+To have name resolution, the DNS server is needed.
 In this section, you will be configuring the DNS server.
 
 . Create the `/etc/named.conf` file.
@@ -692,9 +692,9 @@ dig sno1.lab.example.com
 === Configure HTTP
 
 The HTTP server is needed to serve the ignition configuration files.
-These ignition configuration files will be pulled from HTTP server during the openshift node installation.
+These ignition configuration files will be pulled from the HTTP server during the openshift node installation.
 In this section, you will be configuring the HTTP server.
-There are multiple ways to configure the HTTP server but here directory from user's home directory holds the files.
+There are multiple ways to configure the HTTP server but here directory from the user's home directory holds the files.
 
 . Create the `/etc/httpd/conf.d/userdir.conf` file.
 +
@@ -818,7 +818,7 @@ rm /home/lab-user/public_html/cmd
 [NOTE]
 "HTTP/1.1 200 OK" indicates http server is working.
 
-=== Create Storage Pool for KVMs
+=== Create a Storage Pool for KVMs
 
 All five KVMs need the storage pool for storing the VM disks.
 In this section, you will be creating the storage pool.

diff --git a/modules/appendix/pages/section2.adoc b/modules/appendix/pages/section2.adoc
@@ -8,7 +8,7 @@ image::MCAP_setup_2.png[]
 
 . Download the `rhel-9.4-x86_64-kvm.qcow2` image from the https://access.redhat.com/downloads/content/rhel[Red Hat Customer Portal,window=read-later] to your laptop/desktop.
 
-. Use secured copy (scp) to copy the `rhel-9.4-x86_64-kvm.qcow2` image from your laptop/desktop to hypervisor and then place it in `/root` directory.
+. Use secured copy (scp) to copy the `rhel-9.4-x86_64-kvm.qcow2` image from your laptop/desktop to the hypervisor and then place it in `/root` directory.
 +
 .Sample output
 ----
@@ -63,7 +63,7 @@ cluster_size: 65536
 ...output omitted...
 ----
 
-. Resize the image with additional size of 30G.
+. Resize the image with an additional size of 30G.
 +
 [source,bash,role=execute]
 ----
@@ -72,7 +72,7 @@ qemu-img resize rhel-9.4-x86_64-kvm.qcow2 +30G
 +
 This increases the virtual size of the disk.
 +
-Ensure virtual size is increased by 30GB.
+Ensure the virtual size is increased by 30GB.
 +
 .Sample output
 ----
@@ -121,7 +121,7 @@ https://access.redhat.com/solutions/57263[How to extend a XFS filesytem using th
 virt-customize -a rhel-9.4-x86_64-kvm.qcow2 --root-password password:redhat
 ----
 +
-You can use this password for logging into VM via console.
+You can use this password for logging into VM via the console.
 
 . Disable the `cloud-init` service in qcow2 image.
 +
@@ -207,7 +207,7 @@ Domain 'storage' started
 
 ----
 +
-Verify `storage` VM is in `running` state.
+Verify `storage` VM is in a `running` state.
 +
 .Sample output
 ----

diff --git a/modules/appendix/pages/section3.adoc b/modules/appendix/pages/section3.adoc
@@ -1,12 +1,12 @@
 = Hub VM Deployment without Automation
 
-In this section, you will be creating one KVM with name `hub`.
+In this section, you will be creating one KVM with the name `hub`.
 
 image::MCAP_setup_3.png[]
 
 == Prerequisites
 
-Copy the `rhel-9.4-x86_64-kvm.qcow2` image from `/root` and place it in /var/lib/libvirt/images directory with name as `rhel9-guest.qcow2`.
+Copy the `rhel-9.4-x86_64-kvm.qcow2` image from `/root` and place it in /var/lib/libvirt/images directory with the name as `rhel9-guest.qcow2`.
 
 .Sample output
 ----
@@ -48,7 +48,7 @@ cluster_size: 65536
 ...output omitted...
 ----
 
-. Resize the image with additional size of 120G.
+. Resize the image with an additional size of 120G.
 +
 [source,bash,role=execute]
 ----
@@ -57,7 +57,7 @@ qemu-img resize rhel9-guest.qcow2 +120G
 +
 This increases the virtual size of the disk.
 +
-Ensure virtual size is increased by 120GB.
+Ensure the virtual size is increased by 120GB.
 +
 .Sample output
 ----
@@ -107,7 +107,7 @@ https://access.redhat.com/solutions/57263[How to extend a XFS filesytem using th
 virt-customize -a rhel9-guest.qcow2 --root-password password:redhat
 ----
 +
-You can use this password for logging into VM via console.
+You can use this password for logging into the VM via the console.
 
 . Disable the `cloud-init` service in qcow2 image.
 +
@@ -130,7 +130,7 @@ virt-customize -a rhel9-guest.qcow2 --ssh-inject root:file:/root/.ssh/id_rsa.pub
 virt-customize -a rhel9-guest.qcow2 --selinux-relabel
 ----
 
-. Create the image for `hub` VM using the _rhel9.X_ qcow2 image.
+. Create the image for the `hub` VM using the _rhel9.X_ qcow2 image.
 +
 [source,bash,role=execute]
 ----
@@ -144,7 +144,7 @@ Formatting '/var/lib/libvirt/images/hub.qcow2', fmt=qcow2 cluster_size=65536 ext
 
 . Create the `hub` VM with three 2TB disks.
 Disk path should be storage pool path i.e. `/var/lib/libvirt/images/`.
-mac address for the `hub` VM should be same as from the dhcp configuration.
+mac address for the `hub` VM should be the same as from the dhcp configuration.
 +
 [source,bash,role=execute]
 ----
@@ -190,7 +190,7 @@ Domain 'hub' started
 
 ----
 +
-Verify `hub` VM is in `running` state.
+Verify `hub` VM is in a `running` state.
 +
 .Sample output
 ----
@@ -204,7 +204,7 @@ virsh list --all
 
 . Verify `hub` VM is booted successfully.
 +
-Take the console of the `hub` VM and login as _root_ user with _redhat_ as password.
+Take the console of the `hub` VM and log in as _root_ user with _redhat_ as the password.
 +
 [source,bash,role=execute]
 ----

diff --git a/modules/appendix/pages/section4.adoc b/modules/appendix/pages/section4.adoc
@@ -1,12 +1,12 @@
 = Infrastructure VM Deployment without Automation
 
-In this section, you will be creating three KVMs with name `sno1`, `sno2` and `sno3`.
+In this section, you will be creating three KVMs with the name `sno1`, `sno2`, and `sno3`.
 
 image::MCAP_setup_4.png[]
 
 == Prerequisites
 
-Copy the `rhel-9.4-x86_64-kvm.qcow2` image from `/root` and place it in `/var/lib/libvirt/images` directory with name as `rhel9-guest-sno.qcow2`.
+Copy the `rhel-9.4-x86_64-kvm.qcow2` image from `/root` and place it in `/var/lib/libvirt/images` directory with the name `rhel9-guest-sno.qcow2`.
 
 .Sample output
 ----
@@ -48,7 +48,7 @@ cluster_size: 65536
 ...output omitted...
 ----
 
-. Resize the image with additional size of 120G.
+. Resize the image with an additional size of 120G.
 +
 [source,bash,role=execute]
 ----
@@ -57,7 +57,7 @@ qemu-img resize rhel9-guest-sno.qcow2 +120G
 +
 This increases the virtual size of the disk.
 +
-Ensure virtual size is increased by 120GB.
+Ensure the virtual size is increased by 120GB.
 +
 .Sample output
 ----
@@ -107,7 +107,7 @@ https://access.redhat.com/solutions/57263[How to extend a XFS filesytem using th
 virt-customize -a rhel9-guest-sno.qcow2 --root-password password:redhat
 ----
 +
-You can use this password for logging into VM via console.
+You can use this password for logging into the VM via the console.
 
 . Disable the `cloud-init` service in qcow2 image.
 +
@@ -165,7 +165,7 @@ Formatting '/var/lib/libvirt/images/sno2.qcow2', fmt=qcow2 cluster_size=65536 ex
 Formatting '/var/lib/libvirt/images/sno3.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off compression_type=zlib size=139586437120 backing_file=/var/lib/libvirt/images/rhel9-guest-sno.qcow2 backing_fmt=qcow2 lazy_refcounts=off refcount_bits=16
 ----
 
-. Create the `sno1`, `sno2` and `sno3` VMs.
+. Create the `sno1`, `sno2`, and `sno3` VMs.
 Disk path should be storage pool path i.e. `/var/lib/libvirt/images/`.
 mac address for the `sno1`, `sno2` and `sno3` VMs should be same as from the dhcp configuration.
 +
@@ -229,7 +229,7 @@ You can restart your domain by running:
   virsh --connect qemu:///system start sno3
 ----
 +
-Verify `sno1`, `sno2` and `sno3` VMs are created and in `shut off` state.
+Verify that `sno1`, `sno2` and `sno3` VMs are created and are in `shut off` state.
 +
 .Sample output
 ----
@@ -244,7 +244,7 @@ virsh list --all
  -    sno3      shut off
 ----
 
-. Start the `sno1`, `sno2` and `sno3` VMs.
+. Start the `sno1`, `sno2`, and `sno3` VMs.
 +
 [source,bash,role=execute]
 ----
@@ -261,7 +261,7 @@ Domain 'sno3' started
 
 ----
 +
-Verify `sno1`, `sno2` and `sno3` VMs are in `running` state.
+Verify `sno1`, `sno2`, and `sno3` VMs are in `running` state.
 +
 .Sample output
 ----
@@ -276,9 +276,9 @@ virsh list --all
  25   sno3      running
 ----
 
-. Verify `sno1`, `sno2` and `sno3` VMs are booted successfully.
+. Verify `sno1`, `sno2` and, `sno3` VMs are booted successfully.
 +
-Take the console of the `sno1`, `sno2` and `sno3` VMs and login as _root_ user with _redhat_ as password.
+Take the console of the `sno1`, `sno2`, and `sno3` VMs and login as _root_ user with _redhat_ as password.
 +
 [source,bash,role=execute]
 ----
@@ -297,4 +297,4 @@ Password:
 [root@sno1 ~]#
 ----
 +
-Similarly verify `sno2` and `sno3` VMs are booted successfully.
+Similarly, verify that `sno2` and `sno3` VMs are booted successfully.