PowerPoint Presentation

Architecting Your Cloud: Lessons Learned from 100 CloudStack Deployments Speaker: Shannon WilliamsVice President Market Development, Cloud Platforms

EMEA contact: Olivier MaesSr Dir Market Development EMEA, Cloud PlatformsOlivier.maes@citrix.com, twitter: @omaes721Cloud computing in 10 yearsComputing clouds will have standardizedServers/Storage/Networking will be commodities available on demand.Applications will be designed to leverage distributed computing resourcesKey questions wont have changedApplication PerformanceApplication ReliabilityInfrastructure Security/ComplianceOperational Costs

Goal: Deliver applications quicker with more reliably at a fraction of the current cost.Cloud computing today Start-ups and Web Companies are achieving the 10-year vision todayStandardizing on big public clouds (Amazon, Softlayer, BT, Terremark, etc.)Designing applications that can leverage distributed availability zones for reliabilityEnterprises are generally not leveraging cloud computing Most apps arent written for distributionSecurity/Compliance concerns over leveraging shared resourcesProven mechanism for delivering apps remains standard.

Goal: Provide improved access for developers and operators.Todays goal: provide a basic understanding of different cloud architecturesOutline a process for defining a cloudDescribe the building blocks used to deploy a computing cloudLook at traditional workloads and cloud workloadsConsider architectures that meet a broad set of requirements

Secure, multi-tenant cloud orchestration platformTurnkey platform for delivering IaaS cloudsHypervisor agnosticHighly scalable, secure and openComplete Self-service portalOpen source, open standardsDeploys on premise or as a hosted solution

Since 2008 CloudStack has powered hundreds of clouds

Since becoming part of Apache CS has explodedIt's just amazing! In just 3 months, CloudStack has gone directly to the same level as OpenStack is. This is much steeper community growth than I could have predicted (if anyone had asked me for predictions, that is...).

Source: Cloudstack has proof: Foundations is the way to create a FOSS community http://openlife.cc/blogs/2012/july/cloudstack-has-proof-foundations-way-create-foss-community

INFRA-STRUCTURE

DEV & TEST

DISASTERRECOVERY

BRIDGE &GATEWAY

BYOPLATFORM

WINDOWSON-DEMAND

YOURSERVICE

ESX Hyper-V XenServer KVM OVM VIRTUALIZATION

Compute

Storage

NetworkCloudPlatformPowered by Apache CloudStackCloudPortalCitrix CloudStackNetScalerCloudBridge7CloudPortal Delivers Cloud Apps & the Business Logic

AuthenticationAccount ProvisioningAccount ManagementCloud ManagementUser RolesPortal AdministrationAccount ManagementPricing & BillingProduct DefinitionCatalog ManagementUsage TrackingBillingPayment ProcessingCustomerRelationshipSales CRMTicketing / HelpDeskCommunity ForumsService StatusDashboardUsage ReportingMessagingAlertsService StatusCloudPortalContent ManagementCustomer RelationshipBillingAuthenticationLiferaySalesforce.comZuoraCAS (LDAP/AD)DrupalPlugins

Self Service Cloud Apps

Account S elf ServiceDelegated Account ManagementCustomer ManagementFlexible and Extensible SDKEach cloud drives unique requirements9Service ProvidersEnterpriseWeb 2.0

9

IaaS CloudArchitecture definition is a processWorkload categories give us a starting point1111Possible to categorize workloads into two sets Cloud WorkloadsTraditional WorkloadReliable hardware, backup entire cloud, and restore for users when failure happensCloud WorkloadTell users to expect failure. Users to build apps that can withstand infrastructure failureBoth types of workloads must run reliably in the cloud

321RTO (Recover Time Objective)RPO (Recovery Point Objective)Mission CriticalCriticalRegularReliability & DR are Workload SpecificRecovery Point Objective (RPO) and Recovery Time Objective (RTO) should be determined based on workloadsDeployment and DR plan should be designed per RPO, RTO requirementsDifferent types of workloads will achieve workload reliability in different ways$$$$$Link AggregationStorage Multi-pathingVM HA, Fault ToleranceVM Live MigrationVM Backup/Snapshots Multi-site RedundancyChaos MonkeyEphemeral ResourcesTraditional WorkloadCloud WorkloadExpect failure. Design app for failure. Self-service failure handlingThink Amazon Web ServicesExpect reliability. Back-up entire cloud. Admin controlled failure handlingThink Server Virtualization 1.0Workload reliability drives unique requirementsOther functionality will impact design as wellEvery cloud starts with basic building blocksServersStorageNetworkingHypervisorServer ClustersServer ClustersServer ClustersNetworking Storage

