Why we are migrating to Chef from Puppet
Download as PPTX, PDF2 likes1,237 views
This document discusses the author's experience using Puppet and their reasons for switching to Chef. It notes that they started using Puppet in 2012 when it was more popular than Chef. While Puppet worked well initially, they found it inflexible to apply partial manifests or forget dependencies. In contrast, Chef allowed ordering resources intuitively and using Ruby syntax which they were learning to write recipes. The overall message is that Chef enabled them to "Stay Creative" and "Live Comfortably" in their work.
![$ knife solo cook -o recipe[hdeone]
srv1.example.com
knife-solo make it possible to test
recipes speedy and easily
You also can assemble recipes by
Role
(cook –o role[base])](https://image.slidesharecdn.com/why-we-are-migrating-to-chef-from-puppet-141125003026-conversion-gate01/85/Why-we-are-migrating-to-Chef-from-Puppet-8-320.jpg)
![Puppet
package { 'ganglia-gmond':
ensure => latest,
}
service { 'gmond':
ensure => running,
enable => true,
hasstatus => true,
hasrestart => true,
require => Package['ganglia-gmond'],
}
file { '/etc/ganglia/gmond.conf':
ensure => file,
content => template(“path/to/gmond.conf.erb”),
require => Package['ganglia-gmond'],
notify => Service['gmond'],
}
and we often forget to specify…
Chef
package 'ganglia-gmond'
template '/etc/ganglia/gmond.conf' do
notifies :restart, 'service[gmond]'
end
Just recognized by order
service 'gmond' do
supports :status => true, :restart => true, :reload => true
action [:start, :enable]
end](https://image.slidesharecdn.com/why-we-are-migrating-to-chef-from-puppet-141125003026-conversion-gate01/85/Why-we-are-migrating-to-Chef-from-Puppet-9-320.jpg)
![ephemerals = node['ec2'].select { |k, _|
k.start_with?('block_device_mapping_ephemeral')
} .map { |k, v| [k.split('_').last, "/dev/#{v}"] }
ephemerals.each { |name, device_path|
execute 'mkfs' do
command "mkfs -t #{node['ec2']['ephemeral']['fstype']}
#{device_path}"
not_if "grep -qs #{device_path} /proc/mounts"
end
mount_point = "/media/#{name}"
directory mount_point # create mount point
mount mount_point do
device device_path
fstype node['ec2']['ephemeral']['fstype']
action [:mount, :enable]
end
}
%w(main.cf master.cf).each do |conf|
template "/etc/postfix/#{conf}" do
notifies :restart, 'service[postfix]'
end
end
We are learning Ruby syntax
when writing recipes](https://image.slidesharecdn.com/why-we-are-migrating-to-chef-from-puppet-141125003026-conversion-gate01/85/Why-we-are-migrating-to-Chef-from-Puppet-10-320.jpg)
Ad
More Related Content
Viewers also liked (15)
Similar to Why we are migrating to Chef from Puppet (20)
Ad
Recently uploaded (20)
Ad
Why we are migrating to Chef from Puppet
- 1. Chef Puppet HDE, Inc. SEG dept. Yuu Yamanaka
- 2. Yuu Yamanaka An engineer of SEG dept. DevOps unit (6 years career in HDE)
- 3. Chef Puppet Before explaining that,
- 4. Puppet
- 5. We have started to use Puppet from 2012/04 At the time, Chef was not popular and proven than Puppet We were not Rubyist but Pythonista (Of course, both Puppet and Chef are made by Ruby)
- 6. Can not apply a part of manifests to a node Have to write all dependencies for each resources Own and wordy syntax Puppet But some points stressed us…
- 8. $ knife solo cook -o recipe[hdeone] srv1.example.com knife-solo make it possible to test recipes speedy and easily You also can assemble recipes by Role (cook –o role[base])
- 9. Puppet package { 'ganglia-gmond': ensure => latest, } service { 'gmond': ensure => running, enable => true, hasstatus => true, hasrestart => true, require => Package['ganglia-gmond'], } file { '/etc/ganglia/gmond.conf': ensure => file, content => template(“path/to/gmond.conf.erb”), require => Package['ganglia-gmond'], notify => Service['gmond'], } and we often forget to specify… Chef package 'ganglia-gmond' template '/etc/ganglia/gmond.conf' do notifies :restart, 'service[gmond]' end Just recognized by order service 'gmond' do supports :status => true, :restart => true, :reload => true action [:start, :enable] end
- 10. ephemerals = node['ec2'].select { |k, _| k.start_with?('block_device_mapping_ephemeral') } .map { |k, v| [k.split('_').last, "/dev/#{v}"] } ephemerals.each { |name, device_path| execute 'mkfs' do command "mkfs -t #{node['ec2']['ephemeral']['fstype']} #{device_path}" not_if "grep -qs #{device_path} /proc/mounts" end mount_point = "/media/#{name}" directory mount_point # create mount point mount mount_point do device device_path fstype node['ec2']['ephemeral']['fstype'] action [:mount, :enable] end } %w(main.cf master.cf).each do |conf| template "/etc/postfix/#{conf}" do notifies :restart, 'service[postfix]' end end We are learning Ruby syntax when writing recipes
- 13. It is a simple reason. We would like to use a better tool. Chef Puppet
- 14. Stay Creative Live Comfortably (from DevOps Unit's creed) END
Editor's Notes
- #2: Hi. How is everyone? Since there is 10 minutes break after this, please give your five minutes to me.
- #3: And, hello again! As you know, my name is Yuu Yamanaka. I’m in DevOps unit of SEG dept.
- #4: I’ll speak about Why – However before explaining that,
- #5: I’ll speak Why did
- #6: For the first, we have started to use Puppet from 2012/04, This is the image which is created by me when introduce Puppet to the SEG members Of course, both Puppet …. But I thought Chef is for Rubyist
- #7: Puppet was convenient, But some points stressed us 1st, we can’t apply a part of manifests to remote with Puppet It means we have to apply all manifests to a node, it takes long time 2nd we have to …, I’ll explain it later 3rd Puppet has own and wordy syntax
- #9: Chef can apply partal recipes to nodes by Chef’s knife command. It make
- #10: And convention over configuration, In Japanese “設定よりも規約”
- #11: We can write flexible defninitions by Ruby. I said we are not Rubiest but Pythonista, however I realized, we can learn Ruby syntax when writing recipes!
- #12: And the cooking log is human readable than Puppet.