Skip to content

Commit

Permalink
merging Agility 2018 updates to master (#5)
Browse files Browse the repository at this point in the history
* Update class2.rst

* Update labinfo.rst

* Update labinfo.rst

* Update class2.rst

* Update module1.rst

* Update index.rst

* Update class2.rst

* Update module1.rst

* Update lab1.rst

* Update module1.rst

* Update index.rst

* Create class3.rst

* Create lab1info.rst

* Create class3.rst

* Delete class3.rst

* Create class0.rst

* Update class0.rst

* Create labinfo.rst

* Update index.rst

* Create lab0.rst

* Create labinfo.rst

* Delete class0.rst

* Delete labinfo.rst

* Create lab1.rst

* Update lab1.rst

* Create lab1info.rst

* Update lab0.rst

* Create content-lab0

* Delete labinfo.rst

* Update lab0.rst

* Update lab1.rst

* Create content-lab1

* Delete lab1info.rst

* Delete lab1info.rst

* Delete class3.rst

* Create lab2.rst

* Create content-lab2

* Delete content-lab2

* Create content-lab2.rst

* Delete content-lab0

* Create content-lab0.rst

* Delete content-lab1

* Create content-lab1.rst

* Update index.rst

* Update content-lab0.rst

* Update lab0.rst

* Create lab3.rst

* Create content-lab3.rst

* Update lab2.rst

* Update content-lab2.rst

* Update lab1.rst

* Update content-lab1.rst

* Delete lab0.rst

* Delete content-lab0.rst

* Create lab4.rst

* Create content-lab4.rst

* Create lab5.rst

* Create content-lab5

* Create lab6.rst

* Update index.rst

* Update content-lab2.rst

* Update lab1.rst

* Update lab3.rst

* Update content-lab3.rst

* Update lab4.rst

* Update content-lab4.rst

* Update lab5.rst

* Update content-lab5

* Update lab4.rst

* Rename content-lab5 to content-lab5.rst

* Update index.rst

* Update lab1.rst

* Update lab2.rst

* Update lab3.rst

* Update lab4.rst

* Update lab5.rst

* Update content-lab2.rst

* Update content-lab4.rst

* Add files via upload

* Update content-lab5.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab5.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab5.rst

* Update content-lab5.rst

* Update content-lab1.rst

* Update content-lab2.rst

* Update content-lab3.rst

* Update content-lab4.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Add files via upload

* Update content-lab1.rst

* Add files via upload

* Update content-lab1.rst

* Update content-lab2.rst

* Update content-lab3.rst

* Update content-lab2.rst

* Add files via upload

* Update content-lab4.rst

* Update content-lab1.rst

* Update content-lab1.rst

* Add files via upload

* Update content-lab4.rst

* Update content-lab1.rst

* Update lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Add files via upload

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab3.rst

* Update content-lab2.rst

* Update content-lab3.rst

* Update content-lab2.rst

* Update content-lab3.rst

* Update content-lab2.rst

* Update content-lab3.rst

* Update content-lab3.rst

* Update content-lab3.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab3.rst

* Update content-lab5.rst

* Update content-lab5.rst

* Update content-lab5.rst

* Update content-lab5.rst

* Update content-lab5.rst

* Update content-lab5.rst

* Update content-lab5.rst

* Update content-lab5.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab3.rst

* Update content-lab2.rst

* Update content-lab3.rst

* Update content-lab4.rst

* Update content-lab4.rst

* Update content-lab4.rst

* Update content-lab3.rst

* Update content-lab5.rst

* Update content-lab5.rst

* Update content-lab3.rst

* Update content-lab5.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab2.rst

* Update content-lab3.rst

* Update content-lab4.rst

* Update content-lab5.rst

* Update content-lab3.rst

* Update content-lab4.rst

* Update content-lab5.rst

* Update content-lab4.rst

* Update content-lab2.rst

* Update lab1.rst

* Update content-lab2.rst

* Update content-lab3.rst

* Update content-lab3.rst

* Update lab1.rst

* Update content-lab1.rst

* Update content-lab2.rst

* Update content-lab3.rst

* Update content-lab5.rst

* Update content-lab5.rst

* Update content-lab2.rst

* Update content-lab5.rst

* Update content-lab2.rst

* Update content-lab1.rst

* Update content-lab1.rst

* Update content-lab2.rst

* Update content-lab1.rst

* adding missing content from previous merge
  • Loading branch information
vtog committed Aug 11, 2018
1 parent 0967c9a commit 146e91d
Show file tree
Hide file tree
Showing 33 changed files with 1,363 additions and 75 deletions.
Binary file added docs/_static/class1/image41.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/_static/class1/image42.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/_static/class1/image43.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/_static/class1/image44.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/_static/class1/image45.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/_static/class1/image_lab1task1.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/_static/class1/image_lab1task2.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/_static/class1/image_lab1task3.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/_static/class1/image_lab1task4.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/_static/class1/image_lab1task5.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/_static/class1/image_lab2task1.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/_static/class1/image_lab2task2.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/_static/class1/image_lab2task3.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/_static/class1/image_lab4task1.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/_static/class1/image_overview.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/_static/class1/image_uaggear.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/_static/class1/image_uagsetting.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
8 changes: 5 additions & 3 deletions docs/class2/class2.rst
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
201: VDI the F5 Way
===================
***************
Getting Started
***************

Welcome to “VDI the F5 Way” lab. This guide is intended to complement
lecture material provided by “VDI the F5 Way” course. The purpose of
Expand All @@ -9,7 +10,8 @@ will take you through the process of current deployment to a simplified
and more secure topology with F5 BIG-IP.

.. toctree::
:maxdepth: 1
:maxdepth: 4
:caption: Contents:
:glob:

labinfo
Expand Down
32 changes: 18 additions & 14 deletions docs/class2/labinfo.rst
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
Getting Started
---------------

Jump Host
=========

Please follow the instructions provided by the instructor to start your
lab and access your jump host.
Expand All @@ -9,8 +10,9 @@ lab and access your jump host.
jumphost. No installation or interaction with your local system is
required.


Lab Network Setup
~~~~~~~~~~~~~~~~~
^^^^^^^^^^^^^^^^^

In the interest of focusing as much time as possible on this solution,
we have provided some resources and basic setup ahead of time. These
Expand All @@ -28,25 +30,30 @@ are:
- Windows desktops with Citrix and View clients will be accessed using
RDP to demonstrate functionality

|image0|
.. figure:: /_static/class1/image2.png
:scale: 50 %
:align: center

Figure 1 - Complete lab setup


Connect to Lab Environment
~~~~~~~~~~~~~~~~~~~~~~~~~~
^^^^^^^^^^^^^^^^^^^^^^^^^^

Please refer to Figure 1. We are simulating internal and external access
to VDI with 2 Windows desktops. When viewing the “corporate-pc” session,
to VDI with 2 Windows desktops. When viewing the *“corporate-pc”* session,
imagine you are sitting at your office desk. Likewise, viewing the
“home-pc” session is like you are sitting at home, or anywhere outside
*“home-pc”* session is like you are sitting at home, or anywhere outside
of the company network.

The lab is hosted in a cloud provider Ravello. Lab instructors will
provide a URL and a unique student number to access the environment.
Each attendee is expected to have a computer with a modern browser and a
RDP client.

1. Open browser and go to the URL provided by instructor.
#. Open browser and go to the URL provided by instructor.

2. Scroll down and find “corporate-pc”. Choose to connect with RDP.
#. Scroll down and find “corporate-pc”. Choose to connect with RDP.
Leave this connection for entire lab duration.

+------------+---------------------------+
Expand All @@ -55,7 +62,7 @@ RDP client.
| | Password: ``F5Agility`` |
+------------+---------------------------+

1. Scroll down and find “home-pc”. Choose to connect with RDP. Leave
#. Scroll down and find “home-pc”. Choose to connect with RDP. Leave
this connection for entire lab duration.

+------------+---------------------------+
Expand All @@ -64,12 +71,9 @@ RDP client.
| | Password: ``F5Agility`` |
+------------+---------------------------+

.. |image0| image:: /_static/class1/image2.png
:width: 7.38542in
:height: 4.13542in
.. |image1| image:: /_static/class1/image3.png
:width: 1.86762in
:height: 2.56604in
.. |image2| image:: /_static/class1/image4.png
:width: 1.82075in
:height: 2.56895in
:height: 2.56895in
106 changes: 60 additions & 46 deletions docs/class2/module1/lab1.rst
Original file line number Diff line number Diff line change
@@ -1,8 +1,5 @@
Lab 1.1: Solutions for VMware View
==================================

Task 1 – Access VMware View Desktop environment without F5
-----------------------------------------------------------
==========================================================

Test the functional VMware view environment using the internal
Connection Servers (Internal use case without F5 integration)
Expand All @@ -11,9 +8,12 @@ Access the VDI with a client on the internal network. The workstation
will be preconfigured to initiate the connection through a specific
connection server. Security servers are not used by internal VDI users

|image3|
.. figure:: /_static/class1/image5.png
:scale: 50 %
:align: center

Figure 2 - Accessing Internal View Desktop

Figure 2 - Accessing Internal View Desktop

#. From the "corporate-pc".

Expand All @@ -25,7 +25,7 @@ Figure 2 - Accessing Internal View Desktop

- \+ New server

#. Connection Server address "vmw-connsvr1c.demoisfun.net"
#. Connection Server address "vmw-connsvr1a.demoisfun.net"

#. When prompted for credentials

Expand All @@ -41,7 +41,7 @@ Figure 2 - Accessing Internal View Desktop
on top. May need to slide the blue RDP bar to the left in order to
click the X in Agility Toolbar)

