Hardware VDI vs. Software VDI

35
Session Title: Session Title: Hypervisor-based Hypervisor-based VDI versus blade VDI versus blade PCs: What's the PCs: What's the real performance real performance and cost and cost difference? difference? Glenda Canfield Glenda Canfield

description

Pros & Cons of Hardware vs. Software VDI

Transcript of Hardware VDI vs. Software VDI

Page 1: Hardware VDI vs. Software VDI

Session Title: Session Title: Hypervisor-based Hypervisor-based VDI versus blade VDI versus blade PCs: What's the PCs: What's the

real performance real performance and cost and cost

difference? difference? Glenda CanfieldGlenda Canfield

Page 2: Hardware VDI vs. Software VDI

AgendaAgenda

Why virtual desktop infrastructure Why virtual desktop infrastructure (vdi)?(vdi)?

What is vdi? What is vdi? HP’s vdi implementationHP’s vdi implementation What are Blade PC’s / Consolidated What are Blade PC’s / Consolidated

Client InfrastructureClient Infrastructure What’s the difference in Administrative What’s the difference in Administrative

Overhead & CostOverhead & Cost Key points to take awayKey points to take away

Page 3: Hardware VDI vs. Software VDI

Remote/Consolidated Remote/Consolidated PCPC

Address Critical Business IT Issues:Improves data security and privacyCentralizes management for lower costsLowers power and cooling costsEnables IT to address business opportunitiesUnburden IT:A fundamental shift in how IT manages end-user computingApplies datacenter practices and resources for end-users computingEnd users continue to have traditional, personalized desktop look-and-feel

Remote PC’s

Page 4: Hardware VDI vs. Software VDI

Distributed vs. Remote PCsDistributed vs. Remote PCsWhat is the difference?What is the difference?

Personal Computer

Windows OS

Applications

Thin Client

RDP/RGS

HP Session Allocation Mgr

Blade PC

Windows OS

Applications

Thin Clients

RDP/ICA

Citrix or Terminal Services

Application Server

Application

Server OS

Distributed PCDistributed PC Single user per Single user per

Desktop PCDesktop PC

Remote PCRemote PC

HP CCIHP CCISingle user per Single user per

Blade PCBlade PC

HP VDIHP VDIMultiple users Multiple users

accessing virtual accessing virtual PC’s per serverPC’s per server

Terminal Terminal Server/CitrixServer/Citrix

Multiple users Multiple users accessing accessing

applications per applications per serverserver

Current Current Paradigm Paradigm

Performance Performance StandardStandard

Most FlexibleMost Flexible

Page 5: Hardware VDI vs. Software VDI

Challenges of Desktop Challenges of Desktop ManagementManagement

Remote locationLittle IT Skills locally

Distributed workforceGuest workers and telecommutersOff-shoring and outsourcing of business functions

Complex hardware managementMultiple makes and modelsUnending hardware upgrade cycles

Rising cost of PC ManagementOS and application deploymentBackup and recovery

Limited control of PCsSecurity of sensitive dataCompliance with regulations (SOX, HIPPA)

Page 6: Hardware VDI vs. Software VDI

VDIVDI Data securityData security corporate security initiatives and legally mandated regulatory compliance corporate security initiatives and legally mandated regulatory compliance

Ease & control of centralized managementEase & control of centralized management rising apex associated with upgrading and patching older desktopsrising apex associated with upgrading and patching older desktops Impact of dual/quad core processorsImpact of dual/quad core processors dramatically lowers cost per seatdramatically lowers cost per seat

Broader user baseBroader user base Virtualization technology provides a customized virtual desktop experience for Virtualization technology provides a customized virtual desktop experience for

the userthe user Application compatibility in virtual environmentApplication compatibility in virtual environment

Virtualization-savvy customerVirtualization-savvy customer Customer have experience running virtualization softwareCustomer have experience running virtualization software

Page 7: Hardware VDI vs. Software VDI

Desktop virtualization – an Desktop virtualization – an overviewoverview

VM

SAN

SAN

Desktop

HP Thin Client

PDA

VM

VM

VM

VM

VM

VM

VM

ConnectionBroker Request

Data Center

Internet

or

LAN/WAN

VMware ESX

VMware ESX

Page 8: Hardware VDI vs. Software VDI

Desktop Virtualization - Desktop Virtualization - OverviewOverview

Desktop virtualization – an overviewImproves manageability

