Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Automating OpenStack Deployment with Fuel

9,702 views

Published on

OpenStack CEE Day Budapest. How to build OpenStack in minutes using Mirantis Fuel library

Published in: Technology

Automating OpenStack Deployment with Fuel

  1. 1. ©  MIRANTIS  2013   PAGE  1  ©  MIRANTIS  2013  Automating OpenStackdeployments withFuelTomasz NapieralaSr. OpenStack Engineer
  2. 2. ©  MIRANTIS  2013   PAGE  2  Tomasz Z.NapierałaSenior OpenStack Engineer @ Mirantis, Inc.+16 years in IT industry+8 years with virtualization
  3. 3. ©  MIRANTIS  2013   PAGE  3  Mirantis,Inc.Largest independent vendor of OpenStack services and technology.We operate from Mountain View, California, with remote offices in Russia, Ukraineand Poland.40+ successful OpenStack implementations and 300+ infrastructure experts.
  4. 4. ©  MIRANTIS  2013   PAGE  4  Hungarians and Polish...are friendsLengyel, Magyar – két jó barátegyütt harcol, s issza borát23 march – Day of Hungarian – Polish friendship
  5. 5. ©  MIRANTIS  2013   PAGE  5  Why Fuel?•  No (good) orchestration for infrastructure•  No support for HA out-of-the-box•  There was demand for this•  Scattered resources working on the same thing
  6. 6. ©  MIRANTIS  2013   PAGE  6  Why did we really build Fuel?Manual installation:•  Well, manual ;)•  Tedious•  Error prone•  Time consumingFuel based installation•  Fully automated•  Routine•  Error proof•  Fast
  7. 7. ©  MIRANTIS  2013   PAGE  7  What is Fuel•  OTS product•  Automation library•  Production-grade OpenStack deployments•  Supports multiple deployment topologies•  multi-node (HA & non-HA) and single-node•  End-to-end management of the cloud, including:•  monitoring•  operations•  upgrades between OpenStack releases
  8. 8. ©  MIRANTIS  2013   PAGE  8  Advantages•  Based entirely on open source technologies•  No proprietary, vendor-specific code•  Using expertise from production OpenStackdeployments•  Fully tested integration of all components•  Warranty and 24/7 support•  Continuous enhancements
  9. 9. ©  MIRANTIS  2013   PAGE  9  Ingredients•  Cobbler-based bare metal provisioning•  Puppet manifests for deploying OpenStack•  Scripts for config generation•  Reference OpenStack architecture with robust HA (custom HApatches)•  OpenStack packages•  Support for CentOS, RHEL, Ubuntu•  Support for Essex, Folsom (soon Grizzly)•  Configuration guide
  10. 10. ©  MIRANTIS  2013   PAGE  10  Instant cloud deployment
  11. 11. ©  MIRANTIS  2013   PAGE  11  Building blocksMCollecve  Keepalived  +Galera  +corosync  
  12. 12. ©  MIRANTIS  2013   PAGE  12  Supported systems• x86_64 architectures only6.3   6.3   12.04  
  13. 13. ©  MIRANTIS  2013   PAGE  13  Deployment modelsThe real power
  14. 14. ©  MIRANTIS  2013   PAGE  14  Single node•  All components on onenode•  On physical or virtualmachine•  Ideal for learning anddevelopment•  Not suitable forproductionNodes:  1  
  15. 15. ©  MIRANTIS  2013   PAGE  15  Multi-node non-HA•  Controllers separatedfrom computes•  Additional componentslike Quantum, Cinder•  Control over additionalservicesCompact Swift•  Swift on controllersStandalone Swift•  Swift on ded. nodesNodes:  3+  
  16. 16. ©  MIRANTIS  2013   PAGE  16  Multi-node no HA –Compact Swift
  17. 17. ©  MIRANTIS  2013   PAGE  17  Multi-node no HA –Standalone Swift
  18. 18. ©  MIRANTIS  2013   PAGE  18  Multi-node HA•  3 controllers with HA setup•  Control over additional services•  Full production grade architectureCompact Swift•  Swift oncontrollersStandalone Swift•  Swift ondedicated nodesNodes:  4+  Compact Quantum•  Quantum oncontroller
  19. 19. ©  MIRANTIS  2013   PAGE  19  Multi-node HA Compact
  20. 20. ©  MIRANTIS  2013   PAGE  20  Multi-node HA Compact Swift
  21. 21. ©  MIRANTIS  2013   PAGE  21  Multi-node HA Standalone
  22. 22. ©  MIRANTIS  2013   PAGE  22  HA (ha,ha ha)
  23. 23. ©  MIRANTIS  2013   PAGE  23  HA management• Keepalived for VRRP• Corosync + Pacemaker for Quantum components• HAProxy for managing VIPs
  24. 24. ©  MIRANTIS  2013   PAGE  24  Why Galera?  •  No need to think about failover, no monitor on top•  All nodes are active, all are masters•  The application can read/write to/from any server•  Horizontal scalability for reads and writes•  Has optimizations for high latency networks*•  No data loss
  25. 25. ©  MIRANTIS  2013   PAGE  25  MySQL / Galera
  26. 26. ©  MIRANTIS  2013   PAGE  26  Galera: failure scenario  •  Need 3+ instances for Galera quorum•  Fuel contains DB reconnect patch for OpenStackClient  MySQL/Galera  MySQL/Galera  MySQL/Galera  re-­‐connected  
  27. 27. ©  MIRANTIS  2013   PAGE  27  RabbitMQ HA: failure scenario  •  Mirrored Queues•  Fuel contains “consumer cancellation notification”handling patch for OpenStackClient  Master  Slave  Slave  keeps slavesin the same stateClients  always  consume  from  the  master  RabbitMQ  has  to  re-­‐elect  a  new  master    Consumers  need  to  handle  a  noQficaQon  &  start  consuming  from  a  new  master  consume  becomes a newmaster
  28. 28. ©  MIRANTIS  2013   PAGE  28  HA details
  29. 29. ©  MIRANTIS  2013   PAGE  29  Deployment
  30. 30. ©  MIRANTIS  2013   PAGE  30  How it worksFuel master nodeCobblerPuppetMaster1. Admin creates masternode and installs Fuel on it2. Admin enters h/w infointo Cobbler and runs BMPOpenStack ClusterOpenStackNode 1OpenStackNode 2OpenStackNode NInstalls Cent OS, RHEL, or UbuntuInstalls Puppet agentOpenStack is installedComponents are provisionedaccording to the chosen topology3. Admin picks OpenStack deployment topology,specifies settings, and runs Puppet
  31. 31. ©  MIRANTIS  2013   PAGE  31  Installation overview
  32. 32. ©  MIRANTIS  2013   PAGE  32  Fuel WebAwesome things happen in one month
  33. 33. ©  MIRANTIS  2013   PAGE  33  What is Fuel Web  •  Web-based OpenStack management tool•  Built on top of Fuel library•  Less flexibility than pure Fuel, but very visual andintuitive•  Makes it even easier to spin up and manage anOpenStack-based cloud
  34. 34. ©  MIRANTIS  2013   PAGE  34  Fuel Web demo timeIf time allows
  35. 35. ©  MIRANTIS  2013   PAGE  35  OpenStack  Cluster(s)  How Fuel & Fuel Web fit together  OpenStack  Cluster(s)  Puppet  manifests  Fuel  Web  Cobbler  automaQon  OpenStack  packages   Master  node  (ISO  install)  Web  UI  Fuel  Library    OpenStack  deployment  &  management  Hardware  discovery  
  36. 36. ©  MIRANTIS  2013   PAGE  36  How Boris taught a goat  This  is  kool!  
  37. 37. ©  MIRANTIS  2013   PAGE  37  RoadmapApr 2013•  Support for Grizzly•  Upgrade pilot from Folsom to Grizzly•  NIC bonding•  Full-features support for Xen•  Deploy with specific storage backend for Cinder (Compellent or Ceph)Jun 2013•  Improved HA architecture for OpenStack. Self-healing•  HA for Fuel master node•  Deploy with specific Keystone backend (LDAP/AD)•  Ceilometer•  Certified for 1000+ nodesAug 2013•  Support for multiple data centers•  Hardware provisioning (RAID, BIOS)•  Maintenance mode for hardware
  38. 38. ©  MIRANTIS  2013   PAGE  38  We are hiring!http://www.mirantis.com/careers/
  39. 39. ©  MIRANTIS  2013   PAGE  39  Contact sheet  •  http://fuel.mirantis.com/•  https://github.com/Mirantis/fuel-library
  40. 40. ©  MIRANTIS  2013   PAGE  40  Q&A

×