Skip to content

merging updated guide with full install lab into master #15

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.

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 15 commits into from
Feb 20, 2025
Merged
2 changes: 1 addition & 1 deletion docs/class1/module1/lab1.rst
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ In order to take advantage of the F5 AST, one must simply have the means by whic

Installation can be performed via GitHub repo or by downloading the source tarball from the GitHub repo's release section. These details are covered in :ref:`Installing and Configuring the F5 AST`.

Post-installation, configuration is straightforward and approachable, enabling you to start collecting your F5 BIG-IP data within a matter of minutes. You need only follow a few basic steps to set up the environment, device credentials, device list, and start the containers.
Post installation, configuration is straightforward and approachable, enabling you to start collecting your F5 BIG-IP data within a matter of minutes. You need only follow a few basic steps to set up the environment, device credentials, device list, and start the containers.

You may also `enable data export to F5 <https://github.com/f5devcentral/application-study-tool?tab=readme-ov-file#configure-periodic-metric-data-export-to-f5>`_, allowing your account engineer to view the very same metrics you see. This can be invaluable when looking for assistance from your helpful F5 solutions engineer or architect!

Expand Down
3 changes: 1 addition & 2 deletions docs/class1/module1/lab2.rst
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ The tech industry has come a long way from the days of a single application host

Containers have revolutionized what it means and entails to deploy and manage software, whether it's a single container or a Kubernetes environment consisting of tens, hundreds, or even thousands of interconnected containers.

.. note:: You may have heard the term **micro-services** floating around in recent years. Containerization is a foundational key to the success and proliferation of micro-services architectures.
.. Note:: You may have heard the term **micro-services** floating around in recent years. Containerization is a foundational key to the success and proliferation of micro-services architectures.

At F5, our home is in the heart of application delivery and security, which exposes us to nearly every form of application deployment. We aim to not only stay aligned with modern application infrastructure practices, but also help forge the road ahead and be forward-thinking. Because of this, we are continually evaluating how we design, produce, and deploy our own software.

Expand All @@ -28,7 +28,6 @@ But first, let's take a few moments to briefly get our feet wet with Docker and

For example, use ``Shift + Ctrl + v`` to paste instead of ``Ctrl + v``


#. Navigate to the **Application Study Tool** component with the UDF lab, then select **Access** and **Web Shell**.

#. Once the new tab appears and you're on the terminal, view the Docker version by entering the following command:
Expand Down
Binary file modified docs/class1/module2/images/github_repo_readme.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified docs/class1/module2/images/github_repo_releases_packages.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
16 changes: 5 additions & 11 deletions docs/class1/module2/lab1.rst
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Here it is, served to you on a nice, bountiful SaaS platter: |application-study-

.. note:: This is a fairly comprehensive guide for installing, managing, and updating the F5 AST. We won't follow it verbatim, but will touch on the fundamentals.

We recommend you fully review and keep this and the `Docsite <https://f5devcentral.github.io/application-study-tool/>`_ in your bookmarks.
We recommend you fully review and keep the F5 Application Study Tool repo and the `Docsite <https://f5devcentral.github.io/application-study-tool/>`_ in your bookmarks.

#. On the right side of the page are links to **Releases** and **Packages**

Expand Down Expand Up @@ -61,16 +61,10 @@ Here it is, served to you on a nice, bountiful SaaS platter: |application-study-
# Start the tool
docker-compose up

In this lab, the F5 Application Study Tool has already been installed, partially configured, and started.
In the UDF lab environment, a copy of the F5 Application Study Tool has already been installed, partially configured, and started on the **Application Study Tool** UDF system, exposed via ``http://10.1.1.11:3000``.

However, there's an F5 BIG-IP in our UDF lab environment which is not yet being monitored by F5 AST and needs to be added to the ``config/bigip_receivers.yaml`` file.
If you'd like to perform a full installation yourself, please continue on to :ref:`Installing the F5 AST`.

With that said, we should review and familiarize ourselves with the current configuration and get our hands dirty by modifying it and restarting the OTel container using Docker.
If you'd rather skip the full installation process, :ref:`Configuring the F5 AST` is the place to be. There's an F5 BIG-IP in the UDF course lab environment which is not yet being monitored by the pre-installed F5 AST instance and needs to be added to the ``config/bigip_receivers.yaml`` file. This will give you an opportunity to review, familiarize yourself, and interact with the current pre-installed F5 AST configuration. It's a nice chance to get your hands dirty by modifying it and restarting the OTel container using Docker.

.. attention:: If you are interested in performing the full installation process, you may do so by stopping the currently-running instance of F5 AST and clone the repo into a different directory.

From the new directory, you'll be working with a fresh installation. If you're unsure about how to do this, please ask an instructor or lab assistant for help.

For the sake of this lab and showcasing traffic generation, we pre-staged F5 AST in the event students want to get up and running with accessing the Grafana dashboards right away.

Please select **Next** below and continue on to :ref:`Configuring the F5 AST`
Please select **Next** below and continue on to :ref:`Installing the F5 AST`
Loading
Loading