38
Planning a Successful Cloud Design from Workload to Infrastructure Tim Mackey Citrix Cloud Evangelist

Planning a Successful Cloud - Design from Workload to Infrastructure

Embed Size (px)

DESCRIPTION

Planning a Successful Cloud - Design from Workload to Infrastructure by Tim Mackey, Citrix Cloud Evangelist

Citation preview

Page 1: Planning a Successful Cloud - Design from Workload to Infrastructure

Planning a Successful CloudDesign from Workload to Infrastructure

Tim Mackey

Citrix Cloud Evangelist

Page 2: Planning a Successful Cloud - Design from Workload to Infrastructure

Private Cloud, Why Now?

• Valid alternative to public clouds that are cheap and readily available

• Speed and agility of deployment

• Control of corporate assets

• Cloud Management Platform market maturity

• Future-proofing for nextgen, webscale workloads

“An IaaS cloud is a highly automated

virtual infrastructure that enables self-service resource

requests, and consumption of the

shared environment is tracked for either

chargeback or showback purposes.”

Forrester Research

100’s of pilots and few production deployments in 2011; expected to be 10 times more in 2012 - Gartner

Page 3: Planning a Successful Cloud - Design from Workload to Infrastructure

150+ Large Scale Clouds

In DeploymentEnterprise and Education

Web 2.0

Service Providers and Telcos

Page 4: Planning a Successful Cloud - Design from Workload to Infrastructure

Enterprise Objectives for Cloud

Remove IT as a service delivery critical pathSelf ServiceSelf Service

Reduce IT operational costsManagement Automation

Management Automation

Consistent application and service deploymentWorkload Standardization

Workload Standardization

Manage complete infrastructure, regardless of scaleCentralized ManagementCentralized

Management

Drive reduced capital requirementsSmarter Virtualization

Smarter Virtualization

Capi

tal L

ever

age

Wor

kfor

ce L

ever

age

Visibility into user and line of business usageUsage MeteringUsage Metering

Page 5: Planning a Successful Cloud - Design from Workload to Infrastructure

Server Virtualization++ Cloud

Built for traditional enterprise apps and client-server compute

• Architected for 100s of hosts• Scale-up (server clusters) • Applications assume reliability• IT Management-centric [1:Dozens]• Proprietary vendor stack

Think: vCloud Director

Designed around big data, massive scale and next-gen applications

• Cloud architecture for 1000s of hosts• Scale-out (multi-site server farms)• Applications assume failure• Autonomic [1:1,000’s]• Open, value-added stack

Think: AWS, RAX, GCE, eBay, etc.

• More scalable• Lower cost• More open

Page 6: Planning a Successful Cloud - Design from Workload to Infrastructure

Key Features for Successful Clouds

• Select the correct hypervisor to best match workload needs• Seamlessly manage provisioning process across hypervisorsMulti-Hypervisor Support

• Provide optimal workload performance and availability• Management of multiple availability zones from a single consoleAvailability Zones

• Define virtual and physical network isolation rules• Support load balancing and VPN access rules

Flexible Network Management

• Flexible user, network and provisioning isolation rules• Ability to delegate tenancy for departments and divisionsTenant Isolation

• Freedom to define capacity with no per-VM licensesNo per-VM Licensing

Page 7: Planning a Successful Cloud - Design from Workload to Infrastructure

Server Virtualization++ Amazon-style Cloud

AvailabilityZone

AvailabilityZone

Object Storage

vCenter

vSphere

ESXiCluster

Enterprise Networking (e.g., VLAN)

Enterprise Storage (e.g., SAN)

ESXiCluster

ESXiCluster

CloudStack Management ServerServer Virtualization Availability Zone

AvailabilityZone

ORAND

Page 8: Planning a Successful Cloud - Design from Workload to Infrastructure

Best practices aren’t always

Page 9: Planning a Successful Cloud - Design from Workload to Infrastructure

Density in the cloud

Page 10: Planning a Successful Cloud - Design from Workload to Infrastructure

Traditional Server Virtualization

• Core Objectivesᵒ Server consolidationᵒ Power and cooling savingsᵒ Hardware independence

• Looks Likeᵒ VM Density < 20 ᵒ vCPU = pCPUᵒ vRAM = pRAMᵒ Low IOPSᵒ Redundancy mattersᵒ No templates

10

Page 11: Planning a Successful Cloud - Design from Workload to Infrastructure

Desktop Virtualization

• Core Objectivesᵒ Control of IPᵒ Ensuring patch complianceᵒ Supporting mobile workstyles

