Download as PDF, PPTX
![package "haproxy" do!action :install!end!!template "/etc/haproxy/haproxy.cfg" do!source "haproxy.cfg.erb"!owner "root"!group "root"!mode 0644!notifies :restart, "service[haproxy]"!end!!service "haproxy" do!supports :restart => true!action [:enable, :start]!end!](/image.pl?url=https%3a%2f%2fimage.slidesharecdn.com%2fcheffingadepartment-140617042837-phpapp01%2f75%2fCheffing-a-department-36-2048.jpg&f=jpg&w=240)
Uploaded byAndrzej Grzesik
PDF, PPTX625 views
Cheffing a department
The document discusses using Chef to manage infrastructure for a new development team. It recommends keeping the Chef implementation simple, focusing on readability and versioning of code. It also stresses the importance of code reviews, testing changes, and gaining buy-in from developers by emphasizing simplicity and avoiding introducing yet another tool.
More Related Content
What's hot
Similar to Cheffing a department
More from Andrzej Grzesik
Cheffing a department
- 1.@ags313#cheffingCheffing a dept,one dev at a timeAndrzej Grzesik@ags313andrzejgrzesik.info
- 2.
- 3.
- 5.
- 6.
- 7.my opinions aremy own
- 8.
- 9.
- 10.
- 11.there is lifebeyond Tomcat
- 15.a bit ofbackground
- 16.
- 17.new devsnext toexisting org
- 18.do the rightthingdo it right
- 19.
- 20.
- 21.we need torun it!
- 22.what did wedo?
- 23.started to usechef
- 24.
- 25.it was allamazing
- 26.
- 27.we needed aprod quickly
- 28.and things werebroken*and we didn’t have time nor nerves
- 29.
- 31.
- 33.
- 34.
- 35.what does itlook like?
- 36.package "haproxy" do!action:install!end!!template "/etc/haproxy/haproxy.cfg" do!source "haproxy.cfg.erb"!owner "root"!group "root"!mode 0644!notifies :restart, "service[haproxy]"!end!!service "haproxy" do!supports :restart => true!action [:enable, :start]!end!
- 37.put resources togetherinto recipesorganise recipes into rolesapply roles to machines
- 38.code?easy to readeasyto versionwith concise DSL
- 40.there is alot of this on githubproblem
- 42.
- 43.
- 44.protein scales wellit’sjust 25 years to breed and train a new techie!
- 46.
- 48.
- 49.
- 50.problems?“what could possiblygo wrong”
- 51.
- 52.
- 53.
- 56.
- 57.
- 58.
- 59.
- 60.
- 62.
- 63.chef: server orsolo?
- 64.why NOT chefserver?
- 66.
- 67.
- 68.
- 69.
- 70.
- 71.
- 73.let people makemistakes
- 75.
- 77.
- 79.Law of LargeNumbers
- 80.
- 81.many servers break…a lot
- 83.
- 84.phoenix patterndon’t fixboxes, bake new
- 85.
- 86.How did wedeploy?
- 87.
- 88.
- 89.
- 90.QA/QE to therescue
- 91.
- 92.
- 93.
- 94.summary• keep itsimple• do things• ???• profit
- 95.