1. Johann-Peter Hartmann / Mayflower GmbH
Practical DevOps for
Developers

2. Hi!

3. Nice to meet You!

4. I am Johann.

5. Who are You?

6. Developers?
Ops?
Anything else?

7. Developers:
PHP?
Python?
Ruby?
Java?
Anything else?

8. What do you expect to hear today?
(if you got a good explanation
i‘ll leave out the motivation slides)

9. Motivation
or
Why it‘s more fun to do DevOps as a Dev right now.

10. Hype!
Googles CIO Ben Fried 11
days ago:
„Cult Of DevOps“

11. Actually:
Because we need it.

12. Development in the dark
ages ...

13. Golden Image
VMware /KVM

17. It wasn‘t reliable anymore.

18. And our applications changed

19. Browser
Apache with PHP MySQL

20. Browser
Hip
Apache with PHP MySQL NoSQL
Server

21. Browser
Apache with PHP MySQL
Hip
Memcache
NoSQL
Performance FTW!
Server

22. Browser
Hip
Apache with PHP MySQL NoSQL
Server
Memcache, oops,
Gearman
Redis now

23. Browser
Hip
Apache with PHP MySQL NoSQL
Server
Memcache, oops, Gearman, ahum,
eJabberD
Redis now ActiveMQ

24. Browser
Hip
Apache with Apache with
MySQL NoSQL
PHP PHP
Server
Memcache, Memcache, Gearman,
oops, oops, ahum, eJabberD
Redis now Redis now ActiveMQ

25. Browser
Hip
Apache with Apache with
MySQL NoSQL
PHP PHP
Server
Memcache, Memcache, Gearman,
oops, oops, ahum, eJabberD
Redis now Redis now ActiveMQ

26. Apa Apa MyS Hip Apa Apa MyS Hip
Me Me Gea eJa
Me Me Gea eJa
Development Continuous Integration
Apa Apa Apa Apa MyS MyS Hip Hip
Me Me Me Me Gea Gea eJa eJa
Production

27. Version X+2 Version X+1
Development Continuous Integration
Version X
Production

28. New! With Redis! Not so new with Memcached
Version X+2 Version X+1
Development Continuous Integration
Still without proper Caching :-(
Version X
Production

30. 10th Floor
Test
http://www.flickr.com/photos/75905404@N00/

31. Collection of Fails
Failsafety
Simplicity
Fast Setup Time
Repeatability Self-Service
Consistency
Version Management
http://www.flickr.com/photos/turtlemom_nancy/

32. ?

34. DevOps for Devs in
3 (actually not so easy) steps

35. 1. Manage your Dev-Setup
with Vagrant and VeeWee
(Install VirtualBox and Ruby first)

36. Vagrant
Virtualbox based
automatic creation
and management of
VMs based on
Puppet / Chef

37. Better use rvm, see http://www.jedi.be/blog/2011/03/28/
using-vagrant-as-a-team/
~# gem install vagrant
~# gem install veewee
~# vagrant basebox templates
vagrant basebox define '<boxname>' 'archlinux-i386'
... (40 baseboxes)
vagrant basebox define '<boxname>' 'windows-2008R2-amd64'
~# vagrant basebox define 'natty' 'ubuntu-11.04-server-
amd64'
~# vagrant basebox build 'natty'
~# vagrant basebox export natty
~# vagrant box add 'natty' 'natty.box'

38. http://vagrantbox.es

39. ~# vagrant init 'natty'
~# vagrant up
~# vagrant ssh
Welcome to Ubuntu 11.04 (GNU/Linux 2.6.38-8-server x86_64)
* Documentation: http://www.ubuntu.com/server/doc
vagrant@natty:~$

40. ~# vagrant
Tasks:
vagrant basebox # Commands to manage baseboxes
vagrant box # Commands to manage system boxes
vagrant destroy # Destroy the environment, deleting the created virtual
machines
vagrant halt # Halt the running VMs in the environment
vagrant help [TASK] # Describe available tasks or one specific task
vagrant init [box_name] [box_url] # Initializes the current folder for
Vagrant usage
vagrant package # Package a Vagrant environment for distribution
vagrant provision # Rerun the provisioning scripts on a running VM
vagrant reload # Reload the environment, halting it then restarting
it.
vagrant resume # Resume a suspended Vagrant environment.
vagrant ssh # SSH into the currently running Vagrant environment.
vagrant ssh_config # outputs .ssh/config valid syntax for connecting to
this environment via ssh
vagrant status # Shows the status of the current Vagrant environment.
vagrant suspend # Suspend a running Vagrant environment.
vagrant up # Creates the Vagrant environment
vagrant version # Prints the Vagrant version information

41. 2. Manage your configuration

43. Similarities

44. • Configuration as (Ruby-)Code
• Client-only or Client-server Setup
• there is a series-b funded company in the background
• both are officially supported by amazon
• there are a lot of BIG customers using the tool
• good documentation
• good, vibrant communities

45. • both know the current configuration (ohai and facter)
• You define your nodes (Servers)
• using a lot of pre-existing resources
• and a lot of default community-built cookbooks / modules
• it‘s easy to extend using ruby
• use configuration file templates
• use providers as platform abstractions (for packaging, ...)

46. • Chef is actually Ruby, Puppet provides a DSL
• puppet has the bigger community
• puppet has more documentation
• but chef is growing fast in both regards
• puppet = europe, chef = usa
• chef is more flexible because of native ruby
• chef is more flexible because of clever data structures

47. There is no „better“ tool.

48. There is no „better“ tool.
But we prefer Puppet. Less Ruby :-)

