b2 - integrating on-premises workloads with aws
Post on 24-May-2015
617 Views
Preview:
DESCRIPTION
TRANSCRIPT
AWS Summit 2014
Orchestration and Deployment Options for Hybrid Enterprise Environments Guy Ernest Solutions Architect @guyernest
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
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
Why Hybrid Cloud? • All the things the cloud provides
– Agility – Economics – Scale
• But something gets in the way – Compliance – Previous investment – Legacy workloads – Attitudes
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
Hybrid Considerations
• Core Infrastructure
• Security – Authentication and Entitlements
– Identity Management
– Data Sovereignty
• Operations and Monitoring
• Infrastructure Deployment and Orchestration
Hybrid Considerations
• Cost Containment
• Pace of Innovation
• Cloud Orchestration
• Application Deployment
• Processes and Change Management
Today We’ll Focus On
• Preparing Core Infrastructure
• Orchestration Strategies
• Application Deployment Strategies
Preparing Core Infrastructure
Active Directory
Network Configuration
Encryption
Back-up Appliances
Users & Access Rules
Your Private Network
HSM Appliance
Cloud back-ups
AWS Direct Connect
Your Data Center Your Cloud
Core Infrastructure Considerations Driven by Business Requirements!
• Performance & Latency • Business Continuity • Geography • Data Sovereignty • Security • And Many More…
Some Relevant AWS Services • Amazon Virtual Private Cloud (VPC)
• AWS Direct Connect
• AWS Identity and Access Management (IAM)
Some Relevant AWS Services • AWS CloudFormation
• VM Import / Export
• AWS Management Pack for Microsoft System Center/
VMWare vCenter
• AWS API, SDKs, and Tools
Hybrid Orchestration Strategies
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
Choices, Choices, Choices
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
Three Orchestration Strategies
• Native Integration
• Deploy New Orchestration Layer
• Extend Existing Orchestration Tools
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
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
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
– Open Nebula – Eucalyptus – Netflix Asgard – CloudStack
• No licensing fees
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
New Orchestration Layer Invest in new hybrid orchestration tools. Best When: • Have moderate time constraints • Want the latest and greatest • Have trusted partners
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
New Orchestration Layer - Pros • Get latest and greatest capabilities • Multi-cloud support • Faster than DIY • Vendor-provided support
New Orchestration Layer - Cons • Licensing costs • Rip-and-replace legacy tools • Maintaining feature parity with AWS • Requires some specialized skills
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
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
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
Extend Existing Tools - Cons • Limited feature sets • Licensing costs • Maintaining feature parity with AWS • A “good enough” approach
Application Deployment Strategies
...
Corporate Data Centers
App 1
App 2
App N
... App 1
App 2
App N
Horizontal Run partial application layers on AWS
• Storage • Disaster Recovery • Database • Extend / Burst into AWS
Horizontal - Pros • Can keep sensitive layers in-house
– Data – IP / Trade Secrets – Regulatory Restricted
• Relatively easier compliance
Horizontal - Cons • More complex than vertical • Harder to undo if relationship with cloud
vendor sours
Vertical Deploy full application stacks on AWS • Net-new Workloads • Development and QA
Vertical - Pros • Quick to Implement / Minimal Integration • Good Application Stack Isolation • Leverages Cloud Benefits at Each Layer • Fairly Easy to Undo
Vertical - Cons • Doesn’t Really Leverage In-House IT
Resources • Must Have Well Established Governance
Policies for All Layers
© 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.
Managing Mission Critical Loads Wido Riezebos, CTO Eyefreight
Who is Eyefreight Background • Initial Dutch Government investments into Innovation in Supply Chain Logistics • 2009 Focus on Cost Management within Transportation • 2012 Funded by 2 Dutch Private Equity firms • 2013 Funding of US$ 14m • 2014 Geographical presence
– European headquarters in Utrecht, Netherlands
– US headquarters in Chicago, Illinois
Eyefreight, in other words • Young company with well known customers
• SAAS solution offering freight spend management and visibility – Tightly integrate with mission critical ERP systems – Communicate with hundreds of different parties – Running optimization algorithms on high volumes of data is core
business
Being an Innovative Company • Innovative companies are typically about doing
the right things • However, doing things right is like hygiene
– as in “if you don’t do it right you will get in stinking mess”
• So… get the right guys to ‘do things right’ for you. Think Services, not personnel.
• Only invest in your edge and competitiveness
A bit of background
Transportation Planning
Execution Monitoring
Cost settlement
Transport orders
Shipments Shipments
Order Allocation
Stock orders Sales orders
Transport orders Shipments Shipments
Shipment assignment
Status updates
Managing Mission Critical Loads • So how do we handle “mission critical”?
– Load balancing and fail-over – Streaming replication – Backup and point in time recovery – Configuration management in a massive cluster – Security certification
• Yeah yeah yeah. (You’ve read the book)
Per customer / day • 3000 orders • 200 shipments • 800 updates • 15.000 page hits
Now think 500 customers, 62.000 users, 3 continents
But how to use services to do that • Architect and design a solution that supports
cloud services from day one – Support multi tenancy from the load balancers through all
components down to the database schema – Many clusters with X nodes, using Y databases containing Z
schemas – Create appliances that self configure (dynamic cluster sizing
made easy). Just add a node – Isolate environments (customers, regions). Just add a cluster
And then go for scale • Automate
– Configuration: Packer, Chef, Docker, OSGi – Deployment: CloudFormation, local registry discovery, automatic
schema upgrades, Apache ACE/OBR – Scaling: APM trending / hotspot discovery, dynamic cluster
sizing, aggregated logging – Security: intrusion detection and global auditing
• Automation + capacity on demand = Flexibility
Scaling up; when you need it Why? SLA / Life cycle specific Customer specific Environment specific Load specific Economy of scale
Tips & Lessons learned • There are tools and API’s: Automate your build
process to produce AMI templates • If you need to scale, do not forget the rule of the
weakest link. In our case that is still RDS • Balancing over HTTP is so much easier. REST!
Challenges (potentially new services) • Backup and recovery services are at the level of
a database (not schema). So not necessarily at the level of your customer
• Root cause analysis is a pain in a load balanced cluster. You need to aggregate and correlate your logs centrally
• APM style Metrics at the functional level
Direct benefits, entrepreneurial • If you do not need to invest; then don’t • Instant maturity levels for OPS • Very flexible capacity; complete environments
can be created and abandoned ad-hoc
© 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.
Managing Mission Critical Loads Wido Riezebos, CTO Eyefreight
Thanks!
That’s all great Guy, but how do I actually get started?
Getting Started • Storage / Backups and Archive
• Development and Test
• Net New Workloads
• Disaster Recovery
• Cloud Bursting
• Migrate Legacy Workloads
Getting Started – Storage / Backup
Getting Started – Storage / Backup
Getting Started – Network Topology
Subnet 1
… Subnet 2 Subnet N
Considerations • Overlapping networks • IP stinginess
• VPC CIDR too small • Subnets too small
Getting Started – Connectivity
Considerations • Public Internet vs. Direct Connect • Redundancy
Customer Data Center
DX Location
Getting Started – IAM
Considerations • Identity Federation • AWS vs. App Stack Access • Build vs. Buy
What Next? • AWS Account Team • Trusted Partners • Resources
– http://aws.amazon.com/architecture – http://aws.amazon.com/enterprise
Thank You!
AWS EXPERT? GET CERTIFIED! aws.amazon.com/certification Guy Ernest
Solutions Architect @guyernest
COFFEE BREAK
AWS EXPERT? GET CERTIFIED! aws.amazon.com/certification
#awssummit
top related