Collaborative communication

29
Copyright example42 GmbH - 2016 Collaborative Communication Martin Alfke <[email protected]>

Transcript of Collaborative communication

Page 1: Collaborative communication

Copyright example42 GmbH - 2016

Collaborative Communication

Martin Alfke <[email protected]>

Page 2: Collaborative communication

Copyright example42 GmbH - 2016

– James Fryman @jfryman

“Bringing the work you are already doing ... !

... into the conversations you are already having”

Page 3: Collaborative communication

Copyright example42 GmbH - 2016

Communication

!

!

!

!

• “You cannot not communicate.” Paul Watzlawick

Page 4: Collaborative communication

Copyright example42 GmbH - 2016

Communication!

!

!

!

• Communication is transmission of information from a source to a receiver without loss of information

Page 5: Collaborative communication

Copyright example42 GmbH - 2016

Communication

• One can talk all day without saying anything.

Page 6: Collaborative communication

Copyright example42 GmbH - 2016

Communication

Page 7: Collaborative communication

Copyright example42 GmbH - 2016

Ancient Times

• Pictures

• Alphabet

• Carved in stones

• Invention of paper

Page 8: Collaborative communication

Copyright example42 GmbH - 2016

Modern Times

• Phone

• SMS

• EMail

Page 9: Collaborative communication

Copyright example42 GmbH - 2016

More Modern• ICR

• XMPP/Jabber

• Twitter

• Slack

• ...

Page 10: Collaborative communication

Copyright example42 GmbH - 2016

Collaboration

• Split work load

• Different expertise levels

• Support and train less experienced team members

• Share learning experiences

Page 11: Collaborative communication

Copyright example42 GmbH - 2016

Collaboration• Pair Programming

• 4-eyes principle

• DevOps / OpsDev

• NetOps / OpsNet

• DevNet / NetDev

Page 12: Collaborative communication

Copyright example42 GmbH - 2016

Communication in IT• System stati

• Monitoring

• Build Chain

• Tickets

• Communication

• Email

• XMPP

Page 13: Collaborative communication

Copyright example42 GmbH - 2016

Communication in IT

• need for Monitor wall

• need for large screens

• unsuited for remote work (unless home office)

Page 14: Collaborative communication

Copyright example42 GmbH - 2016

Combining Communication!

!

!

!

• Dashboards (maybe rolling)

• multiple sources of information

Page 15: Collaborative communication

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?)

Page 16: Collaborative communication

Copyright example42 GmbH - 2016

Aligning Communication• API-fied applications

• Jira

• Jenkins

• Icinga2

• Puppet

• ...

Page 17: Collaborative communication

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)

Page 18: Collaborative communication

Copyright example42 GmbH - 2016

Aligning Communication

• GNU approach

• one tool does one thing only

• second things are done with a new tool

Page 19: Collaborative communication

Copyright example42 GmbH - 2016

Communication Simplyfied• One tool to combine everything

!

!

!

!

Page 20: Collaborative communication

Copyright example42 GmbH - 2016

Communication Simplyfied• One tool to combine everything

• Monitor analysis, acknowledgement, downtime

• Deployment

• CfgMgmt run

• Generate reports and graphs

• Trigger CI

Page 21: Collaborative communication

Copyright example42 GmbH - 2016

Communication - OldJohn: Hi Ben, have you seen 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.

Page 22: Collaborative communication

Copyright example42 GmbH - 2016

Communication - NewBob: <bot> generate_report year 2014

<bot>: generating report

<bot>: PROBLEM high load on backend: 8.5

John: Hi Bob, please do not run this report during peak hours.

Bob: Oh. Sorry.

John: <bot> icinga ack -s backend

<bot>: acknowledged problems on backend

<bot>: your report is ready: http://<url>

<bot>: SOLVED load on backend

Page 23: Collaborative communication

Copyright example42 GmbH - 2016

Communication Helper

• Hubot - NodeJS

• Lita - Ruby

• Err - Python

Page 24: Collaborative communication

Copyright example42 GmbH - 2016

ChatOps Tools

• Generic helper with multiple backends (collaboration endpoints) and helpers (work scripts)

Page 25: Collaborative communication

Copyright example42 GmbH - 2016

Demo

• Lita

• XMPP - Prosody

• CI - Jenkins

• Monitoring - Icinga2

Page 26: Collaborative communication

Copyright example42 GmbH - 2016

Discussion

• Flexibility vs. Security

• Needs coding and adoption to infrastructure

Page 27: Collaborative communication

Copyright example42 GmbH - 2016

Links

• Hubot: https://hubot.github.com/

• Lita: https://www.lita.io/

• Err: http://errbot.io/

Page 28: Collaborative communication

Copyright example42 GmbH - 2016

More Links• http://www.slideshare.net/jhand2/chat-ops-a-beginners-

guide?next_slideshow=1

• http://www.slideshare.net/EvanPowell/some-chat-ops-what

• http://code.oursky.com/human-and-cat-friendly-chatops/

• https://zachholman.com/talk/move-fast-break-nothing/

• http://www.slideshare.net/VictorOps/real-world-chatops

• http://devops.com/2014/07/16/chatops-communicating-speed-devops/

Page 29: Collaborative communication

Copyright example42 GmbH - 2016

Collaborative Communication

Martin Alfke <[email protected]>