1. Architecting Your Cloud: Lessons Learned from 100 CloudStack Deployments Speaker: Shannon Williams Vice President Market Development, Cloud Platforms EMEA contact: Olivier Maes Sr Dir Market Development EMEA, Cloud Platforms Olivier.maes@citrix.comOlivier.maes@citrix.com, twitter: @omaes72

2. Cloud computing in 10 years Computing clouds will have standardized Servers/Storage/Networking will be commodities available on demand. Applications will be designed to leverage distributed computing resources Key questions won’t have changed  Application Performance  Application Reliability  Infrastructure Security/Compliance  Operational Costs Goal: Deliver applications quicker with more reliably at a fraction of the current cost.

3. Cloud computing today Start-ups and Web Companies are achieving the 10-year vision today  Standardizing on big public clouds (Amazon, Softlayer, BT, Terremark, etc.)  Designing applications that can leverage distributed availability zones for reliability Enterprises are generally not leveraging cloud computing  Most apps aren’t written for distribution  Security/Compliance concerns over leveraging shared resources  Proven mechanism for delivering apps remains standard. Goal: Provide improved access for developers and operators.

4. Today’s goal: provide a basic understanding of different cloud architectures Outline a process for defining a cloud Describe the building blocks used to deploy a computing cloud Look at traditional workloads and cloud workloads Consider architectures that meet a broad set of requirements

5. Secure, multi-tenant cloud orchestration platform –Turnkey platform for delivering IaaS clouds –Hypervisor agnostic –Highly scalable, secure and open –Complete Self-service portal –Open source, open standards –Deploys on premise or as a hosted solution Since 2008 CloudStack has powered hundreds of clouds

6. Since becoming part of Apache CS has exploded “It'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 http://openlife.cc/blogs/2012/july/cloudstack-has- proof-foundations-way-create-foss-community

7. INFRA- STRUCTURE DEV & TEST DISASTERRECOVERY BRIDGE & GATEWAY BYO PLATFORM WINDOWS ON-DEMAND YOUR SERVICE ESX Hyper-V XenServer KVM OVM VIRTUALIZATION VIRTUALIZATION ComputeCompute StorageStorageNetworkNetwork CloudPlatform Powered by Apache CloudStack CloudPortalCloudPortal NetScalerCloudBridge

8. CloudPortal Delivers Cloud Apps & the Business Logic Authentication Account Provisioning Account Management Cloud Management User Roles Portal Administration Account Management Pricing & Billing Product Definition Catalog Management Usage Tracking Billing Payment Processing Customer Relationship Sales CRM Ticketing / HelpDesk Community Forums Service Status Dashboard Usage Reporting Messaging Alerts Service Status CloudPortal Content ManagementCustomer RelationshipBillingAuthentication LiferaySalesforce.comZuoraCAS (LDAP/AD) Drupal Plugins Self Service Cloud Apps Account S elf Service Delegated Account Management Customer Management Flexible and Extensible SDK

9. Each cloud drives unique requirements 9 Service ProvidersEnterpriseWeb 2.0

10. Implement your environment Develop your technical architecture Determine the necessary functionality and performance Determine how that workload will be delivered reliably Define target workloads IaaS Cloud Architecture definition is a process

11. Workload categories give us a starting point 11 Traditional Enterprise Applications Software Development, Testing and Maintenance Managed IT Services High Performance Computing Batch processing Social Media Applications Disaster Recovery 11

12. Possible to categorize workloads into two sets Cloud Workloads Traditional Workload Reliable hardware, backup entire cloud, and restore for users when failure happens Cloud Workload Tell users to expect failure. Users to build apps that can withstand infrastructure failure Both types of workloads must run reliably in the cloud

13. 3 3 2 2 1 1 RTO (Recover Time Objective) RPO (Recovery Point Objective) Mission Critical Regular Reliability & DR are Workload Specific Recovery Point Objective (RPO) and Recovery Time Objective (RTO) should be determined based on workloads Deployment and DR plan should be designed per RPO, RTO requirements Different types of workloads will achieve workload reliability in different ways $ $$

14. Link Aggregation Storage Multi-pathing VM HA, Fault Tolerance VM Live Migration VM Backup/Snapshots Multi-site Redundancy Chaos Monkey Ephemeral Resources Traditional WorkloadCloud Workload Expect failure. Design app for failure. Self-service failure handling Think Amazon Web Services Expect reliability. Back-up entire cloud. Admin controlled failure handling Think Server Virtualization 1.0 Workload reliability drives unique requirements

