More info at http://blog.carlossanchez.eu/2011/11/15/from-dev-to-devops-slides-from-apachecon-na-vancouver-2011/ The DevOps movement aims to improve communication between developers and operations teams to solve critical issues such as fear of change and risky deployments. But the same way that Agile development would likely fail without continuous integration tools, the DevOps principles need tools to make them real, and provide the automation required to actually be implemented. Most of the so called DevOps tools focus on the operations side, and there should be more than that, the automation must cover the full process, Dev to QA to Ops and be as automated and agile as possible. Tools in each part of the workflow have evolved in their own silos, and with the support of their own target teams. But a true DevOps mentality requires a seamless process from the start of development to the end in production deployments and maintenance, and for a process to be successful there must be tools that take the burden out of humans. Apache Maven has arguably been the most successful tool for development, project standardization and automation introduced in the last years. On the operations side we have open source tools like Puppet or Chef that are becoming increasingly popular to automate infrastructure maintenance and server provisioning. In this presentation we will introduce an end-to-end development-to-production process that will take advantage of Maven and Puppet, each of them at their strong points, and open source tools to automate the handover between them, automating continuous build and deployment, continuous delivery, from source code to any number of application servers managed with Puppet, running either in physical hardware or the cloud, handling new continuous integration builds and releases automatically through several stages and environments such as development, QA, and production.

1. From Dev to DevOps
Carlos Sanchez
@csanchez
http://carlossanchez.eu

2. Apache
@csanchez Maven
Apache
ASF Archiva
Member
Apache
Eclipse IAM Continuum

3. Dev... What?

4. Agile
planning
iterative development
continuous integration
release soon, release often

9. DevQaOps ?

11. DevOps addresses
Fear of change
Risky deployments
It works on my machine!
Siloisation
Dev Change vs. Ops stability

12. Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

13. Our highest priority is to satisfy the customer through early and
continuous delivery of valuable software.
Welcome changing requirements, even late in development.
Agile processes harness change for the customer's competitive
advantage.
Deliver working software frequently, from a couple of weeks
to a couple of months, with a preference to the shorter timescale.
Business people and developers must work together daily
throughout the project.
The most efficient and effective method of conveying information
to and within a development team is face-to-face
conversation.
Agile processes promote sustainable development. The
sponsors, developers, and users should be able to maintain
a constant pace indefinitely.

15. Dev

24. What developers do today to
specify target environments is
NOT enough

26. Ops

27. requirements
Operating System
config files
packages installed
multi stage configurations
dev
QA
pre-production
production

28. Deployment
How do I deploy this?
documentation
manual steps
prone to errors

29. Cloud
How do I deploy this?
to hundreds of servers

30. Infrastructure as Code
Follow development best practices
tagging
branching
releasing
dev, QA, production

31. DevOps

33. Should I worry about my OPS
job?

35. yes

36. yes
my job is to make other
people’s jobs unnecessary

37. yes

38. yes

39. yes no

40. yes no
you should see the NOOPS
guys

41. DevOps is NOT about the tools

42. Nice, BUT
how can I implement IT

43. Nice, BUT
how can I implement IT

44. Tools can enable
change in behavior
and eventually
change culture
Patrick Debois

45. Man is the only animal that
changes environment instead of
adapting

46. Man is the only animal that
changes environment instead of
adapting
(using tools)

47. DevOps tools
everyone thinks is
intelligent enough
every tool thinks it’s cloud
enabled
every tool thinks it’s
DevOps

48. DevOps tools
everyone thinks is
intelligent enough
every tool thinks it’s cloud
enabled
every tool thinks it’s
DevOps

49. DevOps tools: infrastructure automation
infrastructure as code
it’s all invented, now it’s standardized

50. DEVOPS
“MY MACHINES ARE BEING PROVISIONED”

52. Puppet
infrastructure IS code
declarative model
state vs process - no scripting
manifests
ruby
ERB templates
master - agent architecture

53. Puppet file structure
/etc/puppet
manifests/site.pp
manifests/nodes.pp

54. Puppet example
user { 'dave':
ensure => present,
uid => '507',
gid => 'admin',
shell => '/bin/zsh',
home => '/home/dave',
managehome => true,
}
file {'/tmp/test1':
ensure => present,
content => "Hi.",
}

55. Vagrant

56. Vagrant
Oracle VirtualBox cmdline automation
Easy Puppet and Chef provisioning
Keep VM configuration for different projects
Share boxes and configuration files across teams
base box + configuration files

57. Vagrant base boxes
www.vagrantbox.es
anywhere! just (big) files