49. user { 'johann':
ensure => present,
uid => '507',
gid => 'admin',
shell => '/bin/bash',
home => '/home/johann',
managehome => true,
}

50. user "johann" do
username "johann"
password "$1$P$WXmqrQEVj88fVTHevErxq."
shell "/bin/bash"
system true
supports :manage_home => true
end

51. Back to your setup ...

52. Vagrant::Config.run do |config|
config.vm.box = "natty"
end

53. ~# cat Vagrantfile
Vagrant::Config.run do |config|
config.vm.provision :puppet, :module_path => "modules" do
|puppet|
puppet.manifests_path = "manifests"
puppet.manifest_file = "development.pp"
end
config.vm.define :web do |web_config|
web_config.vm.box = "natty"
web_config.vm.host_name = "webserver01"
# web_config.vm.boot_mode = :gui
web_config.vm.network "33.33.33.10"
web_config.vm.forward_port "http", 80, 8080
web_config.vm.forward_port "ssh", 22, 20022
web_config.vm.share_folder "v-data", "/srv/www", "../
silex-demo"
end
end

54. ~# cat manifests/development.pp
import "classes/*"
node "webserver01" {
include web
}
node "dbserver01" {
include db
}
node "ciserver01" {
include ci
}

55. ~# cat manifests/classes/web.pp
class web inherits basenode {
include apache
include apache::php
apache::vhost { 'silex-demo.local':
port => '80',
docroot => '/srv/www/docroot',
}
package { ["mysql-client", "php5-cli", "phpunit", "php5-
curl", "php5-dev", "php5-gd", "php5-imagick", "php5-mcrypt",
"php5-mysql", "php5-xdebug","php5-suhosin", "php-pear",
"php-codesniffer" ]:
ensure => present,
}
}

56. ~# cat manifests/classes/ci.pp
class ci inherits basenode {
include apache
include apache::php
exec { "pear_autodiscover":
command => "/usr/bin/pear config-set auto_discover 1",
}
package { ["pear.phpunit.de/PHP_CodeBrowser",
"pear.phpunit.de/PHPUnit_MockObject", "pear.phpunit.de/
PHPUnit_Selenium", "pear.phpunit.de/PHP_CodeCoverage",
"pear.phpunit.de/PHP_Timer", "pear.phpunit.de/phpcpd",
"pear.phpunit.de/phploc"]:
ensure => latest,
provider => "pear",
require => Exec["pear_autodiscover"]
}
}

57. 3. Make the configuration
part of your sourcecode

58. • application
• data
• docs
• library
• public
• scripts
• jobs
• build
• configuration
• VagrantFile
• manifests
• modules
• temp

59. Ok, that was a lot of work.
Why did i do that again?

60. Collection of Wins
Failsafety
Simplicity
Fast Setup Time
Repeatability Self-Service
Consistency
Version Management
http://www.flickr.com/photos/turtlemom_nancy/

61. There is no golden Image
anymore

62. There is just one directory in
your source ...

63. „vagrant up“
„vagrant provision“

64. Even more vagrant fun ...

65. Fail Safety with Vagrant-Snap
vagrant snap take -d “snap1“
vagrant snap list
vagrant snap go “snap1“

66. What if i need to
simulate 20

67. McCloud
Wrapper likeVagrant around Fog
Transparent local & cloud usage
Supports EC2, OpenStack, KVM, etc

68. What if i need to
simulate 2000
machines?

69. mCollective
dssh/ssh-for-loop on steroids
fast management for loads of servers
uses puppet/facter or chef/ohai, MQ-
based

70. $ mc-package -W "architecture=x86" status apache
* [ ============================================================> ] 10 / 10
host01.example.com version = apache-2.2.9-7
host02.example.com version = apache-2.2.9-7
host03.example.com version = apache-2.2.9-7
host04.example.com version = apache-2.2.9-7
host05.example.com version = apache-2.2.9-7
host06.example.com version = apache-2.2.9-7
host07.example.com version = apache-2.2.9-7
host08.example.com version = apache-2.2.9-7
host09.example.com version = apache-2.2.9-7
host10.example.com version = apache-2.2.9-7
---- package agent summary ----
Nodes: 10 / 10
Versions: 10 * 0.25.5-1.el5
Elapsed Time: 1.03 s

