Successfully reported this slideshow.
Your SlideShare is downloading. ×

Ignite@DevOpsDays - Why devs need ops

Ad

Why Devs needs
                          Ops
                            Or MP’s, Crowds and failure




Saturday, 15 Octo...

Ad

Copyright © Steve Bell 2009




                             MP’s Expenses
Saturday, 15 October 2011

Ad

Saturday, 15 October 2011

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Upcoming SlideShare
Pantheon @ Drupal Down Under
Pantheon @ Drupal Down Under
Loading in …3
×

Check these out next

1 of 20 Ad
1 of 20 Ad

Ignite@DevOpsDays - Why devs need ops

Download to read offline

A 5 minute talk given at DevOpsDays Goteborg wherein I declare that devs and ops need to work together because their skills mesh nicely.

A 5 minute talk given at DevOpsDays Goteborg wherein I declare that devs and ops need to work together because their skills mesh nicely.

Advertisement
Advertisement

More Related Content

Advertisement

Ignite@DevOpsDays - Why devs need ops

  1. 1. Why Devs needs Ops Or MP’s, Crowds and failure Saturday, 15 October 2011
  2. 2. Copyright © Steve Bell 2009 MP’s Expenses Saturday, 15 October 2011
  3. 3. Saturday, 15 October 2011
  4. 4. Simon Willison “You can now build working software in less time than it takes to have the meeting to describe it” Photo courtesy of Tom Coates Saturday, 15 October 2011
  5. 5. Prototyping • 1 Meeting = 6 people * 1 hour = 6 hours • 1 prototype = 1 dev * 6 hours = 6 hours! • New Software Development Stacks for Rapid development • Django, Rails, Node.js, Lift, Moustache, Play, .NET MVC Scalatra... Saturday, 15 October 2011
  6. 6. Example • MP’s Expenses • 1 Developer/ 1 Week • 1 Designer / 2 Days • 1 SysAdmin / 1 Day • EC2 - £50 • Live 10 days after work started Saturday, 15 October 2011
  7. 7. Not always roses • Prototype code does not scale • Prototyping devs don’t think of everything • ...(or even anything!) Saturday, 15 October 2011
  8. 8. Crash #1 • Default Configs • Our default • 50 apache children • 30 MySQL connections • This isn’t going to work well! Saturday, 15 October 2011
  9. 9. Saturday, 15 October 2011
  10. 10. Saturday, 15 October 2011
  11. 11. ORM’s suck mkay • Pages.object.filter (votes__isnull=True).distinct.count • SELECT COUNT(DISTINCT ...) FROM ‘expenses’ LEFT OUTER JOIN ‘vote’ ON (...) WHERE ‘vote.id’ IS NULL Saturday, 15 October 2011
  12. 12. Crash #2 • The code was bad, the SQL was really bad • but it takes a sysadmin to point out... • DB using 135% of CPU • DB and Apaches on the same box = bad idea Saturday, 15 October 2011
  13. 13. How to migrate a DB • There’s a lot of tools • It could be quite an effort • It’s really broken now • SysAdmins are really evil (especially @pnasrat) Saturday, 15 October 2011
  14. 14. How to migrate a DB • ssh mps-live “mysqldump mp_expenses” | sed ‘s/ENGINE=MyISAM/ENGINE=InnoDB/ g’ | sed ‘s/CHARSET=latin1/ CHARSET=utf8/g’ | ssh mysql-big “mysql -u root mp_expenses” Saturday, 15 October 2011
  15. 15. Next time • Things our sysadmin would have suggested if he’d heard about the project prior to the day of release Saturday, 15 October 2011
  16. 16. httpperf / apachebench / curl +forloop Saturday, 15 October 2011
  17. 17. Squid/Varnish Saturday, 15 October 2011
  18. 18. So why didn’t we? • “SysAdmins slow us down” • “SysAdmins ask difficult questions” • “SysAdmins want to puppet everything” Saturday, 15 October 2011
  19. 19. What do we know now • “SysAdmins ask the right questions” • “SysAdmins want repeatability” • “SysAdmins know some gnarly stuff” • “SysAdmins can make us go faster” Saturday, 15 October 2011
  20. 20. DevOps • Sometimes what you need is not a “SysAdmin” • Uptime is important • What you need is “Crash Mat Arranger” • Recovering from failure fast is important Saturday, 15 October 2011

×