Download to read offline
Uploaded byNETWAYS
OSDC 2015: James Fryman | DevOps Next Steps: Event Driven Operation
The document discusses ChatOps and its role in event-driven operations, emphasizing delegation of tasks to automated tools within company communication frameworks. It highlights the importance of design principles that enable team scaling and efficiency in remote work. Additionally, it explores self-service primitives and feedback loops, positioning DevOps as a solution to business challenges.
More Related Content
Similar to OSDC 2015: James Fryman | DevOps Next Steps: Event Driven Operation
OSDC 2015: James Fryman | DevOps Next Steps: Event Driven Operation
- 1. Event Driven Operations DevOpsNext Steps
- 6.
- 12.
- 14.
- 17.
- 18.
- 19.
- 22. ChatOps • Term coinedby GitHub • Delegate responsibility of tasks/actions to an internal robot that also sits inline with your existing company communication structure
- 23. ChatOps • Commontools include: • Hubot • Lita • Err • Introducing… StackStorm
- 25.
- 26.
- 28. Enable Team ScalingEnableTeam Scaling
- 29.
- 30.
- 31.
- 32.
- 33.
- 34.
- 35.
- 36.
- 37.
- 38.
- 39.
- 40.
- 41.
- 42.
- 43. Design Keep a history ofEverything!
- 44.
- 45.
- 46. PassiveChatOps • Queryopen tickets • Query open alerting issues • Acknowledge alerts • Query data from TSDB • Query data from Logging
- 47.
- 48. Primitives • Provision aServer • Query a log • Deploy an Application
- 49.
- 50.
- 51.
- 52.
- 54.
- 55.
- 56.
- 57. A different kindof bus…
- 58.
- 60.
- 61.
- 62.
- 64.
- 65.