71. The Foreman - Machine Life Cycle
Management
Acts as a web front end for Puppet
Shows You the system inventory
Creates new machines and takes care
of provisioning

72. Knowing everything about your
server configuration is great!

73. Create new servers

74. Your (possible)
Todolist

75. 1. Install Vagrant,
Veewee etc

76. 2. Add an
configuration
folder to your

77. 3. Configure Your
Vagrant images
using chef or
puppet

78. 4. Setup a chef-
or puppet-server
using this
configuration

79. 5. Move your CI,
Staging and
Production-Setup
to chef/puppet,
too

81. 6. Create a self-
service-plattform
for the
development team

83. More cool stuff
you can do:

84. Test-Driven
infrastructure
using chef/
puppet-cucumber

85. Automated
monitoring using
nagios or munin

86. Automated
reporting using
graphite

87. Thanks!
Johann-Peter Hartmann
johann__ @ freenode I hope you enjoyed it!
Mail / Jabber:
johann-peter.hartmann@mayflower.de
Further reading:
http://www.planetdevops.net
http://dzone.com
http://twitter.com/#!/DEVOPS_BORAT
http://github.com/johannhartmann/

88. Vegetable Test Driven
Infrastructure
Kontinuierliche Entiwcklung - und dann? I Mayflower GmbH I 28. Oktober 2010 I 87

89. actually a behavior driven design tool
used for test driven infrastructure
cucumber-puppet
chef-cucumber

90. Feature: Manualsearch
In order to find an article
As an developer
I want to use the search function
Scenario: Search for bdd and check resulting page
Given I go to "http://it-republik.de/php/"
When I fill in "search_itr" with "bdd"
And I click "search2"
Then I should see "Suche"

91. Given /^I go to "([^"]*)"$/ do |url|
visit url
end
When /^I fill in "([^"]*)" with "([^"]*)"$/ do |field, value|
fill_in field, :with => value
end
When /^I click "([^"]*)"$/ do |button|
click_button(button)
end
Then /^I should see "([^"]*)"$/ do |text|
response_body.should include(text)
end

92. johann$ cucumber
Feature: Manualsearch
In order to find an article
As an developer
I want to use the search function
Scenario: Search for bdd and check resulting page # features/
search.feature:5
Given I go to "http://it-republik.de/php/" # features/
step_definitions/search_steps.rb:1
When I fill in "search_itr" with "bdd" # features/
step_definitions/search_steps.rb:5
And I click "search2" # features/
step_definitions/search_steps.rb:9
Then I should see "Suche" # features/
step_definitions/search_steps.rb:13
1 scenario (1 passed)
4 steps (4 passed)
0m1.615s

93. Feature: Install inetd
In order to serve the web
the httpd service
must be installed
Scenario: Setup httpd
Given a node of class “web“
When I compile the catalog
Then package “httpd“ should be “installed“
Then there should be a resource “Service[httpd]“
And the service should have “enable“ set to “true“
And State should be “running“
And the service should require “Package[httpd]“
Kontinuierliche Entiwcklung - und dann? I Mayflower GmbH I 28. Oktober 2010 I 92

95. Hey, i understand
Operations - and i‘m
working in marketing

96. Unit Tests
Acceptance Tests
Metrics
Coding Style
... you get the
idea.

97. ... and even
more ...
Packaging
Infrastructure
Updates
Releases
Deployment

100. Wetware
Refactoring

101. Work together

102. Own together

103. Eat together
http://www.flickr.com/photos/vilavelosa/
3815032524/

104. Plan
together
Kontinuierliche Entiwcklung - und dann? I Mayflower GmbH I 28. Oktober 2010 I 103

105. Mayflower
DevOpsification

106. Wetware - Mayflower
1-2 Ops per team
• Admin & Development tasks
• full time working within the
team

107. Wetware - Mayflower
Close cooperation with central operations
Full root access for any development-infrastructre

108. Wetware - Mayflower
1+n Puppet-Master
• central company master
• Team puppet master per team / project
• company master is starting point for the project
puppet configuration

109. Wetware - Mayflower
Example Setup:
• local Developer VM
• CI-Deployment-Server in the DMZ
• Staging in the private Cloud
• Beta happens in the Amazon-Cloud
• Production in AWS, too

110. Wetware - Mayflower
local GIT- / Gitorious-Server
Eucalyptus-Cloud in the DMZ
- as Self-Service!

111. Wetware - Mayflower
Vagrant for Development
Scrum => KanBan
Puppet Nagios