VMworld 2014 Session Notes: EUC2035 — Horizon 6 Technical Overview

Below are my notes from VMworld Session EUC2035 by Justin Venezia and Jim Yanik entitled “Horizon 6 Technical Overview” All credit for the material below belongs to the tremendous authors/speakers, Justin Venezia and Jim Yanik of VMware.

  • Cloud Pod Architecture: Efficiently manage desktop deployments across data centers
  • Overview and Benefits
  • Support single namespace for end users with a global URL
  • Global Entitlement layer to assign and manage desktops and users across multiple pools within or between View pods
  • Scale Horizon deployments easily
  • Support Active/Active and DR data center configurations
  • Support geo-roaming users
  • Simplifies pool entitlements in large environments
  • Brokering with Cloud Pod Architecture
  • Global load balancer sends user to the right location (e.g. London)
  • View returns desktops in all locations in pod federation
  • If user chooses a desktop in New York, desktop will be brokered via Security Server in London without having to redirect to a broker in New York
  • VIPA (View InterPod Architecture Protocol): Allows for exchanging info between pods over the WAN, and can tolerate WAN latency/hiccups
  • One broker per pod that communicates to one broker in another pod, instead of all brokers among all brokers.
  • Just stores transient information (status of desktop, etc.)
  • All static info like global entitlements and global pools are stored in ADLDS layer which talks and replicates via 22389
  • Real World
  • CPA can be used for a single View Pod implementation
  • Plan CPA sites accordingly
  • View Pods in same DC should be in single site.
  • Load balancing and global traffic management still required
  • CPA can do access, authentication, and brokering of virtual and RDS hosted desktops
  • CPA does not address redundancy of other dependencies
  • RDS hosted apps NOT supported
  • CPA Desktop Pools NOT supported within Horizon Workspace Portal
  • Hosted Apps: Deliver applications seamlessly to Horizon-enabled endpoints
  • Supports Windows Server 2008 and 2012 R2
  • Load management works on choosing the host with the most session slots available (Session Slots = Session Cap — Active Sessions)
  • With RDS, sessions start to become the bottleneck in building block sizing. Apps can have multiple sessions per users.
  • 10,000 session limit per pod.
  • RDS hosted desktops do not share sessions with RDS hosted applications.
  • Apps that need to talk to each other (with things like object linked and embedding) need to be on the same server
  • When to use Application Silos
  • Frequent application updates & app management
  • Dedicated and/or predictable compute/network/storage
  • Application criticality
  • Business and security compliance
  • Fewer conflicts & compatibility issues between apps
  • Predictability scalability
  • Do not overscubscribe CPU or memory (consider memory reservations)
  • 1 vCPU to each physical core and enable hyper threading
  • 4 vCPU is the “sweet spot”
  • Disable DRS for RDS Hosts & View Connection/Security Servers
  • Avg IOPS: Light is 3–6, Medium is 6–10; less than virtual desktops
  • The View Optimization Tool comes with 2008/2012 Optimizations
  • Workspace: One login, one experience, any device
  • SaaS Apps, Citrix XenApp, Web Links, Office 265, Google Apps, Packaged ThinApps, Horizon Hosted Apps, Virtual Desktops
  • Aggregation of multiple Horizon pods
  • Multiple forest AD support
  • XenDesktop Virtual Desktops are not supported
  • Workspace does not proxy any XenApp traffic
  • Cloud Pod Architecture not currently supported on Workspace
  • Client Updates:
  • Uniform look and feel of Windows & Mac desktop clients
  • Roaming IP Capabilities: maintain connection through endpoint IP address changes without losing connection
  • Can use old versions of clients with 6.0 unless you want to do apps
  • Automation, Self Service, and Monitoring
  • VMware View Admin API Integration
  • Many common admin takes will be able to be automated with vCO
  • Limited API functionality availability in itial release
  • Focused on automating basic administrative functions
Show your support

Clapping shows how much you appreciated Earl Gay’s story.