# Software Gone Wild Published articles for Software Gone Wild. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Using netlab in Software Testing with Dinesh Dutt DevFeed: [Using netlab in Software Testing with Dinesh Dutt]() Original publisher: [Read original article]() Published: 2026-08-28T06:26:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Software Testing](), [networking](), [software-development](), [Ansible](), [Vagrant]() Tags: [ansible](), [development](), [netlab](), [network](), [networking](), [podcast](), [software](), [software-development](), [software-gone-wild](), [software-testing](), [testing]() ### AI overview This article introduces Episode 208 of Software Gone Wild, a conversation about using netlab to test network management software. It discusses how netlab helps Stardust Systems test new SuzieQ features, along with related history involving Vagrant and Ansible. ### Source excerpt I know a few software development companies use netlab to test their network management software (and contribute back to netlab - thanks a million!), and I always wanted to chat about that. As I have known Dinesh Dutt for ages, it wasn't hard to decide who to invite to have that chat with ;) As it turns out, it's dangerous to put Dinesh1 and me in the same (virtual) room - we were all over the place, from the ancient history of Vagrant in networking labs to the recent Ansible woes, but we did manage to cover how netlab helps Stardust Systems test new SuzieQ features. Read more ... ## AI in Networking with Andrew Yourtchenko DevFeed: [AI in Networking with Andrew Yourtchenko]() Original publisher: [Read original article]() Published: 2026-06-12T06:41:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Artificial Intelligence](), [networking](), [Cisco](), [Deployment]() Tags: [ai](), [cisco](), [deployment](), [networking](), [podcast](), [software-gone-wild]() ### AI overview This episode discusses AI in networking with Andrew Yourtchenko, whose background includes automating Cisco Live networking infrastructure and contributing to IPv6 deployment through Happy Eyeballs. The speakers describe themselves as cautious optimists who recognize limitations in emerging AI tools. ### Source excerpt I always wanted to find someone who is more positive about AI than I am, while having solid "can deliver working stuff at scale" credentials. Andrew Yourtchenko definitely fits the bill. I first met him (online) when he was still an engineer in Cisco TAC, and when we finally met in person, he was busy automating the deployment of Cisco Live networking infrastructure. He was also instrumental in bringing us closer to ubiquitous IPv6 deployment with Happy Eyeballs. Read more ... ## State of Network Automation with Urs Baumann DevFeed: [State of Network Automation with Urs Baumann]() Original publisher: [Read original article]() Published: 2026-04-24T06:41:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Network](), [Artificial Intelligence]() Tags: [ai](), [automation](), [engineering](), [network](), [network-automation](), [podcast](), [software-gone-wild]() ### AI overview The author discusses the limited progress in network automation with Urs Baumann, who says he can still use the same presentation slides created a decade ago. They also discuss the potential impact of AI on network engineering after Baumann completed a master's thesis on the subject. ### Source excerpt I stopped tracking the (lack of) progress in network automation years ago, when I realized I had nothing new to say. As an eternal optimist, I hoped I was just missing something, but Urs Baumann (the guest of Software Gone Wild Episode 206) destroyed my hopes when he said, "I can still use the same slides I created 10 years ago". On a more positive note, he recently completed his Master's thesis on AI in network engineering, so we ended with a nice chat on its potential impact. Read more ... ## Network Device Telemetry Protocols with Dinesh Dutt DevFeed: [Network Device Telemetry Protocols with Dinesh Dutt]() Original publisher: [Read original article]() Published: 2026-03-13T06:41:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [telemetry](), [Network](), [NETCONF](), [Software]() Tags: [automation](), [netconf](), [network](), [podcast](), [software-gone-wild](), [telemetry]() ### AI overview Episode 205 of Software Gone Wild discusses why network operators may use screen scraping instead of protocols such as NETCONF, gNMI, or protobufs. The conversation examines the gap between vendor recommendations and operational reality with Dinesh Dutt. ### Source excerpt Whenever I'm ranting about vendors changing their data models or APIs with every other release, there is inevitably a vendor engineer chiming in, saying, "Life would be so much better if the customers wouldn't insist on doing screen scraping for the last 50 years." While some of that screen scraping is pure inertia, we sometimes have good reasons to do it rather than use protocols like NETCONF, gNMI, or protobufs. In Episode 205 of Software Gone Wild, I'm discussing some of those reasons and exploring the gap between vendor theory and reality with Dinesh Dutt, who is unlucky enough to have become the world's foremost expert on crappy network telemetry. Read more ... ## Infrahub with Damien Garros DevFeed: [Infrahub with Damien Garros]() Original publisher: [Read original article]() Published: 2026-01-16T06:47:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Automation](), [Database](), [Network]() Tags: [automation](), [database](), [graph-database](), [network-automation](), [podcast](), [software-gone-wild](), [tool]() ### AI overview A podcast discussion with Damien Garros examines Infrahub, a network automation tool, including its purpose, intended users, and use of a graph database. ### Source excerpt Why do we need Infrahub, another network automation tool? What does it bring to the table, who should be using it, and why is it using a graph database internally? I discussed these questions with Damien Garros, the driving force behind Infrahub, the founder of OpsMill (the company developing it), and a speaker in the ipSpace.net Network Automation course. Listen to the podcast ## IETF v6ops Working Group with Nick Buraglio DevFeed: [IETF v6ops Working Group with Nick Buraglio]() Original publisher: [Read original article]() Published: 2025-12-11T07:03:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Internet Engineering Task Force (IETF)](), [Networks](), [Deployment]() Tags: [ietf](), [ipv6](), [networks](), [podcast](), [software-gone-wild]() ### AI overview This article discusses why the IETF v6ops Working Group remains active 30 years after the first IPv6 specifications. It highlights the group's work on guidelines for deploying and operating IPv6 networks and references Nick Buraglio's answers in Episode 203 of the Software Gone Wild podcast. ### Source excerpt The first IPv6 specs were published in 1995, and yet 30 years later, we still have a pretty active IETF working group focused on "developing guidelines for the deployment and operation of new and existing IPv6 networks." (taken from the old charter; they updated it in late October 2025). Why is it taking so long, and what problems are they trying to solve? Nick Buraglio, one of the working group chairs, provided some answers in Episode 203 of the Software Gone Wild podcast. Read more ... ## Working for a Vendor with David Gee DevFeed: [Working for a Vendor with David Gee]() Original publisher: [Read original article]() Published: 2025-10-07T06:23:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [Development](), [C](), [Assembly]() Tags: [assembly](), [c](), [development](), [networking](), [podcast](), [software-gone-wild]() ### AI overview An interview with David Gee examines his career across system integrators, networking vendors, software vendors, and his own systems integration business. The article also includes his reflections on creating software, learning from flawed code, and an early control-system project written in C and assembly. ### Source excerpt When I first met David Gee, he worked for a large system integrator. A few years later, he moved to a networking vendor, worked for a few of them, then for a software vendor, and finally decided to start his own system integration business. Obviously, I wanted to know what drove him to make those changes, what lessons he learned working in various parts of the networking industry, and what (looking back with perfect hindsight) he would have changed. Read more ... ## Labbing Network Technology Details with netlab DevFeed: [Labbing Network Technology Details with netlab]() Original publisher: [Read original article]() Published: 2025-09-10T08:08:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [Open Source](), [configuration](), [Orchestration](), [Development]() Tags: [configuration](), [development](), [documentation](), [github](), [netlab](), [network](), [networking](), [open-source](), [orchestration](), [podcast](), [software-gone-wild]() ### AI overview This episode of Software Gone Wild discusses how Ethan Banks uses the open-source netlab tool to quickly check technology details for his N is for Networking podcast. The discussion covers network lab environments, YAML configuration, orchestration, multi-vendor configurations, community contributions, documentation, and user experience. ### Source excerpt It's been over four years since I published the last Software Gone Wild episode. In the meantime, I spent most of my time developing an open-source labbing tool, so it should be no surprise that the first post-hiatus episode focused on a netlab use case: how Ethan Banks (of the PacketPushers fame) is using the tool to quickly check the technology details for his N is for Networking podcast. As expected, our discussion took us all over the place, including (according to Riverside AI): Read more ...