• Save
AWS Summit Stockholm 2014 – B2 – Migrating enterprise applications to AWS
Upcoming SlideShare
Loading in...5
×
 

AWS Summit Stockholm 2014 – B2 – Migrating enterprise applications to AWS

on

  • 527 views

This session discusses strategies, tools, and techniques for migrating enterprise software systems to AWS. These applications are complex by themselves; they are frequently customized; they have many ...

This session discusses strategies, tools, and techniques for migrating enterprise software systems to AWS. These applications are complex by themselves; they are frequently customized; they have many touch points on other systems in the enterprise; and they often have large associated databases. Nevertheless, running enterprise applications in the cloud affords powerful benefits. We identify success factors and best practices.

Statistics

Views

Total Views
527
Views on SlideShare
527
Embed Views
0

Actions

Likes
1
Downloads
34
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Speaker Notes: <br /> [Type your notes here] <br /> <br />
  • Microsoft “License Mobility through Software Assurance” program provides qualifying Microsoft Volume Licensing customers with the flexibility to deploy Windows server based applications in the AWS cloud. <br /> <br /> AWS provides Windows Server, SQL Server on AWS today <br /> Amazon Machine Images (AMIs) jointly developed by Microsoft and AWS <br /> SharePoint Server, Exchange and other Microsoft server products can be licensed to run on AWS <br /> <br /> General info on AWS and License Mobility for a variety of MS server products: http://aws.amazon.com/windows/mslicensemobility/ <br /> <br /> server products: http://aws.amazon.com/windows/mslicensemobility/ <br /> <br /> Detail on AWS and License Mobility with SQL Server: http://aws.amazon.com/windows/mslicensemobility/sql/ <br /> <br /> <br /> <br />
  • Microsoft “License Mobility through Software Assurance” program provides qualifying Microsoft Volume Licensing customers with the flexibility to deploy Windows server based applications in the AWS cloud. <br /> <br /> AWS provides Windows Server, SQL Server on AWS today <br /> Amazon Machine Images (AMIs) jointly developed by Microsoft and AWS <br /> SharePoint Server, Exchange and other Microsoft server products can be licensed to run on AWS <br /> <br /> General info on AWS and License Mobility for a variety of MS server products: http://aws.amazon.com/windows/mslicensemobility/ <br /> <br /> server products: http://aws.amazon.com/windows/mslicensemobility/ <br /> <br /> Detail on AWS and License Mobility with SQL Server: http://aws.amazon.com/windows/mslicensemobility/sql/ <br /> <br /> <br /> <br />
  • Microsoft “License Mobility through Software Assurance” program provides qualifying Microsoft Volume Licensing customers with the flexibility to deploy Windows server based applications in the AWS cloud. <br /> <br /> AWS provides Windows Server, SQL Server on AWS today <br /> Amazon Machine Images (AMIs) jointly developed by Microsoft and AWS <br /> SharePoint Server, Exchange and other Microsoft server products can be licensed to run on AWS <br /> <br /> General info on AWS and License Mobility for a variety of MS server products: http://aws.amazon.com/windows/mslicensemobility/ <br /> <br /> server products: http://aws.amazon.com/windows/mslicensemobility/ <br /> <br /> Detail on AWS and License Mobility with SQL Server: http://aws.amazon.com/windows/mslicensemobility/sql/ <br /> <br /> <br /> <br />
  • Without getting into the industry debate about public vs. private cloud it’s clear that most cloud benefits cannot be realized with on-premise virtualization technologies. In the on-premise virtualization model, you often have to buy expensive hardware and software which virtually eliminates the cost benefits of cloud computing. Although on-premise virtualization allows you to quickly provision new servers, your ability to scale up is limited to your physical infrastructure. You still need to buy physical servers to grow. If you want to scale down you won’t see significant cost-savings as you already paid for the hardware. These limitations of the on-premise virtualization model impact your ability to innovate fast and free up money to invest in new projects. <br /> <br /> NAS is file based, SAN is block based. <br /> <br /> Short for Multiprotocol Label Switching, an IETF initiative that integrates Layer 2 information about network links (bandwidth, latency, utilization) into Layer 3 (IP) within a particular autonomous system--or ISP--in order to simplify and improve IP-packet exchange. <br /> MPLS gives network operators a great deal of flexibility to divert and route traffic around link failures, congestion, and bottlenecks.
  • Without getting into the industry debate about public vs. private cloud it’s clear that most cloud benefits cannot be realized with on-premise virtualization technologies. In the on-premise virtualization model, you often have to buy expensive hardware and software which virtually eliminates the cost benefits of cloud computing. Although on-premise virtualization allows you to quickly provision new servers, your ability to scale up is limited to your physical infrastructure. You still need to buy physical servers to grow. If you want to scale down you won’t see significant cost-savings as you already paid for the hardware. These limitations of the on-premise virtualization model impact your ability to innovate fast and free up money to invest in new projects. <br />
  • Without getting into the industry debate about public vs. private cloud it’s clear that most cloud benefits cannot be realized with on-premise virtualization technologies. In the on-premise virtualization model, you often have to buy expensive hardware and software which virtually eliminates the cost benefits of cloud computing. Although on-premise virtualization allows you to quickly provision new servers, your ability to scale up is limited to your physical infrastructure. You still need to buy physical servers to grow. If you want to scale down you won’t see significant cost-savings as you already paid for the hardware. These limitations of the on-premise virtualization model impact your ability to innovate fast and free up money to invest in new projects. <br />
  • Without getting into the industry debate about public vs. private cloud it’s clear that most cloud benefits cannot be realized with on-premise virtualization technologies. In the on-premise virtualization model, you often have to buy expensive hardware and software which virtually eliminates the cost benefits of cloud computing. Although on-premise virtualization allows you to quickly provision new servers, your ability to scale up is limited to your physical infrastructure. You still need to buy physical servers to grow. If you want to scale down you won’t see significant cost-savings as you already paid for the hardware. These limitations of the on-premise virtualization model impact your ability to innovate fast and free up money to invest in new projects. <br />
  • Without getting into the industry debate about public vs. private cloud it’s clear that most cloud benefits cannot be realized with on-premise virtualization technologies. In the on-premise virtualization model, you often have to buy expensive hardware and software which virtually eliminates the cost benefits of cloud computing. Although on-premise virtualization allows you to quickly provision new servers, your ability to scale up is limited to your physical infrastructure. You still need to buy physical servers to grow. If you want to scale down you won’t see significant cost-savings as you already paid for the hardware. These limitations of the on-premise virtualization model impact your ability to innovate fast and free up money to invest in new projects. <br />
  • Without getting into the industry debate about public vs. private cloud it’s clear that most cloud benefits cannot be realized with on-premise virtualization technologies. In the on-premise virtualization model, you often have to buy expensive hardware and software which virtually eliminates the cost benefits of cloud computing. Although on-premise virtualization allows you to quickly provision new servers, your ability to scale up is limited to your physical infrastructure. You still need to buy physical servers to grow. If you want to scale down you won’t see significant cost-savings as you already paid for the hardware. These limitations of the on-premise virtualization model impact your ability to innovate fast and free up money to invest in new projects. <br />
  • Without getting into the industry debate about public vs. private cloud it’s clear that most cloud benefits cannot be realized with on-premise virtualization technologies. In the on-premise virtualization model, you often have to buy expensive hardware and software which virtually eliminates the cost benefits of cloud computing. Although on-premise virtualization allows you to quickly provision new servers, your ability to scale up is limited to your physical infrastructure. You still need to buy physical servers to grow. If you want to scale down you won’t see significant cost-savings as you already paid for the hardware. These limitations of the on-premise virtualization model impact your ability to innovate fast and free up money to invest in new projects. <br />
  • Speaker Notes: <br /> [Type your notes here] <br /> <br />
  • The Module Objectives <br /> By the end of this training you will be able to do the following: <br /> Identify the Oracle and AWS alliance timeline. <br /> Describe how to identify opportunities that can be solved by AWS products and services and what other customers have done before. <br /> Verify some common best practices using Oracle and AWS product and services. <br /> Describe the support and licensing polices and other online resources.

