3. Engine Yard
Ruby Hosting in the Cloud
Global Support Organization
Rails 3
Thursday, May 6, 2010 3
4. The Race to Deliver
Thursday, May 6, 2010 4
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’!
Thursday, May 6, 2010 5
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
7. Traditional IT Silos
Thursday, May 6, 2010 7
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
Thursday, May 6, 2010 8
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
Thursday, May 6, 2010 9
looking in from the outside you wouldn’t believe how people do operations
11. Developer Dreamland
Thursday, May 6, 2010 11
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
Thursday, May 6, 2010 12
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
Thursday, May 6, 2010 13
it usually takes something terrible for people to realize it was a bad idea.
15. Finger Pointing
Thursday, May 6, 2010 15
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
Thursday, May 6, 2010 16
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
Thursday, May 6, 2010 17
operations doesn’t trust developer’s code
developers feel like operations keeps them from delivering
19. Speeding Things Up
Thursday, May 6, 2010 19
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
Thursday, May 6, 2010 20
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
Thursday, May 6, 2010 21
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
Thursday, May 6, 2010 22
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
Thursday, May 6, 2010 23
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
Thursday, May 6, 2010 24
starting the conversation early instead of waiting to engage other parts of your org
truly understanding the domain in question
25. Sysadmin Coders
Thursday, May 6, 2010 25
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
Thursday, May 6, 2010 26
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
Thursday, May 6, 2010 27
“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
Thursday, May 6, 2010 28
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?
Thursday, May 6, 2010 29
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?
Thursday, May 6, 2010 30
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
Thursday, May 6, 2010 31
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!
Thursday, May 6, 2010 32
never..ending..stream..of..unix..boxes
how do you get them all do your bidding?
33. Puppet
Thursday, May 6, 2010 33
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
Thursday, May 6, 2010 34
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
Thursday, May 6, 2010 35
devops is a proactive approach at covering the product lifecycle from an ops perspective
36. Delight Your Users
Thursday, May 6, 2010 36
delivering your product on time w/ a better sense of reliability in the system
this makes end users happier, and