Merge pull request #112 from f5devcentral/v20_update

module 3 corrections
f5devcentral · Jan 28, 2024 · ebef62c · ebef62c
2 parents 55b7ed0 + 7af9e1d
commit ebef62c
Show file tree

Hide file tree

Showing 14 changed files with 50 additions and 23 deletions.
diff --git a/docs/class5/module3/images/add-app-10.png b/docs/class5/module3/images/add-app-10.png
diff --git a/docs/class5/module3/images/add-app-11.png b/docs/class5/module3/images/add-app-11.png
diff --git a/docs/class5/module3/images/add-app-12.png b/docs/class5/module3/images/add-app-12.png
diff --git a/docs/class5/module3/images/add-app-13.png b/docs/class5/module3/images/add-app-13.png
diff --git a/docs/class5/module3/images/add-app-1b.png b/docs/class5/module3/images/add-app-1b.png
diff --git a/docs/class5/module3/images/add-app-7b.png b/docs/class5/module3/images/add-app-7b.png
diff --git a/docs/class5/module3/images/edit-icon.png b/docs/class5/module3/images/edit-icon.png
diff --git a/docs/class5/module3/images/test-app-1.png b/docs/class5/module3/images/test-app-1.png
diff --git a/docs/class5/module3/lab2.rst b/docs/class5/module3/lab2.rst
@@ -45,6 +45,8 @@ Now, you will create a simple HTTPS application.
 
 #. Click on the **Start Creating** button to reveal the **Virtual Server** and **Pool** configuration options.
 
+   .. image:: ./images/add-app-1b.png
+
 #. Click on **Pools** to show the Pool configuration options.
 
    .. image:: ./images/add-app-2.png
@@ -53,8 +55,8 @@ Now, you will create a simple HTTPS application.
 
    - Enter ``my-pool`` in the **Pool Name** field.
    - Change the **Service Port** to ``443`` (default value was **80**)
-   - In the **Monitor Type** field, click on the down arrow to show the available options.
-   - Deselect **http** and select **icmp**
+   - Click on the **Monitor Type** field to show the available options.
+   - De-select **http** and select **icmp**
    - Click outside of the list to use the selected options.
 
    .. image:: ./images/add-app-3.png
@@ -66,7 +68,9 @@ Now, you will create a simple HTTPS application.
    - In the **Pool** field, select the **my-pool** pool.
    - Change the **Virtual Port** to ``443`` (default value was **80**)
 
-#. In the **Protocols & Profiles** field, click on the **edit icon** to open the settings panel.
+#. In the **Protocols & Profiles** field, click on |edit-icon| (**edit icon**) to open the settings panel.
+
+   .. |edit-icon| image:: ./images/edit-icon.png
 
    .. image:: ./images/add-app-4.png
 
@@ -100,12 +104,16 @@ Now, you will create a simple HTTPS application.
 
    - Click on the **Start Adding** button.
    - Select the instance named **bigip-next.f5labs.com**.
-   - Click on the **+ Add to List** button.
-   - Enter ``10.1.10.20`` in the **Virtual Address** field.
+   - Click on the **+ Add to List** button to see the additional deployment settings.
+
+   .. image:: ./images/add-app-7b.png
+
+
+#. In the **Virtual Address** field, enter ``10.1.10.20`` .
 
    .. image:: ./images/add-app-8.png
 
-#. In the **Members** column, click on the down arrow and then click **+ Pool Members** to open the settings panel.
+#. You will see **0** in the **Members** column, click on the down arrow and then click **+ Pool Members** to define Pool Members.
 
    - Click on the **+ Add Row** button 3 times to create empty entries.
 
@@ -124,8 +132,18 @@ Now, you will create a simple HTTPS application.
    .. image:: ./images/add-app-10.png
 
 
-#. If Validation is successful, click on the **Deploy Changes** button. Then, click on the **Yes, Deploy** button to send the application definition to the BIG-IP Next instance.
-
-   After deployment, the **Application Services** dashboard will show the status of your application.
+#. If validation is successful, you will see **Validated** and a link to **View Results**. Click on the link to view the configuration (JSON format) in a new panel.
 
    .. image:: ./images/add-app-11.png
+
+#. Click on the **Exit** button to close the panel.
+
+
+#. Click on the **Deploy Changes** button. Then, click on the **Yes, Deploy** button to send the application configuration to the BIG-IP Next instance.
+
+   .. image:: ./images/add-app-12.png
+
+
+When the deployment has completed, the **Application Services** dashboard will show the status of the application.
+
+.. image:: ./images/add-app-13.png
diff --git a/docs/class5/module3/lab3.rst b/docs/class5/module3/lab3.rst
@@ -6,23 +6,29 @@ Congratulations! You have now deployed a simple HTTPS application on BIG-IP Next
 Accessing the Client VM
 --------------------------------------------------------------------------------
 
-The UDF lab environment provides an Ubuntu Linux VM instance (**Ubuntu-Client**) with access to an interactive shell for command line testing, as well as a GUI desktop to run web browsers and other tools.
+The UDF lab environment provides an Client VM (Ubuntu Linux) instance with access to an interactive shell for command line testing, as well as a GUI desktop to run web browsers and other tools.
 
