Collaborative Communication. Martin Alfke

Transcription

1 Collaborative Communication Martin Alfke

2 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 Bringing the work you are already doing into the conversations you are already having James

4 Communication... you cannot not communicate Paul Watzlawick

5 Communication... you cannot not communicate but you can not communicate accurately. Paul Watzlawick

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

7 Communication But: one can talk all day without saying anything.

8 Communication

9 Ancient Times Pictures Alphabet Carved in stones Invention of paper

10 Modern Times Phone SMS

11 More Modern IRC XMPP/Jabber Twitter Slack...

12 Collaboration Split work load Different expertise levels Support and train less experienced team members Share learning experiences

13 Collaboration Pair Programming 4-eyes principle DevOps / OpsDev NetOps / OpsNet DevNet / NetDev

14 Communication in IT System stati Monitoring Build Chain Tickets Communication XMPP

15 Communication in IT need for Monitor wall need for large screens how to do that for remote work (home office)?

16 Combining Communication Dashboards (maybe rolling) multiple sources of information

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

18 Aligning Communication API-fied applications Jira Jenkins Icinga2 Puppet...

19 Aligning Communication API requirements Authentication Authorization Error Handling Feedback...

20 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 Aligning Communication GNU approach one tool does one thing only second things are done with a new tool

22 Communication Simplyfied One tool to combine everything

23 Communication Simplyfied One tool to combine everything Monitoring status, acknowledgement, downtime CfgMgmt run Generate reports and graphs Trigger CI...

24 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 Communication - New Bob: <bot> generate_report year <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: <bot>: icinga2: SOLVED high load on backend

26 Communication Helper Hubot - NodeJS Lita - Ruby Err - Python

27 ChatOps Tools Generic helper with multiple backends (collaboration endpoints) and helpers (work scripts)

28 Demo Lita XMPP - Prosody CI - Jenkins Monitoring - Icinga2

29 Discussion Flexibility vs. Security Needs coding and adoption to infrastructure

30 Links Hubot: Lita: Err:

31 More Links

32 Collaborative Communication Martin Alfke example42 GmbH we are... not... yet... hiring... but building a Puppet Expert Network

33 Collaborative Communication Martin Alfke example42 GmbH Q&A