1 / 36

WEBINAR Evolve Thyself — How Operators Become Developers

WEBINAR Evolve Thyself — How Operators Become Developers. Chris Gardner, Senior Analyst Robert Stroud, Principal Analyst. November 6, 2017. Call in at 12:55 p.m. Eastern time. Chris Gardner. Senior Analyst, Infrastructure & Operations Professionals.

tdenham
Download Presentation

WEBINAR Evolve Thyself — How Operators Become Developers

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WEBINAREvolve Thyself — How Operators Become Developers Chris Gardner, Senior Analyst Robert Stroud, Principal Analyst November 6, 2017. Call in at 12:55 p.m. Eastern time.

  2. Chris Gardner Senior Analyst, Infrastructure & Operations Professionals Chris Gardner serves infrastructure and operations professionals as they face the unique opportunities and challenges of migrating business technology into modern, software-defined environments. He specializes in treating elements of infrastructure systems like developers treat their apps: individual pieces of code that can be dynamically shaped and remolded to handle changing business needs at will.

  3. Robert Stroud CGEIT CRISC Principal Analyst, Infrastructure & Operations Professionals Robert Stroud focuses on helping clients navigate the dynamic business transformation and the IT transformation required to deliver agility at high velocity with exceptional quality. A recognized industry leader, speaker, and contributor to multiple best practices and standards, Robert drives thought leadership in the rapidly growing DevOps and continuous deployment domains, assisting clients with their DevOps and continuous deployment transformations as they adopt technologies and practices such as continuous delivery, release automation, organization transformation, and leveraging emerging technologies such as open source and cloud.

  4. Agenda • How infrastructure-as-code (IaC) has changed everything • Becoming a developer: going from roadblock to enabler • The criticality of automation

  5. I started my career as a system admin in the NYC metropolitan area. Speaking to clients and my former peers, I&O has dramatically changed.

  6. Needed in the past: “Deep knowledge of my silo” “Specialization in particular tech” “Proprietary expertise” Needed in the future: “I need to know how to program.” “Products, not projects” “Automate everything.”

  7. Agenda • How infrastructure-as-code (IaC) has changed everything • Becoming a developer: going from roadblock to enabler • The criticality of automation

  8. Infrastructure-as-code is here to stay • What is it? • Software defined • Public and private cloud • Accessible from anywhere • Critical element of continuous delivery • It is impossible to find infrastructure today that is not in some way software defined.

  9. Forrester sees evolution in this space Source: Lead The I&O Software Revolution With Infrastructure-As-CodeForrester report

  10. Infrastructure is now defined by models Source: Lead The I&O Software Revolution With Infrastructure-As-CodeForrester report

  11. The positives • Infrastructure-as-code = ultimate abstraction • Rapidly expanding usage in hybrid cloud environments • Why IaC? • Flexibility • Manageability • Agility • Lower total cost of ownership

  12. The negatives • Sprawl leads to cost inefficiencies. • Configuration drift may break critical applications. • Compliance • PII • GDPR • SOX

  13. Agenda • How infrastructure-as-code (IaC) has changed everything • Becoming a developer: going from roadblock to enabler • The criticality of automation

  14. The changing role of I&O

  15. Breaking down silos Source: Reform Legacy Operations For Composable Infrastructure Forrester report

  16. Cross-pollination Source: How A Sysadmin Becomes A Developer Forrester report

  17. Becoming a developer — languages • Scripts aren’t development. • Error prone • Minimal controls • APIs for software-defined: • Integration • Network • Storage • Containers and cloud • Configuration management DSL is a good place to start.

  18. Becoming a developer — continuous integration • Infrastructure definitions must be stored and recalled from source code repository. • Version control allows easy rollback. • Changes must be automatically tested across the SDLC.

  19. Becoming a developer — continuous delivery • Manage across the SDLC. • The excuse of “it worked on my machine” is dead. • Deploy through automation — no manual activities.

  20. Becoming a developer — Lean and Agile • Value-stream mapping — optimize • Smaller work packages with dynamic feedback • Product releases, not projects

  21. Organizational goal: integrated product teams Source: Optimize Your Cloud Organization For Speed And Customer Delight Forrester report

  22. Automated deployment of releases, not components Source: A Dangerous Disconnect: Executives Overestimate DevOps MaturityForrester report

  23. Source: The Quest For Speed-Plus-Quality Drives Agile And DevOps Tool Selection Forrester report

  24. Agenda • How infrastructure-as-code (IaC) has changed everything • Becoming a developer: going from roadblock to enabler • The criticality of automation

  25. Manual infrastructure management doesn’t cut it anymore • Modern infrastructure management requires automation. • Individuals cannot manage thousands of instances manually.

  26. Automated systems management is one of the top priorities for global technology infrastructure decision makers.

  27. Giving up control — not necessarily a bad thing • Automation makes the operations team available for value-add! • Removal of the “fat finger” • Balance

  28. You need to help the “bad good guys”

  29. Good and bad infrastructure automation • Good: • Automatic changes • Minimal or no approvals for minor changes • Consistent models from dev to production • Cross-silo • Bad: • Manual changes • Approvals for all changes, regardless of criticality • Inconsistent models at different levels • Siloed workforce

  30. Ranking infrastructure automation solutions Source: The Forrester Wave™: Configuration Management Software For Infrastructure Automation, Q4 2017 Forrester report

  31. Ranking continuous delivery and release automation Source: The Forrester Wave™: Continuous Delivery And Release Automation, Q3 2017 Forrester report

  32. Q&A

  33. New: Forrester Insights for Android NOW AVAILABLE ON GOOGLE PLAY Download Forrester’s new Insights app for Android to: • Access research, insights, and key takeaways to accelerate your projects and support your decision making. • Save reports and graphics to read on the device of your choice. • Receive notifications to stay abreast of the latest trends and insights relevant to your initiatives. Also available for iOS forrester.com/app

  34. Robert Stroud rstroud@forrester.com Twitter: @RobertEStroud Chris Gardner chgardner@forrester.com Twitter: @crsmgardner

More Related