#. Open View client and try to reconnect to "vmw-connsvr1c.
#. Open View client and try to reconnect to "vmw-connsvr1a.
demoisfun.net"

#. Notepad should still be on the desktop with the text you input.
Expand All @@ -50,20 +50,23 @@ Figure 2 - Accessing Internal View Desktop

#. Keep the RDP session open for Task 2


Task 2 – Load Balance Connection Servers
----------------------------------------
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Use the F5 iApp for VMware View to configure a load balancing
environment for the Connection Servers. This will increase the number of
Connection Servers available to internal users and load balance access
to these resources (Internal use case with F5 load balancing)

|image5|
.. figure:: /_static/class1/image7.png
:scale: 50 %
:align: center

Figure 3 - Load balance Connection Servers

**Deploy the iApp**

Deploy the iApp
***************
#. From "corporate-pc".

#. Use browser to access the F5 Admin GUI
Expand Down Expand Up @@ -112,9 +115,9 @@ Figure 3 - Load balance Connection Servers
+------------------------------------------------------------------------------------+---------------------------+
| What FQDN will clients use to access the View environment | vmw-LB-CS.demoisfun.net |
+------------------------------------------------------------------------------------+---------------------------+
| Which Servers should be included in this pool | 192.168.10.212 |
| Which Servers should be included in this pool | 192.168.10.210 |
| | |
| | 192.168.10.213 |
| | 192.168.10.211 |
+------------------------------------------------------------------------------------+---------------------------+