58. using Vagrant
$ gem install vagrant
$ vagrant box add centos-6.0-x86_64
http://dl.dropbox.com/u/1627760/centos-6.0-x86_64.box
$ vagrant init myproject
$ vagrant up
$ vagrant ssh
$ vagrant suspend
$ vagrant resume
$ vagrant destroy

59. Vagrant
Vagrant::Config.run do |config|
# Every Vagrant virtual environment requires a box to build off of.
config.vm.box = "centos-6.0-x86_64"
# The url from where the 'config.vm.box' box will be fetched
config.vm.box_url = "http://dl.dropbox.com/u/1627760/centos-6.0-x86_64.box"
# Boot with a GUI so you can see the screen. (Default is headless)
#config.vm.boot_mode = :gui
# Assign this VM to a host only network IP, allowing you to access it via the IP.
# config.vm.network "33.33.33.10"
# Forward a port from the guest to the host, which allows for outside
# computers to access the VM, whereas host only networking does not.
config.vm.forward_port "sonar", 9000, 19000
# Enable provisioning with Puppet stand alone.
config.vm.share_folder("templates", "/tmp/vagrant-puppet/templates", "templates")
config.vm.provision :puppet do |puppet|
puppet.manifest_file = "base.pp"
puppet.module_path = "mymodules"
puppet.options = ["--templatedir","/tmp/vagrant-puppet/templates"]
puppet.options = "-v -d"
end
end

60. manifests/base.pp
package { jdk:
ensure => installed,
name => $operatingsystem ? {
centOS => "java-1.6.0-openjdk-devel",
Ubuntu => "openjdk-6-jdk",
default => "jdk",
},
}

61. VeeWee

62. VeeWee
easily build Vagrant base boxes
https://github.com/jedi4ever/veewee

63. using VeeWee
$ gem install veewee
$ vagrant basebox templates
$ vagrant basebox define 'my-ubuntu-server'
'ubuntu-11.04-server-amd64'
# customize definitions/my-ubuntu-server
$ vagrant basebox build 'my-ubuntu-server'
$ vagrant basebox validate 'my-ubuntu-server'
$ vagrant basebox export 'my-ubuntu-server'
$ vagrant box add 'my-ubuntu-server'
'my-ubuntu-server.box'
$ vagrant init 'my-ubuntu-server'

64. Geppetto

65. http://cloudsmith.github.com/geppetto

66. Puppet DSL

67. Puppet resources
user { 'dave':
ensure => present,
uid => '507',
gid => 'admin',
shell => '/bin/zsh',
home => '/home/dave',
managehome => true,
}

68. Puppet resources
$ puppet resource user root
user { 'root':
home => '/var/root',
shell => '/bin/sh',
uid => '0',
ensure => 'present',
password => '*',
gid => '0',
comment => 'System Administrator'
}

69. Puppet resources
$ puppet resource user dave
ensure=present shell="/bin/zsh" home="/
home/dave" managehome=true
notice: /User[dave]/ensure: created
user { 'dave':
ensure => 'present',
home => '/home/dave',
shell => '/bin/zsh'
}

70. Puppet resources
file {'testfile':
path => '/tmp/testfile',
ensure => present,
mode => 0640,
content => "I'm a test file.",
}
notify {"I'm notifying you.":}

71. Puppet standalone
$ puppet apply my_test_manifest.pp

72. ordering
file {'/tmp/test1':
ensure => present,
content => "Hi.",
}
notify {'/tmp/test1 has already
been synced.':
require => File['/tmp/test1'],
}

