Downloaded 153 times
Uploaded byRightScale
Prepare Your Enterprise Cloud Strategy for 2019: 7 Things to Think About Now
The document outlines essential considerations for enterprises in preparing their cloud strategy for 2019, emphasizing a multi-cloud approach that is increasingly adopted by organizations. Key topics include restructuring teams for cloud expertise, optimizing costs, governance, and automation in operations. The document advocates for defined roles like cloud architects and encourages a cultural shift towards enabling business value through cloud technology.
More Related Content
Similar to Prepare Your Enterprise Cloud Strategy for 2019: 7 Things to Think About Now
![[Webinar] When It Comes To Cloud, Great Power Brings Great Responsibility](https://cdn.slidesharecdn.com/ss_thumbnails/managingoperationsinthecloud121317-171219111814-thumbnail.jpg?width=640&height=640&fit=bounds)
Prepare Your Enterprise Cloud Strategy for 2019: 7 Things to Think About Now
- 1. PREPARE YOUR ENTERPRISECLOUD STRATEGY FOR 2019: 7 THINGS YOU NEED TO THINK ABOUT NOW
- 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. Exciting News! RightScaleis part of Flexera
- 7. • A Multi-CloudMindset • 7 Things to Think About • People & Organization • Culture • Financial • Governance • Purchasing • DevOps • Operations Agenda 6
- 8. Multi-Cloud is theStrategy of Choice Multi-Cloud 85%
- 9. Organizations Already UseMultiple Clouds
- 10. Enterprises Often UseAWS + Azure Source: RightScale 2017 State of the Cloud Report
- 11.
- 12. Lack of Expertiseis a Key Challenge 11
- 13. Enterprise Create CentralCloud Teams 12
- 14. Cloud Architect RoleGrows 13
- 15. • Build aseparate 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
- 16. • 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
- 17. • Define andadvance 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
- 18.
- 19. • From “buildinginfrastructure” 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
- 20.
- 21. Large Amounts ofWasted Cloud Spend Multi-Cloud 85%
- 22. Large Amounts ofWasted Cloud Spend Multi-Cloud 85%
- 23. Cost Optimization isTop Focus 22
- 24. 30-45% Savings How doI execute on an ongoing basis?
- 25. • 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
- 26. Cost Allocation forShowback 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
- 27. • Cloud canbe 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
- 28. Setting up aCost Optimization (Sub) Team 27 Executive Sponsorship Cost Analyst Project Manager Cloud Technical Expert Cloud Resource Owners (Teams, LOBs, BUs)
- 29.
- 30. Don’t Overcommit toVariable Usage Usage commitments for discounts x% coverage of steady state 29 On-demand usage
- 31. RIs Are NotAlways 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
- 32. • Get comfortablewith 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
- 33.
- 34. • Cost • Accesscontrol • Network security • Configuration management/patching • Data security • Business continuity (HA/DR) • Performance • Compliance • Audit • Standards Governance: Do the same things, differently 33
- 35. Multi-Cloud IAM 34 User BUserA 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
- 36. Implement Automated PoliciesAcross Clouds 35
- 37. Breaking Down aPolicy
- 38. From Alert Onlyto Fully Automated Resolution 37 Alert only Alert Approval Automated resolution Fully automated resolution Move toward full automation as you gain confidence in policy conditions
- 39.
- 40. • You needautomation 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
- 41. DevOps Spans ResourcePools VIRTUAL SERVERS PUBLIC CLOUDS DESKTOPS/ LAPTOPS PRIVATE CLOUDS BARE METAL SERVERS CONTAINER CLUSTERS MULTI-CLOUD ORCHESTRATION
- 42. Some Key Elementsof 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
- 43. CI/CD Communications ITSM / CMDB/ Tcketing Alerts & Monitoring Reporting / Dashboards Collaboration A CMP Ties it All Together 42
- 44.
- 45. NoOps: Defined 44 The goalof completely automating the deployment, monitoring, and management of applications and the infrastructure on which they run. Source: Forrester
- 46. NoOps: The Roleof Operations Changes 45 Ad Hoc Action Repeatable Automation Old Ops NoOps
- 47. NoOps: The Roleof 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
- 48. • Cloud AccountProvisioning • Dev/Test Environment Provisioning • Infrastructure Provisioning • Code Deployment • Application Operations • Self-Healing • Automated Policies • ...and more Automation: More than App Provisioning 47
- 49. Contact [email protected] formore info Q&A 48