© 2010 VMware Inc. All rights reserved

EUC2846 - View Enterprise Architecture Design and Implementation Best Practices John Dodge, Sr. Manager, Global Technology Solutions, Global EUC CoE, VMware, Inc.

Confidential1

Design decision entanglement

OS

CPU

Apps

Memory

StorageApps Memory

Storage?

CPU

OS !

Highly entangled decisions must come first

View Design Methodology

Use case definitionPersona, desktop, & pool Pod and blockVMware InfrastructureStorage designUser access device

4

An alternative way to think about use cases

Jobs

Constraints

Outcomes

Use case definition

5

Use Cases

Use Case 1 Workload Category

ConnectivityCategory

AppsOSDevices

Use Case 2 Workload Category

ConnectivityCategory

AppsOSDevices

Customer Requirements

Persona, desktop, and pool design

6

Persona, desktop & pool

PersonaNone

(no persistence)Native OS

Virtual

DesktopOS

Virtual hwLocal apps

Use cases and volume

Pool typesFloating

DedicatedLocal mode

Non-LC

ApplicationsVirtual

TraditionalSaaS

Display ProtocolBandwidth and latency

Features

Use Case attributes

7

Attribute Definition

Workload Category Standard worker

Connectivity classification LAN

Location(s) London

Time of use 7am-7pm GMT, Mon-Fri

Core applications Adobe Acrobat ReaderAdobe Flash playerMicrosoft Office 2010Microsoft IE6

User access device(s) Thin client, iPad

Use of video/multimedia No

Printers Follow me printing

Monitors and connection 1xVGA

Devices USB: Neatworks scanner

Authentication (e.g., Smartcard, SSO) Standard Windows Logon

Persona Application and user profile persistence

Workload categories

8

Attribute DefinitionTask worker user Limited privileges in OS

Cannot install applications or device drivers

Session will run few applications in total and a limited number of applications concurrently

User is not guaranteed session persistence except with redirected user persona

Standard worker user May have limited or granted full access privileges within the OS

May be able to install applications and devices

May or may not be guaranteed session and profile persistencePower user Full privileges to the local operating system

Expected to install applications and devices

Expects session and profile persistence

May expect shared profile in multiple sessions simultaneously

Connectivity classification

9

Attribute Definition

Low bandwidth User access via display protocol over moderate to low bandwidth connection with moderate to high latency (e.g., WAN, Internet).

Local mode Workload runs locally, whether connected to the LAN, connected to the corporate network via a WAN, or disconnected from the network

LAN User access over a high-speed (1GBE or higher), low latency (5ms>) network with low overall utilization

Pod and block design

10

Pod and Block

Pod(s)User/datacenter

topographySecurity boundariesBCDR requirements

Networking

P1 Block 1Pool types

AdministrationProvisioning frequency

Pool design

Px BlockyPool types

AdministrationProvisioning frequency

11 Confidential

vSphere Infrastructure design

12

vSphere Infrastructure

Mgmt block Block 1vCenter

ESX/ESXiNetworking

VMs + images

Pod and block design

Px BlockyvCenter

ESX/ESXiNetworking

VMs + images

Connection ServersSecurity SrvsInfrastructure

Access InfrastructureLoad balancing

Firewalls and VPNBandwidth

Storage design

13 Confidential

Storage

Mgmt block VMs datastoresOS

Disposable disksWorkload IOPSMax footprint

vSphere Infrastructure

RepositoriesHome directoriesPersistent disks

Profile storesTransfer server

TemplatesApplication

Server workloadsDR

User access device design

14

User access device

Clients Client mgmtPatches or updatesSoftware distributionAsset management

Preexisting equipmentOS Licensing

OSMonitorsDevicesSoftwareNetwork

Design Objectives

15 Confidential

Design Objectives

Functional

Non-functional

Constraints

Non-functional Specifications

Non-Functional Specifications (Service Qualities)

•Manageability•Security•Availability•Recoverability•Performance• Love

17

Related design considerations

18 Confidential

Constraints

19

Quality

Knowledge

Standards

Budget

Design Checklist

John Dodge design checklist * Simplicity * User involvement * Balance business and technical (best practices) * Design rationales * Clarity over ambiguity * Reusable * Simplicity

20

Follow this checklist to create lasting

designs

Logical and Technical Specs

Pursue simplicity—keep similar aspects of the design together• Group logical design elements with other logical elements• Combine technical specifications with other technical (or detailed)

specifications

Avoid repeating details whenever possible• Label a logical component once and consistently• Describe the technical specifications once and completely

21

Avoid repeating configuration items or specifications

Make high level logical designs easy to find and understand

Keep technical specs separate for interested parties

22

Implementation Best Practices

22

Key best practices and lessons learned

OS optimization

Antivirus resource demands

Storage design

PCoIP integration

Business case

Avoiding the meandering path to failure

Avoiding the path to failure

Assessment

PoC

PilotProduction design

Production deployment

Increasing odds of successful adoption