6.0
Table Of Contents
- Administering View Cloud Pod Architecture
- Contents
- Administering View Cloud Pod Architecture
- Introduction to Cloud Pod Architecture
- Designing a Cloud Pod Architecture Topology
- Setting Up a Cloud Pod Architecture Environment
- Initialize the Cloud Pod Architecture Feature
- Join Pods to the Pod Federation
- Find and Change a Pod Name
- Create and Configure a Global Entitlement
- Create and Configure a Site
- Assign a Home Site to a User or Group
- Test a Cloud Pod Architecture Configuration
- Sample Scenario: Setting Up a Basic Cloud Pod Architecture Environment
- Managing a Cloud Pod Architecture Environment
- View a Cloud Pod Architecture Configuration
- View Pod Federation Health in View Administrator
- View Desktop Sessions in a Pod Federation
- Determine the Effective Home Site for a User
- Add a Pod to a Site
- Remove a Pod From a Pod Federation
- Modifying Global Entitlements
- Remove a Home Site Association
- Disable the Cloud Pod Architecture Feature
- lmvutil Command Reference
- Index
Global Entitlement Example
The following diagram is a conceptual example of a global entitlement. In this example, NYUser1 is a
member of the global entitlement called My Global Pool. My Global Pool provides an entitlement to three
floating desktop pools, called pool1, pool2, and pool3. pool1 and pool2 are in a pod called NY Pod in the
New York datacenter and pool3 and pool4 are in a pod called LDN Pod in the London datacenter.
New York Datacenter
Pod Federation
Global Entitlement
“My Global Pool”
Members:
NYUser1
NYUser2
Pools:
pool1
pool2
pool3
Scope: Any
pool1 pool2
NY Pod
London Datacenter
pool3 pool4
LDN Pod
NYUser1
Because My Global Pool has a scope policy of ANY, the Cloud Pod Architecture feature looks for desktops
across both NY Pod and LDN Pod when NYUser1 requests a desktop. The Cloud Pod Architecture feature
does not try to allocate a desktop from pool4 because pool4 is not part of My Global Pool.
If NYUser1 logs into NY Pod, the Cloud Pod Architecture feature allocates a desktop from pool1 or pool2, if
a desktop is available. If a desktop is not available in either pool1 or pool2, the Cloud Pod Architecture
feature allocates a desktop from pool3.
For information about creating global entitlements, see “Create and Configure a Global Entitlement,” on
page 18.
Cloud Pod Architecture Topology Limits
A typical Cloud Pod Architecture topology consists of two or more View pods, which are linked together in
a pod federation. Pod federations are subject to certain limits.
Table 2‑1. Pod Federation Limits
Component Limit
Desktops 20,000
Pods 4
Sites 2
View Connection Server instances 20
Administering View Cloud Pod Architecture
12 VMware, Inc.