Opinions on DevOps

Opinions on DevOps

Prezo on DevOps given at DSDM Stockholm.

A204e1fe2002bc6d087391759c3dfab0?s=128

Mårten Gustafson

June 07, 2012
Tweet

Transcript

  1. DevOps

  2. opinions on DevOps

  3. * image from the DevOps wikipedia page

  4. qa disclaimer * I haven’t worked in a business where

    QA has been a separate department for a lot of years * (it’s always been an integral part of dev’t) * Therefore I won’t talk much about qa here
  5. ops on the other hand

  6. outsourced

  7. (un)managed hosting

  8. separate division(s)

  9. design release development test / qa develop development * a

    too common view on ops from dev’t
  10. design release development test / qa develop design development *

    a too common view on ops from dev’t
  11. design release development test / qa develop design development develop

    * a too common view on ops from dev’t
  12. design release development test / qa develop design development test

    / qa develop * a too common view on ops from dev’t
  13. design release development test / qa develop design release development

    test / qa develop * a too common view on ops from dev’t
  14. design release development test / qa develop operations deploy monitor

    * a too common view on ops from dev’t
  15. install monitor patch .... development operations design develop test /

    qa * a more realistic view * two disciplines with their own lifecycle * but as silos, really? * epiphany?
  16. are we building two separate beasts...

  17. ...or one solution?

  18. * full stack ownership (awareness) * cross-functional team

  19. Operating system Server software Datastore Application * full stack ownership

    (awareness) * cross-functional team
  20. Operating system Server software Datastore Application DBA development CTO operations

    * full stack ownership (awareness) * cross-functional team
  21. Operating system Server software Datastore Application DBA development CTO operations

    dysfunctional segregation? * full stack ownership (awareness) * cross-functional team
  22. Operating system Server software Datastore Application team cross-functional team? *

    full stack ownership (awareness) * cross-functional team
  23. “where the team ‘tries to go the distance as a

    unit, passing the ball back and forth’” Hirotaka Takeuchi, Ikujiro Nonaka New New Product Development Game, ’86 * full stack ownership (awareness) * cross-functional team
  24. development affects ops

  25. development affects ops

  26. design install develop monitor test patch .... development operations +

  27. awareness we must be aware of the other teams and

    disciplines around us in order to...
  28. patience ...have patience for us and for them to...

  29. insight * ...gain insight into our respective discipline, skill sets

    and challenges... * see each others work * be close (whatever that means)
  30. understanding ...so that we can come to a better understanding

    about all parts of the equation
  31. DevOps

  32. Dev Development Operations &

  33. Dev Operations & Development

  34. how do we* monitor *) development & operations

  35. how can we* monitor *) development & operations

  36. how do we* log *) development & operations

  37. how can we* log *) development & operations

  38. how do we* deploy *) development & operations

  39. how can we* deploy *) development & operations

  40. how will we* diagnose *) development & operations

  41. development, learn about operations development: learn about operations

  42. development, learn about operations

  43. Development & Operations Operations

  44. Development & Operations

  45. teach dev

  46. VLANs

  47. routing

  48. DNS

  49. patch management

  50. PXE installs

  51. what you do

  52. why you do

  53. ask devs

  54. how should we* architect *) development & operations

  55. what should we* expect *) development & operations

  56. operations, learn about development operations: learn about development

  57. operations, learn about development

  58. shift focus

  59. release...

  60. ...when it makes sense...

  61. ...not to operations

  62. ...not to development

  63. ...but to business

  64. continuously delivery

  65. continuously delivery

  66. continuously: release

  67. continuously: reconfigure

  68. continuously: change dns

  69. continuously: provision servers

  70. continuously: apply security patches

  71. continuously: applies everywhere

  72. "…[the] sysadmin skill… include more…infrastructure software development…an expansion in the

    job…from basic systems administration to… infrastructure engineering…" "…[the] sysadmin skill… include more…infrastructure software development…an expansion in the job…from basic systems administration to… infrastructure engineering…" Jesse Robbins, Opscode O’Reilly Radar, May 2012 * http://radar.oreilly.com/2012/05/infrastructure-automation-jesse-robbins.html
  73. "…[the] sysadmin skill… include more…infrastructure software development…an expansion in the

    job…from basic systems administration to… infrastructure engineering…" Jesse Robbins, Opscode O’Reilly Radar, May 2012 * http://radar.oreilly.com/2012/05/infrastructure-automation-jesse-robbins.html
  74. the important

  75. Development & Operations

  76. & * development and operations... * ...together on a nyan

    cat... * ...to infinity and beyond
  77. AND development operations * development and operations... * ...together on

    a nyan cat... * ...to infinity and beyond
  78. @martengustafson marten.gustafson@gmail.com * kthxbai