Centralizes resources and controlIncreases standardizationReduces cost of administrationEnables rapid deployment of desktops

Increases flexibilityEnables pooling and sharing of desktop infrastructureSeamless desktop experience anywhere

Simplifies securityCentralizes dataCentralizes control

Page 9: Hardware VDI vs. Software VDI

VDI ComponentsVDI Components

Page 10: Hardware VDI vs. Software VDI

VDI Scenario’sVDI Scenario’s

Two basic implementation’s Static 1:1 Every user assigned a VM / Blade

PC connects by it’s IP address or name Dynamic Connection broker connects user to a

VM / Blade PC in a pool and returns VM / Blade PC to pool when the user disconnects

Page 11: Hardware VDI vs. Software VDI

Core requirementsCore requirements Virtualization technologyVirtualization technology Remote protocolRemote protocol Desktop OS and applicationsDesktop OS and applications

Optional componentsOptional components Connection managerConnection manager

ProvidersProviders VMwareVMware

VDI & ESXVDI & ESX MicrosoftMicrosoft

Guest OS, MS V - Motion, RDP,Guest OS, MS V - Motion, RDP,and Softricityand Softricity

CitrixCitrix Presentation ServerPresentation Server XenSource ServerXenSource Server XenDesktop BrokerXenDesktop Broker

SoftwareSoftware

Page 12: Hardware VDI vs. Software VDI

Servers for VDIServers for VDI

Any server on the Any server on the VMware HCLVMware HCL

Works with Microsoft Virtual ServerWorks with Microsoft Virtual Server Some are more favored than othersSome are more favored than others

Excellent for bladesExcellent for blades Traditional VMware Traditional VMware

best sellersbest sellers

Page 13: Hardware VDI vs. Software VDI

VDI User DensityVDI User Density

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Page 14: Hardware VDI vs. Software VDI

StorageStorage

Tremendous storage Tremendous storage opportunityopportunity

Storage is the backbone of Storage is the backbone of VDI solutionsVDI solutions

Careful planning is imperativeCareful planning is imperative How much space per userHow much space per user Investment matches the Investment matches the

importance of the dataimportance of the data Architecture does not have to be Architecture does not have to be

“user data on VM” so variety of “user data on VM” so variety of storage may be neededstorage may be needed

Page 15: Hardware VDI vs. Software VDI

Sizing considerationsSizing considerations Sizing must account forSizing must account for

Number and type of users on the systemNumber and type of users on the system Disk/storage controllersDisk/storage controllers Memory resourcesMemory resources Network sizing and latencyNetwork sizing and latency

Data redirectionData redirection PrintingPrinting Local device redirectionLocal device redirection Remote desktop protocolRemote desktop protocol

Server selection vs. Blade PC’s vs. Server selection vs. Blade PC’s vs. Workstation BladesWorkstation Blades

Page 16: Hardware VDI vs. Software VDI

CCI / Blade PC’sCCI / Blade PC’s

What are they?What are they? How are they Managed?How are they Managed? What’s the use case?What’s the use case? How much do they cost?How much do they cost?

Page 17: Hardware VDI vs. Software VDI

What is CCI/Blade PC’sWhat is CCI/Blade PC’s

Created by the Industry Standard Created by the Industry Standard Server Team @ HPServer Team @ HP

Splintered Off – to become CCISplintered Off – to become CCI Essentially they are Server Blades Essentially they are Server Blades

with far less power and less with far less power and less manageabilitymanageability

Page 18: Hardware VDI vs. Software VDI

How are they managedHow are they managed

They have an AI that is used for They have an AI that is used for managementmanagement

No ILO SupportNo ILO Support

Page 19: Hardware VDI vs. Software VDI

What’s the Use Case for What’s the Use Case for Blade PC’sBlade PC’s

Each user gets their own Hardware Each user gets their own Hardware ResourceResource

They have GPU’s in them (most They have GPU’s in them (most servers do NOT)servers do NOT)

Even if the server had a GPU in it in Even if the server had a GPU in it in a Hypervisor Scenario Today you a Hypervisor Scenario Today you cannot leverage it because of I/O cannot leverage it because of I/O issuesissues

Page 20: Hardware VDI vs. Software VDI

How do they scaleHow do they scale

Very easy to scale – Each user gets Very easy to scale – Each user gets their own bladetheir own blade

They have less single points of They have less single points of failure than “traditional” VDIfailure than “traditional” VDI

