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

ChatOps: Technology and Philosophy

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.

James Fryman

January 07, 2015
Tweet

More Decks by James Fryman

Other Decks in Technology

Transcript

  1. Event Driven Operations
    DevOps Next Steps

    View Slide

  2. View Slide

  3. View Slide

  4. View Slide

  5. View Slide

  6. ChatOps
    Helps

    View Slide

  7. View Slide

  8. View Slide

  9. View Slide

  10. View Slide

  11. View Slide

  12. ChatOps
    Helps

    View Slide

  13. View Slide

  14. ChatOps
    Helps

    View Slide

  15. View Slide

  16. View Slide

  17. ChatOps
    Helps

    View Slide

  18. Event Driven Operations

    View Slide

  19. James Fryman

    View Slide

  20. View Slide

  21. View Slide

  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

    View Slide

  23. ChatOps
    • Common tools include:
    • Hubot
    • Lita
    • Err
    • Introducing…
    StackStorm

    View Slide

  24. View Slide

  25. Shared
    CLI

    View Slide

  26. Shared
    Context

    View Slide

  27. View Slide

  28. Enable Team Scaling
    Enable Team Scaling

    View Slide

  29. Make it

    View Slide

  30. Remote Work

    View Slide

  31. Design

    View Slide

  32. Keep it small

    View Slide

  33. Design
    Reduce Friction

    View Slide

  34. Design
    Describe The
    Service

    View Slide

  35. /ci

    View Slide

  36. /graph

    View Slide

  37. Conway’s Law
    impacts design

    View Slide

  38. Design
    Use standard
    interfaces

    View Slide

  39. Design
    service
    action
    attribute1=foo
    attribute2=bar

    View Slide

  40. Design
    provision
    server
    dest=vmware
    datacenter=be1

    View Slide

  41. Design
    Help comes
    first, not last

    View Slide

  42. Design
    Give it
    Character

    View Slide

  43. Design
    Keep a history
    of Everything!

    View Slide

  44. Iterate

    View Slide

  45. Iterate
    Build Passive
    Tasks

    View Slide

  46. Passive ChatOps
    • Query open tickets
    • Query open alerting issues
    • Acknowledge alerts
    • Query data from TSDB
    • Query data from Logging

    View Slide

  47. Iterate
    Build Primitives
    around Self-
    Service

    View Slide

  48. Primitives
    • Provision a Server
    • Query a log
    • Deploy an Application

    View Slide

  49. Iterate
    Shepherd
    Subject Matter
    Experts

    View Slide

  50. Iterate
    Never explain,
    just do

    View Slide

  51. Mind Hack

    View Slide

  52. Pitfalls

    View Slide

  53. View Slide

  54. Slow Uptake

    View Slide

  55. Access Control

    View Slide

  56. Accelerate

    View Slide

  57. A different kind of bus…

    View Slide

  58. Create Feedback Loops

    View Slide

  59. View Slide

  60. Going Further

    View Slide

  61. Not Just
    Ops…

    View Slide

  62. DevOps
    is a
    Business Problem

    View Slide

  63. View Slide

  64. View Slide

  65. https://github.com/stackstorm
    irc://freenode.net/#stackstorm
    http://docs.stackstorm.com
    [email protected]

    View Slide