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.

Transcript

1. Event Driven Operations DevOps Next Steps
6. ChatOps Helps
12. ChatOps Helps
14. ChatOps Helps
17. ChatOps Helps
18. Event Driven Operations
19. James Fryman
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
25. Shared CLI
26. Shared Context
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
54. Slow Uptake
55. Access Control
56. Accelerate
57. A different kind of bus…
58. Create Feedback Loops
60. Going Further
61. Not Just Ops…
62. DevOps is a Business Problem
64. @jfryman james@stackstorm.com
65. https://github.com/stackstorm irc://freenode.net/#stackstorm http://docs.stackstorm.com support@stackstorm.com