Skip to content

Pull the changes #11

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 2 commits into from
Sep 17, 2024
Merged

Pull the changes #11

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
994c472
Ricardo's feedback incorporated
Sep 16, 2024
e022759
Merge pull request #10 from RedHatQuickCourses/sapandit-feedback
sarveshpandit Sep 17, 2024
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
10 changes: 5 additions & 5 deletions modules/chapter1/pages/section1.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,8 +87,8 @@ Non-volatile Memory Express (NVMe) is an interface that allows host software uti
On the hypervisor, first create 7TB (3.5TB + 3.5TB disks) logical volume (LV) and mount on storage pool directory path.
This stores VMs images.

There is separate storage virtual machine (VM) for shared storage for _Tenant_ cluster.
Create three disks each of 2TB from the 7TB LV and attach it to storage VM.
There is a separate storage virtual machine (VM) for shared storage for _Tenant_ cluster.
Create three disks each of 2TB from the 7TB LV and attach it to the storage VM.
These disks are needed in Ceph deployment on storage VM.

Next, install https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.16/html/red_hat_openshift_data_foundation_architecture/openshift_data_foundation_operators[OpenShift Data Foundation (ODF) operator,window=read-later] on the _Infrastructure_ clusters.
Expand All @@ -107,17 +107,17 @@ Install following operators on _Hub_ cluster which acts as hub cluster.
* Red Hat Advanced Cluster Management (RHACM)
* Logical Volume Manager Storage (LVMS)

Ensure https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html-single/clusters/index#enable-cim[Provisioning and Central Infrastructure Management (CIM),window=read-later] service are deployed on _Hub_ cluster.
Ensure https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html-single/clusters/index#enable-cim[Provisioning and Central Infrastructure Management (CIM),window=read-later] services are deployed on _Hub_ cluster.

=== Infrastructure Cluster

The main role of _Infrastructure_ clusters is to deploy Nested OpenShift VMs using OpenShift Virtualization.
Each _Infrastructure_ cluster has one virtual machine acts as OpenShift node in _Tenant_ cluster.
Each _Infrastructure_ cluster has one virtual machine that acts as OpenShift node in _Tenant_ cluster.

There are three _Infrastructure_ clusters.
Deploy _Infrastructure_ clusters as _Single Node OpenShift (SNO)_ cluster from _Hub_ cluster using RHACM.

Install https://docs.openshift.com/container-platform/4.16/virt/about_virt/about-virt.html[OpenShift Virtualization,window=read-later], OpenShift Data Foundation (ODF) and nmstate operators on _Infrastructure_ clusters.
Install https://docs.openshift.com/container-platform/4.16/virt/about_virt/about-virt.html[OpenShift Virtualization,window=read-later], OpenShift Data Foundation (ODF) and NMState operators on _Infrastructure_ clusters.

Upload discovery ISO to all _Infrastructure_ clusters to boot the _Tenant_ cluster nodes from discovery ISO.

Expand Down
8 changes: 4 additions & 4 deletions modules/chapter1/pages/section2.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
= Initial Setup on Hypervisor

[NOTE]
You can refer how to configure manually i.e. without automation in at the end appendix chapter.
You can refer to how to configure manually i.e. without automation at the end appendix chapter.

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 is done on the hypervisor.
You will need to perform few tasks before the actual deployment of OpenShift clusters.
Few of the tasks are automated with the help of ansible playbooks.

image::MCAP_setup_1.png[]
Expand Down Expand Up @@ -66,7 +66,7 @@ Ensure you are in *_ansible_* directory of the repo.
ansible-playbook playbooks/setup_hypervisor.yaml -vvv | tee -a /tmp/setup_hypervisor.log
----

Tha above command results in verbose play output.
The above command results in verbose play output.
`tee -a` command redirects the output to `/tmp/setup_hypervisor.log` log file.
In case of failure, `/tmp/setup_hypervisor.log` log file can be used for troubleshooting the issue.

Expand Down
2 changes: 1 addition & 1 deletion modules/chapter1/pages/section4.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
= Ceph Storage Deployment

In this section, you will be deploying Ceph on `storage` VM.
This `storage` VM will be single node and three disks Ceph cluster.
This `storage` VM will be a single node with three disks Ceph cluster.

image::MCAP_setup_3.png[]

Expand Down
4 changes: 2 additions & 2 deletions modules/chapter2/pages/section1.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
= Hub VM Deployment

[NOTE]
You can refer how to configure manually i.e. without automation in at the end appendix chapter.
You can refer to how to configure manually i.e. without automation at the end appendix chapter.

In this section, you will be creating one KVM with the name `hub`.

Expand All @@ -22,6 +22,6 @@ Ensure you are in *_ansible_* directory of the repo.
ansible-playbook playbooks/setup_hub.yaml -vvv | tee -a /tmp/setup_hub.log
----

