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
Designing the Cloud Pod Architecture Topology
The insurance company designs a Cloud Pod Architecture topology that includes two sites, one for each
region.
Figure 3‑1. Sample Scenario Cloud Pod Architecture Topology
east1.example
East Pod 1
Eastern Region
east2.example east3.example
east4.example east5.example
central1.example
Central Pod 1
Central Region
central2.example central3.example
central4.example central5.example
central6.example
Central Pod 2
central7.example central8.example
central9.example central10.example
Sales A Sales B
Sales A
Sales B
Sales A
Sales B
In this topology, the Eastern region site contains a single pod that consists of five View Connection Server
instances called east1.example through east5.example.
The Central region site contains two pods, each of which contains five View Connection Server instances.
The View Connection Servers in the first pod are called central1.example through central5.example and the
View Connection Server instances in the second pod are called central6.example through central10.example.
Each pod in the topology contains two desktop pools, called Sales A and Sales B, of sales agent desktops.
Initializing the Cloud Pod Architecture Feature
A View administrator runs the lmvutil command with the --initialize option to intialize the Cloud Pod
Architecture feature.
A View administrator can run this command on any View Connection Server instance in a pod. In this
example, the View administrator runs the command on east1.example.
lmvutil --authAs adminEast --authDomain example --authPassword secret123 --initialize
The five View Connection Server instances in the insurance company's Eastern region are now part of a pod
federation.
Joining Each Pod to the Pod Federation
A View administrator runs the lmvutil command with the --join option on each pod in the Central region
to join those pods to the pod federation.
A View administrator can run this command on any View Connection Server instance in a pod. In this
example, the View administrator runs the command for the first pod on central1.example.
lmvutil --authAs adminCentral --authDomain example --authPassword secret123 --join --joinServer
east1.example --userName example\adminEast --password secret123
Chapter 3 Setting Up a Cloud Pod Architecture Environment
VMware, Inc. 25