Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

CPN210 Defining an Enterprise Cloud Strategy - AWS re: Invent 2012


Published on

Few terms are more confusing than the term "cloud." While we've moved beyond the age of "defining the cloud," there's still a significant amount of confusion in understanding the role of the public cloud in an enterprise IT infrastructure. This presentation defines the elements of a mature enterprise cloud computing strategy that includes all components of a hybrid cloud, how to build out an integrated public/private infrastructure, and strategies for when and where to deploy new systems, and when it makes sense to migrate existing systems.

  • Be the first to comment

CPN210 Defining an Enterprise Cloud Strategy - AWS re: Invent 2012

  1. 1. Defining an EnterpriseCloud StrategyGeorge Reese, enStratusNovember 28, 2012
  2. 2. The four stages of cloud adoption1. Experimentation2. Going “rogue”3. The scramble for order4. Enterprise adoption
  3. 3. Understanding the “rogues”The controls in place in most IT shops have become a barrier tobusiness getting work doneCloud computing has given more widespread and easily consumableaccess to lower levels of technology to all business stakeholdersThe “rogues” use the cloud to gain agility and economic freedom
  4. 4. The “rogues” can put the business at riskGovernanceComplianceRisk management
  5. 5. An enterprise cloud strategy…Preserves (and even enhances)agilityMakes possible the graceful lossof centralized controlMinimizes risk
  6. 6. Why cloud matters to the enterpriseOn-demand, metered provisioning with the perception ofinfinite capacity - On demand When the business needs it - Metered Pay for what is used, dispose of when done - Perception of infinite capacity No worries about resource constraints or location
  7. 7. Cloud computing enables a business tofail fast and fail often
  8. 8. How public cloud computing happenedA handful of companies have achievedmassive economies of scale.Cloud computing gives an enterpriseon-demand access with the perceptionof infinite capacity to the economies ofscale realized by massive scaleorganizations like Amazon.
  9. 9. What makes the cloud so easy? Credit card + need = consumption Limited (or even no) technical knowledge required Immediate gratification
  10. 10. Why is enterprise adoption so hard?No single approach serves all cloudcomputing needsUsing cloud effectively requires anunderstanding of “the whole cloud”Private clouds are technically complex andcross many IT/business disciplinesIT must be involved to manage risk acrossthe enterprise
  11. 11. Elements of a cloud strategyCloud vision:what cloud means to the organizationas a wholeService models: IaaS, PaaS, andSaaSDelivery models: public and privateThe cloud computing stack
  12. 12. Your enterprise cloud strategy MUSTpreserve the benefits of cloud computing
  13. 13. Before defining your cloud strategyYou should have some practical experience (dev/testcounts) in an IaaS like AWSIdeally, some PaaS experienceYou should have a solid appreciation of the value ofcloud computingYou should understand the risks that arise from differentcloud modelsNo unicorns, no FUD
  14. 14. The cloud visionA statement that describes the value of cloud inthe abstract to the enterprise as a whole - Business and IT should agree on this vision - Don’t spend too much time defining a vision —Better to executeAlign processes and controls with the visionMigrate to the cloud to realize this vision, notsimply for the sake of “going cloud”
  15. 15. Service elements fit on a continuum
  16. 16. Do not believe the PaaS hype
  17. 17. The benefits of different service modelsSaaS is the ultimate commoditization of well-understood software problems,but poorly suited to bespoke systems or other custom needs; often poorlysuited to regulated environments.PaaS is the ideal cloud environment for rapid development of bespokesoftware systems that require nothing specific from the underlyinginfrastructure; the focus is on apps. Poorly suited for regulatory and othercompliance needs or any but the simplest infrastructure needs.IaaS provides the maximum control over infrastructure without the need toworry about infrastructure; well suited to complex, custom software systems.Network and storage I/O can be a challenge for IaaS.Virtualized data centers and physical infrastructure still exist and have a rolefor systems with very specific, non-commodity hardware requirements.
  18. 18. Delivery modelsPublic cloud is a multi-tenant cloud infrastructuredelivered by a provider that has achieved scale (IaaS,PaaS, and SaaS) - For the greatest level agilityPrivate cloud is a single-tenant virtualizedinfrastructure with consumption characteristics similarto a public cloud (IaaS and PaaS) - For greater control for regulatory, compliance,or bespoke requirements
  19. 19. A private cloud is not really a cloud
  20. 20. Thecloudcomputingstack
  21. 21. Selecting the right deployment modelSoftware needs will migrate from private/physical to public/SaaS over timedue to commoditizationWhen selecting a deployment model for today, you need to answer twoquestions: - How commoditized is my problem? (e.g. what level of service model is appropriate) - What are the governance and compliance needs? (e.g. what deployment model)Pick the service/delivery model combination that best matches your answers - Bias towards public - Bias towards SaaS - The reality is that public/IaaS is the sweet spot for most bespoke needsWhere you are in the overall adoption of cloud within your enterprise willimpact which projects should go first
  22. 22. Cloud Strategy: The Public CloudDon’t be fooled by the term “enterprise cloud” - You don’t achieve “enterprise” by destroying the value of “cloud” - A public cloud is “enterprise” if it can help you realize your cloud vision across a class of business needsPublic clouds can be secured for many needs - even sensitive data - only specific controls should eliminate the consideration of public for a specific problem
  23. 23. Time to provision matters MUCH morethan contracted service levels oravailability
  24. 24. Cloud Strategy: The Private CloudThe primary goal of your private cloud is tocreate a cloud-like experience capable ofmeeting specific control and applicationarchitecture objectivesVirtualization is NOT sufficient for a cloud-likeexperienceVirtualization + cloud platform = private cloud
  25. 25. Cloud Strategy: GovernanceProper cloud governance enables you to minimize risk andensure compliance across a hybrid cloud infrastructureUnified view of all resources in all cloudsAudit trail across all cloudsUser access controls aligned with job function across all cloudsIntegration with enterprise systems management tools
  26. 26. Approvals processes kill clouds
  27. 27. Cloud Strategy: Legacy and GreenfieldThe biggest architectural issue is how to achieve faulttolerance - Some clouds are better for the more resilient “design for failure” model - Others are better for the traditional VM migration modelNew applications should be created under the “design forfailure” model using distributed databases managed throughautomated cloud management tools orchestrating the behaviorof next generation configuration management toolsBut tools like Amazon RDS, Amazon SQS, etc. make it easierto leverage more traditional technologiesAnd you may still want to migrate existing applications into thecloud to leverage its flexibility
  28. 28. After the cloud strategy…The best first step in execution is a structured proofof conceptGo greenfield for the PoC, don’t migrateCreate measurable, achievable objectivesDon’t tackle too many new things at onceMake it comprehensive, include virtualization, cloudplatform, cloud management, configurationmanagement, public cloudSuccess factors must include buy-in from the“rogues”!
  29. 29. Questions?• Twitter: @GeorgeReese• Email: