Your SlideShare is downloading. ×
Chef's Coffee - provisioning Java applications with Chef (@pavlobaron)
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

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

2,298
views

Published on

Talk I first time did at Jazoon12 in Zurich.

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
2,298
On Slideshare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

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