-In the UDF Deployment tab, find the Client VM resource. The application tests performed in the next section will require you to execute commands from the Linux shell. The shell session can be accessed via either a **Web Shell** or a **terminal shell** within a **WebRDP** desktop GUI session.
-
-If you want to use the Client desktop GUI option, click on the **WebRDP** access method under the **Ubuntu-Server** resource. This opens a new browser tab providing a view of the client desktop GUI. Enter the username (``user``) and password (``user``) to login. From the client desktop, you can launch a Linux **Terminal** window to issue shell commands.
+The application tests performed in the next section will require you to execute commands from the Linux shell. The shell session can be accessed via either a **Web Shell** or a **Terminal** shell from within a **WebRDP** desktop GUI session.
 
 For this lab module, we recommend using the **Web Shell** access method.
 
-#. Under the **Ubuntu-Client** resource of the UDF Deployment tab, click on Access -> **Web Shell**. This will open a console shell window to the Client VM (in a separate browser tab).
+#. In the UDF **Deployment** tab, find the **Ubuntu-Client** resource.
+
+#. Under **Ubuntu-Client**, click on **ACCESS** to see the list of available access methods.
+
+#. Click on **Web Shell** to open a new web browser tab that connects to the console shell of the Client VM.
+
+
+.. note::
+   If you want to use the Client desktop GUI option instead, click on the **WebRDP** access method under the **Ubuntu-Server** (not the **Ubuntu-Client**) resource. This opens a new browser tab that connects to the Client desktop GUI. Enter the username (``user``) and password (``user``) to login. From the Client desktop, you can launch a Linux **Terminal** window to issue shell commands.
 
 
 Test Access to the HTTPS Application
 --------------------------------------------------------------------------------
 
 You will now test the HTTPS application by sending a command line **cURL** request to the BIG-IP Virtual Server. 
 
-#. In the **Client VM shell** (or a Terminal shell running on the Client VM desktop), enter the following command:
+#. In the **Client VM** shell (or a Terminal shell running on the Client VM desktop), enter the following command:
 
    .. code-block:: bash
 
@@ -38,9 +44,11 @@ You will now test the HTTPS application by sending a command line **cURL** reque
       curl -vkI https://10.1.10.20
 
 
-#. Look for the **Server certificate** section. You should see that the **subject** field's **Common Name (CN)** attribute is **\*.f5labs.com**. This confirms that the site is being presented from the BIG-IP deployed application.
+#. Look for the **Server certificate** section. You should see that the **subject** field's **Common Name (CN)** attribute is **\*.f5labs.com**.
+
+   .. image:: ./images/test-app-1.png
 
-   .. image:: ./images/add-app-12.png
+   This confirms that the site is being presented from the BIG-IP deployed application.
 
 |
 

diff --git a/docs/class5/module4/images/service-chain-0.png b/docs/class5/module4/images/service-chain-0.png
diff --git a/docs/class5/module4/lab3.rst b/docs/class5/module4/lab3.rst
@@ -13,12 +13,12 @@ With the **Inline L3** inspection service created, you will now create a service
 
 #. In the **SSL Orchestrator** menu, click on **Service Chains**.
 
-   .. image:: ./images/service-chain-1.png
-
+#. Since there are no **Service Chain** yet, click on the **Start Creating** button to get started.
 
+   .. image:: ./images/service-chain-0.png
 
 
-#. Click the **Start Creating** button to open the **Create Service Chain** panel.
+#. In the **Create Service Chain** panel:
 
    - Enter ``my-service-chain-lab2`` in the **Name** field
 

diff --git a/docs/class5/module4/lab5.rst b/docs/class5/module4/lab5.rst
@@ -7,7 +7,7 @@ Create an Inbound Application with SSL Orchestrator Policy
 
 SSL Orchestrator inspection services, service chain, and traffic policy creation are now done, and now it is time to apply this to an application.
 
-#. In the top left corner of the BIG-IP Central Manager (CM) UI, click on the **Workspace** icon to show the **Workspace Menu**.
+#. In the top left corner of the BIG-IP Central Manager GUI, click on the **Workspace** icon to show the **Workspace Menu**.
 
 #. Click on **Applications** to navigate to the Applications workspace. You should see the application that you created in the previous lab module.
 
@@ -111,6 +111,7 @@ SSL Orchestrator inspection services, service chain, and traffic policy creation
 
 #. If Validation is successful, click on the **Deploy Changes** button. Then, click on the **Yes, Deploy** button to send the application definition to the BIG-IP Next instance.
 
-   After deployment, the **Application Services** dashboard will show the status of your application.
+
+After deployment, the **Application Services** dashboard will show the status of your application.
 
    .. image:: ./images/second-app-4.png
diff --git a/docs/class5/module5/lab5.rst b/docs/class5/module5/lab5.rst
@@ -7,7 +7,7 @@ Create an Inbound Gateway Application with SSL Orchestrator Policy
 
 SSL Orchestrator inspection services, service chain, and traffic policy creation are now done, and it is time to apply this to a gateway application.
 
-#. In the top left corner of the BIG-IP Central Manager (CM) UI, click on the **Workspace** icon to show the **Workspace Menu**.
+#. In the top left corner of the BIG-IP Central Manager GUI, click on the **Workspace** icon to show the **Workspace Menu**.
 
 #. Click on **Applications** to navigate to the Applications workspace. You should see the applications that you created in the previous lab modules.