73. ordering
file {'/tmp/test1':
ensure => present,
content => "Hi.",
} ->
notify {'/tmp/test1 has already
been synced.':}

74. package / file /service / subscribe
package { 'openssh-server':
ensure => present,
before => File['/etc/ssh/sshd_config'],
}
file { '/etc/ssh/sshd_config':
ensure => file,
mode => 600,
source => '/root/learning-manifests/sshd_config',
}
service { 'sshd':
ensure => running,
enable => true,
hasrestart => true,
hasstatus => true,
subscribe => File['/etc/ssh/sshd_config'],
}

75. variables
$longthing = "Imagine I have something really
long in here. Like an SSH key, let's say."
file {'authorized_keys':
path => '/root/.ssh/authorized_keys',
content => $longthing,
}

76. facts
host {'self':
ensure => present,
name => $::fqdn,
host_aliases => ['puppet', $::hostname],
ip => $::ipaddress,
}
file {'motd':
ensure => file,
path => '/etc/motd',
mode => 0644,
content => "Welcome to ${::hostname},na $
{::operatingsystem} island in the sea of ${::domain}.
n",
}

77. conditionals
if $is_virtual {
service {'ntpd':
ensure => stopped,
enable => false,
}
}
else {
service { 'ntpd':
name => 'ntpd',
ensure => running,
enable => true,
hasrestart => true,
require => Package['ntp'],
}
}

78. conditionals
case $operatingsystem {
centos, redhat: { $apache = "httpd" }
debian, ubuntu: { $apache = "apache2" }
default: { fail("Unrecognized operating system for
webserver") }
}
$apache = $operatingsystem ? {
centos => 'httpd',
redhat => 'httpd',
/(?i)(ubuntu|debian)/ => "apache2-$1",
# (Don't actually use that package name.)
default => undef,
}

79. class definition
class ntp {
package { 'ntp':
ensure => installed,
}
service { 'ntp':
name => 'ntpd',
ensure => running,
enable => true,
subscribe => File['ntp.conf'],
}
}

80. class declaration (1)
class {'ntp': }

81. class declaration (2)
include ntp

82. parameterized classes
class paramclassexample ($value1, $value2 = "Default
value") {
notify {"Value 1 is ${value1}.":}
notify {"Value 2 is ${value2}.":}
}
class {'paramclassexample':
value1 => 'Something',
value2 => 'Something else',
}
class {'paramclassexample':
value1 => 'Something',
}

83. modules
{module}/
files/
lib/
manifests/
init.pp
{class}.pp
{defined type}.pp
{namespace}/
{class}.pp
{class}.pp
templates/
tests/

84. templating
file {'/etc/foo.conf':
ensure => file,
require => Package['foo'],
content => template('foo/foo.conf.erb'),
}

85. templates/foo.conf.erb
OS is <%= $::operatingsystem %>

86. node configuration
# nodes.pp
node 'someserver.domain.com' inherits basenode {
$web_fqdn = 'www.domain.com'
include genericwebserver
include some_other_service
}
node 'ldapmaster.domain.com' inherits basenode {
include s_ldap::master
}
node 'humanresources.domain.com' inherits basenode {
include c_humanresources
}

87. Maven and Puppet

88. What am I doing to automate deployment
Ant tasks plugin
ssh commands
Assembly plugin
Cargo

89. What can I do to automate deployment
Handle full deployment including infrastructure
not just webapp deployment
Help Ops with clear, automated manifests
Ability to reproduce production environments
in local box using Vagrant / VirtualBox / VMWare
Use the right tool for the right job

90. Maven-Puppet module
A Maven Puppet module
https://github.com/maestrodev/puppet-maven
fetches Maven artifacts from the repo
manages them with Puppet
no more extra packaging

91. Requirements
Java JDK
Maven

92. Installing Maven
$repo1 = {
id => "myrepo",
username => "myuser",
password => "mypassword",
url => "http://repo.acme.com",
}
# Install Maven
class { "maven::maven":
version => "2.2.1",
} ->
# Create a settings.xml with the repo credentials
class { "maven::settings" :
servers => [$repo1],
}

93. New Maven type
maven { "/tmp/maven-core-2.2.1.jar":
id => "org.apache.maven:maven-core:jar:2.2.1",
repos => ["http://repo1.maven.apache.org/maven2",
"http://mirrors.ibiblio.org/pub/mirrors/maven2"],
}

94. New Maven type
maven { "/tmp/maven-core-2.2.1.jar":
groupId => "org.apache.maven",
artifactId => "maven-core",
version => "2.2.1",
packaging => "jar",
repos => ["http://repo1.maven.apache.org/maven2",
"http://mirrors.ibiblio.org/pub/mirrors/maven2"],
}

95. Example code
Available at
http://github.carlossanchez.eu
http://blog.carlossanchez.eu
https://github.com/maestrodev/puppet-modules

96. Thanks!
http://maestrodev.com
http://carlossanchez.eu
csanchez@maestrodev.com
carlos@apache.org
@csanchez

97. Photo Credits
Son of Man Lego - Alex Eylar
http://www.flickr.com/photos/hoyvinmayvin/4702772452/
Brick wall - Luis Argerich
http://www.flickr.com/photos/lrargerich/4353397797/
Agile vs. Iterative flow - Christopher Little
http://en.wikipedia.org/wiki/File:Agile-vs-iterative-flow.jpg
DevOps - Rajiv.Pant
http://en.wikipedia.org/wiki/File:Devops.png
Pimientos de Padron - Howard Walfish
http://www.flickr.com/photos/h-bomb/4868400647/
Compiling - XKCD
http://xkcd.com/303/
Printer in 1568 - Meggs, Philip B
http://en.wikipedia.org/wiki/File:Printer_in_1568-ce.png
Relativity - M. C. Escher
http://en.wikipedia.org/wiki/File:Escher%27s_Relativity.jpg