Open Source vs. Commercial Tools Panel
summary
Panel compares real tradeoffs: total cost of ownership includes staff time to build and maintain vs vendor support, Ansible and YAML/Jinja/Python plus REST APIs are the common stack, and one customer moves to a commercial product and deploys in two months when timelines compress. Expect to instrument prechecks postchecks and logging because automation failures are inevitable and troubleshooting demands visibility so this group favors a buy borrow build mix with Ansible at the center and an always-logging strategy.
AI-written summary · about
chapters (7)
- 0:00Introduction to panel
- 1:06Cost comparison and TCO
- 5:59Timeline and implementation speed
- 11:13Staff expertise and education
- 16:28Target customer personas
- 21:24Troubleshooting differences
- 24:31Summary and final thoughts
related talks
01h 01mEngineering Panel Finale: A Tale of Different Network Automation Perspectives
50mJust Enough Network Automation to Get You Started
46mBuild, buy, or use open source? All your answers in one chart
38mPanel: Open Source Management Based on Open Source
41mOpen-Source: Open Choice – A DevOps Guide for OSS Adoption
38mOpen-Source - Open Choice: A DevOps Guide for OSS Adoption
30mAdventures with Open Source Business Models
30mIs Building an Observability Platform with Open Source the Right Choice?
