Modern IT environments require lots of communication either to other people in the same department or teams or even cross-company communication. Especially the first part where team members need information on upcoming changes, deployments done and issues fixed, we as System Administrators or Engineers, Infrastructure Engineers or DevOps team members always have to do things multiple times:
First we use a tool to identify the actual state, then we use another tool to identify and run tasks and last but least we communicate findings, results or fixes. Everything we do when using the tools is something we do alone by ourselves. Other team members might learn by shouting in the room that we work on something. Remote staff might even be unaware.
This talk will give an introduction to ChatOps - a combination of using tools and communication in parallel.
We try to find possible use cases, identify requirements for ChatOps and learn about existing solutions. The talk will finish with a ChatOps live demo using Icinga2 and Jenkins.
2. Copyright example42 GmbH - 2016
about me
started as SysAdmin
Slackware on 15 floppy disks
Puppet since 2007
Puppet Certified Professional, Instructor and
Consultant
Infrastructure Engineer
CEO & Co-Founder example42 GmbH
3. Copyright example42 GmbH - 2016
– James Fryman @jfryman
“Bringing the work you are already doing ...
!
... into the conversations you are already
having”
4. Copyright example42 GmbH - 2016
Communication
!
!
!
!
“... you cannot not communicate…” Paul Watzlawick -
1967
5. Copyright example42 GmbH - 2016
Communication
!
!
!
!
“... you cannot not communicate… but you can
not communicate accurately.” Paul Watzlawick - 1967
6. Copyright example42 GmbH - 2016
Communication
!
!
!
!
Communication is transmission of information from a
source to a receiver without loss of information
12. Copyright example42 GmbH - 2016
Collaboration
Split work load
Different expertise levels
Support and train less experienced team members
Share learning experiences
14. Copyright example42 GmbH - 2016
Communication in IT
System stati
Monitoring
Build Chain
Tickets
Communication
Email
XMPP
15. Copyright example42 GmbH - 2016
Communication in IT
need for Monitor wall
need for large screens
how to do that for remote work (home office)?
16. Copyright example42 GmbH - 2016
Combining Communication
!
!
!
!
Dashboards (maybe rolling)
multiple sources of information
17. Copyright example42 GmbH - 2016
Communication Overlay
Why switching tools?
Why specifying content or information in multiple
locations
How to ensure everybody knows the same?
What have been the tasks that were done solving the
problem? (Documentation - Wiki?)
19. Copyright example42 GmbH - 2016
Aligning Communication
API requirements
Authentication
Authorization
Error Handling
Feedback
...
20. Copyright example42 GmbH - 2016
Aligning Communication
!
!
Do everything in one place
Automate everything
“Protect yourself from yourself and make your code
super-secure” (J. Fryman, DevOpsDays Berlin 2014)
21. Copyright example42 GmbH - 2016
Aligning Communication
GNU approach
one tool does one thing only
second things are done with a new tool
23. Copyright example42 GmbH - 2016
Communication Simplyfied
One tool to combine everything
Monitoring status, acknowledgement, downtime
CfgMgmt run
Generate reports and graphs
Trigger CI
...
24. Copyright example42 GmbH - 2016
Communication - Old
John: Hi Ben, do you see the spike in load on backend systems?
Ben: Hi John, wait, I have a look....
Ben: Yes, looks weird. I will analyse.
John: Hi Ben, forget it. It was Bob running a report.
John: Ben?
Ben: Hi John, I restarted the server. But now we have an issue
with customer sessions.
Ben: Uuh. Bad.
25. Copyright example42 GmbH - 2016
Communication - New
Bob: <bot> generate_report year 2013-2015
<bot>: generate_report: generating report for Bob
<bot>: icinga2: PROBLEM high load on backend: avg 28.5
John: Hi Bob, please do not run this report during peak hours.
Bob: Oh. Sorry.
John: <bot> icinga2 ack -s backend
<bot>: icinga2: acknowledged problems on backend
<bot>: generate_report: Bob: your report is ready: http://<url>
<bot>: icinga2: SOLVED high load on backend
32. Copyright example42 GmbH - 2016
Collaborative
Communication
Martin Alfke
example42 GmbH
!
we are .... not ... yet ...
hiring ...
!
but building a Puppet Expert
Network