Cloud IaaS Migration Roadmap

Transcription

1 Cloud IaaS Migration Roadmap A framework for migrating an existing onpremise infrastructure to a public cloud provider Richard Weiss November 3rd 2015

2 Richard Weiss Principal Consultant, Pythian Group SQL Server and Wintel Guru IT professional for over 20 years Senior Data Management roles with First Data, Western Union and AAA National Retail Foundation, Data Standards Committee member Blogger at Pythian.com

3 HOW DID WE GET HERE? INFRASTRUCTURE EVOLUTION The 1:1 Data Center Virtualization emerges Massive virtualization Public Cloud connections IaaS mass adoption & hybrid cloud infrastructure convergence Pythian Confidential

4 THE WORLD IS CHANGING FAST Big Data 90 percent of the data created in the last two years alone. Mobile 2 billion (plus) smart devices shipped in 2014 alone. Social 84 percent of customers depend on social sites for purchasing advice. Cloud 62 percent of total workloads will be in the cloud by Internet of Things 75 billion devices connected to the internet by 2020.

5 TRADITIONAL ENTERPRISE TECHNOLOGY PARADIGMS ARE BROKEN 50% of large enterprises will have hybrid cloud deployments by % of new software is now being built for the cloud. 46% of IT spend moving to cloud by 2020

6 Business Agility CLOUD ADOPTION DRIVERS Accelerated time to market Leverage elastic resources Reduced CAPEX Predictable Budgeting Leverage OPEX model Improved Consumer Experience Geographic proximity and diversity Increased availability Service and Product Expansion CDN, Machine Learning, Big Data Integration Risk Mitigation Shared responsibility for compliance Hybrid cloud offers options for sensitive data Address data sovereignty challenges

7 BUSINESS TRANSFORMATION DRIVEN BY CLOUD ADOPTION

8 PUBLIC CLOUD DETRACTORS THE CRITICS CAN T ALL BE WRONG

9 A LOOK AT THE PUBLIC CLOUD SPACE

10 PATH TO CLOUD

11 MAKING THE MOVE HYBRID OR THE FULL MONTY? Public Cloud Private Cloud Pythian Confidential

12 THE FIVE MAJOR CLOUD TRANSFORMATION PHASES Assess: Analysis & Planning Prepare: POC, Validation & Final Roadmap Build: Construct Infrastructure Migration: Execute Transformation Optimization: Cloud Enhancements Existing and projected cost comparison & analysis Service and Application Classification Infrastructure architecture discovery Replatforming IaaS vs. PaaS & Hybrid considerations Initial roadmap creation Telco and required connectivity constructs Proof of concept implementation Security configuration and validation Acquire licensing keys/kits Roadmap finalization and hardening Establish networking & authentication infrastructure Build server infrastructure Provision all required storage and services Implement monitoring constructs Repeat, each applicable region Create detailed migration & rollback plans Perform mock migrations and UAT validation Begin migrations with non-production environments Implement production migration process Monitor and Trend Identify ondemand cost saving opportunities Identify IaaS optimizations & consolidation Investigate replatforming opportunities Leverage cloud provider services

13 MIGRATION TIMELINE Phase 1: Analysis & Planning Phase 2: POC & Roadmap Phase 3: Build Phase 4: Migration Phase 5: Optimization

14 PHASE 1: CLOUD ASSESSMENT, ANALYSIS AND PLANNING PHASE Assess Application Classifications Consumer facing (B2C) Client facing (B2B) Production internal application (batch processing, ancillary, etc.) Assess Infrastructure Architecture Networking Authentication Business application (ERP, CRM, Etc.) Storage Enterprise service bus Non-production (Test/DEV) Existing cloud services DR and SLA requirements Outliers / Specialty Compliance considerations PII, HIPPA, PCI, data residency, etc. Compute and OS considerations Scalability Licensing & Mobility Integration / External dependencies HA/DR/SLA s Telco / Circuit requirements Specialty appliances and services