VMWare /XenSource are complex to VMWare /XenSource are complex to scale compared to Blade PC’sscale compared to Blade PC’s

Page 21: Hardware VDI vs. Software VDI

Capacity & Scalability: Capacity & Scalability: Machine DensityMachine DensityEvaluation Evaluation

CriteriaCriteriaWhat density level will meet user performance targets?What density level will meet user performance targets?

Driving Driving FactorsFactors

Density in a virtualized environment is limited by practical Density in a virtualized environment is limited by practical considerations.considerations.Background

VMware ESX architecture combined with the demands of a remote desktop computing VM place practical limitations on the number of VMs per physical host

• # of VMs per processor core• memory needs of VMs vs. amount of memory in the host server• host server subsystems technology (storage, memory, CPU, etc.)

General Guidelines (actuals vary by implementation)

• sweet spot seems to be 6 VMs per processor core−lower for heavier loads, higher (maximum 10) for light loads

• consensus seems to be no more than 25% memory over commitment

Complementary technology higher speed CPUs more (and faster) memory faster storage subsystems VMware resource management

Alternate technology HP blade PCs provide a consistent / fixed base for capacity planning HP blade PCs provide performance consistent with dedicated hardware

Page 22: Hardware VDI vs. Software VDI

Capacity and Scalability: Capacity and Scalability: StorageStorage

Evaluation Evaluation CriteriaCriteria

What storage configuration meets both desired user performance What storage configuration meets both desired user performance targets and business (e.g. cost) needs?targets and business (e.g. cost) needs?

Driving Driving FactorsFactors

Density in a virtualized environment present unique Density in a virtualized environment present unique challenges to a data center architecture.challenges to a data center architecture.

BackgroundBackgroundCarefully size storage as high VM density can require complex configurations as each VM has it’s own Carefully size storage as high VM density can require complex configurations as each VM has it’s own storage requirement for the OS, image, applications, etc…storage requirement for the OS, image, applications, etc… Incorrect / insufficient storage configuration can result in a direct impact to VDI end usersIncorrect / insufficient storage configuration can result in a direct impact to VDI end users

VMs and their host servers can be affected by storage bottlenecksVMs and their host servers can be affected by storage bottlenecks Tiered storage is one recommendationTiered storage is one recommendation

Local storage for ESX bootLocal storage for ESX boot SAN for VMs (iSCSI for low performance / kiosk VMs)SAN for VMs (iSCSI for low performance / kiosk VMs) NAS for redirected user dataNAS for redirected user data Separate file system (SAN or local) for redirected kernel swap filesSeparate file system (SAN or local) for redirected kernel swap files

General guidelinesGeneral guidelinesLimits have been presented by HP and VMWare for configuring SAN storage in a VDI environmentLimits have been presented by HP and VMWare for configuring SAN storage in a VDI environment

Best practice is 10 - 20 VMs per LUN (30 maximum)Best practice is 10 - 20 VMs per LUN (30 maximum) 100 - 200GB per LUN100 - 200GB per LUN

Complementary technologyComplementary technology HP storage products (SAN, NAS, iSCSI, direct attach)HP storage products (SAN, NAS, iSCSI, direct attach) HP storage virtualizationHP storage virtualization shared storage / streaming for OS and applicationsshared storage / streaming for OS and applications

Alternate technologyAlternate technology HP blade PCs can utilize either existing local blade PC hard drive or redirected to network HP blade PCs can utilize either existing local blade PC hard drive or redirected to network

storagestorage

Page 23: Hardware VDI vs. Software VDI

Performance CPUPerformance CPUBackgroundBackgroundVMWare identifies VDI system loads as “highly interactive” environments bound by the limits of the vCPU VMWare identifies VDI system loads as “highly interactive” environments bound by the limits of the vCPU

vCPU utilization can be high (up to 100%) and uneven with large / frequent fluctuationsvCPU utilization can be high (up to 100%) and uneven with large / frequent fluctuations

In general, CPU-bound environments present a higher vCPU virtualization overheadIn general, CPU-bound environments present a higher vCPU virtualization overhead VMware scheduler must schedule vCPU execution when resource is available on a physical CPUVMware scheduler must schedule vCPU execution when resource is available on a physical CPU

If no resources are available, the machine is left in a “ready” state during which all VM operation is suspended If no resources are available, the machine is left in a “ready” state during which all VM operation is suspended (ready states can range from very minimal to significant)(ready states can range from very minimal to significant)

