An Agile Approach to Accelerate Mass Migration | AWS Public Sector Summit 2016
•Download as PPTX, PDF•
17 likes•7,453 views
The complexities of a cloud transformation program that involves the migration of hundreds or thousands of servers can present a significant challenge to program management and the coordination of IT teams tasked with the success and support of migration. This session outlines a highly collaborative agile approach to accelerate migration activities through automation of the iterative capture, sharing, and documentation of decisions and information, incorporated into a common DevOps solution.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (10)
Similar to An Agile Approach to Accelerate Mass Migration | AWS Public Sector Summit 2016
Similar to An Agile Approach to Accelerate Mass Migration | AWS Public Sector Summit 2016 (20)
More from Amazon Web Services
More from Amazon Web Services (20)
Recently uploaded
Recently uploaded (20)
An Agile Approach to Accelerate Mass Migration | AWS Public Sector Summit 2016
- 1. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Rodney Grilli, Sr. IT Transformation Consultant, AWS grillir@amazon.com June 21, 2016 An Agile Approach to Accelerate Mass Migration
- 2. What we’ll cover today Review of the AWS Cloud Adoption & Migration Frameworks Large migration planning & execution considerations Migration playbook Central migration portal Lessons learned
- 3. AWS Cloud Adoption & Migration Frameworks
- 4. Cloud adoption is more than just technology… Why? Cloud Strategy Business strategy Enabler of the Business DevOps What are others doing? How? Industry Cost Control Reporting Operational Effectiveness Talent Optimization IT as Utility Application Transformation Security Compliance and Governance Measure Continuous Deployment On Demand Fail early & Iterate When? Cloud Adoption Roadmap
- 5. Cloud adoption is a journey It requires planning and an adoption roadmap. Cloud adoption strategy should be aligned closely with business goals and objectives. It can be disruptive and will drive significant change. Most start small, learn, iterate, and accelerate. Value can be achieved quickly.
- 6. Elements of a successful journey Executive Sponsorship Cloud-First Strategy Principles & Standards Experiment Cloud Center of Excellence Organizational Change Adoption Roadmap Align on business requirements; bring all stakeholders with you. Create your vision; incentivize team members to follow your lead. Define architectures, patterns, governance; measure, monitor, iterate. Publish guidance and guard rails for how to adopt cloud successfully. Provide centralized expertise; guide decentralized innovations. Define new operating models, policies, processes, economics; provide training. Start small and iterate, measure, manage, and update plan.
- 7. AWS Cloud Adoption Framework (CAF)
- 8. The AWS Cloud Migration Process •Portfolio discovery •Goals and Drivers •Prioritized backlog •Foundations (target zone setup) •Setup Factory (Tools, Teams, Process) •Application optimization •Process optimization •Operational optimization •Cost optimization Discover Analyze Plan Design Migrate Integrate Validate Operate Migration Factory Initiate Optimize Prioritized Backlog (PLAN) App 1 … App n
- 9. Large migration planning and execution considerations
- 10. Data center lease ending Major capital depreciated Strategic decision to go all in AWS Drivers
- 11. Business needs are a major factor in defining migration timelines: Short (< 3 months) Mid range (3 – 12 months) Longer term (1 – 3 years) Timelines
- 12. Migrate dev first, then production Live migrate production, then backfill dev Workload migration approaches
- 13. Hundreds to thousands of servers Aggressive migration timeline Large number of participants Combination of the above What is a large migration?
- 14. Application migration challenges Lack of accurate discovery tools and processes Lack of application contexts / information Inaccurate on premise costs Lack of detail and scope with respect to operating model, governance, risk, compliance, security, software licensing, etc. Increased cost Longer time to value Inaction Challenges
- 15. Additional large migration challenges Efficient coordination and communications across a large team made up of business, application, development, operations, and partner participants Discovering, transforming, and deploying complex sets of workload components Demand for automated management of AWS infrastructure and applications Insufficient WAN bandwidth to support ongoing operations + parallel server and data migrations
- 16. Small to medium migration Area Characteristic Program & project management Can get by with PMs managing activities with Microsoft Project & spreadsheets Can successfully leverage email and status calls to collect verbal updates, and report on status Infrastructure provisioning & workload migration Can get by with manual AWS infrastructure provisioning and workload migration Team size Small to medium IT team, possibly some business stakeholders Team skills Combination of IT & business staff that manage and execute the migration; may use contractors/partners to assist Level of project scope & visibility Smaller IT project or major business initiative in a smaller company
- 17. Large migration Area Characteristic Program & project management Requires automated workflow and tracking for technical and program-level visibility Infrastructure provisioning & workload migration Requires automation of AWS infrastructure provisioning and workload migration Team size 10s to 100s of staff performing coordinated/sequenced activities Team skills Combination of IT & Business staff that have the context, and AWS and/or Partner staff that have the specific SME skills to drive down risk & optimize every aspect of the migration Level of project scope & visibility Typically Tier 1 Business initiatives tied to strategic business goals/outcomes
- 19. The Migration Bubble – Components Planning and Assessment Migration Tools Consulting Partners Internal Training Duplicate Environments Lease Penalties
- 20. The Migration Bubble Cost Time Planning Migration Bubble Operation and Optimization • Discovery and assessment • Duplicate environments • Staff training • Migration consulting • 3rd party tooling • Lease penalties
- 22. Application Migration & Disposition Options Application Interviews App. Automated Discovery App. Migration Options App. Analysis Application Discovery Migration & Disposition Options Retain Retire Rehost Repurchase Replatform Refactor This is the “do nothing” option. Legacy costs remain and obsolescence costs typically increase over time Decommission and archive data as necessary “Lift and Shift” or “Forklifting.” Automated and scripted migrations are highly effective Either a replacement through procurement, or/and upgrade Opportunities to address significant infrastructure upgrades can be realized which positively affects compliance, regulatory and obsolescence drivers Re-architecting and recoding require investment in new capabilities. Potentially significant business disruption DescriptionComplexity Low Low Med Med High High
- 23. Application Owner Meeting Connectivity Requirements Data Migration Requirements Identify Application Artifacts Document Success Criteria Identify Testing Process Resolve Dependency ConflictsApplication Dependencies Review Existing Blueprints Verify VPC Connectivity Complete Artifact Checklist Firewall RequestsFirewall Port Determination Intra-port Requirements Week 1 Week 2 Initial Architecture Design Application Installation VPC Port Exception Allocate Credentials Verify Subnet Connectivity Deploy AMI’s App Owner ReviewApp Architecture Review VPC Architecture Design Identify Enhancement Opportunities Test Connectivity Migrate Data End to End Testing Owner Sign-off Update Final Design Document Baseline Performance Map out application migration activities Discover Design Build Key
- 24. Develop an Agile Phased Migration Plan Phase 1 AWSGOVDEV1 AWSGovDev2 AWSIntranet1 AWSInventory1 AWSKEYSTONE2 AWSrectrac1 AWSWEB10 Phase 2 AWSEMS3 AWSFireDEV2 AWSFirehouse2 AWSOneRoof2 AWSPAGEGATE2 Phase 3 AWSAWATCH1 AWSFBO1 AWSSQL12 AWSSQLDW1 AWSSQLFBO1 AWSTicketMGR3 AWSTicketMGR4 AWSTKTMGRWEB1 Phase 4 AWS3MSelfCHK1 AWSAPPSQL1 AWSAPPSQLDEV1 AWSILS3 AWSPAC3 AWSPRIVATESP1 AWSSPPRODAPP1 AWSSPPRODAPP2 Phase 4 – Cont. AWSSPPRODAPP3 AWSSPPRODSQL1 AWSSPPRODSQL2 AWSSPPRODWFE1 AWSSPPRODWFE2 AWSSQLDEV2 AWSTime3 AWSTimeDEV3 Each Phase – Multi Week Sprint + 2-Days for Lessons Learned
- 25. Workload Migration Playbook phases Varies by customer but typically ~9 phases and ~40 high-level activities
- 26. Workload Migration Playbook variations Application (infrastructure) migration option choices Application disposition option choices A number of factors drive the specific activities required for each individual workload migration
- 27. Service Description Application Discovery Service • Discover on-premises application inventory and dependencies. • Simplify your application migration planning process. • https://aws.amazon.com/application-discovery/ VM Import/Export • Import virtual machine images from your existing environment to Amazon EC2 instances and export them back to your on-premises environment. • https://aws.amazon.com/ec2/vm-import/ Management Portal for vCenter • Migrate VMware VMs to Amazon EC2 and manage AWS resources from within vCenter. • http://aws.amazon.com/ec2/vcenter-portal/ Database Migration Service • Migrate your databases to AWS with zero downtime. • Supports migrations between similar and different database platforms. • https://aws.amazon.com/dms/ Import/ Export Snowball • Efficiently and securely transfer large amounts of data from on-premises data centers to AWS. AWS migration support tools
- 28. Migration Technologies Description & Partners Discovery & Planning Discover IT assets across your application portfolio, identify dependencies and requirements, and build your comprehensive migration plan with this technology suite. Workload Mobility Execute migrations to AWS by capturing your host server, configuration, storage, and network states, then provision and configure your AWS target resources. Application Profiling Gain valuable insights into your applications by capturing and analyzing performance data, usage, and monitoring dependencies before and after migration. Partner discovery & automated migration tools https://aws.amazon.com/migration/partner-solutions/
- 30. Central knowledge management Collaborate & document decisions Multimedia training
- 31. Automated Workload Migration Playbook Automated workflow, customized to meet customer’s desired migration approach Migration Playbook templates, customized by workload
- 32. Real-time workload migration dashboard Finance Time Management Fin VerticalHR Knowledge Management QBR 721 Payroll Audit Tax Tracking Sales Deals Travel Tool Customer Portal Golden Marketing Inspector Operations APAC Vertical Compliance Enables: Portfolio-level transparency of migration progress Drill down to individual workload task details
- 33. Team management and modeling Define teams and identify realistic working hours for individual resources
- 34. Real-time program dashboard Enables: Portfolio-level transparency across tracks Detail-level drill down through Epic, Story, and task-level activities
- 35. Report on work across roadmap tracks
- 36. Manage releases with Kanban
- 37. Central asset management An online asset inventory integrated with Automated Migration Playbook enables: Bulk updates of data captured during discovery Tracking of asset status throughout the migration Aggregate reporting
- 38. Central Help Desk An online help desk integrated with Automated Migration Playbook enables: Tracking of end user issues to specific migration activities throughout the migration Improved feedback loops Assistance with detection and quicker resolution of issues
- 39. Lessons learned
- 40. Lessons learned Up-front planning Comprehensive discovery of workload components and dependencies Transparency via Central Migration Portal Proper project management Automated Migration Playbook
- 41. Key takeaways Migration as part of larger IT transformation framework Migration automation, focus on business processes not servers Leveraging AWS ecosystem – APN Consulting and Technology Partners, AWS Professional Services to reduce risk and optimize activities and business outcomes
- 42. Resources • AWS Cloud Adoption Framework • https://aws.amazon.com/professional-services/CAF/ • AWS Professional Services • https://aws.amazon.com/professional-services/ • AWS Migration Partner Solutions • https://aws.amazon.com/migration/partner-solutions/ • AWS Training • Migrating to AWS - 2 Day Instructor Lead Course • https://aws.amazon.com/contact-us/aws-training/ • AWS Whitepapers • A Practical Guide to Cloud Migration • https://d0.awsstatic.com/whitepapers/the-path-to-the-cloud-dec2015.pdf • Migrating Your Existing Applications to the AWS Cloud • http://media.amazonwebservices.com/CloudMigration-main.pdf
Editor's Notes
- Today we will cover a review of the cloud adoption framework. We will also cover large migration planning and execution considerations. We will talk about a migration playbook. And discuss how it fits into a broader central migration portal we will also cover lessons learned that you can include in the planning for your large-scale migration. We will not cover today a comprehensive discussion of: Developing a cloud adoption roadmap Reviewing the entire ecosystem of migration tools End to end migration execution These topics have been covered in other webinars in this series. Transition: Now lets take a quick look at the AWS Cloud Adoption Framework.
- Clearing: This slide represents a number of non-technical questions, concerns, and techniques that you need to address during your migration planning. Content: as you can see, there are a number of things you need to think about and planned for. Transition: To better organize these items, it is helpful to discuss them in the context of a journey.
- Clearing: so what makes up the journey? Content: requires planning and an adoption roadmap. Your strategy should be aligned closely with your business goals and objectives. It can be disruptive and will drive significant change not only to you're IT organization but in many cases to your business as well. Most journey starts small, you can learn iterate and accelerate as you gain knowledge and experience. Transitions: So how do you know if you are being successful in your journey?
- Clearing: here you see seven key elements to a successful journey. Content: aligning on business requirements, creating a vision, defining architectures in patterns and validating those architectures, providing guard rails to make it safe to experiment, building a cloud Center of excellence to allow you to crawl first, then train others to build momentum and walk, leading to institutionalizing processes, further accelerating your journey. Organizational change is difficult and migrating to the cloud will require you to consider very carefully how much change your organization will be able to absorb. Transitions: to help you be more successful, AWS has created the cloud adoption framework, based on our experiences helping customers with their journeys.
- The AWS Cloud Adoption framework is a simple and agile process to achieve sustainable business value with AWS cloud services. This adaptive four-phase framework is designed for small or large cloud transformations. It organizes the planning cycle and aligns the cloud strategy to the business objectives. Align Cloud & Business Strategy - Understand the business strategy, needs and requirements. Incorporate the business requirements into the cloud adoption strategy. Engage stakeholders, develop business case and TCO Rapid Discovery & Planning - Baseline your capabilities referencing our cloud adoption perspectives. Fully understand and document the opportunities to develop your cloud capabilities. Plan your journey and develop your unique strategic adoption roadmap. Execute the plan Realize & Sustain Business Value - Integrate best practices, run, measure and report the value of your cloud services. Look for opportunities to enhance, simplify, and optimize your environment. Update business case and TCO models Innovate & Transform - Increase the value of the cloud by; Incorporating a DevOps approach of continual improvement, Review your applications and develop a strategy to innovate & transform the application portfolio, Develop a cloud first strategy of agile application development, fail fast and increase application value to the business
- Now let’s cover some large migration planning and execution considerations.
- Content: There are many drivers for large-scale migrations. Many of our customers are wanting to migrate to AWS in order to prevent them from renewing their existing data center leases. Other customers are trying to prevent major capital expenses associated with refreshing existing depreciated hardware. And there are a number of customers that are planning large-scale migrations as part of a strategic decision to go all in with AWS. Transition: Now let’s look at migration timelines.
- Content: Business needs are a major factor in the finding migration timelines. Many customers are looking to migrate within a three month 12 months time frame. But we are seeing increases and customers that are aggressively planning migrations in even shorter periods. These aggressive migrations are typically being driven by the drivers that we just discussed. Transition:
- It is also very important to consider the migration approach the customer is planning. Many customers start by migrating their development environments first, followed by migrating their production environment. This allows for them to gain experience deploying in managing workloads on the AWS. Based on those lessons learned, they continue to promote their workloads from development to test and once final validation is complete, they promote the workloads into production. In some cases, we have customers that instead choose to migrate production first to ensure that they can deliver on their short timeline. Once production is migrated, they then backfill their development and test environments. One of our customers, Computer Sciences Corp., did just that. They were driven by a decision to split their company into two new companies, one focused on commercial and another on federal customers. Because they were splitting into two companies they had to maintain all existing back-office systems while cloning them for the to-be-created new federal Organization. You can learn more about CSC's journey by watching the AWS re:Invent 2015 session titled “GovCloud is not just for Govies” on Youtube. There is no right or wrong approach and decisions should be driven by your business drivers.
- Clearing: Content: Before we can discuss large migrations we first need to define what makes a large migration different than a normal migration. There're a number of factors that lead to a migration being considered large. The first factor is around the number of servers being migrated. We typically consider migrations of hundreds to thousands of servers as being large. Aggressive timelines are another factor. Especially when considering migrations that must be completed in a short number of months. Also, a large number of participants, made up of IT and business staff, along with Partners and AWS increase the complexity of communications and execution and warrant managing the initiative as a large migration. Transition: now that we have defined a large migration, let’s look as some common migration challenges.
- Let’s hit the challenges head on and start with the laying out what the challenges are that our customers typically face as they are considering migration to AWS – and we all know migrations are not easy whether they are from physical to physical or physical to virtual, including into AWS.
- Large migrations face these additional challenges….... Clearing: Content: here are some examples of challenges faced during large migrations. (go into detail about each) Transition: So, what are some characteristics of small to medium migrations.
- Content: small to medium migrations have the following characteristics. (go into detail about each one) Transition: So, how are large migrations different?
- Content: Large migrations have the following characteristics (go into detail about each one) Transition: Move to the migration playbook transition slide
- Where you’re having to deal with Planning and assessment, migration tools, consulting partners, internal training, etc. and all of these components have one common thread – how to estimate their cost, so that your Total Cost of Ownership reflects it and even more so – estimate the total cost of “Migration” so that you can figure out – is it worth it? What’s my breakeven point? Do I wait for few more months, as an example, so I don’t incur lease penalties, etc.
- This graphic depicts what we mean by bubble…where timeline stretches out and costs rise, especially more so when there’s no clarity or direction on each component. And the time and actual costs do add to the overall cost of migration.
- Transition: now let's look at what makes up a migration playbook.
- Once you have fully thought through those aspects, let’s go ahead and build a plan to migrate.
- And really build an agile migration plan – where you start small with workloads with lower complexity (and you can
- Clearing: here you can see the major phases of a workload migration playbook. Content: the workload migration playbook varies by customer but typically consists of around nine phases and around 40 high level activities. For large migrations these 40 activities must be multiplied by the 10s or 100s of workloads being migrated. Many activities must be carried out for each server in the workload. This results in potentially thousands of the activities that must be sequenced and coordinated. Discover, Plan, Provision Infrastructure, Capture Images, Deploy, Configure, Define Data Sync, Test, Cutover Transition: Let’s look closer at what drives variations in the playbook.
- Clearing: here you see information about both application migration and disposition options. Content: with application migration options you would include a different set of activities in your migration playbook depending on your choice of converting VM's verse cloning hosts verse container rising your apps and so on. Similarly, your choice of re-factoring vs re-platforming vs lifting and shifting a workload will require different activities. Transition: so what are some tools that can help? This graphic depicts in a decision tree format the steps you go through based on your application disposition. If we’re not talking about decommissioning and the ones not moving after assessment, you’re faced with the decisions as to whether you want to refactor, lift and shift, or refactor. You’ll notice that in refactoring and replatforming – the path is little bit longer, but you’re able to leverage AWS’s benefit fully – beyond just the benefit of no recurring hardware costs in the future, or pay for power, cooling, and risk that your hardware is obsolete. Lift and shift is where you can move quicker now, and migrate using several third party tools, so you gain advantage in immediate cost savings, but you still may have a monolithic application sitting in cloud not fully benefitting from what AWS has to offer. Lift and shift by far remains the most popular method we see our customers going to, at least initially to help build experience and comfort level with using AWS technologies and they refactor/redesign applications later on.
- Content: AWS has a rich ecosystem of consulting and technology partners, and you may want to leverage their tools for migration. For example, AWS has teamed up with Racemi which we announced in June at our Symposium, where you can leverage their Dynacenter migration software for no charge. Transition:
- Transition: now let's revisit some lessons learned while helping our customers migrate their workloads to AWS.
- Clearing: Content: Central console (operational, administrative) to provide some transparent visibility into the status of jobs in-progress/completed/failed or of the landscape of sources systems to be migrated with a health status of the agent. Without this, customers will be in the dark and fully dependent on individuals/partners to provide tedious status updates on calls or emails with each wave of application migration. This will result in the migration process being a black box. Transition: So, let’s also look at some key takeaways.
- Content: Transition: Move to questions