Tha above command results in verbose play output.
The above command results in verbose play output.
`tee -a` command redirects the output to `/tmp/setup_hub.log` log file.
In case of failure, `/tmp/setup_hub.log` log file can be used for troubleshooting the issue.
8 changes: 4 additions & 4 deletions modules/chapter2/pages/section2.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -202,19 +202,19 @@ Boot the VM, and ensure it is booted with RHEL CoreOS (Live).
image::hub_vm_5.png[]

. Go back to https://console.redhat.com/openshift/cluster-list[console.redhat.com] to resume assisted installation of _Hub_ cluster.
Notice the host is getting discovered and status as `Ready`.
Notice the host is getting discovered and status is `Ready`.
+
Click btn:[Next].
+
image::console_redhat_host_discovery_ready.png[]
+
It may take few minutes to update status as `Ready`.

. Once status is `Ready`, click btn:[Next].
. In storage section, once status is `Ready`, click btn:[Next].
+
image::console_redhat_storage.png[]

. Once status is `Ready`, click btn:[Next].
. In networking section, once status is `Ready`, click btn:[Next].
+
image::console_redhat_networking.png[]

Expand Down Expand Up @@ -254,6 +254,6 @@ image::console_redhat_install_proceed.png[]
+
image::console_redhat_cluster_install_finalizing.png[]

. Installation completes in approximately in 15 minutes.
. Installation completes in approximately 15 minutes.
+
image::console_redhat_install_complete.png[]
4 changes: 2 additions & 2 deletions modules/chapter2/pages/section3.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ dr-xr-x---. 13 root root 4096 Aug 22 15:18 ..
-rw-r--r--. 1 root root 12127 Aug 22 15:20 kubeconfig
----

. Get the `kubeconfig` file, password for `kubeadmin` user and web console url from console.redhat.com.
. Get the `kubeconfig` file, the password for `kubeadmin` user, and the web console URL from console.redhat.com.
+
image::console_redhat_install_download.png[]

Expand Down Expand Up @@ -136,7 +136,7 @@ Get the `kubadmin` user's passwrod from `/root/hub/kubeadmin-password` file.
+
image::vnc_hub_cluster_access_3.png[]

. Once you logged in as `kubadmin` user, this is how the first screen looks like.
. Once you logged in as `kubadmin` user, this is what the first screen looks like.
+
image::vnc_hub_cluster_access_4.png[]

Expand Down
2 changes: 1 addition & 1 deletion modules/chapter3/pages/index.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,5 +5,5 @@ This chapter covers deployment of the _Infrastructure_ clusters.
Chapter goals:

* Deploy Single Node OpenShift (SNO) clusters as KVMs on bare metal using RHACM from _Hub_ cluster.
* Install OpenShift Virtualization, OpenShift DataFoundation and nmstate operators on _Infrastructure_ clusters.
* Install OpenShift Virtualization, OpenShift DataFoundation and NMState operators on _Infrastructure_ clusters.
* Configure necessary network settings on _Infrastructure_ clusters.
4 changes: 2 additions & 2 deletions modules/chapter3/pages/section1.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
= Infrastructure VMs Deployment

[NOTE]
You can refer how to configure manually i.e. without automation in at the end appendix chapter.
You can refer to how to configure manually i.e. without automation at the end appendix chapter.

In this section, you will be creating three KVMs with name `sno1`, `sno2` and `sno3`.

Expand All @@ -22,6 +22,6 @@ Ensure you are in *_ansible_* directory of the repo.
ansible-playbook playbooks/setup_sno.yaml -vvv | tee -a /tmp/setup_sno.log
----

Tha above command results in verbose play output.
The above command results in verbose play output.
`tee -a` command redirects the output to `/tmp/setup_sno.log` log file.
In case of failure, `/tmp/setup_sno.log` log file can be used for troubleshooting the issue.
4 changes: 2 additions & 2 deletions modules/chapter3/pages/section2.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ image::MCAP_setup_1.png[]

. Set the OpenShift `clusterimageset` to 4.16.8 on stable channel.
+
This will allow to deploy the _Infrastructure_ and _Tenant_ clusters with same OpenShift version.
This will allow you to deploy the _Infrastructure_ and _Tenant_ clusters with same OpenShift version.

.. Get the images with _visible_ label as _true_ from `clusterimageset`.
+
Expand Down Expand Up @@ -105,7 +105,7 @@ Base domain: `lab.example.com`
+
Select `4.16.8` version of OpenShift from the menu.
+
Check box the `Install single node OpenShift (SNO)`
Check the box `Install single node OpenShift (SNO)`.
+
image::hub_console_sno1_details.png[]

Expand Down
Loading