Merge pull request #104 from f5devcentral/v20_update

V20 update draft

docs/class5/appendix/appendix1.rst

@@ -11,86 +11,100 @@ Next instance command shell. For expanded information on the Debug
 utility and its various options, visit the official reference:
 https://clouddocs.f5.com/bigip-next/latest/support/debug_utility.html
 
-Step 1: Create an SSH Key
+
+Create an SSH Key
 --------------------------------------------------------------------------------
 
-In Windows (PowerShell), Mac, and Linux, issue the following command:
-ssh-keygen. When prompted, assigning a passphrase is optional, but if
-set it will be needed for all future use of this SSH key. When the
-operation completes, you'll be left with two files - one with a “.pub”
-extension (the public key), and another with the same name but without
-the extension (the private key). The public key will be shared with the
-remote system (Central Manager and BIG-IP Next instance). Open the
-public key in a text editor and copy the contents.
+#. In Windows (PowerShell), Mac, and Linux, issue the following command: ``ssh-keygen``. 
+
+#. When prompted, assigning a passphrase is optional, but if
+   set it will be needed for all future use of this SSH key. 
+
+   When the operation completes, you'll be left with two files - one with a ".pub"
+   extension (the public key), and another with the same name but without
+   the extension (the private key). The public key will be shared with the
+   remote system (Central Manager and BIG-IP Next instance). 
+
+#. Open the public key in a text editor and copy the contents.
 
-Step 2: Access the Debug Utility
+
+Access the Debug Utility
 --------------------------------------------------------------------------------
 
-In the F5 Central Manager UI, click on the **Manage Instances** button,
-or select **Infrastructure** from the left side menu. Under
-**Instances** - **My Instances**, click on a BIG-IP Next instance to
-display the properties drawer. In the left side menu of the properties
-drawer, navigate to **Debug**. Click the **Proceed** button. Paste the
-contents of the previously create SSH public key in the window or click
-the Browse button to select this file. When ready, click the **Start
-Debug Session** button. A new black box will appear in the drawer with
-instructions on how to access the BIG-IP Next command shell. If you used
-the default options when creating the SSH key (ex.
-/home/student/.ssh/id_rsa), then follow the instructions as displayed.
-Example:
+#. In the F5 Central Manager UI, click on the **Manage Instances** button,
+   or select **Infrastructure** from the left side menu. 
+
+#. Under **Instances** - **My Instances**, click on a BIG-IP Next instance to
+   display the properties drawer.
+
+#. In the left side menu of the properties drawer, navigate to **Debug**. 
+
+#. Click the **Proceed** button. 
 
-.. code-block:: bash
+#. Paste the contents of the previously create SSH public key in the window or click
+   the Browse button to select this file. 
 
-   ssh admin@10.1.1.7 -p 2222
+#. When ready, click the **Start Debug Session** button. A new black box will appear 
+   in the drawer with instructions on how to access the BIG-IP Next command shell.
 
-If you used a different filename when creating the SSH key, specify this
-private key explicitly in the SSH command with the -i argument.
+   If you used the default options when creating the SSH key (for example: ``/home/student/.ssh/id_rsa``), then follow the instructions as displayed.
 
-.. code-block:: bash
 
-   ssh -i mykey admin@10.1.1.7 -p 2222
+   .. code-block:: bash
 
-Once inside the BIG-IP Next command shell, you will have access to
-various commands for troubleshooting data plan issues, including:
+      ssh admin@10.1.1.7 -p 2222
 
--  tmctl - displays various TMM traffic processing statistics.
+   If you used a different filename when creating the SSH key, specify this
+   private key explicitly in the SSH command with the -i argument.
 
--  bdt_cli - displays TMM networking information such as ARP and route
-   entries.
+   .. code-block:: bash
 
--  tcpdump - captures and replays packets sent and received on network
-   interfaces.
+      ssh -i mykey admin@10.1.1.7 -p 2222
 
--  wget - retrieves files using HTTP, HTTPS, FTP, and FTPS.
+   Once inside the BIG-IP Next command shell, you will have access to
+   various commands for troubleshooting data plan issues, including:
 
--  ping - tests reachability of remote hosts on IP networks using ICMP.
+   -  tmctl - displays various TMM traffic processing statistics.
 
--  traceroute - displays the packet route in hops to a remote host.
+   -  bdt_cli - displays TMM networking information such as ARP and route
+      entries.
 
-To stop debugging, close the SSH window then click the **Stop Debug
-Session** button in the Central Manager UI.
+   -  tcpdump - captures and replays packets sent and received on network
+      interfaces.
 
+   -  wget - retrieves files using HTTP, HTTPS, FTP, and FTPS.
 
