diff --git a/4.14/lab-environment.html b/4.14/lab-environment.html index bff9159..6120658 100644 --- a/4.14/lab-environment.html +++ b/4.14/lab-environment.html @@ -988,6 +988,9 @@

Con systemctl enable podman-webcache --now +
+

Verify that the webcache container has started successfully by executing podman ps. If it is not running, check the status of the podman-webcache systemd unit.

+

Install Ksushy Tool

@@ -1010,6 +1013,9 @@

Ins

+
+

Verify that the ksushy service is running. Furthermore, you can check that the port number 9000 TCP is being used by a python application (ksushy) by executing netstat -lntp | grep 9000.

+

Configure Disconnected Registry

@@ -1027,6 +1033,7 @@

https://raw.githubusercontent.com/RHsyseng/5g-ran-deployments-on-ocp-lab/lab-4.14/lab-materials/lab-env-data/gitea/podman-gitea.service -o /etc/systemd/system/podman-gitea.service systemctl daemon-reload systemctl enable podman-gitea --now -sleep 10 +sleep 20 podman exec --user 1000 gitea /bin/sh -c 'gitea admin user create --username student --password student --email student@5g-deployment.lab --must-change-password=false --admin' curl -u 'student:student' -H 'Content-Type: application/json' -X POST --data '{"service":"2","clone_addr":"https://github.com/RHsyseng/5g-ran-deployments-on-ocp-lab.git","uid":1,"repo_name":"5g-ran-deployments-on-ocp-lab"}' http://infra.5g-deployment.lab:3000/api/v1/repos/migrate curl -u 'student:student' -H 'Content-Type: application/json' -X POST --data '{"service":"2","clone_addr":"https://github.com/RHsyseng/5g-ran-lab-aap-integration-tools.git","uid":1,"repo_name":"aap-integration-tools"}' http://infra.5g-deployment.lab:3000/api/v1/repos/migrate @@ -1105,7 +1112,41 @@

-

After that you need to add the following entries to your local /etc/hosts file:

+

Verify that the haproxy systemd unit started successfully. After that, you need to add the following entries to your laptop’s local /etc/hosts file. This line will help you to connect to the different exposed services that are being set in the lab host. Notice that:

+

+
+
    +
  • +

    HYPERVISOR_REACHABLE_IP is the IP address of the lab server you are configuring. It must be an IP address that you can connect from your laptop, usually the IP address you are using to connect via SSH to the lab server.

    +
    • +
+
+
+

For example, your lab server now should have similar interfaces (podman, virbr0 and 5gdeploymentlab) as my lab:

+
+
+
+
ip -o a
+1: lo    inet 127.0.0.1/8 scope host lo\       valid_lft forever preferred_lft forever
+1: lo    inet6 ::1/128 scope host \       valid_lft forever preferred_lft forever
+2: ens1f0    inet 10.19.32.199/26 brd 10.19.32.255 scope global dynamic noprefixroute ens1f0\       valid_lft 13481sec preferred_lft 13481sec
+2: ens1f0    inet6 2620:52:0:1343::8d/128 scope global dynamic noprefixroute \       valid_lft 13481sec preferred_lft 13481sec
+2: ens1f0    inet6 2620:52:0:1343:e643:4bff:febd:9046/64 scope global dynamic noprefixroute \       valid_lft 2591777sec preferred_lft 604577sec
+2: ens1f0    inet6 fe80::e643:4bff:febd:9046/64 scope link noprefixroute \       valid_lft forever preferred_lft forever
+6: virbr0    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0\       valid_lft forever preferred_lft forever
+7: 5gdeploymentlab    inet 192.168.125.1/24 brd 192.168.125.255 scope global 5gdeploymentlab\       valid_lft forever preferred_lft forever
+8: podman0    inet 10.88.0.1/16 brd 10.88.255.255 scope global podman0\       valid_lft forever preferred_lft forever
+8: podman0    inet6 fe80::b85e:c8ff:feb9:e105/64 scope link \       valid_lft forever preferred_lft forever
+9: veth0    inet6 fe80::5828:77ff:fe5d:869f/64 scope link \       valid_lft forever preferred_lft forever
+
+
+
+

Then, obtain the IP you are connecting to via SSH. In my case it is 10.19.32.199. Finally append this entry to your laptop’s local /etc/hosts:

+
+
+
+
10.19.32.199 infra.5g-deployment.lab api.hub.5g-deployment.lab multicloud-console.apps.hub.5g-deployment.lab console-openshift-console.apps.hub.5g-deployment.lab oauth-openshift.apps.hub.5g-deployment.lab openshift-gitops-server-openshift-gitops.apps.hub.5g-deployment.lab assisted-service-multicluster-engine.apps.hub.5g-deployment.lab automation-hub-aap.apps.hub.5g-deployment.lab automation-aap.apps.hub.5g-deployment.lab api.sno1.5g-deployment.lab api.sno2.5g-deployment.lab
+
@@ -1116,7 +1157,15 @@

Create SNO Nodes VMs

-

Before running the following commands, make sure you have generated a SSH key pair in your default location ~/.ssh/. That SSH key will allow you to connect to the VMs you are about to create:

+

Before running the following commands, make sure you have generated a SSH key pair in your default location ~/.ssh/.

+
+
+
+
ssh-keygen -t rsa -b 2048
+
+
+
+

That SSH key will allow you to connect to the VMs you are about to create:

@@ -1126,7 +1175,7 @@

-

If you need or want to connect to any of the VMs you can do so by just executing:

+

If you need or want to connect to any of the VMs, once they are started, you can do so by just executing:

@@ -1155,7 +1204,7 @@

-If you’re using MacOS and you’re getting errors while running sed -i commands, make sure you are using gnu-sed: brew install gnu-sed. +If you’re using MacOS and you’re getting errors while running sed -i commands, make sure you are using gnu-sed by executing brew install gnu-sed. @@ -1232,7 +1281,7 @@

-

Once the cluster is deployed, the kubeconfig can be gathered as follows:

+

Once the cluster is deployed:

@@ -1241,10 +1290,23 @@

+

The kubeconfig can be gathered as follows:

+

+
+
+
oc extract secret/sno1-admin-kubeconfig --to=- -n sno1 > /root/sno1kubeconfig
+
+
+
+

Now, with the proper credentials you can check the status of the SNO1 cluster:

+
+
+
+
oc --kubeconfig /root/sno1kubeconfig get nodes,clusterversion
 
 NAME                      STATUS   ROLES                         AGE     VERSION
 node/openshift-master-0   Ready    control-plane,master,worker   94m     v1.27.6+f67aeb3
@@ -1293,7 +1355,7 @@ 
Configure Ans
 
 
 
-Change the aap_manifest_file_path var value to match the path where you stored the manifest in the hypervisor host and change the value for the student user.
+Change the aap_manifest_file_path var value to match the path where you stored the manifest in the hypervisor host and change the strong_student_password var to set a password for the AAP student user.
 
 
 
@@ -1301,7 +1363,7 @@ 
Configure Ans
 

 

 
curl -L https://raw.githubusercontent.com/RHsyseng/5g-ran-deployments-on-ocp-lab/lab-4.14/lab-materials/lab-env-data/aap2/configure-aap.yaml -o /root/configure-aap.yaml
-ansible-playbook /root/configure-aap.yaml -e strong_student_password=yourstrongstudentpassword -e aap_manifest_file_path=/path/to/your/manifest

+ansible-playbook /root/configure-aap.yaml -e strong_student_password=yourstrongstudentpassword -e aap_manifest_file_path=/path/to/your/manifest -e ansible_python_interpreter=/usr/bin/python3.11
diff --git a/sitemap.xml b/sitemap.xml index e79c85e..622bca0 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -2,118 +2,118 @@ https://labs.sysdeseng.com/4.14/5g-ran-context.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/acronyms.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/adding-aap-automation.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/check-deployment-is-finished.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/closing-thoughts.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/common-pitfalls.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/crafting-cluster-telco-related-infra-operators-configs.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/crafting-deployments-iac.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/deployment-considerations.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/index.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/integration-with-aap.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/introduction.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/lab-environment-introduction.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/lab-environment.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/managing-at-scale.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/managing-existing-clusters.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/monitoring-the-deployment.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/ocp-gitops.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/policygen-deepdive.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/rhacm-policies.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/running-the-deployment.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/sno-intro.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/talm.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/telco-related-infra-operators-intro.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/troubleshooting-tips.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/using-talm-to-update-clusters.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/ztp-at-scale.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/ztp-intro.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z https://labs.sysdeseng.com/4.14/ztp-workflow.html -2024-01-12T16:33:54.490Z +2024-02-19T08:01:55.000Z