migrating to the cloud - mpcmscpmp.org/.../27-oct-2014-migrating-to-the-cloud... · migrating to...

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

Upload: duongdien

Post on 11-Jun-2018

217 views

Category:

Documents


0 download

TRANSCRIPT

Migrating to the Cloud

October 27, Kuala Lumpur

Shaun Norris

Intro

Bristol-Myers Squibb moved clinical trials to 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.

On-Premises Cloud # of Simulations

# of Servers

Total Run Time (hr)

2000

2

60

2000

256

1.2

Russell Towell Senior Solutions Specialist

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-to-market is close to zero.

Roberto Ciacci Digital Marketing Manager

SunPower migrated its leasing app to the cloud

Strict security requirements: 2-hour recovery after a disaster

Easy access to business data, with near 100% availability

T H E C H AL L E N G E

Mirrors dev, test and production across two regions

Can recover within 5 minutes of a disaster

Savings of $30,000 per year

T H E O U T C O M E

faster deployment than on-premises

A (very) brief history of how software is built

.

Agile was (part of) the answer…

"Diagram by Karn G. Bulsuk (http://www.bulsuk.com)".

Typical Application Delivery Pipeline

Some organisations were a little agile…

Some were a lot more agile …

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

What did infrastructure often look like?

Desktops Server Room

Datacentre

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.

Who was responsible for what?

Developers QA / Test Engineers

Operations Administrators

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

DevOps

Full-stack developers doing Agile Many activities shift ‘left’ in the pipeline - Security

- QA and testing

- Stabilization

- Infrastructure setup and testing

If you build it … you run it

Developers building, testing and running code

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

Infrastructure in a DevOps project

Cloud dev/test/production infrastructure environments

Cloud Computing

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

Step by Step Migration

1. Cloud Assessment

2. Proof of Concept

3. Data Migration

4. Application Migration

5. Leverage the Cloud

6. Optimise

Phase 1: Cloud Assessment

Security and Compliance

Financial

Technical and Functionality

Understand your dependencies

Candidate Applications

For

Cloud Migration

Security and Compliance Considerations

Risk tolerance CIA+D of my data Regulations Threats IP and Legal

Technical and Functional Assessment

Which apps should move first Will the cloud work for my apps? Can we reuse existing tools? Support contracts?

Identify Dependencies

Classify Apps by: • Security

• Compliance

• Customer group

• Level of coupling • Licensing

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).

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?

IT Tool re-use in the cloud

Resource Management Resource Configuration System Management Integration Tools

License Migration to the Cloud

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

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

Phase 2: Cloud Proof of Concept

Deploy

Choose a relatively simple candidate application to move first. Use this project to gain understanding and expertise for future migrations.

Why migrate to the AWS cloud?

Deploy

Pay Only for What You Use

Low Cost No Up-Front Capital Expense

Self-Service Infrastructure

Deploy

Easily Scale Up and Down

Improve Agility & Time-to-Market

Web Applications

Enterprise Applications

Oracle, SAP, Microsoft, IBM Line-of-Business Applications

Digital Media Distribution Gaming Media Sharing Social Media

What are Customers running on AWS?

AWS Lunch and Learn

What are Customers running on AWS?

Big Data & High Performance Computing

Disaster Recovery & Archive

Analytics for Consumer Web Genome Sequencing Large Scale Batch Processing

Backup & Recovery Disaster Recovery Archive

What sets AWS apart?

Building and managing cloud since 2006

40+ services to support any cloud workload

History of rapid, customer-driven releases

11 regions, 28 availability zones, 52 edge locations

45 proactive price reductions to date

8,000+ SIs and ISVs; 1,600+ Marketplace products

Experience

Service Breadth & Depth

Pace of Innovation

Global Footprint

Pricing Philosophy

Ecosystem

*as of July 31, 2014

Cloud Security with AWS

“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

Visibility

View your entire infrastructure with a click

Control

You have sole authority on where

data is stored

Auditability

3rd party validation

SOC 1/SSAE 16/ISAE 3402 PCI DSS Level 1

DIACAP & FISMA ISO 27001

FedRAMP (SM) FIPS 140-2

SOC 2 SOC 3 HIPAA

ITAR MPAA

CSA

Service Breadth & Depth

A broad and deep platform helps customers build sophisticated, scalable applications

Platform Services

Caching

Relational

No SQL

Hadoop

Real-time

Data Workflows

Data Warehouse

Queuing

Orchestration

App Streaming

Transcoding

Email

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 CDN and Points of Presence Availability Zones

Enterprise Applications

Virtual Desktops Collaboration and Sharing

Databases Analytics App Services Deployment & Management Mobile Services

AWS Rapid Pace of Innovation

2009

Amazon RDS Amazon VPC Auto Scaling

Elastic Load Balancing

+48

2010

Amazon SNS

AWS Identity & Access Management

Amazon Route 53

+61

2011

Amazon ElastiCache

Amazon SES

AWS CloudFormation

AWS Direct Connect

AWS Elastic Beanstalk

GovCloud

+82

Amazon CloudTrail

Amazon CloudHSM

Amazon WorkSpaces

Amazon Kinesis

Amazon Elastic Transcoder

Amazon AppStream

AWS OpsWorks

+280

2013

Amazon SWF

Amazon Redshift

Amazon Glacier

Amazon Dynamo DB

Amazon CloudSearch

AWS Storage Gateway

AWS Data Pipeline

+159

2012

Since inception AWS has: • Released 942 new services and features • Introduced over 35 major new services • Announced 45 price reductions

2008

+24 Amazon EBS Amazon CloudFront

+285

2014

Amazon Cognito

Amazon Zocalo

Amazon Mobile Analytics

*as of Aug 18, 2014

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, 2014. 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 http://aws.amazon.com/resources/analyst-reports/. 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.

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?

Before you go…

[email protected]

@shaunnorris on twitter

AWS has published a migration whitepaper:

j.mp/AWSMigration

Thanks for attending today!