-Step 3: Test Network Traffic with TCPDUMP
+   -  ping - tests reachability of remote hosts on IP networks using ICMP.
+
+   -  traceroute - displays the packet route in hops to a remote host.
+
+#. To stop debugging, close the SSH window then click the **Stop Debug Session**
+   button in the Central Manager UI.
+
+
+Test Network Traffic with TCPDUMP
 --------------------------------------------------------------------------------
 
-As a final step in this appendix, use the ``tcpdump`` command in the BIG-IP
+You can use the ``tcpdump`` command in the BIG-IP
 Next debug shell to view the traffic flowing to/from the BIG-IP Next
-instance data plane. In this lab, the client facing VLAN is named
-**clientside**, and the server facing VLAN is named **serverside**. You
-can verify these names with the following command:
+instance data plane.
+
+#. In this lab environment, the client facing VLAN is named
+   **clientside**, and the server facing VLAN is named **serverside**. You
+   can verify these names with the following command:
+
+   .. code-block:: bash
+
+      ip link
 
-.. code-block:: bash
 
-   ip link
+#. Assuming an application has been deployed on the BIG-IP Next instance,
+   start a tcpdump capture listening on the **clientside** VLAN:
 
-Assuming an application has been deployed on the BIG-IP Next instance,
-start a tcpdump capture listening on the **clientside** VLAN:
+   .. code-block:: bash
 
-.. code-block:: bash
+      tcpdump -lnni clientside
 
-   tcpdump -lnni clientside
 
-From a client browser, access the application deployed to the BIG-IP
-Next instance. This should generate traffic in the tcpdump capture
-window.
+#. From a client browser, access the application deployed to the BIG-IP
+   Next instance. This should generate traffic in the tcpdump capture window.

docs/class5/appendix/appendix3.rst

@@ -0,0 +1,6 @@
+Appendix 3 - BIG-IP Next SSL Orchestrator API References
+================================================================================
+
+.. todo::
+
+   Get API documentation links

docs/class5/class5.rst

@@ -1,17 +1,12 @@
 SSLO 102: BIG-IP Next SSL Orchestrator (AppWorld 2024 | 2 hours)
 ===============================================================================================
 
-.. todo:: 
-
-   This lab is still under development
-
-
 
 .. note::
 
    This lab relies on UDF Blueprint: **AppWorld 2024 - SSL Orchestrator Next**
 
-   The code provided for this lab was tested with **BIG-IP Next 20.2 / SSL Orchestrator 20.0**.
+   The code provided for this lab was tested with **BIG-IP Next 20.1 / SSL Orchestrator 20.1**.
 
 |
 

docs/class5/conclusion.rst

@@ -17,7 +17,7 @@ Note that the lab environment will also shut down automatically at the end of th
 
 |
 
-More SSL Orchestrator Labs
+Explore More SSL Orchestrator Labs
 ================================================================================
 
 To learn more about SSL Orchestrator, consider attending one of the other labs in this series:
@@ -53,7 +53,7 @@ Revision History
      - **Changes**
    * - 1.0 (AppWorld 2024)
      - Kevin Stewart, Jason Chiu
-     - Lab created - BIG-IP Next 20.2 - SSL Orchestrator (Limited Availability release)
+     - Lab created - BIG-IP Next 20.1 - SSL Orchestrator (Limited Availability release)
 
 
 Lab Guide Repository (GitHub)

docs/class5/module1/lab3.rst

@@ -4,7 +4,7 @@ What's new in SSL Orchestrator?
 BIG-IP Next SSL Orchestrator Features
 ------------------------------------------------------------------------------
 
-The flagship **SSL Orchestrator** release on BIG-IP Next provides the following features:
+The **BIG-IP Next SSL Orchestrator (BIG-IP Next 20.1)** release on BIG-IP Next provides the following features:
 
 - **Inbound Application Mode**: SSL Orchestrator security policy can natively attach to a standard BIG-IP Next application workflow.
 
@@ -26,6 +26,4 @@ The flagship **SSL Orchestrator** release on BIG-IP Next provides the following
 
 - **High Availability Support**: High availability is the ability to pair BIG-IP instances for greater availability and protection against unintended outages.
 
-- **Journeys Configuration Migration Support**: The Journeys migration tool allows customers to move an existing BIG-IP SSL Orchestrator configuration to BIG-IP Next.
-
 - **iRules Support**: BIG-IP Next carries forward the full extensibility of F5 iRules to provide programmatic access to the BIG-IP data plane. iRules present an unparalleled flexibility within the F5 BIG-IP full proxy architecture to tune and adjust traffic flows, and even application behavior, at wire speed.

docs/class5/module2/lab1.rst

@@ -1,17 +1,9 @@
 .. role:: red
 .. role:: bred
 
-
-.. todo:: 
-
-   Instructions and screenshots pending completion of the UDF blueprint
-
-
-
 Accessing the Virtual Lab
 ================================================================================
 
-
 If you are not familiar with the process for joining a training course, refer to:
 
 - |join_link|