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.

7 tools for your devops stack


Published on

7 tools for your devops stack as presented at FlossUK 2012 in Edinburgh

Published in: Technology, Business

7 tools for your devops stack

  1. 1. 7 Tools for your devops stack Kris Buytaert FlossUK 2012 , Edinburgh
  2. 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• Building Clouds since before the bookstore• Some books, some papers, some blogs• But mostly, trying to be good at my job
  3. 3. Whats this devops thing anyhow ?
  4. 4. World , 200X-2009Patrick Debois, Gildas Le Nadan, Andrew Clay Shafer, Kris Buytaert, JezzHumble, Lindsay Holmwood, John Willis, Chris Read, Julian Simpson, 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 ....
  5. 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. 6. Devops, a definition:
  7. 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. 8. William Edwards Deming1986, Out of the Crisis.
  9. 9. “DevOps is a cultural andprofessional movement” Adam Jacob
  10. 10. CAMS● Culture● Automation● Measurement● Sharing Damon Edwards and John Willis
  11. 11. Culture :
  12. 12. Devs vs Ops
  13. 13. Breaking the SilosDevs Ops Getting Along
  14. 14. What tool?
  15. 15. Automation:
  16. 16. We all know / use● Deployment automation : ● Fai , kickstart, preseed, cobbler,● Configuration Management ● Puppet, chef, cfengine, bcfg2● Build Automation ● Jenkins, maven, ant, cruisecontrol, hudson
  17. 17. The Marionette Collective● Distributed ssh ++● Orchestration● 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
  18. 18. 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
  19. 19. 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 Elapsed Time: 1.73 s
  20. 20. fpm● Yes the F stands for Effing● #packagingsucks ● Missing upstream ● Ancient upstream ● Unneeded dependencies ● Broken upstream ● Distro Policies● “Maximum RPM” ?● Packaging is needed ● Dependencies, tooling, repositories● Anger driven development
  21. 21. fpm
  22. 22. 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
  23. 23. fpm in action●● Fork, pull● Jenkins pulls , builds , pushes to repo
  24. 24. Measurement:
  25. 25. But Monitoring Sucks !● #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
  26. 26. Why #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
  27. 27. Logstash● Not your average centralized logging tool● Elasticsearch backed● Shipper● Indexer● Web
  28. 28. Logstash ● Collect from anywhere ● Filter ● Send anywhere ● Queuing support
  29. 29. Logstash in Action
  30. 30. Kibana in Action
  31. 31. Graphite● Graphing at Scale● Graphing at Ease● Any metric is a graph● echo "somestring $somevalue $timestamp" | nc <%= graphitehost %> 2003
  32. 32. Graphite Composer x
  33. 33. Graphite API
  34. 34. Friends of Graphite● Collection : ● Statsd, ● Collectd, ● Jmxtrans ● Logster● Dashboards ● Tattle ● Gdash ● ...
  35. 35. Sharing:
  36. 36. ● Open Source● Github● Talk about Experiences● Open Spaces
  37. 37. Sushi
  38. 38. Vagrant● Abstraction layer for VirtualBox● Integrates well with Puppet/Chef● Project = ● Vagrantfile ● Manifests / Cookbooks● Portable, Small , Versionable● Use veewee to build your boxen
  39. 39. 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
  40. 40. Vagrant Blah● Vagrant init● Vagrant up● Vagrant provision● Vagrant down● Vagrant destroy
  41. 41. Quiz Time :Which tool did I forget ?
  42. 42. You
  43. 43. Links
  44. 44. ContactKris BuytaertKris.Buytaert@inuits.beFurther Reading@krisbuytaert Inuits t Hemeltje Duboistraat 50 2060 Antwerpen Belgium 891.514.231 +32 475 961221