Talk I first time did at Jazoon12 in Zurich.

1. Pavlo Baron
Chef's
Coffee

2. Pavlo Baron
pavlo.baron@codecentric.de
@pavlobaron

3. DevOps?

4. A „natural“ roles conflict

6. Ops

7. Architects

8. Managers

9. The shift

10. Application

11. A complex application is
much more
than just the sum of its
components. It's code,
configuration, environments,
infrastructure, security,
nodes, databases, services

12. Fences
hurt

13. infrastructure=code

14. Chef

15. Pick one

16. You pick the general strategy:
- hosted Chef
- own Chef server
- Chef solo (mini)

18. hit the road

19. You decide where to keep
configuration JSON/Ruby DSL
„code“:
- file based under own
version control
- in Chef's configuration
database

21. play god

22. You decide which
environments you need / have
and configure / manage them
separately:
dev, test, QA, team, preprod,
integration, load test, prod,
whatnot

24. play cook

25. You pick necessary
cookbooks and their included
recipes from:
- OpsCode repository
- community sources
- GitHub
- own ones

27. play theatre

28. You define roles and
corresponding run-lists (including
transitive dependencies) and
assign them to machines:
- web-server
- app-server
- queue server
- whatnot-server

30. Further abstractions for that are:
- providers / resources
- templates
- data bags
- files
- attributes
You can use all of them to tweak
your deployment / config

31. Knife is your
weapon

32. ohai is your oracle

33. rastru cture=code
inf

34. ip ts,
sc r
r o ld
y o u a n d
ru n a rn
n le
the ract
st
ab

35. And isn't excessive
abstraction what
really makes a
good Enteprise Java
solution? ;)

36. let it run

38. again and again

39. and Java?

40. You use same stuff, e.g.:
- your environments
- application, JDK, tomcat, DB
cookbooks
- adjust your attributes
- configure infrastructure same
way (load-balancer etc.)

41. Thank you

42. Most images originate from
istockphoto.com
except few ones taken
from Wikipedia and product pages
or generated through public
online generators