Migration Planning
•Download as PPTX, PDF•
14 likes•14,826 views
In this presentation we will discuss the planning considerations as well as some applicable methodologies and tools involved in the development and execution of a large AWS migration strategy.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (19)
Similar to Migration Planning
Similar to Migration Planning (20)
More from Amazon Web Services
More from Amazon Web Services (20)
Recently uploaded
Recently uploaded (20)
Migration Planning
- 1. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Lawrence Guillory, CEO, Racemi Rodney Grilli – Sr. IT Transformation Consultant AWS grillir@amazon.com June 20, 2016 AWS Migration Planning
- 2. Welcome & Objectives Overview of AWS Methods & Frameworks Defining the “Migration Bubble” AWS Migration Planning & Execution Considerations Racemi & other Partner Solutions Building the Migration Plan 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
- 10. The Migration Bubble – Components Planning and Assessment Migration Tools Consulting Partners Internal Training Duplicate Environments Lease Penalties
- 11. 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
- 12. 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
- 13. AWS Migration Planning and Execution Considerations
- 14. Understand Your Business Drivers What is your business driver for migrating to the AWS cloud? • Cost • Agility • Freedom to experiment • Faster development • Significant business-impacting event (timeline driven) Knowing your business driver helps you plan your cloud migration.
- 15. Understand Your Costs It is important to accurately understand your current costs in order to know how to plan and build your migration model for optimal cost efficiency
- 16. On-premises Cost Considerations Network costs Storage costs Server costs Hardware – server, rack chassis PDUs, ToR switches (+maintenance) Software - OS, virtualization licenses (maintenance) Overhead cost Space Power Cooling Hardware – storage disks, SAN/FC switches Overhead cost Storage admin costs Network hardware – LAN switches, load balancer bandwidth costs Network admin costs Overhead cost IT labor costs Server admin Virtualization admin 1 2 3 4 Space Power Cooling Space Power Cooling illustrative Diagram doesn’t include every cost item. E.g. software costs can include database, management, middle tier software costs. Facilities cost can include costs associated with upgrades, maintenance, building security, taxes etc. IT labor costs can include security admin and application admin costs.
- 17. AWS Migration Cost Considerations 3rd Party Costs • 3rd Party Migration Tools • Storage Vendors • 3rd Party Application Licensing • OS Licensing AWS Costs • AWS Direct Connect • Amazon EC2 (right-sized based on utilization metrics) • Amazon EBS (anticipated usable volume size) • Amazon EBS snapshots • Amazon S3 (usable storage) • Amazon Elastic Load Balancing • Amazon CloudFront • Other Applicable Costs (Amazon RDS, Amazon Redshift, Amazon EMR, etc.) • 2nd (or 3rd) Availability Zone Labor • Employees (FTE) • Onshore Consultants • Offshore Consultants • Refactoring Effort • Unsupported OS • OS Upgrade • Database to RDS • Tools Change Management • Governance • Operating Model • Training • Financial Management and Measurements • Configuration Management • Service Management • Continuous Delivery / Continuous Integration
- 18. Speed and Process Decisions Change Migration Costs The cost of migration has many levers that can be pulled in order to speed up or slow down the process. Each of these has a corresponding cost associated with it.
- 19. Understand Your Staffing CIO Office PM Office Architecture Team Finance Team Security Team Compliance Team Migration Team Business Teams Application Teams Operations Team Application Portfolio Discovery I A I I C R I C C Application Analysis A C C C I R Storage and Database Analysis A C C C R C Migration Design I A C C R C Migration Factory I A C I C R Operations and Optimization C I I I R A R: Responsible A: Accountable C: Consulted I: Informed Establish a Cloud CoE • Define Roles & Responsibilities • Identify Skills & Competencies
- 20. Application Discovery & Assessment
- 21. 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
- 22. Identify Strategic Vision (example) • Modernize the Workforce • Improve IT agility through the development of cloud based service and hosting capabilities • Transform the organization into a leader in delivering solutions & capabilities via strategic partner integrations Setting a strategic vision is critical to any transformation initiative. It inspires & unifies the entire organization, while providing a clear target state to guide their day to day activities.
- 23. Define Sourcing Strategy (example) Strategies • Choose SaaS for highly commoditized business capabilities • Choose PaaS for standard business capabilities • Choose IaaS for workloads that are not readily supported by PaaS or SaaS. Desired Outcomes • Rapid development, agility, flexibility • Single set of processes for IT Operations • Cost effective licensing, on demand provisioning, and shift from fixed to variable costs
- 24. Define the Sourcing Model (example)
- 25. Define Sourcing Values and Input Methodology (example) Assessment Criterion Input Classification Justification (1-Low / 3-High ) Weight Level of Differentiation to the Organization - Impact on competitive research - Impact on LOB1 and LOB2 recruiting 1 – Non differentiator 2 – Low differentiator 3 – Core differentiator 60% Complexity of Operation - Number and complexity of business rules/processes 1 – Low complexity of operation 2 – Moderate complexity of operation 3 – High complexity of operation 20% Skills and competencies - Specialized skills required to support and operate 1 – Highly specialized skills that are a challenge to hire and retain 2 – Moderate specialized IT/product skills 3 – Common IT/Admin/Programming skills 20%
- 26. Define Hosting Values and Input Methodology (example) Assessment Criterion Input Classification Justification (1-High fit / 5-Low fit) Weight Technical Architecture - Architecture Styles - Technical Complexity - Application Hosting 1 – Cloud developed, three tier web applications with Amazon AMIs existing. 2 - Somewhat complex; tech environment is still relatively stable but the integration points with other applications are complex. Core application though is web capable. 3 - Highly complex, not cloud, not web, or new to UITS. 40% Commodity vs. Specialty - # of products/services supporting the capability - # of customers for the capability 1 - Large number of products/services with large number of customer across multiple segments 2 – Small group of niche products/services with a small number of customers across one or a small number of segments 3 – Unique to UA students and/or faculty with no existing products/services available to deliver the capability 40% Risk - Technical Risk Score - Technical Risk Summary - Technical Alignment - Sensitive Data 1 – Low Risk, non strategic application 2 – Medium Risk, strategic or business application internally facing or with small exposure 3 – High Risk, Strategic, externally facing, revenue generating application, Sensitive Data 20%
- 27. Application Assessment Output (example)
- 28. 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
- 29. 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. Racemi Cloud Solutions Lawrence Guillory, CEO, Racemi
- 31. Racemi Overview • Industry Leading Cloud Migration Software • World class Global Professional Services • Cloud Discovery & Cloud Migration
- 32. Six keys to accelerate cloud migrations 1. Gain support - execute small quick wins 2. Build momentum - start now, do not over think it 3. Earn credibility - use industry experts 4. Ensure success - use proven methods 5. Lead the project - be decisive 6. Leave a legacy - share the success
- 33. Customer Enablement • Unlimited No-cost migrations into GovCloud (US) • No-cost discovery and migration services (limited) • Penny migrations launching today in Amazon Marketplace • Booth 500. www.racemi.com/free
- 34. Build the Migration Plan
- 35. Use 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 2 … App n
- 36. Include Migration Readiness Activities • Business Assessment • Financial Assessment • Technical Assessment • Regulatory and Compliance Assessment • Security Assessment • Contractual Assessment
- 37. 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
- 38. 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
- 39. Lessons Learned
- 40. 1st Lesson Learned Early Planning, Communication and Buy-In is Essential • Map out the timeline • Understand and Categorize your Applications • Define your strategy • Limit the variables “Without a plan, there can be no victory”
- 41. 2nd Lesson Learned Personnel requirements in the cloud really are different from traditional operations Strong Ops need for Software Engineering skills Minimized need for deep Network or Storage Not just in Ops…also for QA, Release, Dev and Security
- 42. 3rd Lesson Learned The Burden of “Day Jobs” During Migration Existing Staff frequently asked to: − Maintain current infrastructure − Learn new skills − Build out new infrastructure − Migrate applications to the new environment − Decommission the old environment Do all of the above on the same salary
- 43. 4th Lesson Learned Establish Foundational Cloud Capabilities Region & Account Strategy VPC Strategy Hybrid Capabilities WAN DNS Operations Security & Compliance
- 44. Migration Progress 5th Lesson Learned Build Momentum, Monitor and Report Status
- 45. 6th Lesson Learned Help is available from AWS – Use it! Documentation and Whitepapers Solution Architects Professional Services/APN Partners Trainers Technical Account Managers (TAM)
- 46. Key Takeaways Have a strategy and a Plan (even if it changes as you migrate) Understand the components of your Migration Bubble and their corresponding costs Determine the best “migration path” for each application to optimize cost/outcome in the migration process Leverage the Tools: APN Partners, Tooling, and AWS to shorten the migration window Go fast!
- 47. 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
- We’ll cover the following topics -
- 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
- 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.
- 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.
- So, let’s break them down in manageable chunks and address them head on -
- In today’s world, speed and timing matter. This agility combined with innovation (USP) has proven to be a game-changer for several organizations across various industries. Innovation requires research and development. Organizations need resources, including people and technology, to promote and support such experimentation. And when you have an idea, if you take too long to productize it and release to the market, you might lose to your competition. Many organizations have realized that the cloud enables speed, agility, and the freedom to experiment while being cost-efficient. By running your applications in the cloud, your development and technology teams can focus on creating innovative solutions instead of firefighting everyday problems. The top business drivers for organizations to migrate to and use cloud include cost, agility, freedom to experiment, and faster development. A few migration projects have been driven by a specific timeline that was based on an event that significantly affects the customer’s business operations. For example, an expiring lease on a data center led one organization to explore the benefits of migrating to the AWS cloud. Although the business driver for this scenario can be associated with cost, their cloud migration project was driven by a specific timeline––all resources must be migrated to the cloud before the lease expiration. Other examples of such significant events include hardware refresh cycles, expiring IT Outsourcing (ITO) contracts, or a large-scale IT/digital transformation program. Your business driver for migrating to the cloud plays a key role in planning your cloud migration journey. It will help you in determining a migration strategy and prioritizing applications. It is important to note that although your organization might have identified an overall business driver to migrate to the cloud, you could still have specific motivations at a much granular level like data center, business unit, application, team, and workload. Example An organization decides to migrate all their data centers to the AWS cloud over the next two years with a long-term goal to increase agility and reduce time to market. However, the lease on one of their data centers is expiring in six months. So the immediate need (at the data center level) is to migrate all the resources in that data center to the AWS cloud.
- First and foremost – let’s hit the ones most customers are challenged with upfront - your on-prem costs. And why? So that you can make an informed decision on whether migration now or later makes sense, including getting a handle on the cost of migration itself! We have all heard from customers that many customers get started on AWS for the cost savings as that’s an important data point for your decision to migrate, but we also hear that stay for the agility and innovation – or as I call is strategic value that cloud enables them to do – and it’s difficult to quantify that in terms of hard dollars or cost savings, so we won’t discuss that in this webinar.
- In my experience, most customers have a fairly decent understanding of and good data on Server costs, storage costs, and network costs, including OS costs and maintenance expenses (areas highlighted in blue). However, where I see customers struggle is in blue areas and even more so on the yellow areas. But, even in areas where customers feel like they have good data,
- Now, we just talked about various cost drivers and elements that make up the TCO or cost to run your applications on-prem. But when you’re thinking about migration - you’re probably starting with the “cost to migrate” first– and speed and process decisions affect the migration costs that we’ll talk about now.
- This matrix shows an example of the roles and responsibilities that various teams within a Cloud CoE may assume throughout a cloud migration project. R: Responsible – team that does the work to complete the task/phase A: Accountable – team that is ultimately held accountable for the completion of the task/phase C: Consulted – team whose advice is sought during completion of the task/phase I: Informed – team who is kept up-to-date on progress and/or outcome of the task/phase
- 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:
- Assessing your cloud migration readiness helps to build a business case for migrating your application to the cloud. It will also help in early identification of special considerations and constraints that might require more time for migrating the application to the cloud or even limit the migration of the application. For example, if some applications in your environment have specific compliance and regulatory requirements, those need to be highlighted early in the process to be taken into due consideration during migration planning. A technical assessment is required to understand which applications are more suited to the cloud architecturally and strategically. At some point during the migration process, you will have to determine which applications will move into the cloud first and which applications will move later. This topic will be covered in more detail in later modules.
- 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