Update lab slides

Author: niloysh

images/adding-subscribers-1.png

@@ -12,15 +12,15 @@ In this lab, you will learn how the 5G Core network is deployed in a Kubernetes
 ---
 
 # Review the AMF ConfigMap
-- Open the `configmap` file in the amf directory. This file contains the main configuration for the AMF.
+- Open the `~/open5gs-k8s/open5gs/common/amf/amf-configmap.yaml` file. This file contains the main configuration for the AMF.
 - Look for settings related to Public Land Mobile Network (`PLMN`) and Single Network Slice Selection Assistance Information (`SNSSAI`). Note these settings as they specify which networks and slices the AMF supports.
 
 **Question**: Which `PLMN` and `SNSSAI` values are set in this file? What do you think will happen if we connect a UE with `SNSSAI=3-000003`?
 
 ---
 
 # Analyze the AMF Deployment
-- Open the `deployment` file in the amf directory. This file is responsible for deploying the AMF as a pod within the Kubernetes cluster.
+- Open the `deployment.yaml` file in the amf directory. This file is responsible for deploying the AMF as a pod within the Kubernetes cluster.
 - Notice the exposed ports, such as `38412` for `SCTP` communication, which is critical for 5G signaling.
 - Observe the Multus configuration for secondary interfaces, which allows the AMF to interact with other 5G components through its `N2` interface.
 
@@ -32,7 +32,7 @@ In this lab, you will learn how the 5G Core network is deployed in a Kubernetes
 ---
 
 # Examine the AMF Service
-- Open the `service` file for the AMF. This file exposes port `80` to other pods, using the `amf-namf` service allowing the AMF to communicate with other 5G core components through the service-based interface.
+- Open the `service.yaml` file for the AMF. This file exposes port `80` to other pods, using the `amf-namf` service allowing the AMF to communicate with other 5G core components through the service-based interface.
 
 **Question**: Which NF depends on this service being available?
 **Hint**: Check the `initContainers` in the `deployment.yaml` files, which control the order of function startup by making some network functions wait for others.

images/adding-subscribers-2.png

@@ -0,0 +1,45 @@
+---
+marp: true
+theme: default
+paginate: true
+# size: 4:3
+---
+# AMF Configmap
+
+If a UE attempts to connect with `SNSSAI=3-000003` - an unsupported SNSSAI, in the AMF, you might see messages like:
+```bash
+[WARN] Requested SNSSAI (SST=3, SD=000003) is not supported by the AMF
+[ERROR] No suitable slice found for UE with SNSSAI: SST=3, SD=000003
+```
+
+---
+# AMF Deployment
+
+- **Service-based Interface (SBI):** Port 80 allows the AMF to interact with the Network Repository Function (NRF), enabling service discovery and registration.
+
+- **N2 Interface:** Port 38412 is used to establish connectivity with the gNodeB, managing signaling and control information over SCTP.
+
+- **Metrics Collection:** Port 9000 provides a dedicated endpoint for monitoring and gathering metrics, aiding in network performance management.
+
+The IP address assigned to the `N2` interface on the AMF is `10.10.3.200`.
+
+---
+# AMF Service
+
+```yaml
+template:
+    metadata:
+      labels:
+        app: open5gs
+        nf: ausf   <===== the AUSF function
+    spec:
+      initContainers:
+      - name: wait-amf    <===== waits for AMF to be running
+        image: busybox:1.32.0
+        env:
+        - name: DEPENDENCIES
+          value: amf-namf:80    <==== the amf service
+```
+
+- When a UE tries to connect, it sends a registration request to the AMF. The AMF is the primary point of contact for the UE in the 5G core network.
+- Upon receiving the registration request, the AMF sends an authentication request to the AUSF.

images/deployment.png

@@ -21,8 +21,6 @@ spec:
           { "name": "n3network", "interface": "n3", "ips": [ "10.10.3.200/24" ] }
           ]'
     spec:
-      # nodeSelector:
-      #   kubernetes.io/hostname: cn231
       initContainers:
       - name: wait-scp
         image: busybox:1.32.0

images/open5gs-common.png