15. Other functionality will impact design as well VM Features Resizing High Availabity Cloning Monitoring Windows Support Linux Support Naming Grouping Security Networking Features Dedicated user networks Integrated Firewall Integrated Load Balancing IP Address Management Multiple Guest Networks VPN Termination Intrusion Prevention Storage Features Persistent Storage Ephemeral Disk Automated Disk Snapshots Cloud Storage access Disk Monitoring Encryption Template Management Master Template Library User Template upload User ISO upload Blank VM creation Private templates Template migration Management Features Delegated Administration Live Migration of VMs Live Migration of Storage Usage Metering User Interface Console Access Multi- Hypervisor Open-Source Multi- Datacenter

16. Every cloud starts with basic building blocks ServersServers StorageStorage NetworkingNetworking HypervisorHypervisor Server Clusters NetworkingNetworking StorageStorage ResourcesAvailability Zones Clouds

17. Two sample zone architectures -Traditional server virtualization zone -Amazon-Style availability zone

18. Designing a zone for a traditional workload vCentervCenter ESXi Cluster Enterprise Networking (e.g., VLAN) Enterprise Storage (e.g., SAN) Hypervisor Storage SAN Networking L2 VLANs Network Services Load Balancing PV-LANs Multi-tier Apps Multi-tier VLANs OVF Feature Rich– vSphere, vCenter

19. Designing a zone for a traditional workload Can 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 approaches vCentervCenter ESXi Cluster Enterprise Networking (e.g., VLAN) Enterprise Storage (e.g., SAN)

20. Designing a zone for an Amazon-style workload Hypervisor Storage Local EBS Networking L3 SDN based L2 Elastic IP Network Services Security Groups ELB Multi-tier Apps L3 SDN based VPC Simple - XenServer Object store GSLB CloudFormation Software Defined Networks (e.g., Security Groups, EIP, ELB,...) Amazon-Style Availability Zone Server Racks Elastic Block Storage

21. Availability Zone Object Storage Software Defined Networks (e.g., Security Groups, EIP, ELB,...) Amazon-Style Availability Zone Server Racks Elastic Block Storage Amazon-Style Cloud Object store is critical for Amazon-style cloud CloudStack Mgmt. Server CloudStack Mgmt. Server

22. Availability Zone Object Storage Amazon-Style Cloud Object store is critical for Amazon-style cloud CloudStack Mgmt. Server CloudStack Mgmt. Server Workloads are distributed across availability zones No guarantee on zone reliability Applications designed to handle node level failue DBs and Templates snapped to object store. In event of failure, images are recreated on new availability zone. Dramatically less expensive

23. Cloud Transition – General to Workload specific General architecture for any workload Limited definitive failure/disaster recovery strategy Focused on legacy or cloud app architectures Workload-centric architecture Workload-specific failure/disaster recovery Separate legacy and cloud app architectures with interoperability Past Today General Architecture General Architecture Traditional-Style Amazon-Style

24. Object Storage vCentervCenter ESXi Cluster Enterprise Networking (e.g., VLAN) Enterprise Storage (e.g., SAN) Availability Zone Server Virtualization Availability Zone CloudStack Mgmt. Server CloudStack Mgmt. Server Support for different styles is required

25. CloudStack Management Cluster San Jose Miami London Tokyo Hosted Dehli Hosted Rio Availability zones will be distributed globally

26. Private CloudPublic Cloud Services Enterprise Data Center Dedicated resource Total control/security Internal network Shared resources Elastic scaling Pay as you go Public internet Enterprise Data Center Managed Private Cloud Hosted Private CloudFederated/Hybrid Cloud Services 3 rd party operated Enterprise 3 rd party hosted & operated Multi-tenant Users 3 rd party owned and operated SLA bound Security Dedicated resource Mix of shared and dedicated resources Shared facility and staff VPN access On Premise Hosted Multi-tenant Users Availability zones are becoming on-demand

27. Key takeaways 1.Understand your workload and the type of cloud you want to build. 2.Consider the services you will be delivering from the cloud in the future. 3.Choose a platform and architecture that is flexible enough to support you today and in the future.

28. Work better. Live better.