VMware Horizon 7 Series – Part 5a – Cloud Pod Architecture

Cloud Pod Architecture lets you publish a single icon that load balances connections across multiple pools in multiple pods in multiple sites (datacenters).

  • Global Entitlements – Entitlements are the same thing as icons. When you create an entitlement (local or global), you are publishing an icon from a pool.
    • For local entitlement, the icon is only published from one pool.
    • For global entitlement, the icon can be published from multiple pools. The pools can be in one pod or from multiple pods.
    • Don’t configure both global and local entitlements for the same pool.
    • A single pool can only belong to one global entitlement.
    • Horizon 6.2 and newer supports Global Entitlements for applications. However, it’s one application per global entitlement.
  • Pod Federation – Global entitlements can’t be created until a Pod Federation is created. This federation could be one pod or multiple pods.
    • The pods can be separated into sites. A site can contain multiple pods.
  • Global Load Balancing – Use NetScaler GSLB or F5 GTM to connect Horizon Clients to a globally available Horizon Connection Server. The connected Horizon Connection Server then uses Global Entitlements to select a site/pod/pool.
    • When a user launches a Global Entitlement, the Connection Server selects a pod based on the Global Entitlement Scoping, which can be All Sites, Within site, or Within Pod. This is from the perspective of the Connection Server the user is currently connected to. Horizon will prefer the local pod if possible.
    • Users or groups can be assigned to Home Sites. Global Entitlements can be configured to prefer Home Sites over the normal site/pod selection criteria.
  • Dedicated Assignment – For Dedicated Assignment pools, global entitlement only helps with the initial connection. Once the user is assigned to a desktop then that desktop is always selected. Users are not automatically provided with a desktop from another site if the site containing their dedicated desktop has gone down. The desktop request will fail because the dedicated desktop isn’t available. The administrator could configure a separate Global Entitlement for the users to provide a floating desktop until such time the original site recovers. That floating entitlement should be arranged to deliver desktops from other sites as required.
  • Firewall Ports – The Horizon Connection Servers participating in Cloud Pod Architecture communicate with each other over TCP 22389, TCP 22636, and TCP 8472. Make sure these ports are open.
  • RBAC – View Administrator includes a new administrator privilege: Manage Global Sessions. The regular Administrators role has access to multiple pods. The new Local Administrators role can only manage the local pod.

Limits:

  • Max users = 50,000
  • Max Pods = 25
  • Max Sites = 5
  • Max Horizon Connection Servers = 125

Traffic flow

  • Use F5 or NetScaler to connect users to an Horizon Connection Server in any pod. If active/active, use proximity load balancing to control which pod is initially accessed.
  • The Horizon Connection Server looks up the Global Entitlements to determine the destination pod for the Pool.
  • User’s PCoIP session goes through the initially connected Horizon Connection Server and across the DCI (Datacenter Interconnect) circuit to the remote pod. There’s no way to re-route Blast/PCoIP through a Horizon Connection Server in the remote pod. In fact, the Horizon Connection Servers in the remote pod are never accessed. You need sufficient DCI bandwidth to handle this Blast/PCoIP traffic.

Configuring First Pod

  1. In View Administrator, on the left, expand View Configuration and click Cloud Pod Architecture.
  2. On the right, click Initialize the Cloud Pod Architecture feature.
    1
  3. Click OK to initialize.
    2
  4. A status page is displayed.
    3
  5. Click OK to reload the client.
    4
  6. On the left, expand View Configuration and click Cloud Pod Architecture.
    5
  7. On the right, feel free to rename the federation by clicking the Edit button.
    6
    7
  8. On the left, expand View Configuration and click Sites.
    8
  9. On the right, click the Edit button to rename the Default First Site to be more descriptive.
    9
    10
  10. If you click the site to highlight it, you can Edit the Pod in the lower half to make the name more descriptive.
    11
    12
  11. If you add a Replica server after global entitlements are enabled, see KB2080521 Setting up the Cloud Pod Architecture feature on a replicated View Connection Server instance.
  12. See KB2080522 Restoring View Connection Server instances in a Cloud Pod Architecture pod federation.

Additional Pods – Join Federation

  1. Connect to View Administrator in the 2nd pod.
  2. On the left, expand View Configuration and click Cloud Pod Architecture.
  3. On the right, click Join the pod federation.
    13
  4. Enter the name of an existing Horizon Connection Server that is already joined to the federation.
  5. Enter credentials and click OK.
    14
  6. The Join status is displayed.
    15
  7. Click OK to reload the client.
    16
  8. On the left, expand View Configuration and click Sites.
    17
  9. If this pod is in a different site then click Add to create a new site.
    18
  10. Give the site a name and click OK.
    19
  11. Highlight the 1st site.
  12. On the bottom, highlight the new pod and click Edit.
    20
  13. Rename the pod and put it in the 2nd site. Click OK.
    21

Leave a Reply

Your email address will not be published. Required fields are marked *