Transcript of "Enhancing the User Experience for Multi-Pod VMware View Deployments"
Enhancing the UserExperience for Multi-Pod VMware View DeploymentsBruno Germain, F5 Networks #vmworldsponsor
2F5 & VMware• F5 & VMware are active, global partners• 4 years of history as managed partners• Primary partnership goals Compatibility / Interoperability testing New Solution Development New Solution Documentation• Across all major F5 and VMware products• Ongoing cooperative solution development• Coordinated back-end customer support
3Application Delivery Networking Services L4-L7• Glue between end users and application workloads• Policy-driven traffic management• Dynamic configuration and automation of policies
5Our Objective TodayExplain how to provide… A. A single URL B. With user to pod session affinity C. With the ability to failover to a backup pod…for large and/or distributed VMware View deployments
64 Use Cases – 4 DesignsUse Case Datacenter(s) Pod(s) Entitlement(s) 1 Single Multiple Single 2 Multiple Multiple Single 3 Multiple Multiple Multiple 4 Multiple Multiple Dynamic
7Use Case #1 – Multi Pod, Single Site• Customer Acme has 16,000 View Users at their HQ• Provide a Single URL with intelligent routing to users cluster/pool• Simplify Pool/User management through load balancing
8 SSL Clarification 1. DNS Request to 3. 2. SSL View Non SSL View GTM for View Connection ServiceGTM GTMLTM/APM LTM/APM Connection / Connection / Security Security Servers Servers
10 Use Case #2 – Multi Pod, Multi Site• Customer Acme has two primary sites with 8000 users per location, they provide DR services for critical workloads• Users travel, work from home and require a single intelligent access point into their View desktop view.acme.com Chicago Dallas
11Multiple Sites, Multiple Pods, 1 Name Space view_north.company.comview_east.company.com view.company.com view_west.company.com view_south.company.com
12Persistence = Happy Users A New Server Creates a Fresh Desktop View Connection Servers Pod 1 Lost Connection Reconnect! Pod 2 Pre-Existing Server, Pre-Existing DesktopPersistence based on the Username,ensures that anytime a user disconnectsand soon thereafter reconnects, they willbe assigned to the same connectionserver, and will see the same desktoplayout they had prior to the disconnect.
16 iQueryHealth Check to Both Pods: East & West 10.1.1.20 192.168.2.20
17 User has lowest latency DNS Answer: to West Pod.“view.company.com. IN A 192.168.2.20” 192.168.2.20
18 Password is cached using 256 bit encryptionPW
19User Name Current LTM looks up User. Pod? <Current Assignment>Bob Smith WestFran Kelly EastJim Adams Noneetc…
20 APM Obtains User’s Current APM queries Pod & Pool Member Active Directory.Username & Password are sent to AD. AD User’s Group Membership Domain Active Directory UN PW Domain
21 View ServersBased on the Pod & Pool info inAD, LTM sends the user to the correct View server
22 View ServersThe View Server replies with a user token. Client uses that token to automatically reconnect directly to the View server.
23Use Case #3 – Multi Pod, Multi Site, Multi Desktop• Customer Acme has three sites with 6000 users per location, they provide DR services for critical workloads with secondary entitlements to backup desktops view.acme.com Chicago New York Dallas
25Use Case #4 – Multi Pod, Multi Site, Smart Desktop• Customer Acme has three sites with 6000 users per location, they provide optimized user experience and DR services for their desktop workloads. view.acme.com Chicago New York Dallas