Upgrade to Pro — share decks privately, control downloads, hide ads and more …

ChatOps: Technology and Philosophy

E1e1b442f49570070c40b735cf0688f4?s=47 James Fryman
January 07, 2015

ChatOps: Technology and Philosophy

What are some best practices for implementing and maintaining ChatOps in your environment? And what about the philosophy of ChatOps? Where did it come from and where is it going?

You can see a recorded video of this talk at: https://www.youtube.com/watch?v=37LmuHToYjQ. Special thanks to NetWays for the Video.

E1e1b442f49570070c40b735cf0688f4?s=128

James Fryman

January 07, 2015
Tweet

More Decks by James Fryman

Other Decks in Technology

Transcript

  1. Event Driven Operations DevOps Next Steps

  2. None
  3. None
  4. None
  5. None
  6. ChatOps Helps

  7. None
  8. None
  9. None
  10. None
  11. None
  12. ChatOps Helps

  13. None
  14. ChatOps Helps

  15. None
  16. None
  17. ChatOps Helps

  18. Event Driven Operations

  19. James Fryman

  20. None
  21. None
  22. ChatOps • Term coined by GitHub • Delegate responsibility of

    tasks/actions to an internal robot that also sits inline with your existing company communication structure
  23. ChatOps • Common tools include: • Hubot • Lita •

    Err • Introducing… StackStorm
  24. None
  25. Shared CLI

  26. Shared Context

  27. None
  28. Enable Team Scaling Enable Team Scaling

  29. Make it

  30. Remote Work

  31. Design

  32. Keep it small

  33. Design Reduce Friction

  34. Design Describe The Service

  35. /ci

  36. /graph

  37. Conway’s Law impacts design

  38. Design Use standard interfaces

  39. Design service action attribute1=foo attribute2=bar

  40. Design provision server dest=vmware datacenter=be1

  41. Design Help comes first, not last

  42. Design Give it Character

  43. Design Keep a history of Everything!

  44. Iterate

  45. Iterate Build Passive Tasks

  46. Passive ChatOps • Query open tickets • Query open alerting

    issues • Acknowledge alerts • Query data from TSDB • Query data from Logging
  47. Iterate Build Primitives around Self- Service

  48. Primitives • Provision a Server • Query a log •

    Deploy an Application
  49. Iterate Shepherd Subject Matter Experts

  50. Iterate Never explain, just do

  51. Mind Hack

  52. Pitfalls

  53. None
  54. Slow Uptake

  55. Access Control

  56. Accelerate

  57. A different kind of bus…

  58. Create Feedback Loops

  59. None
  60. Going Further

  61. Not Just Ops…

  62. DevOps is a Business Problem

  63. None
  64. @jfryman james@stackstorm.com

  65. https://github.com/stackstorm irc://freenode.net/#stackstorm http://docs.stackstorm.com support@stackstorm.com