Orchestration & Deployment Options for Hybrid Enterprise Environments (ARC310) | AWS re:Invent 2013

1,542 views

Published on

Configure once, deploy anywhere is one of the most sought-after enterprise operations requirements. Large-scale IT shops want to keep the flexibility of using on-premises and cloud environments simultaneously while maintaining the monolithic custom, complex deployment workflows and operations. This session brings together several hybrid enterprise requirements and compares orchestration and deployment models in depth without a vendor pitch or a bias. This session outlines several key factors to consider from the point of view of a large-scale real IT shop executive. Since each IT shop is unique, this session compares strengths, weaknesses, opportunities, and the risks of each model and then helps participants create new hybrid orchestration and deployment options for the hybrid enterprise environments.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,542
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
52
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Orchestration & Deployment Options for Hybrid Enterprise Environments (ARC310) | AWS re:Invent 2013

  1. 1. ARC310: Orchestration and Deployment Options for Hybrid Enterprise Environments Donn Morrill, Amazon Web Services November 13, 2013 © 2013 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.
  2. 2. What is Hybrid Cloud? A composition of two or more distinct cloud infrastructures that remain unique entities, but are bound together by standardized or proprietary technology that enables data and application portability. “Special Publication 800-145 - The NIST Definition of Cloud Computing” – September, 2011
  3. 3. Requisite Gartner Quote “Nearly half of large enterprises will have hybrid cloud deployments by the end of 2017.” http://www.gartner.com/newsroom/id/2599315 - October 1, 2013
  4. 4. Why Hybrid Cloud? • All the things the cloud provides – Agility – Economics – Scale • But something gets in the way – – – – Compliance Previous investment Legacy workloads Attitudes
  5. 5. What do Enterprises Want in Hybrid? • Ability to deploy identical stacks • Interoperability between clouds • Ability to leverage one provisioning framework • Ability to leverage one operational framework
  6. 6. Hybrid Considerations • Core Infrastructure • Security – Authentication and Entitlements – Identity Management – Data Sovereignty • Operations and Monitoring
  7. 7. Hybrid Considerations • Cost Containment • Pace of Innovation • Cloud Orchestration • Application Deployment • Processes and Change Management
  8. 8. Today We’ll Focus On • Preparing Core Infrastructure • Orchestration Strategies • Application Deployment Strategies
  9. 9. Preparing Core Infrastructure Active Directory Users & Access Rules Network Configuration Your Private Network Encryption HSM Appliance Back-up Appliances Cloud back-ups Your Data Center Your Cloud AWS Direct Connect
  10. 10. Core Infrastructure Considerations Driven by Business Requirements! • • • • • • Performance & Latency Business Continuity Geography Data Sovereignty Security And Many More…
  11. 11. Some Relevant AWS Services • Amazon Virtual Private Cloud (VPC) – ARC202: Wednesday, 1:30 – Delfino 4003 • AWS Direct Connect – ARC304: Friday, 9:00 AM – Lando 4303 • AWS Identity and Access Management (IAM) – SEC201: Wednesday, 1:30 – Marcello 4406
  12. 12. Some Relevant AWS Services • AWS CloudFormation • VM Import / Export • AWS Management Pack for Microsoft System Center • AWS API, SDKs, and Tools
  13. 13. Hybrid Orchestration Strategies
  14. 14. A Decision Framework DIMENSION LOW MEDIUM HIGH Organizational Buy-In None or grassroots Divisional Top Down (CIO/CEO) IT Capabilities In-house Limited Partner Limited In-house Limited Trusted Partner In-house Advanced Trusted Partner(s) IT Vision Operational Somewhat forward thinking Innovative and cutting edge AWS Experience None/Limited Some Extensive
  15. 15. Choices, Choices, Choices
  16. 16. Tool Capabilities Considerations • • • • • • • Multi Public Cloud Support Monitoring and Alerting Identity Federation Service Catalog End-user Self Provisioning Cost Reporting and Chargeback Cloud-based Operation
  17. 17. Three Orchestration Strategies • Native Integration • Deploy New Orchestration Layer • Extend Existing Orchestration Tools
  18. 18. Native Integration Build a custom layer using API-level capabilities. Best When: • Have in-house development skills • Need very fine-grained control • Licensing costs are a big issue
  19. 19. Native Integration DIMENSION LOW MEDIUM HIGH Organizational Buy-In None or grassroots Divisional Top Down (CIO/CEO) IT Capabilities In-house Limited Partner Limited In-house Limited Trusted Partner In-house Advanced Trusted Partner(s) IT Vision Operational Somewhat forward thinking Innovative and cutting edge AWS Experience None / Limited Some Extensive
  20. 20. Native Integration - Pros • • • • Incorporate all services or only what you need Maximum flexibility React quickly to new features and services Leverage existing open-source tools – Eucalyptus – Netflix Asgard – CloudStack • No licensing fees
  21. 21. Native Integration - Cons • • • • Need in-house development skills Possible long development cycles Private cloud must support API-level access Support must come from in-house
  22. 22. New Orchestration Layer Invest in new hybrid orchestration tools. Best When: • Have moderate time constraints • Want the latest and greatest • Have trusted partners
  23. 23. New Orchestration Layer DIMENSION LOW MEDIUM HIGH Organizational Buy-In None or grassroots Divisional Top Down (CIO/CEO) IT Capabilities In-house Limited Partner Limited In-house Limited Trusted Partner In-house Advanced Trusted Partner(s) IT Vision Operational Somewhat forward thinking Innovative and cutting edge AWS Experience None / Limited Some Extensive
  24. 24. New Orchestration Layer - Pros • • • • Get latest and greatest capabilities Multi-cloud support Faster than DIY Vendor-provided support
  25. 25. New Orchestration Layer - Cons • • • • Licensing costs Rip-and-replace legacy tools Maintaining feature parity with AWS Requires some specialized skills
  26. 26. Extend Existing Tools Leverage existing investments in tools Best When: • Have aggressive time constraints • Don’t need latest and greatest • Have strong relationship with existing tools vendor
  27. 27. Extend Existing Tools DIMENSION LOW MEDIUM HIGH Organizational Buy-In None or grassroots Divisional Top Down (CIO/CEO) IT Capabilities In-house Limited Partner Limited In-house Limited Trusted Partner In-house Advanced Trusted Partner(s) IT Vision Operational Somewhat forward thinking Innovative and cutting edge AWS Experience None / Limited Some Extensive
  28. 28. Extend Existing Tools - Pros • • • • • No rip-and-replace Can be fastest path to hybrid Familiarity with tools and vendors Vendor-provided support Requires least amount of specialized skills
  29. 29. Extend Existing Tools - Cons • • • • Limited feature sets Licensing costs Maintaining feature parity with AWS A “good enough” approach
  30. 30. Application Deployment Strategies App 1 App 2 App N App 2 ... ... Corporate Data Centers App 1 App N
  31. 31. Horizontal Run partial application layers on AWS • • • • Storage Disaster Recovery Database Extend / Burst into AWS
  32. 32. Horizontal - Pros • Can keep sensitive layers in-house – Data – IP / Trade Secrets – Regulatory Restricted • Relatively easier compliance
  33. 33. Horizontal - Cons • More complex than vertical • Harder to undo if relationship with cloud vendor sours
  34. 34. Vertical Deploy full application stacks on AWS • Net-new Workloads • Development and QA
  35. 35. Vertical - Pros • • • • Quick to Implement / Minimal Integration Good Application Stack Isolation Leverages Cloud Benefits at Each Layer Fairly Easy to Undo
  36. 36. Vertical - Cons • Doesn’t Really Leverage In-House IT Resources • Must Have Well Established Governance Policies for All Layers
  37. 37. That’s all great Donn, but how do I actually get started?
  38. 38. Getting Started • Storage / Backups and Archive • Development and Test • Net New Workloads • Disaster Recovery • Cloud Bursting • Migrate Legacy Workloads
  39. 39. Getting Started – Storage / Backup
  40. 40. Getting Started – Storage / Backup
  41. 41. Getting Started – Network Topology Considerations • Overlapping networks • IP stinginess • • … VPC CIDR too small Subnets too small Subnet 1 Subnet 2 Subnet N
  42. 42. Getting Started – Connectivity Considerations • Public Internet vs. Direct Connect • Redundancy DX Location Customer Data Center
  43. 43. Getting Started – IAM Considerations • Identity Federation • AWS vs. App Stack Access • Build vs. Buy
  44. 44. What Next? • AWS Account Team • Trusted Partners • Resources – http://aws.amazon.com/architecture – http://aws.amazon.com/enterprise
  45. 45. Please give us your feedback on this presentation ARC310 As a thank you, we will select prize winners daily for completed surveys!

×