240 likes | 481 Views
Migrating Workloads From AWS To HP OpenStack Public Cloud. Agenda. History: HP Cloud & OpenStack Tour: Migrated Projects Factors: Impacting Migration Efforts Lessons: Specific Learnings Perspective: From A “Customer” Conclusions. ‘Cloud Computing’ Timeline.
E N D
Agenda • History: HP Cloud & OpenStack • Tour: Migrated Projects • Factors: Impacting Migration Efforts • Lessons: Specific Learnings • Perspective: From A “Customer” • Conclusions
‘Cloud Computing’ Timeline • 1996 – Compaq’s George Favaloro and/or Sean O’Sullivan coin the term “Cloud Computing” • 2003 – Ben Black/Chris Pinkham at Amazon write a paper on standardizing Amazon infrastructure, mentions possibility of selling virtual servers as a service. • 2006 – Amazon Web Service offered • 2008 – Eucalyptus (open source) • 2010 – Microsoft Azure • 2011 – HP joins OpenStack…
HP Cloud Timeline 2014 HP Cloud Networking Cloud OS on OpenStack HPCS delivers common OS based on OpenStack October 2012 US East datacenter opens April 2012 US West datacenter opens January 2013 Application PaaS early access August 2012 GA for Object Storage & CDN 2013 March 2013 Load Balancing, Monitoring & DNSearly access March 2011 HP announces cloud strategy May 2012 Public beta 1000s on-boarded! September 2011 Private beta 1000s on-boarded! 2012 December 2012 GA for Compute 2011 July 2011 HP joins OpenStack
Image Based Fraud Detection HP Public Cloud
HP’s Getting Started with Windows 8 App Guiding Users through Learning Win 8 • Windows 8 “Helper” app • Tile content updates automatically (displays various topics that help can be obtained on) • Shipped on millions of PCs Windows 8 Question? Call HP SmartFriend at (866) 939-0270
Scheduled Delivery Content Generation • Subscription Mgmt • Content Vault • Simple Content Generation • Subscription Data • Web Print Platform • Prepares content for delivery • Executes delivery HP Web Connected Printer
Landscape Of Migrations Solution Complexity AWS Integration Highly Complex, Multi-Tiered Solution Simple App; Designed For Migration Team
Analogy: Custom vs Pre-Packaged Get exactly what is wanted but Takes a little extra time Get a solution quickly but Live with what is offered vs
Domain-Centric Permissions Model Tenants (a.k.a., Projects) span regions: Users: Devs VM VM VM VM Developer 1 Tenant 1 (Project #1-Dev) Developer 2 VM VM VM VM Developer 3 Developer 4 VM VM VM VM Developer 5 Tenant 2 (Project #1-Prod) : Prod = No Developers(Testers may be granted limited temporary access) VM VM VM VM Tester 1 Tester 2 VM VM VM VM Tester 3 Tenant 3 (Wiz-Bang-Dev) VM VM VM VM Users: Ops VM VM VM VM Ops Member 1 Tenant Ω(Business Core Infra) : Ops ONLY Ops Member 2 VM VM VM VM Ops Member 3 Ops Member 4
Application Migration vs Architecture Migration Monolithic App; Traditional Infrastructure Monolithic App; Cloud Infrastructure Cloud Architecture; Cloud Infrastructure Cloud Infrastructure
Using Heat at Scale First, A Simple Example • The template produces:
An application ‘super-stack’ is comprised of: • 1 DBaaS (MySQL) • 5 Load-Balancers • 52 virtual machines, • 148 block-storage volumes (some boot-drives, many data-drives), • ~250 other virtual objects gluing everything together • Net: ~450 'things'
Application-Deployment Orchestration Map: OpenStack Cloud Business Application / Partner Business Code & Middleware: Ready to go! Interaction Per-Instance Orchestrated Configuration Setup & Management (Puppet) Interaction E2E Orchestration: Automated provisioning of whole stack topologies Heat
Single-Business Public Cloud Domain: 16k+Cloud resources(>99% via Heat!)
Key Things To Remember • Automate. Automate. Automate. • Cattle, not pets • Deliver large-scale deployments………consistently • Tooling for Enterprise deployments • paradigm{AWS} != paradigm{OpenStack} • Sub-assemblies vs components • Solution Migration vs Architecture Migration