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
Procedure
u
On any View Connection Server instance in the pod, run the lmvutil command with
the --initialize option.
lmvutil --initialize
For example:
lmvutil --authAs adminEast --authDomain domainEast --authPassword "*" --initialize
In this example, the user is authenticating as adminEast in the domain domainEast. Because the user
types "*" instead of an actual password, the command prompts the user for a password. You must
provide authentication information, even if you are logged in as the same administrator user that runs
the lmvutil command.
During the initialization process, View sets up the Global Data Layer on each View Connection Server
instance in the pod, configures the VIPA interpod communication channel, and establishes a replication
agreement between each View Connection Server instance. The initialization process can take several
minutes.
After the initialization process is finished, the pod federation contains a single initialized pod. The Cloud
Pod Architecture feature assigns a default name to the pod based on the host name of the View Connection
Server instance on which you ran the initialization command. For example, if the host name is CS1, the
default pod name is Cluster-CS1. You can change the default pod name. See “Find and Change a Pod
Name,” on page 17.
What to do next
To add more pods to the pod federation, see “Join Pods to the Pod Federation,” on page 16.
Join Pods to the Pod Federation
During the Cloud Pod Architecture initialization process, the Cloud Pod Architecture feature creates a pod
federation that contains a single pod. You can use the lmvutil command to join additional pods to the pod
federation. Joining additional pods is optional.
IMPORTANT Do not stop or start a View Connection Server instance while you are joining it to a pod
federation. The View Connection Server service might not restart correctly. You can stop and start the View
Connection Server after it is successfully joined to the pod federation.
Prerequisites
n
Make sure that the View Connection Server instances that you want to join have different host names.
You cannot join servers that have the same name, even if they are in different domains.
n
Become familiar with the lmvutil command authentication options and requirements and verify that
you have sufficient privileges to run the lmvutil command. See “lmvutil Command Authentication,”
on page 43.
n
Initialize the Cloud Pod Architecture feature. See “Initialize the Cloud Pod Architecture Feature,” on
page 15.
Administering View Cloud Pod Architecture
16 VMware, Inc.