This document discusses DevOps and the movement towards closer collaboration between development and operations teams. It advocates that operations work should start early in the development process, with developers and operations communicating about non-functional requirements, security, backups, monitoring and more. Both developers and operations staff should aim to automate infrastructure and deployments. The goal is reproducible, reliable deployments of applications and their supporting systems.

1. Devops, Devops, Devops Kris Buytaert

2. Kris Buytaert I used to be a Dev,

3. Then Became an Op

4. Senior Linux and Open Source Consultant @inuits.be

5. „ Infrastructure Architect“

6. Building Clouds since 2004

7. Surviving the 10 th floor test

8. Co-Author Virtualization with Xen

9. Guest Editor at Virtualization.com

10. But mostly, a DevOp

11. Alternative Titles Grumpy old Sysadmin

12. Devops, Devops, Devops

13. Surviving the 10 th floor test

14. Agile Administration

15. Devministration, your new Job Title

16. Devop, definition 30 something

17. Senior Infrastructure guy

18. Development background

19. Open Source Expcerience

20. Mostly European (.be / .uk)

21. Likes Belgian Beer

22. Likes Sushi

23. The community of developers whose work you see on the Web, who probably don’t know what ADO or UML or JPA even stand for, deploy better systems at less cost in less time at lower risk than we see in the Enterprise. This is true even when you factor in the greater flexibility and velocity of startups. Tim Bray , on his blog January 2010

24. The Old Days “Put this Code Live, here's a tarball” NOW!

25. What dependencies ?

26. No machines available ?