Successfully reported this slideshow.
Activate your 14 day free trial to unlock unlimited reading.
World , 200X-2009
Patrick Debois, Gildas Le Nadan, Andrew Clay Shafer, Kris Buytaert, Jezz
Humble, 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
Goteborg , October 2011
8 Events being planned for 2013.
● Devops is a growing professional and cultural
● We don't 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
● 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 everybody's job.
1986, Out of the Crisis.
Damon Edwards and John Willis
Why ops like to package
● Packages give you features
•Consistency, security, dependencies
● Uniquely identify where files come from
•Package or cfg-mgmt
● Source repo not always available
•Firewall / Cloud etc ..
● Weird deployment locations , no easy access
● Little overhead when you automate
● CONFIG does not belong in a package
fpm in action
● Fork, pull
● Jenkins pulls , builds , pushes to repo
● (variants for Nagios Plugins / Jenkins Plugins
The Marionette Collective
● Distributed ssh ++
● What version of ssh do I have installed on my
● On what servers is XYZ running ?
● Clean al my ssl certs ?
● Restart apache on all servers with fact X
Monitoring is AWESOME. Metrics are AWESOME. I love it. Here's what I don't 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
● Not actually having any real choices
John Vincent (@lusis) on his blog http://lusislog.blogspot.com/2011/06/why-
A sub movement
● #monitoringsucks trending
● 2008 Study :Nagios + Friends
● 2011 Conclusion : Nagios/Icinga are the only
● Monitoring and trending at scale , new kids
Graphite, Icinga, flapjack, etc
● Old Cool Kids, Ganglia
● Not your average centralized logging tool
● Elasticsearch backed
● Collect from anywhere
● Send anywhere
● Queuing support
● Open Source
● Talk about Experiences
● Open Spaces
● Build identical environments
● Share code
● Shared ownership of content , code and
● Abstraction layer for VirtualBox
● Integrates well with Puppet/Chef
● Project =
● Manifests / Cookbooks
● Portable, Small , Versionable
● Use veewee to build your boxen
Vagrant::Config.run 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 vagrantup.com.
config.vm.define :mongo1 do |mongo1_config|
mongo1_config.ssh.max_tries = 100
mongo1_config.vm.box = "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"
config.vm.define :mongo2 do |mongo2_config|
mongo2_config.ssh.max_tries = 100
mongo2_config.vm.box = "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"
● Vagrant init
● Vagrant up
● Vagrant provision
● Vagrant down
● Vagrant destroy