• Save
Automating OpenStack Deployment with Fuel
Upcoming SlideShare
Loading in...5

Automating OpenStack Deployment with Fuel



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

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



Total Views
Views on SlideShare
Embed Views



1 Embed 1

https://twitter.com 1



Upload Details

Uploaded via as Adobe PDF

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.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Automating OpenStack Deployment with Fuel Automating OpenStack Deployment with Fuel Presentation Transcript

  • ©  MIRANTIS  2013   PAGE  1  ©  MIRANTIS  2013  Automating OpenStackdeployments withFuelTomasz NapieralaSr. OpenStack Engineer
  • ©  MIRANTIS  2013   PAGE  2  Tomasz Z.NapierałaSenior OpenStack Engineer @ Mirantis, Inc.+16 years in IT industry+8 years with virtualization
  • ©  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.
  • ©  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
  • ©  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
  • ©  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
  • ©  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
  • ©  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
  • ©  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
  • ©  MIRANTIS  2013   PAGE  10  Instant cloud deployment
  • ©  MIRANTIS  2013   PAGE  11  Building blocksMCollecve  Keepalived  +Galera  +corosync  
  • ©  MIRANTIS  2013   PAGE  12  Supported systems• x86_64 architectures only6.3   6.3   12.04  
  • ©  MIRANTIS  2013   PAGE  13  Deployment modelsThe real power
  • ©  MIRANTIS  2013   PAGE  14  Single node•  All components on onenode•  On physical or virtualmachine•  Ideal for learning anddevelopment•  Not suitable forproductionNodes:  1  
  • ©  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+  
  • ©  MIRANTIS  2013   PAGE  16  Multi-node no HA –Compact Swift
  • ©  MIRANTIS  2013   PAGE  17  Multi-node no HA –Standalone Swift
  • ©  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
  • ©  MIRANTIS  2013   PAGE  19  Multi-node HA Compact
  • ©  MIRANTIS  2013   PAGE  20  Multi-node HA Compact Swift
  • ©  MIRANTIS  2013   PAGE  21  Multi-node HA Standalone
  • ©  MIRANTIS  2013   PAGE  22  HA (ha,ha ha)
  • ©  MIRANTIS  2013   PAGE  23  HA management• Keepalived for VRRP• Corosync + Pacemaker for Quantum components• HAProxy for managing VIPs
  • ©  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
  • ©  MIRANTIS  2013   PAGE  25  MySQL / Galera
  • ©  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  
  • ©  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
  • ©  MIRANTIS  2013   PAGE  28  HA details
  • ©  MIRANTIS  2013   PAGE  29  Deployment
  • ©  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
  • ©  MIRANTIS  2013   PAGE  31  Installation overview
  • ©  MIRANTIS  2013   PAGE  32  Fuel WebAwesome things happen in one month
  • ©  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
  • ©  MIRANTIS  2013   PAGE  34  Fuel Web demo timeIf time allows
  • ©  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  
  • ©  MIRANTIS  2013   PAGE  36  How Boris taught a goat  This  is  kool!  
  • ©  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
  • ©  MIRANTIS  2013   PAGE  38  We are hiring!http://www.mirantis.com/careers/
  • ©  MIRANTIS  2013   PAGE  39  Contact sheet  •  http://fuel.mirantis.com/•  https://github.com/Mirantis/fuel-library
  • ©  MIRANTIS  2013   PAGE  40  Q&A