Rise of DevOps

A talk I gave at Red Dirt RubyConf in 2010 about this DevOps thing that people were getting into.

Transcript

1. Rise of DevOps Images from http://blackandwtf.tumblr.com 1 Thursday, May 6, 2010
2. Corey Donohoe github.com/atmos twitter.com/atmos atmos.org 2 Thursday, May 6, 2010
3. Engine Yard Ruby Hosting in the Cloud Global Support Organization Rails 3 3 Thursday, May 6, 2010
4. The Race to Deliver 4 Thursday, May 6, 2010 your idea is probably competing against others with similar interests how do we adopt agile practices inside of the rest of our organization
5. Stop Trippin’! 5 Thursday, May 6, 2010 you do not wanna be that guy tripping over the stuff you can manage easily. devops is about giving you a competitive advantage devops is about delivering high quality operations setups
6. New Business Ideas 6 Thursday, May 6, 2010 take us and our customers to new levels
7. Traditional IT Silos 7 Thursday, May 6, 2010 traditionally we might have operations, dbas, networking people, release managers, etc. a lot of smart people with generally narrow skill sets. we see these environments as ruby gains more adoption.
8. Fragile Deployment 8 Thursday, May 6, 2010 it becomes a balancing act to keep the production systems in a good state. a lot production systems are “that box in the corner” you can’t touch.
9. That’s Just Dumb 9 Thursday, May 6, 2010 looking in from the outside you wouldn’t believe how people do operations
10. That’s Crazy 10 Thursday, May 6, 2010 WHY WOULD YOU EVER DO THAT?
11. Developer Dreamland 11 Thursday, May 6, 2010 a lot of really creative hackers come up with stuff that’s difficult to support from operations some developer in your org got an elephant to do a hand stand on his shiny new mac. sometimes called “it works on my machine” syndrome
12. Operations Support 12 Thursday, May 6, 2010 but your operations feel like they’re holding the elephant up it requires them to have super human powers and a mexican wrestling mask
13. Support Fallout 13 Thursday, May 6, 2010 it usually takes something terrible for people to realize it was a bad idea.
14. Developer Outrage 14 Thursday, May 6, 2010 developers cry out, “it works on my machine!!!” fuckin’ ops guys.
15. Finger Pointing 15 Thursday, May 6, 2010 basically no one believes they are at fault, so and so isn’t “agile” enough doesn’t accomplish the task at hand
16. Distaste for Change 16 Thursday, May 6, 2010 historically operations hate introducing new things they have to support. the default answer for “can we support X” becomes “NO!” change control boards or something similar are introduced.
17. Distrust is Common 17 Thursday, May 6, 2010 operations doesn’t trust developer’s code developers feel like operations keeps them from delivering
18. How Can We Fix This? 18 Thursday, May 6, 2010
19. Speeding Things Up 19 Thursday, May 6, 2010 how do we get operations to work as quickly as a productive “agile” team? how do we identify problems in operations/deployment earlier?
20. The Same Team 20 Thursday, May 6, 2010 we’re all working toward the same goal, even though we’re different it’s the job of the parties involved to bridge the gaps w/ the rest of their org
21. Helping Others Out 21 Thursday, May 6, 2010 even though you still sort of think of yourself as different, lend a hand outside your group. pair with your dba, or a developer. when was the last time you did that?
22. Automation 22 Thursday, May 6, 2010 automation is historically an afterthought. making system automation a first class requirement, configs and/or provisioning. we still can’t do really “brain dumps”
23. Testing 23 Thursday, May 6, 2010 testing is still emerging in this area. people are doing really cool stuff with cucumber. we do a few different things at EY to validate automation.
24. Better Communication 24 Thursday, May 6, 2010 starting the conversation early instead of waiting to engage other parts of your org truly understanding the domain in question
25. Sysadmin Coders 25 Thursday, May 6, 2010 embracing ruby and python to get the job done. the best coders i know are often badass sysadmins too, they understand everything.
26. Shipping Early 26 Thursday, May 6, 2010 avoid building something that really won’t get the job done. get everyone who will be involved, involved early. having the automation in place for operations early in the development cycle.
27. The Last Mile 27 Thursday, May 6, 2010 “dev complete” is different from “live, in production, making us money” hold up in wrapping up that last mile costs us money.
28. Make Everyone Happy 28 Thursday, May 6, 2010 a workplace where you love everyone in every department is awesome. it makes working on the product a pleasant experience. same parts that make agile work for development can apply to the sysadmin’s work.
29. where’s my BOFH? 29 Thursday, May 6, 2010 they’re still there, but he’s likely your “Buddy Operator from Helena” tools and approaches exist now that align with good system administration goals. these tools should start being adopted now
30. where’s this headed? 30 Thursday, May 6, 2010 adopting agile-like practices in all aspects of delivering a product. specifically, operations should step up their game because they’re being left behind.
31. The Cloud 31 Thursday, May 6, 2010 while no one clearly defines what “the cloud” is i think of it as automated provisioning of IT infrastructure devops makes even more sense because we have as much disposable hardware as we want
32. The Penguins are Coming! 32 Thursday, May 6, 2010 never..ending..stream..of..unix..boxes how do you get them all do your bidding?
33. Puppet 33 Thursday, May 6, 2010 puppet is a tool from the guys at puppetlabs, formerly reductivelabs. we use it internally at EY for managing lots of things customer’s don’t interact with they have a pretty vibrant user community
34. Cuttin’ Up with Chef 34 Thursday, May 6, 2010 opscode has their own platform where people can share cookbooks you can compose your recipes for your system based on the work of others there’s a huge number of open source cookbooks available on GH, EY uses chef
35. Celebrate Your Product 35 Thursday, May 6, 2010 devops is a proactive approach at covering the product lifecycle from an ops perspective
36. Delight Your Users 36 Thursday, May 6, 2010 delivering your product on time w/ a better sense of reliability in the system this makes end users happier, and
37. Enjoy Yourself 37 Thursday, May 6, 2010 enjoy yourself, be a maker, an automator, and perhaps a devop Thanks