#. **Client Optimization** (leave these default—Do not compress…)
Expand All @@ -126,7 +129,7 @@ Figure 3 - Load balance Connection Servers
#. Press the **Finished** button

View the objects which were created by the iApp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
***********************************************

#. Select the Components tab at the top of the page

Expand All @@ -151,7 +154,7 @@ View the objects which were created by the iApp
#. Review the remaining parameters (any questions)

View the properties of the iApp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
*******************************

#. Select the Properties tab at the top of the page

Expand All @@ -167,8 +170,8 @@ View the properties of the iApp

- What are the pro’s and con’s of unchecking this parameter?

Test the connection server load balancing using both VMware View client and browser access methods.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Test the connection server load balancing using both VMware View client and browser access methods
**************************************************************************************************

#. From "corporate-pc"

Expand Down Expand Up @@ -217,7 +220,7 @@ Test the connection server load balancing using both VMware View client and brow
#. Close the IE browser window

Task 3 – Access View Desktop through Security Server
----------------------------------------------------
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Test the functional VMware View environment using external Security
Servers. (External use case without F5 integration)
Expand All @@ -226,9 +229,11 @@ This environment shows a user connecting to a native VMware security
server which is statically mapped to a VMware connection server. This is
a non-redundant external access model

|image8|

Figure 4 - Access external View Desktop
.. figure:: /_static/class1/image10.png
:scale: 50 %
:align: center

Figure 4 - Access external View Desktop

#. From the "home-pc"

Expand All @@ -253,7 +258,7 @@ Figure 4 - Access external View Desktop
#. Close the View client

#. Access the application through your browser
``https://vmw-secursvr1a.demoisfun.net``
``https://vmw-uag1a.demoisfun.net``

#. Select VMware Horizon View HTML access

Expand All @@ -271,8 +276,9 @@ Figure 4 - Access external View Desktop

#. Close the browser window


