rightscale webinar: considerations for choosing cloud providers
Post on 17-Jun-2015
Embed Size (px)
DESCRIPTIONRightScale has deep experience with a wide range of cloud providers, so customers often ask us for advice on which public and private clouds are right for their use cases. While there is no one right answer, we share an evaluation framework for selecting a portfolio of clouds that meets your strategic needs. We provide an in-depth look at how to align your cloud infrastructure selection with your technical and business requirements. 1. How many clouds will you need? 2. How should you build a cloud portfolio? 3. Public, private, or hybrid? Which type is best for each use case 4. Six considerations for selecting the right cloud
- 1. CONSIDERATIONS FOR CHOOSING CLOUD PROVIDERS
2. Rishi VaishVP of Product, RightScaleKim WeinsVP of Marketing, RightScaleQ&ABen IngallsSales Development Representative, RightScalePlease use the Questions window to ask questions at any timeYour Panel Today 3. Market StatsBuilding a Cloud Portfolio6 Considerations for Choosing CloudsGeographyDemandAvailabilityFunctionalitySecurity and ComplianceCostAgenda2 4. About RightScaleSelf-ServiceCloud AnalyticsRightScale Cloud Portfolio ManagementCloud ManagementDesignPrivate/VirtualizedEnvironmentsPublicCloudsOtherServicesAutomateMulti-Cloud OrchestrationOperateDeployReportOptimize 5. Public Cloud OnlyPrivateCloud94% of Respondents are Using Cloud58%7%29%Publicand PrivateSource: RightScale 2014 State of the Cloud ReportCloud Usage is Ubiquitous 6. Hybrid is the Preferred StrategySource: RightScale 2014 State of the Cloud Report 7. 4%4%5%8%9%11%12%18%49%8%17%10%17%14%25%19%15%25%10%12%8%10%11%10%10%14%9%0%20%40%60%80%100%HP CloudGoogle IaaSSoftlayer/IBMGoogle App EngineRackspace Public CloudAzure IaaSAzure PaaSVMware vCHSAWSEnterprise Public Cloud Usage% of Respondents Running ApplicationsRunning appsExperimentingPlan to useAWS is Dominating Public Cloud AdoptionSource: RightScale 2014 State of the Cloud Report 8. 6%13%15%21%26%52%9%12%25%15%17%10%3%6%12%7%10%6%0%20%40%60%80%EucalyptusCitrix CloudStackOpenStackMicrosoft System CenterVMware vCloud DirectorVMware vSphere/vCenterEnterprise Private Cloud Usage% of Respondents Running ApplicationsRunning appsExperimentingPlan to useVMware Dominates Private EnvironmentsSource: RightScale 2014 State of the Cloud Report 9. Its a Portfolio 10. 1. Operate anywhere2. Leverage existing investments3. Optimize costs4. Access unique capabilities5. Create resilient architectures6. Maintain vendor leverage7. Future-proof your cloud strategy8. Multi-cloud happensWhy a Cloud Portfolio?9 11. Application PortfolioRequirements FiltersResource PoolsApp 1App 2App 3GeographyDemandFunctionalityComplianceAvailabilityChoosing the Best Venue for an ApplicationApp NHosted PrivatePublic Cloud 2Public Cloud 1CostExisting DCApp 4App 5Internal PrivateVirtualizedApp 1App 2App 3App 4App 5App 6App 7 12. Preserving Future Portability: Two Approaches11AWSAzureGoogleCloudStackOpenStackvSphereMulti-Cloud ImageConfiguration ScriptsContainers 13. 12You Need a Framework 14. 6 Considerations For Choosing Clouds13GeographyDemandAvailabilityFunctionalitySecurity & ComplianceCost 15. 6 Considerations For Choosing Clouds14GeographyDemandAvailabilityFunctionalitySecurity & ComplianceCost 16. Geography: Where Are Your Apps? Users? 17. Map Against Cloud OptionsAmazon Web ServicesDatapipeGoogle Cloud PlatformHP CloudIBM SoftLayerRackspaceWindows AzurePublic CloudsSingaporeHong KongTokyoDallasDC AreaNYC AreaSF AreaSeattleChicagoDublinLondonAmsterdamOregonSo PauloLas VegasSoutheastMidwestShanghaiSydneyW EuropePrivate CloudsCloudStackOpenStackvSphere 18. CloudConsiderationsPublicIf there is a provider that has a datacenter in the geographyPrivateIf no public provider or you have a private cloud in the geographyVirtualizedIf you already have a virtualized datacenter in the geographyHybridIf you need to span public and private for different geographiesGeography17General ConsiderationsYou may need more than one public cloud providerPlan for zones or regions for DR in each geographyConsider data residency requirementsYou may need special business relationships in certain geographies 19. 6 Considerations For Choosing Clouds18GeographyDemandAvailabilityFunctionalitySecurity & ComplianceCost 20. Demand: How Will It Evolve?VariableSteady StateSpiky 21. Public CloudCloudburstWhat About Hybrid Cloudbursting?20Low latencyPrivate NetworkPrivate Cloud 22. CloudConsiderationsPublicGood fit for large, spiky or transient workloadsPrivateProvides elasticity within a fixed pool of resourcesVirtualizedWorks for very steady and predictable demandHybridProvides the flexibility to move between the above optionsDemand21General ConsiderationsGreenfield workloads tend to be unpredictableDev and Test are very transient/variable workloadsMarketing campaigns and promos can be spikyThink about seasonal variationsCloudbursting and split-tier architectures are advanced options, but not widely used 23. 6 Considerations For Choosing Clouds22GeographyDemandAvailabilityFunctionalitySecurity & ComplianceCost 24. Availability? Dev/Test is About Agility23AWSVMwareAWS 25. While Production Requires HA/DR24Load BalancersApp ServersMaster DBSlave DBApp ServersSlave DBReplicate >Replicate >Load BalancersPRIMARYWARM DRDNS 26. Outage-Proof with Independent Control Plane25Replicate >< Failover> < Failover>Your PublicCloud ARightScalePrimaryRightScaleBackupYour PublicCloud BYour PrivateCloudRightScale UI RightScale APIUser A User B User CGlobally HostedScalableResilientSaaS PlatformYour CloudApplicationsSecure authenticationand communication 27. CloudConsiderationsPublicAchieved through best practice architectures, not just SLAsPrivateOn-premise and hosted datacenters have outages tooVirtualizedSee aboveHybridConsider hybrid DR scenariosAvailability26General ConsiderationsOutages happen regardless of public or private. Plan for resiliency.SLAs in the cloud will be different 28. 6 Considerations For Choosing Clouds27GeographyDemandAvailabilityFunctionalitySecurity & ComplianceCost 29. Functionality: An Evolving Feature Set28 30. CloudConsiderationsPublicIaaS+/PaaS features, networking options, hybrid options, etc..PrivateDepends on your private cloud platform and implementationVirtualizedHow do you cloud-enable your virtualized environmentHybridHow will you replace cloud-specific features?Functionality29General ConsiderationsIf portability is a goal, plan for substitutes for cloud-specific featuresStay up-to-date with the latest offerings 31. 6 Considerations For Choosing Clouds30GeographyDemandAvailabilityFunctionalitySecurity & ComplianceCost 32. 31Cloud Security EcosystemCloud ProviderEnterpriseRightScale3rd Party VendorsPlan for a Cloud Security Ecosystem 33. Options Abound32RightScale provides visibility, governance, auditing across cloudsCloud providers offer cloud-specific security options3rd party vendors offer multi-cloud optionsAbility for segregation of duties: encryption provider vs cloud storage providerCapabilityWho?Encrypt data in transitVendor, EnterpriseEncrypt data at restVendor, Cloud, EnterpriseSecure communicationsRightScale, Cloud, Enterprise, VendorSystems Configuration /Network segmentationCloud, Enterprise, RightScaleIntegrate with IAMRightScale, Cloud, Enterprise, VendorsPrivileged identity managementRightScale, Cloud, EnterpriseBackup/Replicate dataRightScale, Cloud, Enterprise, VendorCoordinate BC & DRRightScale, Cloud, Enterprise, VendorLog cloud activityRightScale, Cloud, Enterprise, VendorShared Responsibility for Cloud Security 34. Cloud Provider Certifications33 35. CloudConsiderationsPublicEnsure cloud provider has certifications necessary for your appsPrivateIf you need to own the infrastructureVirtualizedIf you need to own the infrastructureHybridCompliance itself does not force hybridSecurity & Compliance34General ConsiderationsSecurity/Compliance in the cloud is a shared responsibilityCompliance requirements does NOT automatically mean you have to go privateSome enterprises are not comfortable with certain types of data in the public cloud 36. 6 Considerations For Choosing Clouds35GeographyDemandAvailabilityFunctionalitySecurity & ComplianceCost 37. Is Public or Private Most Cost-Effective?36VariableloadSeasonalityTraditional on-premise provisioning 38. Have you accounted for all your costs?Are your loads steady-state?Will usage of steady-state loads change in the future? Seasonality? Growth?How much do you need to overprovision on-premise infrastructure to cover spikes?What is the value of agility and flexibility?What is affinity for CapEx vs OpEx?Assessing Cost: Public vs Private37 39. Instance CapabilitiesInstance RAM/MemoryWhat generation of chips?Included storage? Or not?SSD drives?Purchase Options and DiscountsReserved InstancesSpot pricingSustained useEAsOther DiscountsSupport and ServicesFuture Price CutsPublic Cloud: Not Always Apples-to-Apples38 40. Accurate Planning with Cloud Analytics39 41. CloudConsiderationsPublicCombine on-demand pricing with RIs/Sustained Use/DiscountsPrivateAre you considering all costs?VirtualizedAre there sunk costs you want to take advantage of?HybridPreserve portability for cost arbitrageCost40General ConsiderationsPublic cloud providers have thousands of price pointsVirtualized environments may have a heavy licensing fee to the virtualization vendorMany enterprises are maintaining multiple public cloud optionsNegotiation leverage comes with portability 42. Hybrid and Multi-Cloud are Strategies of ChoiceExpect a Portfolio of CloudsChoose Clouds to Meet Business and Technical RequirementsWrap Up41 43. 42Thank You and Q&ANext Steps: RightScale Definitive Guide to Cloud Portfolio Management: http://www.rightscale.com/lp/cloud-portfolio-management-guide RightScale Definitive Guide to Cloud Strategy: http://www.rightscale.com/lp/cloud-strategy-guide 44. THANK YOU.