![Puppet
exec { "maven-untar":
manifests command => "tar xf /tmp/x.tgz",
cwd => "/opt",
creates => "/opt/apache-maven-${version}",
ruby-like path => ["/bin"],
} ->
ERB templates file { "/usr/bin/mvn":
ensure => link,
target => "/opt/apache-maven-${version}/bin/mvn",
}
file { "/usr/local/bin/mvn":
ensure => absent,
require => Exec["maven-untar"],
}
file { "$home/.mavenrc":
mode => "0600",
owner => $user,
content => template("maven/mavenrc.erb"),
require => User[$user],
}](https://image.slidesharecdn.com/2012-02fromdevtodevops-fosdem-120205081327-phpapp01/75/From-Dev-to-DevOps-FOSDEM-2012-47-2048.jpg)
![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](https://image.slidesharecdn.com/2012-02fromdevtodevops-fosdem-120205081327-phpapp01/75/From-Dev-to-DevOps-FOSDEM-2012-57-2048.jpg)
![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],
}](https://image.slidesharecdn.com/2012-02fromdevtodevops-fosdem-120205081327-phpapp01/75/From-Dev-to-DevOps-FOSDEM-2012-68-2048.jpg)
![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"],
}](https://image.slidesharecdn.com/2012-02fromdevtodevops-fosdem-120205081327-phpapp01/75/From-Dev-to-DevOps-FOSDEM-2012-69-2048.jpg)
![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"],
}](https://image.slidesharecdn.com/2012-02fromdevtodevops-fosdem-120205081327-phpapp01/75/From-Dev-to-DevOps-FOSDEM-2012-70-2048.jpg)
![ordering
file {'/tmp/test1':
ensure => present,
content => "Hi.",
}
notify {'/tmp/test1 has already
been synced.':
require => File['/tmp/test1'],
}](https://image.slidesharecdn.com/2012-02fromdevtodevops-fosdem-120205081327-phpapp01/75/From-Dev-to-DevOps-FOSDEM-2012-76-2048.jpg)
![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'],
}](https://image.slidesharecdn.com/2012-02fromdevtodevops-fosdem-120205081327-phpapp01/75/From-Dev-to-DevOps-FOSDEM-2012-78-2048.jpg)
![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",
}](https://image.slidesharecdn.com/2012-02fromdevtodevops-fosdem-120205081327-phpapp01/75/From-Dev-to-DevOps-FOSDEM-2012-80-2048.jpg)
![conditionals
if $is_virtual {
service {'ntpd':
ensure => stopped,
enable => false,
}
}
else {
service { 'ntpd':
name => 'ntpd',
ensure => running,
enable => true,
hasrestart => true,
require => Package['ntp'],
}
}](https://image.slidesharecdn.com/2012-02fromdevtodevops-fosdem-120205081327-phpapp01/75/From-Dev-to-DevOps-FOSDEM-2012-81-2048.jpg)
![class definition
class ntp {
package { 'ntp':
ensure => installed,
}
service { 'ntp':
name => 'ntpd',
ensure => running,
enable => true,
subscribe => File['ntp.conf'],
}
}](https://image.slidesharecdn.com/2012-02fromdevtodevops-fosdem-120205081327-phpapp01/75/From-Dev-to-DevOps-FOSDEM-2012-83-2048.jpg)
![templating
file {'/etc/foo.conf':
ensure => file,
require => Package['foo'],
content => template('foo/foo.conf.erb'),
}](https://image.slidesharecdn.com/2012-02fromdevtodevops-fosdem-120205081327-phpapp01/75/From-Dev-to-DevOps-FOSDEM-2012-88-2048.jpg)
Uploaded byCarlos Sanchez
From Dev to DevOps - FOSDEM 2012
The document discusses the transition from traditional development to DevOps, focusing on agile methodologies and continuous integration. It emphasizes the importance of collaboration between developers and operations teams, as well as the use of tools like Puppet and Vagrant for infrastructure as code and deployment automation. Additionally, it highlights the need for flexibility in responding to changing requirements and the adoption of best practices in deployment processes.
More Related Content
Similar to From Dev to DevOps - FOSDEM 2012
From Dev to DevOps - FOSDEM 2012
- 1. From Dev toDevOps Carlos Sanchez @csanchez http://carlossanchez.eu http://maestrodev.com
- 2. Apache @csanchez Maven Apache ASF Archiva Member Apache Eclipse IAM Continuum blog.carlossanchez.eu
- 3.
- 4. Agile planning iterative development continuous integration release soon, release often
- 9.
- 11. DevOps addresses Fear of change Risky deployments It works on my machine! Siloisation Dev Change vs. Ops stability
- 12. Individuals and interactionsover processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
- 13. Our highest priorityis 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.
- 21. What developers dotoday to specify target environments is NOT enough
- 23.
- 24. requirements Operating System config files packagesinstalled multi stage configurations dev QA pre-production production
- 25. Deployment How do Ideploy this? documentation manual steps prone to errors
- 26. Cloud How do Ideploy this? to hundreds of servers
- 27. Infrastructure as Code Newsolutions bring new challenges Follow development best practices tagging branching releasing dev, QA, production
- 28.
- 30. Should I worryabout my OPS job?
- 32.
- 33. yes my jobis to make other people’s jobs unnecessary
- 34.
- 35.
- 36.
- 37. yes no you shouldsee the NOOPS guys
- 38. DevOps is NOTabout the tools
- 39. Nice, BUT how canI implement IT
- 40. Nice, BUT how canI implement IT
- 41. Tools can enable changein behavior and eventually change culture Patrick Debois
- 42. DevOps tools everyone isintelligent enough every tool is cloud enabled every tool is DevOps(tm)
- 43. DevOps tools everyone isintelligent enough every tool is cloud enabled every tool is DevOps(tm)
- 44. DevOps tools: infrastructureautomation infrastructure as code it’s all invented, now it’s standardized
- 45. New solutions bringnew problems DEVOPS “MY MACHINES ARE BEING PROVISIONED”
- 47. Puppet exec { "maven-untar": manifests command => "tar xf /tmp/x.tgz", cwd => "/opt", creates => "/opt/apache-maven-${version}", ruby-like path => ["/bin"], } -> ERB templates file { "/usr/bin/mvn": ensure => link, target => "/opt/apache-maven-${version}/bin/mvn", } file { "/usr/local/bin/mvn": ensure => absent, require => Exec["maven-untar"], } file { "$home/.mavenrc": mode => "0600", owner => $user, content => template("maven/mavenrc.erb"), require => User[$user], }
- 48. Puppet infrastructure IS code package { 'openssh-server': ensure => present, }
- 49. Puppet declarative model state vsprocess no scripting service { 'ntp': name => 'ntpd', ensure => running, }
- 50.
- 51. Puppet file structure /etc/puppet manifests/site.pp manifests/nodes.pp
- 52. 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.", }
- 53.
- 54. 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
- 55. Vagrant base boxes www.vagrantbox.es anywhere! just (big) files
- 56. using Vagrant $ geminstall 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
- 57. 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
- 58. manifests/base.pp package { jdk: ensure => installed, name => $operatingsystem ? { centOS => "java-1.6.0-openjdk-devel", Ubuntu => "openjdk-6-jdk", default => "jdk", }, }
- 59.
- 60. VeeWee easily build Vagrant base boxes https://github.com/jedi4ever/veewee
- 61. using VeeWee $ geminstall 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'
- 62.
- 63.
- 64.
- 65. What am Idoing to automate deployment Ant tasks plugin ssh commands Assembly plugin Cargo Capistrano
- 66. What can Ido 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
- 67. 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
- 68. 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], }
- 69. 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"], }
- 70. 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"], }
- 71.
- 72. Puppet resources user {'dave': ensure => present, uid => '507', gid => 'admin', shell => '/bin/zsh', home => '/home/dave', managehome => true, }
- 73. Puppet resources $puppet resource user root user { 'root': home => '/var/root', shell => '/bin/sh', uid => '0', ensure => 'present', password => '*', gid => '0', comment => 'System Administrator' }
- 74. Puppet resources file {'testfile': path => '/tmp/testfile', ensure => present, mode => 0640, content => "I'm a test file.", } notify {"I'm notifying you.":}
- 75. Puppet standalone $ puppetapply my_test_manifest.pp
- 76. ordering file {'/tmp/test1': ensure => present, content => "Hi.", } notify {'/tmp/test1 has already been synced.': require => File['/tmp/test1'], }
- 77. ordering file {'/tmp/test1': ensure => present, content => "Hi.", } -> notify {'/tmp/test1 has already been synced.':}
- 78. 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'], }
- 79. variables $longthing = "ImagineI have something really long in here. Like an SSH key, let's say." file {'authorized_keys': path => '/root/.ssh/authorized_keys', content => $longthing, }
- 80. 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", }
- 81. conditionals if $is_virtual { service {'ntpd': ensure => stopped, enable => false, } } else { service { 'ntpd': name => 'ntpd', ensure => running, enable => true, hasrestart => true, require => Package['ntp'], } }
- 82. 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, }
- 83. class definition class ntp{ package { 'ntp': ensure => installed, } service { 'ntp': name => 'ntpd', ensure => running, enable => true, subscribe => File['ntp.conf'], } }
- 84. class declaration (1) class{'ntp': }
- 85.
- 86. 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', }
- 87. modules {module}/ files/ lib/ manifests/ init.pp {class}.pp {defined type}.pp {namespace}/ {class}.pp {class}.pp templates/ tests/
- 88. templating file {'/etc/foo.conf': ensure => file, require => Package['foo'], content => template('foo/foo.conf.erb'), }
- 89. templates/foo.conf.erb OS is <%=$::operatingsystem %>
- 90. 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 }
- 91. Example code andslides Available at http://slideshare.carlossanchez.eu http://github.carlossanchez.eu http://blog.carlossanchez.eu https://github.com/maestrodev/puppet-modules
- 92.
- 93. 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 Teacher and class - Herald Post http://www.flickr.com/photos/heraldpost/5169295832/
Editor's Notes
- #2 \n
- #3 question? #developers vs #ops vs #devops\n
- #4 \n
- #5 \n
- #6 \n
- #7 \n
- #8 \n
- #9 \n
- #10 \n
- #11 \n
- #12 \n
- #13 \n
- #14 \n
- #15 \n
- #16 \n
- #17 \n
- #18 \n
- #19 \n
- #20 \n
- #21 \n
- #22 \n
- #23 \n
- #24 \n
- #25 \n
- #26 \n
- #27 \n
- #28 \n
- #29 \n
- #30 \n
- #31 \n
- #32 \n
- #33 question? what do you do to specify ops requirements?\n
- #34 \n
- #35 question? what do you do to specify ops requirements?\n
- #36 \n
- #37 \n
- #38 \n
- #39 \n
- #40 question? who&#x2019;s able to roll back to a previous version of software? and system?\n
- #41 \n
- #42 \n
- #43 \n
- #44 \n
- #45 \n
- #46 \n
- #47 \n
- #48 \n
- #49 \n
- #50 \n
- #51 \n
- #52 \n
- #53 \n
- #54 \n
- #55 \n
- #56 \n
- #57 \n
- #58 \n
- #59 \n
- #60 \n
- #61 \n
- #62 \n
- #63 \n
- #64 \n
- #65 \n
- #66 \n
- #67 \n
- #68 \n
- #69 \n
- #70 \n
- #71 \n
- #72 \n
- #73 \n
- #74 \n
- #75 \n
- #76 \n
- #77 \n
- #78 \n
- #79 \n
- #80 \n
- #81 \n
- #82 \n
- #83 \n
- #84 \n
- #85 \n
- #86 \n
- #87 \n
- #88 \n
- #89 \n
- #90 \n
- #91 \n
- #92 \n
- #93 \n
- #94 \n
- #95 \n
- #96 \n
- #97 \n
- #98 \n
- #99 \n
- #100 \n
- #101 \n
- #102 \n
- #103 \n
- #104 \n
- #105 \n
- #106 \n
- #107 \n