Migrating to the Cloud

Transcription

1 Migrating to the Cloud October 27, Kuala Lumpur Shaun Norris

2 Intro

3 Bristol-Myers Squibb moved clinical trials to cloud # of Simulations # of Servers Total Run Time (hr) On-Premises Cloud Clinical trial simulations took 98% less time More efficient and iterative simulations results in fewer human trials 64% savings on clinical trial costs We re using fewer subjects in these trials, and needing fewer blood samples. Russell Towell Senior Solutions Specialist

4 Lamborghini moved their website to the cloud Less than one week to prepare dev & test environment Website was online in less than one month Seamlessly handled a 250% increase in visitors Today our time-tomarket is close to zero. Roberto Ciacci Digital Marketing Manager

5 SunPower migrated its leasing app to the cloud THE CHALLENGE THE OUTCOME Strict security requirements: 2-hour recovery after a disaster Easy access to business data, with near 100% availability faster deployment than on-premises Mirrors dev, test and production across two regions Can recover within 5 minutes of a disaster Savings of $30,000 per year

6 A (very) brief history of how software is built

7 .

8

9 Agile was (part of) the answer "Diagram by Karn G. Bulsuk (

10 Typical Application Delivery Pipeline

11 Some organisations were a little agile

12 Some were a lot more agile

13 Even with Agile development Environments were often wildly different from dev to test to prod Features in production like load-balancing, network gear were not available in dev or test due to cost / skills etc. Deployment build and packaging were usually manual and once-off

14 What did infrastructure often look like? Desktops Server Room Datacentre

15 End Result? Production deployments were risky, often with unexpected downtime Risk mitigation like Change Control (Change Prevention?) was very popular with operations to try and limit number of changes. With changes piling up, and releases being throttled, more and more features would go into every release, increasing the risk further. End Result? Production operations often was the bottleneck.

16 Who was responsible for what? Developers QA / Test Engineers Operations Administrators

17 How is this issue being solved? The DevOps movement started in 2009 Blurs the line between development and operations Small, frequent changes to production Faster feedback cycles Often uses Cloud computing

18 DevOps Full-stack developers doing Agile Many activities shift left in the pipeline - Security - QA and testing - Stabilization - Infrastructure setup and testing

19 If you build it you run it Developers building, testing and running code

20 Automate everything Automated unit, functional and security testing during development - xunit + selenium Automated continuous build and integration - Jenkins, TravisCI, Gradle, Electric Cloud tools Automated Infrastructure Deployment - Chef, Puppet, CloudFormation, Elastic Beanstalk Automated log analysis and production feedback - splunk, SumoLogic, Loggly, OSS options

21 Infrastructure in a DevOps project Cloud dev/test/production infrastructure environments

22 Cloud Computing minutes Go global in Focus on what matters Increase speed and agility Stop guessing at capacity Pay as you use

23 Step by Step Migration 6. Optimise 2. Proof of Concept 1. Cloud Assessment 3. Data Migration 4. Application Migration 5. Leverage the Cloud

24 Phase 1: Cloud Assessment Security and Compliance Financial Technical and Functionality Understand your dependencies Candidate Applications For Cloud Migration

25 Security and Compliance Considerations Risk tolerance CIA+D of my data Regulations Threats IP and Legal

26 Technical and Functional Assessment Which apps should move first Will the cloud work for my apps? Can we reuse existing tools? Support contracts?

27 Identify Dependencies Classify Apps by: Security Compliance Customer group Level of coupling Licensing

28 Migration Candidates Applications with under-utilized assets that need to scale and are running out of capacity that have architectural flexibility that utilize traditional tape drives to backup data that require global deployment Deprioritize applications that require specialized hardware to function (for example, mainframe or specialized encryption hardware).

29 Migration Considerations Can you map architecture to cloud? Can application be virtualized? Does application need specialized hardware? Third party software licenses? Level of effort to migrate? Are their application components which are not cloud-ready? Network requirements?

30 IT Tool re-use in the cloud Resource Management Resource Configuration System Management Integration Tools

31 License Migration to the Cloud Three main options in AWS cloud: Bring Your Own License (BYOL) Utility Pricing Model SaaS through an AWS Partner

