Upgrade to Pro — share decks privately, control downloads, hide ads and more …

A One stop solution for Puppet and Openstack -...

A One stop solution for Puppet and Openstack - PuppetConf 13'

Daniel Lobato García

August 23, 2013
Tweet

More Decks by Daniel Lobato García

Other Decks in Programming

Transcript

  1. A one stop solution for Puppet and Openstack Daniel Lobato

    Garcia daniel.lobato.garcia@cern,ch @eLobatoss
  2. What is CERN Between Geneva and the Jura mountains, straddling

    the Swiss- French border Mission: learn what is the universe made of and how does it work? 3
  3. Fundamental questions in physics Why do particles have mass? What

    is 96% of the universe made of? Why isn’t there anti-matter in the universe? What was the state of matter after the Big Bang? 4
  4. Current status • 270 Openstack hypervisors • 2900 virtual machines

    • 300 users • 14 Puppet masters • 6 Foreman backend nodes • Some production services migrating to our cloud – early birds 9
  5. Goals • Ramp up to 15K hypervisors – 150-200K vms

    in 2015 • Multi-site (Hungary) 10
  6. Why? • Unnecessary homebrew stack of tools • Shift to

    cloud standards with minimal customizations • High turnover – can’t teach new tools 13
  7. Modules • Puppet definitions for every use case you can

    imagine. • Dynamic environments • Hadoop node • Openstack hypervisor • … you name it 20
  8. Foreman • Lifecycle management tool for VMs and physical servers

    • External Node Classifier – tells the puppet master what a node should look like 28
  9. 29

  10. 30

  11. Power operations & Foreman 8/12/2013 Document reference 31 Foreman Proxy

    Physical box IPMI Physical box IPMI Physical box IPMI VM VM VM Openstack Nova API
  12. Scalability experiences • Split up services • Puppet – critical

    vs non critical 35 12 backend nodes Batch 4 backend nodes Interactive
  13. Scalability experiences • Foreman – split into different services 36

    ENC Reports processing UI/API Load balancer 9443 – UI/API 9444 – Reports 9445 – ENC …
  14. Scalability experiences • Autoscale via alarms (Heat) • Define situations

    (i.e: load threshold..) • Spin up VMs as needed 37
  15. 40