Your SlideShare is downloading. ×
11 Tools for your Open Source devops stack
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

11 Tools for your Open Source devops stack


Published on

11 Tools for your Open Source devops stack as presented at Linuxcon 2012 Barcelona, and T-Dose , Fall 2012

11 Tools for your Open Source devops stack as presented at Linuxcon 2012 Barcelona, and T-Dose , Fall 2012

Published in: Technology
1 Comment
No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. 11 Tools for your devops stack Kris Buytaert @krisbuytaert
  • 2. Kris Buytaert• I used to be a Dev,• Then Became an Op• Chief Trolling Officer and Open Source Consultant• Everything is an effing DNS Problem
  • 3. Whats this devops thing anyhow ?
  • 4. World , 200X-2009 Patrick Debois, Gildas Le Nadan, Andrew Clay Shafer, Kris Buytaert, JezzHumble, Lindsay Holmwood, John Willis, Chris Read, Julian Simpson, Luke Kanies, John Allspaw and lots of others .. Gent , October 2009 Mountain View , June 2010 Hamburg , October 2010 Boston, March 2011 Mountain View, June 2011 Bangalore, Melbourne, Goteborg , October 2011 Rome, earlier this month! ....
  • 5. ● Devops is a growing professional and cultural movement● We dont have all the answers yet● We are reaching out to different communities● We will point out problems we see..● Only the name is new While we are still working out the solutions
  • 6. Devops, a definition:
  • 7. ● Adopt the new philosophy. We are in a new economic age. Western management must awaken to the challenge, must learn their responsibilities, and take on leadership for change.● Cease dependence on inspection to achieve quality. Eliminate the need for massive inspection by building quality into the product in the first place.● Improve constantly and forever the system of production and service, to improve quality and productivity, and thus constantly decrease costs.● Institute training on the job.● Institute leadership The aim of supervision should be to help people and machines and gadgets do a better job.● Drive out fear, so that everyone may work effectively for the company.● Break down barriers between departments. People in research, design, sales, and production must work as a team, in order to foresee problems of production and usage that may be encountered with the product or service.● Eliminate slogans, exhortations, and targets for the work force asking for zero defects and new levels of productivity. Such exhortations only create adversarial relationships, as the bulk of the causes of low quality and low productivity belong to the system and thus lie beyond the power of the work force. ● Eliminate management by objective. Eliminate management by numbers and numerical goals. Instead substitute with leadership. ● Remove barriers that rob the hourly worker of his right to pride of workmanship. The responsibility of supervisors must be changed from sheer numbers to quality. ● Remove barriers that rob people in management and in engineering of their right to pride of workmanship.● Institute a vigorous program of education and self-improvement.● Put everybody in the company to work to accomplish the transformation. The transformation is everybodys job.
  • 8. William Edwards Deming1986, Out of the Crisis.
  • 9. CAMS● Culture● Automation● Measurement● Sharing Damon Edwards and John Willis
  • 10. Culture, automation, Measturement, sharing
  • 11. Devs vs Ops
  • 12. Breaking the SilosDevs Ops Getting Along
  • 13. What tool?
  • 14. Culture,Automation, Measurement, Sharing
  • 15. “Solved problems”● Deployment automation : ● Fai , kickstart, preseed, cobbler,● Configuration Management ● Puppet, chef, cfengine, ● ....
  • 16. “challenges”• Build & Release Management• Package & Repository management• Orchestration
  • 17. Jenkins● Open Source Continuous Integration Server● A zillion plugins (400)● Have developers build stable and deployable code● Test Infra code
  • 18. Jenkins
  • 19. fpm #packagingsucks ● Missing upstream ● Ancient upstream ● Unneeded dependencies ● Broken upstream ● Distro Policies● “Maximum RPM” ?● Packaging is needed ● Dependencies, tooling, repositories● Anger driven development
  • 20. fpm
  • 21. fpmfpm -t rpm -s dir -n hornetq -v 2.2.5 hornetqExecuting(%prep): /bin/sh -e /var/tmp/rpm-tmp.nNkVwh+ umask 022+ cd /usr/local/build-rpm-hornetq-2.2.5.x86_64.rpm/BUILD+ exit 0Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.yUd4MV+ umask 022+ cd /usr/local/build-rpm-hornetq-2.2.5.x86_64.rpm/BUILD+ cd /usr/local/build-rpm-hornetq-2.2.5.x86_64.rpm/BUILD+ tar -zxf /usr/local/build-rpm-hornetq-2.2.5.x86_64.rpm/data.tar.gz+ exit 0Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.jkpqeA+ umask 022+ cd /usr/local/build-rpm-hornetq-2.2.5.x86_64.rpm/BUILD+ /usr/lib/rpm/brp-compress+ /usr/lib/rpm/brp-strip+ /usr/lib/rpm/brp-strip-static-archive+ /usr/lib/rpm/brp-strip-comment-noteProcessing files: hornetq-2.2.5-1.x86_64Checking for unpackaged file(s): /usr/lib/rpm/check-files /usr/local/build-rpm-hornetq-2.2.5.x86_64.rpm/BUILDWrote: /usr/local/build-rpm-hornetq-2.2.5.x86_64.rpm/SRPMS/hornetq-2.2.5-1.src.rpmWrote: /usr/local/build-rpm-hornetq-2.2.5.x86_64.rpm/RPMS/x86_64/hornetq-2.2.5-1.x86_64.rpmExecuting(%clean): /bin/sh -e /var/tmp/rpm-tmp.z2UL3B+ umask 022+ cd /usr/local/build-rpm-hornetq-2.2.5.x86_64.rpm/BUILD+ rm -rf /usr/local/build-rpm-hornetq-2.2.5.x86_64.rpm/BUILD+ exit 0Created /usr/local/hornetq-2.2.5.x86_64.rpm
  • 22. fpm in action●● Fork, pull● Jenkins pulls , builds , pushes to repo● (variants for Nagios Plugins / Jenkins Plugins available)
  • 23. The Marionette Collective● Distributed ssh ++● What version of ssh do I have installed on my servers ?● On what servers is XYZ running ?● Clean al my ssl certs ?● Restart apache on all servers with fact X
  • 24. mc-servicemc-service httpd status -W /uat/ * [ ============================================================> ] 80 /80 status=stopped status=stopped status=stopped status=stopped status=stopped status=stopped status=running status=stopped status=stopped status=stopped status=stopped status=running
  • 25. mc-packagemc-package -W /dev/ status jdk * [ ============================================================> ] 33 / version = version = version = version = version = version = version = version = version = version = version = version = version = version = version = version = version = -absent---- package agent summary ---- Nodes: 33/33 Versions: 1 * 1.5.0_17-fcs, 1 * 1.5.0_19-fcs, 1 * 1.6.0_13-fcs, 1 * 1.6.0_20-fcs, 1 * 1.6.0_23-fcs, 2 * 1.6.0_24-fcs, 2 * 1.6.0_29-fcs Elapsed Time: 1.73 s
  • 26. Culture, Automation,Measurement, Sharing
  • 27. #monitoringsucks Monitoring is AWESOME. Metrics are AWESOME. I love it. Heres what I dont love:● Having my hands tied with the model of host and service bindings.● Having to set up "fake" hosts just to group arbitrary metrics together● Having to either collect metrics twice - once for alerting and another for trending● Only being able to see my metrics in 5 minute intervals● Having to chose between shitty interface but great monitoring or shitty monitoring but great interface● Dealing with a monitoring system that thinks IT is the system of truth for my environment● Not actually having any real choices John Vincent (@lusis) on his blog monitoring-sucks.html
  • 28. A sub movement● #monitoringsucks trending●● 2008 Study :Nagios + Friends● 2011 Conclusion : Nagios/Icinga are the only automatable alternatives● Monitoring and trending at scale , new kids Graphite, Icinga, flapjack, etc● Old Cool Kids, Ganglia
  • 29. Logstash● Not your average centralized logging tool● Elasticsearch backed● Shipper● Indexer● Web
  • 30. Logstash ● Collect from anywhere ● Filter ● Send anywhere ● Queuing support
  • 31. Logstash in Action
  • 32. Kibana in Action
  • 33. Puppet and Logstash● puppet-logstash● Includes Logstash / Kibana / Grok / ES modules as submodules !● git clone● git submodule init● git submodule update● vagrant up
  • 34. Graphite● Graphing at Scale● Graphing at Ease● Any metric is a graph● echo "somestring $somevalue $timestamp" | nc <%= graphitehost %> 2003
  • 35. Graphite Composer x
  • 36. Graphite API
  • 37. Friends of Graphite● Collection : ● Statsd, ● Collectd + Carbonplugin ● Jmxtrans ● Logster● Dashboards ● Tattle ● Gdash ● ...
  • 38. Gdash In action
  • 39. Puppet and Graphite● graphite/● Includes Graphite / Gdash / Jmxtrans / Logster / Collectd / Statsd / Tattle and more modules as submodules !● git clone● git submodule init● git submodule update● vagrant up
  • 40. Culture, Automation, Measurement,Sharing
  • 41. ● Open Source● Github● Talk about Experiences● Open Spaces
  • 42. Sharing environments● Build identical environments● Share code● Shared ownership of content , code and configuration
  • 43. Vagrant● Abstraction layer for VirtualBox● Integrates well with Puppet/Chef● Project = ● Vagrantfile ● Manifests / Cookbooks● Portable, Small , Versionable● Use veewee to build your boxen
  • 44. do |config| # All Vagrant configuration is done here. The most common configuration # options are documented and commented below. For a complete reference, # please see the online documentation at config.vm.define :mongo1 do |mongo1_config| mongo1_config.ssh.max_tries = 100 = "MyCentOS2""") mongo1_config.vm.host_name = "mongo1" mongo1_config.vm.provision :puppet do |mongo1_puppet| mongo1_puppet.pp_path = "/tmp/vagrant-puppet" mongo1_puppet.manifests_path = "manifests" mongo1_puppet.module_path = "modules" mongo1_puppet.manifest_file = "site.pp" end end config.vm.define :mongo2 do |mongo2_config| mongo2_config.ssh.max_tries = 100 = "MyCentOS2""") mongo2_config.vm.host_name = "mongo2" mongo2_config.vm.provision :puppet do |mongo2_puppet| mongo2_puppet.pp_path = "/tmp/vagrant-puppet" mongo2_puppet.manifests_path = "manifests" mongo2_puppet.module_path = "modules" mongo2_puppet.manifest_file = "site.pp" end end
  • 45. Vagrant Rocks● Vagrant init● Vagrant up● Vagrant provision● Vagrant down● Vagrant destroy
  • 46. Sushi
  • 47. Quiz Time :Which tool did I forget ?
  • 48. You
  • 49. Links
  • 50. ContactKris BuytaertKris.Buytaert@inuits.beFurther Reading@krisbuytaert Inuits Duboistraat 50 2060 Antwerpen Belgium 891.514.231 +32 475 961221