Task 4 – Load Balance Security Servers
--------------------------------------
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Use the F5 iApp for VMware View to configure a load balancing
environment for the Security Servers. This will increase the number of
Expand All @@ -284,11 +290,14 @@ Security Servers are directly mapped to 2 existing connection servers in
the environment (not the 2 Connections Servers that are load balances in
the steps above)

|image10|

Figure 5 - Load balance Security Servers
.. figure:: /_static/class1/image12.png
:scale: 50 %
:align: center

Figure 5 - Load balance Security Servers

**Deploy the iApp**
Deploy the iApp
***************

#. From "corporate-pc"

Expand Down Expand Up @@ -326,7 +335,7 @@ Figure 5 - Load balance Security Servers
+------------------------------------------------------------------------------------+---------------------------+
| What virtual server IP address do you want to use for remote, untrusted clients? | 192.168.3.150 |
+====================================================================================+===========================+
| What FQDN will clients use to access the View environment? | vmw-LB-SS.demoisfun.net |
| What FQDN will clients use to access the View environment? | vmw-UAG.demoisfun.net |
+------------------------------------------------------------------------------------+---------------------------+
| Which Servers should be included in this pool? | 192.168.3.214 |
| | |
Expand All @@ -339,9 +348,9 @@ Figure 5 - Load balance Security Servers

#. Press the **Finished** button

View the objects which were created by the iApp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

View the objects which were created by the iApp
***********************************************
#. Select the Components tab at the top of the page

#. Is the Virtual server available?
Expand All @@ -352,17 +361,17 @@ View the objects which were created by the iApp

#. Review the remaining parameters (any questions)

Test the Security Server load balancing using both VMware View client and browser access methods
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Test the Security Server load balancing using both VMware View client and browser access methods
************************************************************************************************
#. From "home-pc"

#. Open View client and connect to the Virtual Server just created with
iApp.

- \+ New Server

- vmw-LB-SS.demoisfun.net (192.168.3.150)
- vmw-LB-UAG.demoisfun.net (192.168.3.150)

- Press the Connect button

Expand All @@ -382,7 +391,7 @@ Test the Security Server load balancing using both VMware View client and browse

#. Open IE and browser to

- ``https://vmw-LB-SS.demoisfun.net``
- ``https://vmw-UAG.demoisfun.net``

#. Select VMware Horizon View HTML access

Expand All @@ -403,18 +412,20 @@ Test the Security Server load balancing using both VMware View client and browse
#. Close the browser window

Task 5 – Replace Security Servers and leverage APM as a PCOIP proxy
-------------------------------------------------------------------
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

This environment will utilize Big-IP as a PCOIP Proxy. This eliminates
the requirement for all Security Servers. The Connection Servers will be
load balanced. Authentication is handled by the F5 APM module

|image11|

Figure 6 - Replace Security Servers

**Deploy the iApp**
.. figure:: /_static/class1/image13.png
:scale: 50 %
:align: center
Figure 6 - Replace Security Servers

Deploy the iApp
***************
#. From "corporate-pc"

#. Create a new Application Service by selecting iApps -> Application
Expand All @@ -428,8 +439,9 @@ Figure 6 - Replace Security Servers

- Select ``f5.vmware_view.v1.5.1`` for the template


iApp Configuration
~~~~~~~~~~~~~~~~~~
******************

#. Review the **Welcome to the iAPP template for VMware Horizon View**

Expand Down Expand Up @@ -472,9 +484,9 @@ iApp Configuration
+====================================================================================+================================+
| What FQDN will clients use to access the View environment? | vmw-PROXY-VIEW.demoisfun.net |
+------------------------------------------------------------------------------------+--------------------------------+
| Which Servers should be included in this pool? | 192.168.10.212 |
| Which Servers should be included in this pool? | 192.168.10.210 |
| | |
| | 192.168.10.213 |
| | 192.168.10.211 |
+------------------------------------------------------------------------------------+--------------------------------+

#. **Application Health**
Expand All @@ -483,8 +495,9 @@ iApp Configuration

#. Press the **Finished** button


View the objects which were created by the iApp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
***********************************************

#. Select the Components tab at the top of the page

Expand All @@ -496,8 +509,9 @@ View the objects which were created by the iApp

#. Review the remaining parameters (any questions)


Test the APM (PCoIP) functionality using both VMware View client and browser access methods
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
*******************************************************************************************

#. From "home-pc"

Expand Down

0 comments on commit 146e91d

Please sign in to comment.