The document discusses the challenges faced by SlideShare in deploying to production, including tedious manual deployment processes, lack of automation and visibility. This led to long downtimes, wasted time troubleshooting issues and arguments between teams. To address these problems, SlideShare implemented DevOps practices like automated deployments, continuous integration, monitoring and alerting tools. This improved deployment frequency from zero to 5 times a day, increased visibility, shared ownership and helped scale their engineering processes.

1. We deploy 5 times a day on production
DevOps at SlideShare
Kapil Mohan & Mayank Joshi
Devopsdays Bangalore 2011

2. http://slideshare.net/kapil/meeting/live

3. The Plan
1) Why DevOps @SlideShare?
2) Tools & culture for DevOps
3) Q & A

4. The Plan
1) Why DevOps @SlideShare?
2) Tools & culture for DevOps
3) Q & A

5. Once upon a time...
Deployments to production
for 4 months: ZERO
Everybody was scared to
deploy
Deployment was a tedious
job

6. F%#K
Deployment Day!
Ops guy's hand

7. Manual steps to
setup a new server
Non-repeatable,
error-prone,
un-maintainable
~1 server/guy/day
BORING!
WTF slide of the day

8. Long downtimes
Time wasted in
digging the root
cause
Time wasted in
adding capacity
Site Down

9. Zero visibility led to
arguments & blames
No shared
responsibility
It's Your Problem

10. ...and
Crazy growth,
millions of users
worldwide
Engineering needed
to scale up!

11. Why DevOps @SlideShare?
Deployments were a blocker
Building & maintaining servers was PITA
Zero visibility into the system
No shared ownership
Needed better engineering practices

12. Agile & Lean

13. http://slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-fl ickr

14. The Plan
1) Why DevOps @SlideShare?
2) Tools & culture for DevOps
3) Q & A

15. Systems Automation!
Object oriented,
incremental, repeatable
5-50 today!
IP for the company
Ruby – readable by devs

16. Scripted Deployments
Repeatable, powerful
No release manager
Devs “see” their code
going to production
Ops can deploy on their
own

17. Source Control
Moved from SVN to Git
Using GitSVN glue
Merging, branching FTW!
Dev and Ops can access
all repositories

18. Continuous Integration
BDD using RSpec
Centralized build server
using CCrb
Web-based dashboard
Blackbox application
testing using Selenium

19. Ruthless Monitoring
Web-based performance
dashboards (New Relic,
Ganglia)
Detailed, time-based
profiling
Devs have visibility

20. Alerting
Web-based
dashboard, emails,
SMS
Nagios everything
On-call Devs!

21. Visibility
Akamai
Website Pulse
Slow query reports
Nagios alerts

22. Management's Role
IRC, Email, Phone, Face to face - Get them to
'talk'
Force collaboration when troubleshooting issues,
downtimes
Build cross functional teams
STOP blaming!

23. Tools & Culture

24. 5 deployments a day :)

25. Thank you

26. We are hiring!
http://slideshare.net/about/workatslideshare

27. Image credits
Image on slide 6 - http://www.rodcolledge.com/rod_colledge/2009/03/dbas-behaving-badly-110-
backups.html
Image on slide 9 – http://www.lifehack.org/articles/communication/how-to-win-arguments-dos-
donts-and-sneaky-tactics.html
Image on slide 10 (top right) – http://labnol.blogspot.com/2007/09/slideshare-upload-ppt-
presentations-pdf.html
Image on slide 12 (left) - http://blog.une.edu.au/robbi/category/design/
Image on slide 12 (right) – http://www.startuplessonslearned.com/
Image on slide 15 – http://adainitiative.org/2011/04/puppet-labs-sponsors-the-ada-initiative/
Image on slide 16 – http://decrypt.ysance.com/2010/06/cloud-aws-infrastructure-vs-physical-
infrastructure-1/