CPU resource control (such as reservations and limits) can result in an increase in ready timeCPU resource control (such as reservations and limits) can result in an increase in ready time vSMP scheduling in a VDI environment can result in vSMP scheduling in a VDI environment can result in significantsignificant scheduling issues scheduling issues

General guidelinesGeneral guidelines (actuals vary widely by implementation) (actuals vary widely by implementation)

Size VM density accordingly (start small, then increase incrementally)Size VM density accordingly (start small, then increase incrementally) Avoid the use of vSMP in a VDI environmentAvoid the use of vSMP in a VDI environment Monitor key CPU and vCPU performance statisticsMonitor key CPU and vCPU performance statistics Carefully examine, plan, and Carefully examine, plan, and graduallygradually implement the use of resource management implement the use of resource management Carefully adjust server specific CPU tuning settingsCarefully adjust server specific CPU tuning settings

Complementary technologyComplementary technology faster CPUs with more physical coresfaster CPUs with more physical cores

Alternate technologyAlternate technology HP blade PCs provide dedicated CPU resource for each bladeHP blade PCs provide dedicated CPU resource for each blade

Page 24: Hardware VDI vs. Software VDI

How Much do they costHow Much do they cost

1500-2000 per blade not including 1500-2000 per blade not including the enclosurethe enclosure

Page 25: Hardware VDI vs. Software VDI

Categories of Evaluation Categories of Evaluation MetricsMetrics

Quantitative Host up timeVM up time

Response time LatencyCPU Utilization %CPU Ready %Allocated memory utilization % (host)Allocated memory utilization % (guest)Memory balooningvmKernal swapping

Storage I/O UtilizationNetwork Network Utilization

External storageNetwork InfrastructureProvisioning TimeTrouble Response / Resolution time

AvailabilityEnd-User Performance

CPU

Subsystem/Infrastructure

Systems Management

Host Server Performance

Memory

Page 26: Hardware VDI vs. Software VDI

What are Workstation What are Workstation BladesBlades

Page 27: Hardware VDI vs. Software VDI

Whats the use caseWhats the use case

Page 28: Hardware VDI vs. Software VDI

How do they scaleHow do they scale

Page 29: Hardware VDI vs. Software VDI

How much do they costHow much do they cost

Page 30: Hardware VDI vs. Software VDI

Basic Connection Broker Basic Connection Broker FunctionFunction

12,3

4

6

5

Client sends a connection request to Client sends a connection request to the connection broker. Some the connection broker. Some connection brokers offer a specific connection brokers offer a specific client to facilitate the connection client to facilitate the connection and most provide the option to and most provide the option to connect using a Browser, connect using a Browser,

The Connection broker validates the The Connection broker validates the user name. user name.

Most connection brokers provide the Most connection brokers provide the ability for the user to access ability for the user to access multiple VM Pools. If the user is multiple VM Pools. If the user is permitted to access pools they are permitted to access pools they are prompted with the pool they wish to prompted with the pool they wish to connect to. connect to.

The connection broker then provides The connection broker then provides a RDP connection to an available a RDP connection to an available Virtual machine in the pool. Virtual machine in the pool.

The Client Connects to the assigned The Client Connects to the assigned VMVM

The Connection Broker is then The Connection Broker is then updated with the machines current updated with the machines current status – Activestatus – Active

When user disconnects When user disconnects the connection broker then makes the connection broker then makes the virtual machine available to the virtual machine available to another user. another user.

Page 31: Hardware VDI vs. Software VDI

ProtocolsProtocols

Can’t talk about VDI without going Can’t talk about VDI without going through the different protocolsthrough the different protocols

RGSRGS ICAICA RDPRDP

Page 32: Hardware VDI vs. Software VDI

The need for desktop The need for desktop virtualizationvirtualization

Low Resource Utilization

The desktop is the least utilized resource on the

network!

Security Threats

Data Theft Virus / Malware

Phishing Hacking

Need for preventive/ proactive measures

Heterogeneity High Management Costs Admin Inefficiencies

> 70% of TCO ($6,800* / user/ year) ) *Gartner

Too tactically focused

Page 33: Hardware VDI vs. Software VDI

What is the best option What is the best option for youfor you

Depends on your end goalDepends on your end goal

Page 34: Hardware VDI vs. Software VDI

Summary Key PointsSummary Key Points

Page 35: Hardware VDI vs. Software VDI

Questions?Questions?