32 Define Success Criteria for Migration Success Criteria Legacy AWS Cloud Capex $1m $300k Opex $20k/year $10k/year Procurement 3 month lead time Launch in < 5 mins Time to Market 8 months 2 months Reliability? 10 regions, 26 AZs Availability? 99.99% uptime Capacity Planning Build out DC for peak Virtually unlimited

33 Phase 2: Cloud Proof of Concept Choose a relatively simple candidate application to move first. Use this project to gain understanding and expertise for future migrations. Deploy

34 Why migrate to the AWS cloud? No Up-Front Capital Expense Low Cost Pay Only for What You Use Self-Service Infrastructure Easily Scale Up and Down Improve Agility & Time-to-Market Deploy Deploy

35 What are Customers running on AWS? Enterprise Applications Oracle, SAP, Microsoft, IBM Line-of-Business Applications Web Applications Digital Media Distribution Gaming Media Sharing Social Media

36 What are Customers running on AWS? Big Data & High Performance Computing Analytics for Consumer Web Genome Sequencing Large Scale Batch Processing Disaster Recovery & Archive Backup & Recovery Disaster Recovery Archive AWS Lunch and Learn

37 What sets AWS apart? Experience Building and managing cloud since 2006 Service Breadth & Depth 40+ services to support any cloud workload Pace of Innovation History of rapid, customer-driven releases Global Footprint 11 regions, 28 availability zones, 52 edge locations Pricing Philosophy 45 proactive price reductions to date Ecosystem 8,000+ SIs and ISVs; 1,600+ Marketplace products *as of July 31, 2014

38 Cloud Security with AWS Visibility View your entire infrastructure with a click Control You have sole authority on where data is stored SOC 1/SSAE 16/ISAE 3402 PCI DSS Level 1 DIACAP & FISMA ISO FedRAMP (SM) Auditability FIPS SOC 2 3 rd party validation SOC 3 HIPAA ITAR MPAA CSA Based on our experience, I believe that we can be even more secure in the AWS cloud than in our own data centers. Tom Soderstrom, CTO, NASA JPL

39 Service Breadth & Depth Enterprise Applications Virtual Desktops Collaboration and Sharing Databases Analytics App Services Deployment & Management Mobile Services Platform Services Relational No SQL Caching Hadoop Real-time Data Warehouse Data Workflows Queuing Orchestration App Streaming Transcoding Search Containers Dev/ops Tools Resource Templates Usage Tracking Monitoring and Logs Identity Sync Mobile Analytics Notifications Foundation Services Compute (VMs, Auto-scaling and Load Balancing) Storage (Object, Block and Archive) Security & Access Control Networking Infrastructure Regions Availability Zones CDN and Points of Presence A broad and deep platform helps customers build sophisticated, scalable applications

40 AWS Rapid Pace of Innovation Since inception AWS has: Released 942 new services and features Introduced over 35 major new services Announced 45 price reductions Amazon Elastic Transcoder AWS OpsWorks +285 AWS Storage Gateway Amazon CloudHSM +24 Amazon EBS Amazon CloudFront Elastic Load Balancing Auto Scaling Amazon VPC Amazon RDS Amazon SNS AWS Identity & Access Management Amazon Route Amazon SES AWS Elastic Beanstalk AWS CloudFormation Amazon ElastiCache AWS Direct Connect GovCloud 2011 Amazon Dynamo DB Amazon CloudSearch Amazon SWF Amazon Glacier Amazon Redshift AWS Data Pipeline 2012 Amazon AppStream Amazon CloudTrail Amazon WorkSpaces Amazon Kinesis 2013 Amazon Cognito Amazon Mobile Analytics Amazon Zocalo 2014 *as of Aug 18, 2014

41 Gartner 2014 Magic Quadrant for Cloud Infrastructure as a Service Gartner Magic Quadrant for Cloud Infrastructure as a Service, Lydia Leong, Douglas Toombs, Bob Gill, Gregor Petri, Tiny Haynes, May 28, This Magic Quadrant graphic was published by Gartner, Inc. as part of a larger research note and should be evaluated in the context of the entire report. The Gartner report is available at Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings. Gartner research publications consist of the opinions of Gartner's research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.

42 Final Thoughts or? What would be the impact to your business if you could deliver new features to production 2-10x faster, with fewer errors?

43 Before you on twitter AWS has published a migration whitepaper: j.mp/awsmigration

44 Thanks for attending today!