Administering View Cloud Pod Architecture

Introduction to Cloud Pod
Architecture 1
The Cloud Pod Architecture feature uses standard View components to provide cross-datacenter
administration, global and flexible user-to-desktop mapping, high availability desktops, and disaster
recovery capabilities.
This chapter includes the following topics:
n
“Understanding Cloud Pod Architecture,” on page 7
n
“Configuring and Managing a Cloud Pod Architecture Environment,” on page 8
n
“Cloud Pod Architecture Limitations,” on page 8
Understanding Cloud Pod Architecture
With the Cloud Pod Architecture feature, you can link together multiple View pods to provide a single large
desktop and application brokering and management environment.
A View pod consists of a set of View Connection Server instances, shared storage, a database server, and the
vSphere and network infrastructures required to host desktop virtual machines and application pools. In a
traditional View implementation, you manage each pod independently. With the Cloud Pod Architecture
feature, you can join together multiple pods to form a single View implementation called a pod federation.
A pod federation can span multiple sites and datacenters and simultaneously simplify the administration
effort required to manage a large-scale View deployment.
Figure 1‑1. Basic Cloud Pod Architecture Topology
Security
Server
User
View
Connection
Server
View
Connection
Server
Security
Server
View
Connection
Server
View
Connection
Server
Security
Server
Security
Server
London Pod
London Datacenter
Interpod
communication
Remote
desktop or
application
New York Pod
New York Datacenter
Global Data Layer
In the example topology, two previously standalone View pods in different datacenters are joined together
to form a single pod federation. An end user in this environment can connect to a View Connection Server
instance in the New York datacenter and receive a desktop or application in the London data center.
VMware, Inc.
7