Desktops, DevOps and Odd Socks - Chapter 2

Back in 2014 Glenn gave a presentation to his local DevOps community about the role Enterprise Desktop IT in DevOps community. Since then much has changed. Glenn has moved jobs, halfway across the world in fact, to work at Puppet (formerly PuppetLabs), a DevOps tooling company. In Chapter 2, Glenn will briefly revisit the role Desktop IT in Enterprise DevOps, and talk about where we can find some unlikely champions, or at least allies, of DevOps in traditional Enterprises.

Transcript

1. Desktops, DevOps, and Odd Socks
2. Before I begin….
3. Glenn Sarti • Senior Software Engineer at Puppet Specialising in Windows • 15 years in Desktop Engineering and IT Navy, Government, Mining, Finance • Windows DevOps advocate
4. Glenn Sarti • 14 years in Desktop Engineering and IT Navy, Government, Mining, Finance • Half Developer, half Ops • Last 8 months learning DevOps and tools
6. DevOps It’s all about servers and applications
7. DevOps Is it only about servers and applications?
8. What does Enterprise Desktop IT look like?
10. 2010 2011 2012 2013 Application Installs Desktops Builds Some stats… 684K 4,606 1.3M 8,962 947K 8,788  7,502
11. An application install every 24 seconds A desktop build started every 57 minutes
12. • Cross skilled • Customer centric • Desktop IT is ubiquitous • D.R.Y. and W.A.L. Culture of Desktop IT
13. So what can Desktop IT offer DevOps?
14. BE A FRIEND SOLVE PROBLEMS PROVIDE SUPPORT
15. So what can DevOps offer Desktop IT? *
17. • Long time between releases • Have version history but no control • Lots of moving parts PXE, WDS, SYSPREP , GPO, AD, DNS, DHCP , SCCM etc. Current Challenges
18. Treat the desktop build like an application
19. Continuous Delivery of Desktop
20. Continuous Delivery of Desktop Version Control
21. Continuous Delivery of Desktop Continuous Integration
22. Continuous Delivery of Desktop Quality Gates
23. Continuous Delivery of Desktop Automation
24. Continuously Delivered Desktop
25. Other DevOps lessons… • Use CM tools to build Desktop Infrastructure • Gather metrics for desktop unit and infrastructure performance • DevOps is thriving in the Windows eco system
26. What about other allies?
27. Audit and Compliance perhaps?
29. But it’s not quite true...
30. Joanne Molesky ThoughtWorks • Principal Consultant • IT Risk and Compliance • Accredited Auditor (CISA CRISC)
32. TLDR version Ways to help DevOps and Audit work together
33. Create a common understanding • Learn the language (Speak Audit) • Focus on the intent • Provide some documentation • Create visibility and transparency
34. Mind your Access • No account sharing • Least privilege • Guard your secrets • Guard your pipeline
35. Mind your Access • Appropriate approvals • Know your information • Clean up after yourself
36. Provide evidence • Automatable! • Turn on auditing features • Protect logs
37. Risk based approach to change • Not CAB for everything • Define the criteria for risk Low, medium and high • Reduce risk with practise
38. Measure things that matter • What is the outcome? • Have we reduced risks? • Are we getting better?
39. Take responsibility • Know your business • Know the risks • Seek frequent feedback • Act accordingly
40. Reasonable requests?
41. What about ITIL?
43. But it’s not quite true...
44. Jason Gray BankWest • Head of Service Integrity • ITIL 2011 expert • Agile – ICAgile Prof. Cert.
45. Jason Gray Agile, Continuous Delivery, devops… Friend or Foe??? LEADit – Service Management 2014 http://c.ymcdn.com/sites/www.itsmf.org.au/resource/resmgr/Docs/503_gray_jason_140813.pdf
50. Sound familiar?
51. What about something more generic?
53. Effective DevOps Jennifer Davis & Katherine Daniels • Should be in everyone’s DevOps Library!
54. Four Pillars • Collaboration • Affinity • Tools • Scaling
55. Four Pillars • Collaboration • Affinity • Tools • Scaling
56. Collaboration Empathy and Trust
57. Collaboration - Empathy • Listening • Asking Questions • Imagining Other’s perspectives • Appreciate individual differences
59. Collaboration - Trust • Swift Trust • Self-disclosure • Trust but verify • Perception of fairness
60. Collaboration - Trust Why is trust important?
61. Collaboration - Trust The five dysfunctions of a team “Dysfunction #1: Absence of Trust”
63. The future
65. @glennsarti http://glennsarti.github.io/ https://speakerdeck.com/glennsarti All images are copyright of their respective owners