AWS Summit Stockholm 2014 – B2 – Migrating enterprise applications to AWS AWS Summit Stockholm 2014 – B2 – Migrating enterprise applications to AWS Presentation Transcript

  • © 2014 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified, or distributed in whole or in part without the express consent of Amazon.com, Inc. Migrating Enterprise Applications to AWS Martin Elwin Manager, Solutions Architecture
  • 2 Licensing and Architecture 3 Migration Approach and Best Practices 5 Customer Project Migration: Lessons Learned We Will Discuss 1 Calculating Total Cost of Ownership (TCO) 4 Tools for Migration
  • Calculating TCO
  • In Your TCO Analysis 3- or 5-year amortization Use 3-year heavy RIs or fixed RIs Use volume RI discounts Ratios (VM:physical, servers:racks, people:servers) Mention tiered pricing (Less expensive at every tier : network I/O, storage) Cost benefits of automation (Auto Scaling, APIs, AWS CloudFormation, AWS OpsWorks, Trusted Advisor, optimization) DOs DON’Ts BONUS
  • In Your TCO Analysis Forget power/cooling (compute, storage, shared network) Forget administration costs (procurement, design, build, operations, network, security personnel) Forget rent/real estate (building deprecation, taxes, shared services staff) Forget VMware licensing and maintenance costs Forget to mention cost of “redundancy”, multi-AZ facility DOs BONUS DON’Ts
  • In Your TCO Analysis Time from ordering to procurement (Releasing early = increased revenue) Cost of “capacity on shelf” (top of step) Incremental cost of adding an on-premises server when physical space is maxed out Real cost of resource shortfalls (bottom of step) Cost of disappointed or lost customers when unable to scale fast enough DOs DON’Ts BONUS
  • Licensing and Architecture
  • Microsoft Licensing and Support Pay-as-you-go • SQL Server Standard Edition • Windows Server BYOL • SQL Server Enterprise Edition • SharePoint Server • Microsoft Windows Server Microsoft “License Mobility through Software Assurance”
  • Oracle Licensing and Support Processor & socket licensing 0.25 core multiplier for standard licenses (sockets) 0.5 core multiplier for enterprise licenses (processor) BYOL • Enterprise license agreement • Unlimited license agreement • Oracle partner network • BPO license • Oracle Technology Network Pay-as-you-go • RDS for Oracle SE One
  • SAP Licensing and Support Pay-as-you-go • SAP Hana One Business Edition • BOBJ BI 4.0 w/5 user licenses • Trial / Developer Editions BYOL • Primary model for most SAP applications • Existing licenses can be used on AWS User-based Licensing
  • Technology Stack On-Premises Solution AWS Network VPN, MPLS Amazon VPC, VPN, AWS Direct Connect Security Firewalls, NACLs, routing tables, disk encryption, SSL, IDS, IPS AWS security groups, AWS CloudHSM, NACLs, routing tables, disk encryption, SSL, IDS, IPS Storage DAS, SAN, NAS, SSD Amazon EBS, Amazon S3, Amazon EC2 Instance storage (SSD), GlusterFS Computer Hardware, virtualization Amazon EC2 Content delivery CDN solutions Amazon CloudFront Databases DB2, MS SQL Server, MySQL, Oracle, PostgresSQL, MongoDB, Couchbase Amazon RDS, Amazon DynamoDB, DB2, MS SQL Server, MySQL,PostgesSQL, Oracle, MongoDB, Couchbase Load balancing Hardware and software load balancers, HA Proxy Elastic Load Balancing, software load balancers, HA Proxy Scaling Hardware and software clustering, Apache ZooKeeper Auto Scaling, software clustering, Apache ZooKeeper Domain name services DNS providers Amazon Route 53 On-Premises Infrastructure Mapped to AWS
  • Technology Stack On-Premises Solution AWS Analytics Hadoop, Cassandra Amazon Elastic MapReduce, Hadoop, Cassandra Data warehousing Specialized hardware and software solutions Amazon RedShift Messaging and workflow Messaging and workflow software Amazon Simple Queue Service, Amazon Simple Notification Service, Amazon Simple Workflow Service Caching Memcached, SAP Hana Amazon ElastiCache, Memcached, SAP Hana Archiving Tape library, off site tape storage Amazon Glacier Email Email software Amazon Simple Email Service Identity management LDAP AWS IAM, LDAP Deployment Chef, Puppet AMIs, AWS CloudFormation, AWS OpsWorks, AWS Elastic Beanstalk, Chef, Puppet Management and monitoring CA, BMC, Rightscale Amazon CloudWatch, CA, BMC, Rightscale On-Premises Infrastructure Mapped to AWS
  • Services Key to Enterprise Migrations
  • Services Key to Enterprise Migrations PIOPS
  • Services Key to Enterprise Migrations AWS Direct Connect
  • Services Key to Enterprise Migrations AWS CloudFormation
  • Enterprise Migration Path $$$$ $$ Value to Business HighLowMedium TimetoExecute $$$$ Phase 1 Phase 2
  • 2 VPC Database Backup to AWS
  • Disaster Recovery Site on AWS
  • Enterprise Application Basic Architecture
  • Enterprise Application HA Architecture
  • Enterprise Application Detailed Architecture
  • Enterprise Application Detailed Architecture
  • Enterprise Application Detailed Architecture
  • Enterprise Application Detailed Architecture
  • Migration Approach and Best Practices
  • People, Process, Technology Migration Experience Knowledge & Training Not Primary Business Activity Fear Attempting Too Much at Once Migration Challenges
  • Identifying Applications to Move Standalone applications are easy to move Application with loosely coupled SOA-based integrations are good candidates Tightly integrated application needs more planning
  • Invest in Proof of Concept Early Will answer tons of questions quickly Will help identify gaps and touch points Give you a good estimation of the task ahead
  • • File transfer to Amazon S3 or EC2 using S/FTP, SCP, UDP, Aspera, Attunity • Configure on-premises backup application (like NetBackup, CA, CommVault, Riverbed) to use Amazon S3 • AWS Storage Gateway for asynchronous backup to Amazon S3 • AWS Import/Export service: Ship your disk to AWS • Database backup tools like Oracle Secure Back • Database replication tools like GoldenGate, DbVisit Migrating Data into AWS Cloud
  • The Migration Continuum Forklift Embrace AWS Optimize for AWS • May be only option for some apps • Run AWS like a virtual co-lo (low effort) • Does not optimize for on- demand (overprovisioned) • Minor modifications to improve cloud usage • Automating servers can lower operational burden • Leveraging more scalable storage • Redesign with AWS in mind (high effort) • Embrace scalable services (reduce admin) • Closer to fully utilized resources at all times Forklift Embrace Optimize Effort Benefits Operational Burden
  • Tools for Migration
  • Management and Monitoring BMC CLM, Boundary, HP OpenView, Tivoli, CA Spectrum Automation Manager, MS System Center Plug-in, Oracle EM Plug-in, RightScale, SAP Data Provider AWS CloudWatch Auditing and Logging Alert Logic Log Manager CA Audit, CloudCheckr Trend Micro, Xceedium Xsuite Ylastic AWS CloudWatch Alert Cost Management CloudHealth Apptio AWS Trusted Advisor Data Migration Data Expedition Aspera Attunity CloudBeam Riverbed Whitewater Tsunami AWS Storage Gateway Backup and Recovery CA, Commvault EMC Data Domain Netapp Oracle OSB Panzura Riverbed Whitewater Symantec, Zadara Amazon EBS Snapshot Migration Tools
  • Customer Project Migration Lessons Learned
  • Global manufacturing company with operations in APAC, Europe, and North America Vendor consolidation1 Infrastructure management challenge across multiple locations2 Hardware refresh cycles and cost optimization 3 Business Overview Key Business Drivers
  • What Was Achieved • Capital and operational cost reduction by avoiding new hardware purchases and by redeploying IT staff to projects that directly supported the core business • Other benefits included: – 55% reduction in total IT operations costs – 35% reduction in backup infrastructure costs – Ability to start and stop nonproduction services to reduce operational costs – Reduction in the number of IT vendors (from 6 to 3) – Able to perform an office relocation of HQ in early 2013, with no interruptions to business leveraging the centralized AWS computing platform
  • Migration Process Migrate Business Critical Applications •Migrate infrastructure components like domain controller, monitoring solutions •Migrate E-Business Suite, OBIEE •Tune – enhance - optimize Migrate Non- Mission Critical Applications •Migrate Test / DEV application •Migrate noncritical applications like Track-it •Migrate backups and validate restore process Proof of Concept •Build POC environments for each critical application and validate functionality •Perform functional, integration testing Assessment •Complete study of IT infrastructure & costs, including recommendations and a detailed plan •Perform cost analysis and estimate project duration and resources
  • AWS Architecture US East AZ-1 Headquarters VPC Public Subnet VPC Private Subnet Location 2 Internet OBIEE EBS R12 Monitoring Solution OpenVPN VPN Connection VPN Connection
  • AWS Infrastructure • Complete infrastructure for North America on Amazon Web Services – Office locations and warehouses connected via VPN to VPC on AWS – Oracle EBS/OBIEE on Linux • Complete in-house infrastructure including SQL Server, Oracle EBS, OBIEE and domain controllers, track-it applications , LACROSSE etc. • Migrate from Tivoli tape backups to Amazon S3 backups using Zamanda/Glacier, Snapshots • Integrated active directory with Salesforce.com, Office 365, various file, print, fax services throughout North America • All production backups to Amazon S3 using third-party tool • All nonproduction backups to Amazon S3 (reduced redundancy store)
  • © 2014 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified, or distributed in whole or in part without the express consent of Amazon.com, Inc. Thanks! Migrating Enterprise Applications to AWS Martin Elwin Manager, Solutions Architecture
  • Resources Here are some additional resources: • Get started with a free trial – http://aws.amazon.com/free • White papers – http://aws.amazon.com/whitepapers/ • Reference architectures – http://aws.amazon.com/architecture/ • Enterprise on AWS – http://aws.amazon.com/enterprise-it/ • Executive-level overview : Extending Your Infrastructure to the AWS Cloud (4 minutes) – http://www.youtube.com/watch?v=CsGqu5L_PFI • Simple Monthly Pricing Calculator – http://calculator.s3.amazonaws.com/calc5.html • TCO calculator for web applications – http://aws.amazon.com/tco-calculator/
  • © Copyright 2013. Apps Associates LLC. 44 Customer Migration (Discussed in the Slides) Overview • Source – Infrastructure – on-premise hosted servers – Hardware – (Dell PowerEdge, HP ML110) – Storage – (Dell Power vault) – Database – Oracle 9i/10g, SQL server – Fusion middleware – Packaged applications – Oracle E- Business Suite, Oracle Business Intelligence Suite, La-crosse, Mobile Field Service – Integration with Force.com platform – Firewalls, direct connectivity across multiple locations - (CISCO , Barracuda) – Tape backups - (Dell ML6000) • AWS – EC2, Amazon EBS, Amazon VPC – Multiple instance types (m1.medium, m1.large, m1.xlarge ) – Storage EBS , PIOPS, Amazon S3, Amazon Glacier – Management and monitoring using Nimsoft Monitoring Solution hosted on AWS – Connectivity using VPN tunnels – Archiving using Amazon Glacier – Data transfer using AWS Export/Import – DR configuration across regions
  • © Copyright 2013. Apps Associates LLC. 45 Customer Source System Technical Details • Oracle E-Business Suite – Database (RHEL 4) • Oracle 9i – 8 cores / 32-bit – E-Business Suite (RHEL 4) • 11.5.8 – 4 cores / 32-bit • Oracle Business Intelligence – Database (RHEL 5) • Oracle 10g – 4 cores – OBIEE 10g (RHEL 5) • OBIEE 11g – 4 cores • Microsoft SQL servers – Database (Win2008Hyper-V ) • MS SQL Server 2005 • Mobile Field Server – MWA ( Win 2008VM Ware ) • Oracle E-Business Suite – Database & E-Business Suite • Oracle Business Intelligence – Database & OBIEE 10g • Multiple VPN tunnels from multiple customer locations