@@ -36,7 +36,7 @@ git clone https://github.com/niloysh/open5gs-k8s.git
 cd open5gs-k8s
 ```
 **3. Set Up Your Testbed**
-Make sure you’ve set up your testbed using the [Testbed Automator](https://github.com/niloysh/testbed-automator). Verify that all pods are in the `RUNNING` state.
+Make sure you’ve set up your testbed using the [Testbed Automator](https://github.com/niloysh/testbed-automator). Verify that all pods are in the `RUNNING` state. You can quickly check the status of all pods with `kubectl get pods -A`.
 
 
 ---
@@ -53,16 +53,74 @@ The diagram below highlights key interfaces, including the `N2`, `N3`, and `N4`
 ![w:700 center](images/core-network.png)
 
 ---
-# Core Deployment Configuration (1/2)
-Navigate to the `open5gs` directory, which contains two subdirectories: `common` and `slice`.
+# Core Deployment Configuration (1/6)
+Navigate to the `~/open5gs-k8s/open5gs` directory, which contains two subdirectories: `common` and `slices`.
 
-The `common` directory holds subdirectories for each network function (e.g., amf, smf). Each network function subdirectory contains:
-- `deployment.yaml`: Defines the deployment for the network function, running the appropriate open5gs image.
-- `service.yaml`: Configures the Kubernetes service for the network function, exposing the necessary ports, for example **port 80** for the NRF for communication with other NFs.
-- `configmap.yaml`: Contains configuration settings specific to the network function. For example, the AMF configmap contains the supported **PLMN**.
+![bg right 80%](images/open5gs-common.png)
 
 ---
-# Core Deployment Configuration (2/2)
+# Core Deployment Configuration (2/6)
+
+The `common` directory holds subdirectories for each network function (e.g., amf, smf). Each network function subdirectory (e.g., `amf`) contains a `deployment.yaml`, `service.yaml`, and `configmap.yaml`.
+
+![bg right 80%](images/vscode-1.png)
+
+---
+# Core Deployment Configuration (3/6)
+
+The `deployment.yaml` file defines the deployment for the network function, running the appropriate open5gs image.
+```yaml
+kind: Deployment
+metadata:
+  name: open5gs-amf  <==== name of the deployment
+  labels:
+    app: open5gs
+    nf: amf
+spec:
+    ...
+      containers:
+      - image: ghcr.io/niloysh/open5gs:v2.6.4-aio  <==== container image
+```
+---
+# Core Deployment Configuration (4/6)
+
+The `service.yaml` file configures the Kubernetes service for the network function, exposing the necessary ports, for example **port 80** for communication with other NFs over the service based interface (SBI).
+
+```yaml
+apiVersion: v1
+kind: Service
+metadata:
+  name: amf-namf   <==== name of the service
+  ...
+spec:
+  ports:
+    - name: sbi
+      port: 80    <==== exposed port
+    ...
+```
+
+
+---
+# Core Deployment Configuration (5/6)
+The `configmap.yaml` file contains configuration settings specific to the network function. For example, the AMF configmap contains the supported **PLMN**.
+
+```yaml
+kind: ConfigMap
+metadata:
+  name: amf-configmap
+  ...
+data:   <==== network function specific configuration
+    ...
+      plmn_support:
+        - plmn_id:
+            mcc: 001
+            mnc: 01
+ ...
+```
+
+
+---
+# Core Deployment Configuration (6/6)
 <style> img[alt~="center"] { display: block; margin: 0 auto; } </style>
 
 ![w:800 center](images/slice-setup.png)
@@ -100,38 +158,45 @@ Once all the pods are in the `RUNNING` stage, we can take a look at the logs.
 For example, we can look at the AMF logs as follows:
 
 ```bash
-kubectl logs open5gs-amf-<replace_id> -n open5gs
+kubectl logs deployments/open5gs-amf -n open5gs
 ```
 ![](images/amf-initialize.png)
 
-You should see logs similar to those seen above.
+You should see logs similar to those seen above, e.g., stating `AMF initialize done`.
 
 ---
 # Phase 2 - Subscriber Management
 ---
-# Adding Subscribers using the Open5GS GUI (1/2)
+# Adding Subscribers using the Open5GS GUI (1/4)
+<style> img[alt~="center"] { display: block; margin: 0 auto; } </style>
 Now that our core has been deployed, let's add some subscribers using the Open5GS GUI.
 
 Navigate to http://localhost:30300/ and login with credentials: **username:** `admin` and **password:** `1423`. We can now add subscribers as shown.
 
-![w:800](images/open5gs-webui-1.png)
+![w:800 center](images/open5gs-webui-1.png)
+
+---
+# Adding Subscribers using the Open5GS GUI (2/4)
+
+**Navigate to `data/sample-subscribers.md`** in VSCode. You should see two subscribers, `Subscriber 1` and `Subscriber 2`, one for each slice. 
+
+![](images/sample-subscribers.png)
+
+---
+# Adding Subscribers using the Open5GS GUI (3/4)
+
+Use the GUI to **fill out the fields** given in `data/sample-subscribers.md` for each subscriber, leaving other fields at their default values.
+
+![w:1000](images/adding-subscribers-1.png)
 
 ---
-# Adding Subscribers using the Open5GS GUI (2/2)
+# Adding Subscribers using the Open5GS GUI (4/4)
+
+You can scroll down to get to `SST`, `SD` etc. Don't forget to set `Type` to `ipv4`.
 
-1. **Navigate to `data/sample-subscribers.md`**. You should see two subscribers, one for each slice. An example subscriber (Subscriber 1) is shown below:
+![w:1000](images/adding-subscribers-2.png)
 
-    ```
-    IMSI: 001010000000001
-    Key: 465B5CE8B199B49FAA5F0A2EE238A6BC
-    OPC: E8ED289DEBA952E4283B54E88E6183CA
-    SST: 1
-    SD: 000001
-    DNN/APN: internet
-    Type: ipv4
-    ```
-2. **Fill out the fields** using the GUI, leaving other fields at their default values.
-**Note**: You can scroll down to get to `SST`, `SD` etc. Don't forget to set `Type` to `ipv4`.
+**Note**: Do the same for Subscriber 2.
 
 ---
 # Phase 3 - RAN Deployment
@@ -150,11 +215,11 @@ This script will automatically perform the following tasks:
 # Verifying the RAN Deployment (1/3)
 In your terminal where the `kubectl get pods -n open5gs` command is running, you should observe a new pods for UERANSIM as shown below:
 
-![](images/ueransim-running-1.png)
+![w:1000 center](images/ueransim-running-1.png)
 
-We can also check the AMF logs again. You should see something like this.
+We can also check the AMF logs again. You should see `Number of AMF-Sessions is now 2` indicating 2 UEs connected.
 
-![](images/amf-connect-1.png)
+![w:1000 center](images/amf-connect-1.png)
 
 ---
 # Verifying the RAN Deployment (2/3)
@@ -193,7 +258,7 @@ kubectl exec -it deployments/ueransim-ue1 -n open5gs -- /bin/bash
 
 **2. Verify Interface:** Inside the pod, run `ip a` to check the interfaces. Look for the `uesimtun0` interface, which indicates the active PDU session and connection to the 5G network.
 
-![](images/uesimtun0.png)
+![w:1000 center](images/uesimtun0.png)
 
 ---
 # Sending Traffic through the Slices (2/3)