ResourcesAvailability ZonesCloudsTwo sample zone architecturesTraditional server virtualization zoneAmazon-Style availability zoneDesigning a zone for a traditional workloadvCenterESXi ClusterESXi ClusterESXi ClusterEnterprise Networking (e.g., VLAN)Enterprise Storage (e.g., SAN) Hypervisor

Storage

SAN NetworkingL2 VLANs Network Services

Load BalancingPV-LANs Multi-tier Apps

Multi-tier VLANsOVFFeature Rich vSphere, vCenterDesigning a zone for a traditional workloadCan achieve significant reliability for applications running in one zone. Reliability of individual nodes is very high.All zone storage is replicated to a second storage platform (synchronous or asynchronous)In event of failure, images are recovered from second storage array.Existing workloads will run reliably.Little cost benefit over existing approachesvCenterESXi ClusterESXi ClusterESXi ClusterEnterprise Networking (e.g., VLAN)Enterprise Storage (e.g., SAN)Designing a zone for an Amazon-style workload Hypervisor

Storage

LocalEBSNetworking

L3SDN based L2Elastic IP Network Services

Security GroupsELB Multi-tier Apps

L3SDN based VPCSimple - XenServerObject storeGSLBCloudFormationSoftware Defined Networks (e.g., Security Groups, EIP, ELB,...)Amazon-Style Availability ZoneServer RacksServer RacksServer RacksServer RacksServer RacksServer RacksServer RacksServer RacksServer RacksServer RacksServer RacksServer RacksElastic Block StorageAvailability ZoneAvailability ZoneAvailability ZoneObject StorageSoftware Defined Networks (e.g., Security Groups, EIP, ELB,...)Amazon-Style Availability ZoneServer RacksServer RacksServer RacksServer RacksServer RacksServer RacksServer RacksServer RacksServer RacksServer RacksServer RacksServer RacksElastic Block StorageAmazon-Style Cloud Object store is critical for Amazon-style cloudCloudStack Mgmt. ServerAvailability ZoneAvailability ZoneAvailability ZoneObject StorageAmazon-Style CloudObject store is critical for Amazon-style cloudCloudStack Mgmt. ServerWorkloads are distributed across availability zonesNo guarantee on zone reliabilityApplications designed to handle node level failueDBs and Templates snapped to object store.In event of failure, images are recreated on new availability zone.Dramatically less expensiveCloud Transition General to Workload specificGeneral architecture for any workloadLimited definitive failure/disaster recovery strategyFocused on legacy or cloud app architectures

Workload-centric architectureWorkload-specific failure/disaster recoverySeparate legacy and cloud app architectures with interoperabilityPastTodayGeneralArchitectureTraditional-StyleAmazon-StyleObject StoragevCenterESXi ClusterESXi ClusterESXi ClusterEnterprise Networking (e.g., VLAN)Enterprise Storage (e.g., SAN)Availability ZoneAvailability ZoneAvailability ZoneServer Virtualization Availability ZoneCloudStack Mgmt. ServerSupport for different styles is required

CloudStack Management Cluster

San JoseMiamiLondonTokyo

Hosted Dehli

Hosted RioAvailability zones will be distributed globallyPrivate CloudPublicCloud ServicesEnterpriseData CenterDedicated resourceTotal control/securityInternal networkShared resourcesElastic scalingPay as you goPublic internetEnterpriseData CenterManagedPrivate CloudHosted Private CloudFederated/HybridCloud Services3rd partyoperatedEnterprise3rd party hosted & operatedMulti-tenant Users3rd party owned and operated SLA boundSecurityDedicated resourceMix of shared and dedicated resourcesShared facility and staffVPN accessOn PremiseHosted

Multi-tenant UsersAvailability zones are becoming on-demand

26Key takeawaysUnderstand your workload and the type of cloud you want to build.Consider the services you will be delivering from the cloud in the future.Choose a platform and architecture that is flexible enough to support you today and in the future.

Work better. Live better.Track01, track 1172573.92