Downloaded 105 times
Uploaded byDevOpsGroup
DevOpsGuys - Cloud Adoption Frameworks - IPExpo April 2018
The document outlines the importance of Cloud Adoption Frameworks (CAF) and Cloud Migration Frameworks (CMF) for successful cloud strategies and transformations. It discusses the differences between CAF and CMF, emphasizing the need for organizations to understand their readiness, governance, and operational changes when transitioning to cloud environments. Additionally, it highlights best practices and considerations for various stakeholders to ensure effective cloud implementation and management.
More Related Content
Similar to DevOpsGuys - Cloud Adoption Frameworks - IPExpo April 2018
DevOpsGuys - Cloud Adoption Frameworks - IPExpo April 2018
- 1. www.devopsguys.com | Phone:0800 368 7378 | e-mail: [email protected] | 2017 Cloud Adoption Frameworks What are they and why do you need one? DOG - Confidential
- 2.
- 3. 3@DevOpsGuys #IPExpo DevOpsGuys Cloud Adoption& Migration Frameworks are a collection of best practices to help you avoid making the same mistakes they did
- 4. 4@DevOpsGuys #IPExpo Impressive quoteto make me seem deep Sir Isaac Newton If I have seen further than others, it is by standing upon the shoulders of giants
- 5. 5@DevOpsGuys #IPExpo Today’s Agenda •Whatare CAF and CMF’s? •What’s the different between them? •How can I use them most effectively to increase the changes of making my cloud journey a success?
- 6. Cloud Adoption versusCloud Migration Frameworks What’s the difference?
- 7. 7@DevOpsGuys #IPExpo What’s the difference betweena CAF and a CMF? Adopt Cloud ? Retire? Go out of Business? NO Cloud Migration Framework YES Tactical How Cloud Adoption Framework Strategic Why&What
- 8.
- 9. 9@DevOpsGuys #IPExpo Cloud migrationwill continue to grow
- 10. Cloud Adoption Frameworks Startwith the big picture first.
- 11. 11@DevOpsGuys #IPExpo Cloud AdoptionFramework •What things to I need to think about before deciding to migrate to the cloud? •Is my organisation ready to go to the Cloud? •How will the way we do things will need to change? •Who will need to be involved? •Etc etc etc
- 12. 12@DevOpsGuys #IPExpo AWS CloudAdoption Framework Non-Technical Technical
- 13. 13@DevOpsGuys #IPExpo Microsoft CloudAdoption Principles Establish Cloud Program Team Cloud Analysis Cloud Guidance & Architecture Cloud Engagement & Reporting IT Cost Considerations Current State • Investment • Capacity • Utilisation Cost Analysis •Application Inventory •Cost model •Vendor landscape •TCO Analysis Hybrid Cloud Mindset Public versus Private Cloud Workload Placement • On-premise • IaaS • PaaS • SaaS Maximise Benefits Replace (SaaS) Rebuild (PaaS) ReHost (IaaS) Refactor (Hybrid) Migration Emphasis? Focus on Application Modernization ? (Top Down) Focus on Environment Rationalization ? (Bottom Up) Focus on Flexibility? (Opportunistic) Workload Migration Precedence Precedence matrix (Now vs Next) Business Considerations • TCO • Business Criticality • Financial Impact • Dev/Test/New Technical Considerations • Architecture • OS/Web/DB platform • CPU/Disk/RAM requirements • Complexity • CapacityGRC Considerations • SLA • Compliance • Data Classification • Performance • Security
- 14.
- 15. 15@DevOpsGuys #IPExpo AWS CloudAdoption Framework Non-Technical Technical
- 16. 16@DevOpsGuys #IPExpo Business • Howdo we make sure that we remain focussed on Outcomes not Outputs? • How do we ensure alignment between our Cloud Strategy, our IT Strategy and our Business Strategy • How will we manage the (many) risks?
- 17. 17@DevOpsGuys #IPExpo Outputs vOutcomes Let’s pretend: we are a highway construction company: https://hbr.org/2012/11/its-not-just-semantics-managing- outcomes OutcomesOutputs • Number of highway miles built • Number of highway miles repaired • Number of bridges built • etc • Improved Traffic flow • Reduced Travel times • Reduction in Accidents
- 18. 18@DevOpsGuys #IPExpo People • Howwill your job roles change? • How do we align incentives (particularly for Dev vs Ops) • How to career paths change? • Who will get what training? • How are we going to manage all of this change?
- 19. 19@DevOpsGuys #IPExpo Governance • Howare we going to manage all of this? • How will we know when we’re succeeding? • How will we ensure Compliance to our regulatory frameworks? • How will we report all this to our Stakeholders?
- 20. 20@DevOpsGuys #IPExpo Platform • Whatshould your cloud platform look like? • IaaS vs PaaS vs SaaS? • Vendor tools versus 3rd party? • Ticket-based versus self-service? • Who is responsible for what?
- 21. 21@DevOpsGuys #IPExpo Security • Howdo we build Security into our Cloud Strategy, not bolt it on at the end? • How to we align IDAM in the Cloud and On-Premise (Hint: Azure Active Directory) • How will when know when we’ve been hacked? • What will we do when we are hacked?
- 22. 22@DevOpsGuys #IPExpo Operations • Howdo we manage the cloud, effectively? • How does Operations change in a cloudy world? • What happens to ITIL? • How badly will we screw it up if we just treat it like “just another data centre”?
- 23. Cloud Migration Frameworks Howto get to where you’re going…
- 24. •Project Control •Strategy (business driver) •KeyStakeholders and Team •Plan (Scope, Schedule, Resources) •Cost estimation •Portfolio discovery •Migration plan •Operating Model •Security Readiness & Plan •Prioritized backlog •Application groups •Migration strategy •Success criteria •Ops Integration - Foundations and Landing zone (target zone setup) •Setup Factory (Tools, Teams, Process) •Pilot migration Activate Execute •Application optimization •Process optimization •Operational optimization •Cost optimization Optimize Discover Design Build Integrate Validate Cutover AWS Migration Framework Prioritized Backlog (PLAN)
- 25. AWS Migration Patterns(Path to Cloud) Discover, Assess & Prioritize Applications Use MigrationTools Transition Production Redesign Application/ Infrastructure Architecture App Code Development PurchaseCOTS/ SaaS &licensing Validation Modifyunderlying Infrastructure Full ALM / SDLC ManualConfig ManualDeploy ManualInstall Determine MigrationPath Automate Manual Install & Setup Integration Determine newplatform
- 26. 26@DevOpsGuys #IPExpo Microsoft CloudAdoption Principles Establish Cloud Program Team Cloud Analysis Cloud Guidance & Architecture Cloud Engagement & Reporting IT Cost Consideration s Current State • Investment • Capacity • Utilisation Cost Analysis •Application Inventory •Cost model •Vendor landscape •TCO Analysis Hybrid Cloud Mindset Public versus Private Cloud Workload Placement • On-premise • IaaS • PaaS • SaaS Maximise Benefits Replace (SaaS) Rebuild (PaaS) ReHost (IaaS) Refactor (Hybrid) Migration Emphasis? Focus on Application Modernization ? (Top Down) Focus on Environment Rationalization ? (Bottom Up) Focus on Flexibility? (Opportunistic) Workload Migration Precedence Precedence matrix (Now vs Next) Business Considerations • TCO • Business Criticality • Financial Impact • Dev/Test/New Technical Considerations • Architecture • OS/Web/DB platform • CPU/Disk/RAM requirements • Complexity • Capacity GRC Considerations • SLA • Compliance • Data Classification • Performance • Security
- 27.
- 28. Breaking down theAzure migration journey
- 29. Migration strategies: Rehostapp (i.e., lift and shift)
- 30.
- 31.
- 32.
- 33. Doing in theDevOps Way Use the Cloud Adoption to kick-start DevOps Transformation
- 34.
- 35.
- 36.
- 37.
- 38.
- 39.
- 40. 40 Conclusion • CAF =Big Picture Why and What • CMF = the HOW of a successful migration • Don’t re-invent the wheel • But DO think beyond just the Technical • Involve the entire organisation • Great opportunity to introduce DevOps patterns, practices and behaviours and modernise the way you work.
- 41. 41 Impressive quote tomake me seem deep Sir Isaac Newton If I have seen further than others, it is by standing upon the shoulders of giants
- 42.
Editor's Notes
- #2 Cloud Adoption Frameworks - what are they and why do you need one? Most of the major cloud vendors have published "Cloud Adoption Frameworks" (CAFs"), as have advisory groups like Gartner and Forrester. But what are they, do you need one, and what's the value in adopting one for your cloud journey? In this session Steve Thair, CTO of UK DevOps consultancy, DevOpsGuys , will look at 4 Cloud Adoption Frameworks, discuss their relative strengths and weaknesses, talk about the different types of CAFs, different types of cloud adoption strategies and how DevOps could (and should) play a role in your cloud strategy.
- #3 Put your hands up if you have migrated PRODUCTION systems into the Cloud (so all you “cloud native” folks can keep your hands down ) OK Great. Keep your hands up if those systems are MATERIAL (in the Accounting sense of the word) to the financial success of your organisation – if they went down for a day, you’d lose enough money that you’d probably have to disclose it to shareholders, investors etc Ok, Great. How many of you wished you’d known what you know NOW when you first started on your migration journey?
- #4 Or in the words of Sir Isaac Newton…
- #9 Confluence of migration triggers/catalysts [including outsourced datacenter contract expirations, integrating acquisitions, urgent capacity needs, software and hardware refresh, end of support, security threats (e.g., Spectre), compliance (e.g., GDPR), Need to deliver applications faster]
- #10 2018 will be a big year for cloud migration. This is a secular trend.
- #14 Microsoft’s is a bit of a halfway house between a CAF and a CMF…
- #15 I’d argue this is more of a Cloud Migration Framework than a Cloud Adoption Framework – it’s a set of steps
- #18 Also – it is a move away from something that is just a commodity
- #27 Microsoft’s is a bit of a halfway house between a CAF and a CMF…
- #28 Technical (e.g., Networking) | Process (e.g., DevOps) | People (e.g., cloud 101 skills)
- #29 Replace – consider for completeness. [Azure Migrate discovers for O365?] Let’s talk about the various paths along your migration journey. It all starts with discovering your on-prem apps, data, and infrastructure, assessing them for migration readiness and determine the mix of tactics that you will use during the move – ranging from simple lift and shift to various levels of modernization during migration (i.e., refactor, rearchitect, rebuild). And then once in Azure, how do you keep your workloads optimized continuously (e.g., security, monitoring, backups, opex spends). Note: In some cases you might just retire the workload or replace it with a SaaS solution – we won’t cover those aspects in detail here
- #30 What is it about: Redeploy the application as-is to Azure Value: Low effort, quick ROI Triggers: End of support, datacenter contract expiration, apps that don’t need a lot of investment going forward Target workloads: Apps (.NET, Java, Node.js), data (SQL Server, MySQL, PostgreSQL, NoSQL), infrastructure (Windows Server, Linux), special purpose (SAP) Azure technologies: Azure IaaS, Azure SQL Database (Managed Instance), Azure Database for MySQL/PostgreSQL, SAP on Azure Migration tools:
- #35 What they found was that high performing IT organisations were different in 5 key areas… Culture – they embraced change, were more autonomous and more empowered Automation – they were leveraging the latest automation tools like Puppet, Chef and Ansible Lean IT – they were embracing Lean IT principles borrowed from manufacturing (particularly automotive and the Toyota Production System e.g. Kanban) but more importantly focussing on small batch sizes and the flow of work through the system Measurement – they were using advanced measurement techniques to provide constant feedback on their customer needs, and the impact of their IT initiatives. Less opinion, more data science! Sharing – a focus on breaking down silos between departments and sharing knowledge and best practice, often using ideas drawn from open source software development. Let’s quickly drill down into 2 of those in a bit more detail – breaking down the silos and the flow of work… [click]
- #36 Where you start across the DevOps pipeline is very dependent on the organisation Where is your constraint?
- #38 The idea of a DevOps product delivery team is that they own a defined product from initial design and development right through into production deployment AND operations – Dev & Ops together in a vertically integrated team. The product owner is empowered to prioritise the backlog of work, based on the organisational goals, customer needs and the fast feedback of data from customers and product (remember the M for measurement in CALMS). The goal here is to balance out the “user stories” (new features) with the “Operability stories” (things that make it easier to manage, reduce outages or cloud hosting costs etc). All of this underpinned by a focus on automating as much as possible, to free up time for higher value work.