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.

Prepare Your Enterprise Cloud Strategy for 2019: 7 Things to Think About Now

431 views

Published on

Cloud adoption just keeps on growing and now is the time to take control. Your enterprise cloud strategy for 2019 needs to address the broad impact of cloud use in your company. Your strategy should also cover implications for your technical processes, as well as supporting areas including finance, governance, organization, and culture.

Published in: Technology
  • Be the first to comment

Prepare Your Enterprise Cloud Strategy for 2019: 7 Things to Think About Now

  1. 1. PREPARE YOUR ENTERPRISE CLOUD STRATEGY FOR 2019: 7 THINGS YOU NEED TO THINK ABOUT NOW
  2. 2. • Kim Weins • VP Marketing & Product, RightScale • Now: VP Cloud Strategy, Flexera • Bailey Caldwell • VP Customer Success, RightScale • Now: VP Cloud Solutions Engineering Presenters
  3. 3. Exciting News! RightScale is part of Flexera
  4. 4. • A Multi-Cloud Mindset • 7 Things to Think About • People & Organization • Culture • Financial • Governance • Purchasing • DevOps • Operations Agenda 6
  5. 5. Multi-Cloud is the Strategy of Choice Multi-Cloud 85%
  6. 6. Organizations Already Use Multiple Clouds
  7. 7. Enterprises Often Use AWS + Azure Source: RightScale 2017 State of the Cloud Report
  8. 8. RE-THINK PEOPLE & ORGANIZATION
  9. 9. Lack of Expertise is a Key Challenge 11
  10. 10. Enterprise Create Central Cloud Teams 12
  11. 11. Cloud Architect Role Grows 13
  12. 12. • Build a separate Cloud Team or Center of Excellence • Strong Exec sponsorship is a must • Combine Architects, IT Ops from the get go • Develop capabilities for cloud cost management • Treat App Dev and Business Units as your customers • Break down traditional compute/storage/network silos • Include some “net new” resources with cloud expertise Tips for Building Your Cloud Team 14
  13. 13. • Fully Dedicated • Exec Sponsor • Cloud Architect(s) • DevOps Engineers • Cost Management & Governance • Partially Dedicated • I&O • Application Development • Integration/Network • Security • Finance • Purchasing Cloud Team Members/Roles 15
  14. 14. • Define and advance cloud processes and architectures. Act as a focal point to coordinate and collaborate on cloud decisions • Select cloud providers and define relationships • Define cloud architectures • Foster DevOps processes • Cost management and governance processes • Coordinate with infrastructure and operations • Create security, compliance and access management processes • ...and more The Role of Cloud Architect(s) 16
  15. 15. RE-THINK CULTURE
  16. 16. • From “building infrastructure” to “enabling business value” • From “gatekeeper” to “guardrails + governance” • From “capacity management” to “optimization” • Brokering and instant access • Everything “as code” (infrastructure, policies, processes) • Build in and test for failure (monkeys) 5 Ways Cloud Changes Your IT Culture 18
  17. 17. RE-THINK FINANCIAL
  18. 18. Large Amounts of Wasted Cloud Spend Multi-Cloud 85%
  19. 19. Large Amounts of Wasted Cloud Spend Multi-Cloud 85%
  20. 20. Cost Optimization is Top Focus 22
  21. 21. 30-45% Savings How do I execute on an ongoing basis?
  22. 22. • It’s complicated -- millions of line items!! • Try opening that in your spreadsheet! • Each cloud provider bills differently • Different services from the same cloud provider bill differently • Ex: One cloud provider has inconsistent region naming • Frequent updates • Multiple times a day • Constant change • Cloud providers are adding new items and changing how they bill • Think multi-cloud cost management The Challenge of Cloud Billing 24
  23. 23. Cost Allocation for Showback 25 Priority Tags Accounts 1 env=test 2 env=prod 3 dept=qa 4 756122054 Allocation Rules Billing Centers Dev CS Sales Prod Dev Support Demo Marketing Demo Child Billing Centers
  24. 24. • Cloud can be a mix of “CapEx” and “OpEx” • Some companies may be able to capitalize parts of cloud spend (Reserved Instance purchases, contractual commitments) • OpEx requires a new approach • From “approval and ROI” to “continuous optimization” • Optimize now, saves me money immediately • Finance/accounting teams need to shift their mindset • Will GAAP rules evolve? A Shift from CapEx to OpEx 26
  25. 25. Setting up a Cost Optimization (Sub) Team 27 Executive Sponsorship Cost Analyst Project Manager Cloud Technical Expert Cloud Resource Owners (Teams, LOBs, BUs)
  26. 26. RE-THINK PURCHASING
  27. 27. Don’t Overcommit to Variable Usage Usage commitments for discounts x% coverage of steady state 29 On-demand usage
  28. 28. RIs Are Not Always the Best Way to Save 30 Savings for RI based on m5.large running Linux in US East. RI savings will vary based on instance type and region
  29. 29. • Get comfortable with cloud provider contracts • Joint responsibility for SLAs & Security • Less room for negotiating key terms • Multi-cloud provides negotiating leverage • Make sure IT/Dev are architected for portability • Don’t overbuy for larger discounts • Purchase discounts only based on go-forward steady state levels • Hold IT and cloud consumers accountable for efficiencies • Optimize today for lower cloud bill next month To Dos for the Purchasing Team 31
  30. 30. RE-THINK GOVERNANCE
  31. 31. • Cost • Access control • Network security • Configuration management/patching • Data security • Business continuity (HA/DR) • Performance • Compliance • Audit • Standards Governance: Do the same things, differently 33
  32. 32. Multi-Cloud IAM 34 User BUser A User EUser DUser C Enterprise Account Cloud Account Cloud Account Cloud Account Cloud Account Cloud Account Cloud Account Account 2Account 1 RightScale Access Control Authorization Authenticate with cloud credentials ADFS Active Directory Authentication
  33. 33. Implement Automated Policies Across Clouds 35
  34. 34. Breaking Down a Policy
  35. 35. From Alert Only to Fully Automated Resolution 37 Alert only Alert Approval Automated resolution Fully automated resolution Move toward full automation as you gain confidence in policy conditions
  36. 36. RE-THINK DEVOPS
  37. 37. • You need automation to gain benefits of cloud: • Accelerate time to market • Shut instances down when not in use (nights, weekends) • Auto-scale up or down • Adjust instances sizes when underutilized • Expand/move to other regions • Move to other clouds • You need automation to manage applications in cloud: • Respond to instances that die • Avoid or recover from failures/outages • Address security vulnerabilities. • ...and more The Cloud is “About” Automation 39
  38. 38. DevOps Spans Resource Pools VIRTUAL SERVERS PUBLIC CLOUDS DESKTOPS/ LAPTOPS PRIVATE CLOUDS BARE METAL SERVERS CONTAINER CLUSTERS MULTI-CLOUD ORCHESTRATION
  39. 39. Some Key Elements of DevOps 41 Processes Tools Self-Service access to infrastructure CMP (RightScale), ITSM Continuous integration/delivery Github, Jenkins, Travis Configuration management Chef, Puppet, Ansible, Terraform Containerization Docker, Swarm, Kubernetes Continuous monitoring NewRelic, Datadog
  40. 40. CI/CD Communications ITSM / CMDB / Tcketing Alerts & Monitoring Reporting / Dashboards Collaboration A CMP Ties it All Together 42
  41. 41. RE-THINK OPERATIONS
  42. 42. NoOps: Defined 44 The goal of completely automating the deployment, monitoring, and management of applications and the infrastructure on which they run. Source: Forrester
  43. 43. NoOps: The Role of Operations Changes 45 Ad Hoc Action Repeatable Automation Old Ops NoOps
  44. 44. NoOps: The Role of Operations Changes 46 Situation Old Ops NoOps Request for a new server Fulfill request once approved Automated self-service for requester within guardrails Server overloaded Add a server Autoscaling array Server failed Reboot Detect and auto-reboot New code ready Push code to production Trigger automated push once tests are completed Need a backup on dev Take a snapshot Push button snapshots on dev
  45. 45. • Cloud Account Provisioning • Dev/Test Environment Provisioning • Infrastructure Provisioning • Code Deployment • Application Operations • Self-Healing • Automated Policies • ...and more Automation: More than App Provisioning 47
  46. 46. Contact sales@rightscale.com for more info Q&A 48

×