• Looks Likeᵒ 50 -100 VMs per hostᵒ 2-4 vCores = pCoreᵒ 1-2 vRAM = pRAMᵒ High IOPSᵒ Boot stormsᵒ Network contentionᵒ Highly templated

11

Page 12: Planning a Successful Cloud - Design from Workload to Infrastructure

Cloud Services

• Core Objectivesᵒ Agile provisioningᵒ High degrees of tenant isolationᵒ Low operating margins

• Looks Likeᵒ 50-250 VMs per hostᵒ 2-8 vCore = pCoreᵒ vRAM = pRAMᵒ Moderate IOPSᵒ Network contentionᵒ Largely templated

12

Page 13: Planning a Successful Cloud - Design from Workload to Infrastructure

Planning the network

Page 14: Planning a Successful Cloud - Design from Workload to Infrastructure

Before Virtualization

• Simple management model

• Provisioning took a long time

• Topologies fairly static

Page 15: Planning a Successful Cloud - Design from Workload to Infrastructure

Along Comes Server Virtualization

• Multiple VMs/hostᵒ Loss of visibilityᵒ Loss of control

• Edge moves into hostᵒ Network admins need to understand

server virtualization

Page 16: Planning a Successful Cloud - Design from Workload to Infrastructure

Example 1 – Mirroring Traffic

• Without virtualization this is pretty easy

• With virtualization you now have multiple VMs

Page 17: Planning a Successful Cloud - Design from Workload to Infrastructure

Example 1 – Mirroring Traffic

• Without virtualization this is pretty easy

• With virtualization you now have multiple VMsᵒ Plus VMs can move

• Better to monitor at virtual switch

Page 18: Planning a Successful Cloud - Design from Workload to Infrastructure

Example 2 – Network Policies

• Server admins have significant impact on the networkᵒ IP and MAC Addressᵒ Virtual NICsᵒ Protocols and ports

• Granular network control requires awareness of virtual machinesᵒ Define policies at virtual switch

Page 19: Planning a Successful Cloud - Design from Workload to Infrastructure

Network Management Tools Lag

• Assumptions of fixed topologyᵒ Fine for physicalᵒ Challenge for dynamic environment

• Not virtualization awareᵒ Incorrect topologyᵒ Incomplete topologyᵒ VM actions obsolete data

X

Page 20: Planning a Successful Cloud - Design from Workload to Infrastructure

Virtual Machine Density Planning

• Host capacities are growing rapidlyᵒ vSphere 5 > 512 VMsᵒ RHEV 3 > 1000 VMsᵒ Hyper-V > 2048 VMs

• Clouds and VDI push limits

• Top of rack switch selection matters?ᵒ ARP tableᵒ Switching performance dropsᵒ VM starts, but can’t connect

VMVM

VMVMVM

VMVM

VMVMVM

Host 1

Host 2

VMVM

VMVMVM

VMVM

VMVM

Page 21: Planning a Successful Cloud - Design from Workload to Infrastructure

Storage choice is critical

Page 22: Planning a Successful Cloud - Design from Workload to Infrastructure

Shared storage growth and provisioning time

1,000

500

VMs

Cost, AU

100 200

500VMs

Provisioning efficiencyAU – arbitrary units

Page 23: Planning a Successful Cloud - Design from Workload to Infrastructure

Combined efficiency and storage evolution

Redesign

1,000

500

VMs

100 200 Cost, AU

VMs

1,000

500

Cost, AU100 200

?Alternatives

AU – arbitrary units

Page 24: Planning a Successful Cloud - Design from Workload to Infrastructure

Redesign

Efficiency and pod storage

1,000

500

VMs

100 200 Cost, AU

POD #1

POD #2

POD #31,000

500

VMs

100 200 Cost, AUAU – arbitrary units

No redesign

Page 25: Planning a Successful Cloud - Design from Workload to Infrastructure

What about local storage?

1,000

500

VMs

Cost, AU 100 200

50VMs

Provisioning efficiencyAU – arbitrary units

Page 26: Planning a Successful Cloud - Design from Workload to Infrastructure

PODtrend

Traditionaltrend

Cost-Performance Trends

Shared Storage Local Storage

1,000

500

VMs

Cost, AU100 200

1,000

500

VMs

100 200 Cost, AU

Local storage

Performancetrend

Local storagetrend

Page 27: Planning a Successful Cloud - Design from Workload to Infrastructure

Understanding disk usage and sizing

VM_COUNT * VM_DISK + SWAP = TOTAL_DISK

VM_COUNT * (OS_PARTITION + USR_DATA) + SWAP = TOTAL_DISK

VM_COUNT = (TOTAL_DISK – SWAP) ÷ (OS_PARTITION + USR_DATA)

VM_DISK SWAPUSR_DATAOS_PARTITION

TOTAL_DISK

Page 28: Planning a Successful Cloud - Design from Workload to Infrastructure

Templates and thin provisioning matter

VM_COUNT * USR_DATA + OS_PARTITION + SWAP = TOTAL_DISK

VM_COUNT = (TOTAL_DISK – SWAP – OS_PARTITION) ÷ USR_DATA

SWAP

TOTAL_DISK

OS_PARTITION USR_DATA

Page 29: Planning a Successful Cloud - Design from Workload to Infrastructure

Storage performance

IO per Disk

RAID PENALTY0 11 25 46 610 250 4

Write Penalties

RPM IOPS

SSD 5,000+

SAS 15,000 175

SAS 10,000 125

SAS 7,200 75

VM Utilization

ITEM ~VALUE

IOPS per VM 20

Size, KB 4-8

Writes, % 80

Reads, % 20

IOPS = [IOPS per DISK]*[Disk Count]*([% of Reads]+[% of Writes] ÷ [RAID Write Penalty])

VM_COUNT = IOPS ÷ [IOPS per VM]

Page 30: Planning a Successful Cloud - Design from Workload to Infrastructure

Blueprint for success ….

Page 31: Planning a Successful Cloud - Design from Workload to Infrastructure

Cloud Builder Lessons from Zynga

• Public clouds are minivans

• zCloud is a race carᵒ zCloud is optimized for social gamingᵒ Know your application requirements

• Don’t rent what you can own cheaperᵒ Cloud operator doesn’t care about your successᵒ Optimized applications might be key

• Ensure you have backup plansᵒ Usage can and does spikeᵒ Outages can and do happen

vs.

Page 32: Planning a Successful Cloud - Design from Workload to Infrastructure

Cloud Builder Lessons From Telcos

• Utility computing fits business modelᵒ Traditionally operate a low margin business modelᵒ Understand tiered service offeringsᵒ Have a history with instant provisioning

• Tiered service demands infrastructure flexibilityᵒ “Cost per instance” is paramountᵒ Charge extra for premium featuresᵒ Instance doesn’t imply virtualizationᵒ Be prepared to change vendors if better model appears

• Provisioning agility expectedᵒ Customers expect instant self service access and detailed billing

Page 33: Planning a Successful Cloud - Design from Workload to Infrastructure

Service Offerings

• Clearly define what you want to offerᵒ What types of applicationsᵒ Who has access, and who owns themᵒ What type of access

• Define how templates need to be managedᵒ Operating system supportᵒ Patching requirements

• Define expectations around compliance and availabilityᵒ Who owns backup and monitoring

Page 34: Planning a Successful Cloud - Design from Workload to Infrastructure

Define Tenancy Requirements

• Department data local to departmentᵒ Where is the application data stored

• Data and service isolationᵒ VM migration and host HAᵒ Network services

• Encryption of PII/PCIᵒ Where do keys live when data location unknownᵒ Need encryption designed for the cloud

• Showback to stakeholdersᵒ More than just usage, compliance and audits

Page 35: Planning a Successful Cloud - Design from Workload to Infrastructure

Virtualization Infrastructure

• Hypervisor defined by service offeringsᵒ Don’t select hypervisor based on “standards”ᵒ Understand true costs of virtualizationᵒ Multiple hypervisors are “OK”ᵒ Bare metal can be a hypervisor

• To “Pool” resources or notᵒ Is there a real requirement for pooled resourcesᵒ Can the cloud management solution do better?ᵒ Real cost of shared storage

• Primary storage defined by hypervisor

• Template storage defined by solutionᵒ Typically low cost options like NFS

Page 36: Planning a Successful Cloud - Design from Workload to Infrastructure

Cloud Operations

• Design for maintainability

• Monitor critical componentsᵒ Management servers and system support VMsᵒ Hypervisor hosts, and critical infrastructureᵒ End user deployment environments

If your cloud has maintenance windows, you’re doing it wrong.- Allan Leinwand Former CTO Zynga

Page 37: Planning a Successful Cloud - Design from Workload to Infrastructure

Secure multi-tenant cloud orchestration platform• Turn-key platform for IaaS delivery• Hypervisor agnostic• Massively scalable, secure and open• Simple deployment and administration

History• Project open sourced (GPLv3) May 2010• Acquired by Citrix July 2011• Relicensed under ASL v2 April 3rd, 2012• Apache incubating project April 16, 2012• Graduated March 20, 2013

Over 200 contributing organizations

Page 38: Planning a Successful Cloud - Design from Workload to Infrastructure

Work better. Live better.