Administering View Cloud Pod Architecture
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
- Creating Cloud Pod Architecture Sites
- Entitling Users and Groups in the Pod Federation
- Finding and Allocating Desktops and Applications in the Pod Federation
- Global Entitlement Example
- Cloud Pod Architecture Topology Limits
- Cloud Pod Architecture Port Requirements
- Security Considerations for Cloud Pod Architecture Topologies
- Setting Up a 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 and Application Sessions in the Pod Federation
- Determine the Effective Home Site for a User
- Add a Pod to a Site
- Modifying Global Entitlements
- Remove a Home Site Association
- Remove a Pod From the Pod Federation
- Uninitialize the Cloud Pod Architecture Feature
- lmvutil Command Reference
- lmvutil Command Use
- Initializing the Cloud Pod Architecture Feature
- Disabling the Cloud Pod Architecture Feature
- Managing Pod Federations
- Managing Sites
- Managing Global Entitlements
- Managing Home Sites
- Viewing a Cloud Pod Architecture Configuration
- Listing Global Entitlements
- Listing the Pools in a Global Entitlement
- Listing the Users or Groups in a Global Entitlement
- Listing the Home Sites for a User or Group
- Listing the Effective Home Site for a User
- Listing Dedicated Desktop Pool Assignments
- Listing the Pods or Sites in a Cloud Pod Architecture Topology
- Managing SSL Certificates
- Index
Sharing Key Data in the Global Data Layer
View Connection Server instances in a pod federation use the Global Data Layer to share key data. Shared
data includes information about the pod federation topology, user and group entitlements, policies, and
other Cloud Pod Architecture configuration information.
In a Cloud Pod Architecture environment, shared data is replicated on every View Connection Server
instance in a pod federation. Entitlement and topology configuration information stored in the Global Data
Layer determines where and how desktops are allocated across the pod federation.
View sets up the Global Data Layer on each View Connection Server instance in a pod federation when you
initialize the Cloud Pod Architecture feature.
Sending Messages Between Pods
View Connection Server instances communicate in a Cloud Pod Architecture environment by using an
interpod communication protocol called the View InterPod API (VIPA).
View Connection Server instances use the VIPA communication channel to launch new desktops, find
existing desktops, and share health status data and other information. View configures the VIPA
communication channel when you initialize the Cloud Pod Architecture feature.
Configuring and Managing a Cloud Pod Architecture Environment
You use View Administrator and the lmvutil command-line interface to configure and manage a Cloud Pod
Architecture environment. lmvutil is installed as part of the View installation. You can also use View
Administrator to view pod health and desktop session information.
NOTE You cannot use View Administrator to create and manage Cloud Pod Architecture home sites. You
must use the lmvutil command to perform these tasks.
Cloud Pod Architecture Limitations
The Cloud Pod Architecture feature is not supported in an IPv6 environment.
Administering View Cloud Pod Architecture
8 VMware, Inc.