Pavlo BaronChefsCoffee
Pavlo Baronpavlo.baron@codecentric.de             @pavlobaron
DevOps?
A „natural“ roles conflict
Ops
Architects
Managers
The shift
Application
A complex application ismuch morethan just the sum of itscomponents. Its code,configuration, environments,infrastructure, ...
Fences   hurt
infrastructure=code
Chef
Pick one
You pick the general strategy:- hosted Chef- own Chef server- Chef solo (mini)
hit the road
You decide where to keepconfiguration JSON/Ruby DSL„code“:- file based under own     version control- in Chefs configurati...
play god
You decide whichenvironments you need / haveand configure / manage themseparately:dev, test, QA, team, preprod,integration...
play cook
You pick necessarycookbooks and their includedrecipes from:- OpsCode repository- community sources- GitHub- own ones
play theatre
You define roles andcorresponding run-lists (includingtransitive dependencies) andassign them to machines:- web-server- ap...
Further abstractions for that are:    - providers / resources    - templates    - data bags    - files    - attributesYou ...
Knife is yourweapon
ohai is your oracle
rastru cture=codeinf
ip ts,                  sc r           r o ld     y o u      a n dru n       a rn     n  le the ract      st   ab
And isnt excessive   abstraction what     really makes agood Enteprise Java         solution? ;)
let it run
again and again
and Java?
You use same stuff, e.g.:- your environments- application, JDK, tomcat, DB   cookbooks- adjust your attributes- configure ...
Thank you
Most images originate from               istockphoto.com           except few ones takenfrom Wikipedia and product pages  ...
Chef's Coffee - provisioning Java applications with Chef (@pavlobaron)
Chef's Coffee - provisioning Java applications with Chef (@pavlobaron)
Chef's Coffee - provisioning Java applications with Chef (@pavlobaron)
Chef's Coffee - provisioning Java applications with Chef (@pavlobaron)
Chef's Coffee - provisioning Java applications with Chef (@pavlobaron)
Chef's Coffee - provisioning Java applications with Chef (@pavlobaron)
Chef's Coffee - provisioning Java applications with Chef (@pavlobaron)
Upcoming SlideShare
Loading in …5
×

Chef's Coffee - provisioning Java applications with Chef (@pavlobaron)

3,098 views

Published on

Talk I first time did at Jazoon12 in Zurich.

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,098
On SlideShare
0
From Embeds
0
Number of Embeds
67
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Chef's Coffee - provisioning Java applications with Chef (@pavlobaron)

  1. 1. Pavlo BaronChefsCoffee
  2. 2. Pavlo Baronpavlo.baron@codecentric.de @pavlobaron
  3. 3. DevOps?
  4. 4. A „natural“ roles conflict
  5. 5. Ops
  6. 6. Architects
  7. 7. Managers
  8. 8. The shift
  9. 9. Application
  10. 10. A complex application ismuch morethan just the sum of itscomponents. Its code,configuration, environments,infrastructure, security,nodes, databases, services
  11. 11. Fences hurt
  12. 12. infrastructure=code
  13. 13. Chef
  14. 14. Pick one
  15. 15. You pick the general strategy:- hosted Chef- own Chef server- Chef solo (mini)
  16. 16. hit the road
  17. 17. You decide where to keepconfiguration JSON/Ruby DSL„code“:- file based under own version control- in Chefs configuration database
  18. 18. play god
  19. 19. You decide whichenvironments you need / haveand configure / manage themseparately:dev, test, QA, team, preprod,integration, load test, prod,whatnot
  20. 20. play cook
  21. 21. You pick necessarycookbooks and their includedrecipes from:- OpsCode repository- community sources- GitHub- own ones
  22. 22. play theatre
  23. 23. You define roles andcorresponding run-lists (includingtransitive dependencies) andassign them to machines:- web-server- app-server- queue server- whatnot-server
  24. 24. Further abstractions for that are: - providers / resources - templates - data bags - files - attributesYou can use all of them to tweakyour deployment / config
  25. 25. Knife is yourweapon
  26. 26. ohai is your oracle
  27. 27. rastru cture=codeinf
  28. 28. ip ts, sc r r o ld y o u a n dru n a rn n le the ract st ab
  29. 29. And isnt excessive abstraction what really makes agood Enteprise Java solution? ;)
  30. 30. let it run
  31. 31. again and again
  32. 32. and Java?
  33. 33. You use same stuff, e.g.:- your environments- application, JDK, tomcat, DB cookbooks- adjust your attributes- configure infrastructure same way (load-balancer etc.)
  34. 34. Thank you
  35. 35. Most images originate from istockphoto.com except few ones takenfrom Wikipedia and product pages or generated through public online generators

×