15 PHASE 1: CLOUD ASSESSMENT, ANALYSIS & PLANNING PHASE CONTINUED Identify Target Platforms & Costing Migration Planning Considerations Cloud provider analysis / Selection Hybrid requirements Replatforming considerations IaaS vs. PaaS vs. SaaS each application Target connectivity considerations for all endpoints (public internet, dedicated circuits, IPSEC, etc.) Exclusion considerations (specialized HW, legacy, telco, etc.) Costing analysis / CAPEX to OPEX Existing co-location and facility contracts Vendor inclusion / reduction Current staffing skillset Regional cloud targets and availability Migration timeline considerations Migration methodology forklift/hybrid Application grouping and dependency identification Migration tools and/or vendors, evaluation, and selection Outlier considerations (high performance, non-conforming applications, etc.) Identify stateful and stateless Systems Define POC scope and deliverables Establish POC success criteria Initial migration roadmap creation

17 PHASE 2: PROOF OF CONCEPT, VALIDATION, AND ROADMAP FINALIZATION PHASE POC, Validation, Course Correction & Roadmap Finalization Implementation of required connectivity constructs (VPN, Express Route, Direct Connect, etc.) Execution of backlog items scoped within the phase 1 POC Scope and Deliverables roadmap Perform functional, performance and security testing and validation for all proof of concept implementations Course correct migration approach as necessary Utilize POC Process and discovery findings to complete the final migration roadmap Acquire proper licensing activation kits and keys. Ensure licensing compliance and mobility. Final migration roadmap should include contingency procedures as well as infrastructure construct precedence/dependency workflow.

19 PHASE 3: CLOUD INFRASTRUCTURE BUILD PHASE Create Infrastructure Constructs in Public Cloud Platform Define and implement network infrastructure and IP Ranges Define and implement network layer security devices (Firewalls, VPN, Etc.) Provision authentication and backbone mechanisms (LDAP, AD, DNS, Etc.) Implement integration between cloud resources such as AD and the existing on-premise infrastructure. Pre-Build all IaaS components which will be required prior to migration. Ensure that failover / secondary regions are also configured and integrated as necessary Provision all required Blob Storage and services Create/Deploy monitoring constructs Enlist a 3 rd party provider to conduct penetration testing Ensure staff/vendors have appropriate cloud platform accounts/access

20 A DOG AND A BABY

22 PHASE 4: MIGRATION PHASE Migrate On-Premise Infrastructure to Public Cloud Platform Collaborate with all applicable stakeholders to identify and inform regarding all planned and potential business impacting migration timelines. Get stakeholder buy-in for contingency and communication plans. Incorporate stakeholder feedback to finalize / expand on the detailed technical migration plan, Includes maintenance windows and detailed rollback / contingency plan(s). Perform mock migration(s) User acceptance testing of mock migration(s) Initiate the final migration process starting with non-production systems Migration of production systems User acceptance testing and validation of production systems Monitor for errors and established baseline anomalies Finalize and disseminate infrastructure documentation to staff and vendors

24 PHASE 5: OPTIMIZATION PHASE THE FINAL FRONTIER Optimization Phase Monitor and trend performance and usage patterns Optimize infrastructure and application for the cloud Perform comparative analysis on operational and performance metrics of cloud infrastructure against known on-premise baselines. Optimize service and server performance tiers Identify IaaS and application architecture optimization opportunities Investigate replatforming opportunities (PaaS / DBaaS / XaaS) for migrated applications Identify dynamic costing optimizations Investigate further consolidation opportunities Identify automation opportunities leveraging the cloud fabric and platform services

25 BUT WAIT THERE S MORE ADDITIONAL TIPS FOR SUCCESS Engage potential cloud providers early in the process. Competition is robust and significant financial incentives may be available based on commitment levels. It sounds counterintuitive, but your current data center provider may actually help with migration tools and managed services. Obtain a trusted third party opinion. Don t force a square peg in a round hole. Not every application is a cloud candidate. Get your house in order before attempting a migration.

26 ANY QUESTIONS? Pythian Confidential