1. Devops - The Art of being Specializing Generalist Sai *Venkatakrishnan

3. I love Linux, Lisp, Python & Opensource

4. Open Source Contributor

5. Former Watir team member

6. Currently part of Multiverse STM team

7. Love to work on Opensource, Databases, Concurrency, Scalability and Performance problems & Lisp

8. Budding Devop...

9. DevOps... Why?

10. Why now? LinkedIn Signal's Architecture - http://sna-projects.com/blog/2010/10/linkedin-signal-a-look-under-the-hood/

11. 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

13. What dependencies ?

14. No machines available ?

15. What database ?

16. Security ?

17. High Availability ?

18. Scalability ?

19. My computer can't install this ?

20. Devs vs Ops

22. Are these Logs ? Or this is actualy customer data ?

23. How many users are there , should they launch 100 queries each ?? Oh we're having 10K users

24. Why is debugging enabled ?

25. Who wrote this ? Why are we doing that?

26. There is a firewall b/w webserver & DB?

27. The filesystem is encrypted?

28. 11 days into operations

30. Get Devs and Ops to talk asap or keep them as one :)

32. Security

33. Backups

34. High Availability

35. Upgradability

36. Configuration Mgmt

37. Monitoring

39. Continous integration

40. Build Pipelines

41. Configuration Management

42. Automated deployment on test/staging platforms

43. Virtualization & Cloud

44. Continuous Deployment <-- Holy Grail

46. Automate & test your infrastructure & deployment not just your code and tests

47. Knowing as much as about deployment & production environment eliminates assumptions.

48. Repetability and openness is good

49. Going Live

51. If my computer can't install it , the installer is borken

52. Reproducable

55. Modify 2000 files,

56. Cluster management

64. Monitoring

65. Upgrading

66. Continuous deployment

67. Feed it back to development. Make effective business & design decisions.

68. High Availabilty

69. Scalability

70. Monitor

73. Thank You...

74. Images: http://www.flickr.com/photos/huffstutterrobertl/4135257384/ http://www.flickr.com/photos/brighton/2153602543/ http://www.flickr.com/photos/gchorus/2074271352/ http://www.flickr.com/photos/49024304@N00/2951673691/sizes/l/ http://www.flickr.com/photos/30302096@N06/2953698548/ http://www.flickr.com/photos/jamescridland/613445810/ http://www.flickr.com/photos/johnmcga/4468003947/