# network automation Published articles for network automation. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Building for the AI era: Inside Cisco IT's Wi-Fi 7 revolution DevFeed: [Building for the AI era: Inside Cisco IT's Wi-Fi 7 revolution]() Original publisher: [Read original article]() Author: Chris Tomazic Published: 2026-09-14T13:00:21Z Content type: article Language: en Sources: [Cisco Blogs]() Topics: [Wi-Fi 7](), [Cisco IT](), [cisco networking](), [networking](), [Deployment](), [Latency](), [Security](), [Authentication]() Tags: [authentication](), [cisco-catalyst-center](), [cisco-it](), [cisco-meraki](), [cisco-networking](), [cisco-on-cisco](), [deployment](), [enterprise-networking](), [infrastructure](), [latency](), [network-automation](), [networking](), [security](), [wi-fi-7]() ### AI overview Cisco IT describes a global Wi-Fi 7 rollout for 90,000 employees and hundreds of facilities. Its integrated Cisco networking portfolio, prior preparation with Wi-Fi 6 and 6E, certificate-based authentication, and Meraki Dashboard experience helped make the upgrade routine, seamless, and free of downtime. ### Source excerpt Cisco IT upgraded to Wi-Fi 7 for 90,000 employees with zero downtime and record speed. See how a fully integrated Cisco networking stack, built for the AI era, made a complex global rollout simple and seamless. ## Scrapli vs Nornir: What's the Difference DevFeed: [Scrapli vs Nornir: What's the Difference]() Original publisher: [Read original article]() Author: Roger Perkin Published: 2026-08-06T11:08:45Z Content type: comparison Language: en Sources: [Roger Perkin Network Automation Consultant]() Topics: [Python](), [Network](), [async](), [NETCONF](), [ssh]() Tags: [async](), [netconf](), [network-automation](), [python](), [scrapli](), [ssh](), [vs]() ### AI overview This comparison explains that Scrapli and Nornir address different layers of Python network automation rather than directly competing. It describes Scrapli as a connection-focused library for communicating with individual network devices and notes its support for SSH, Telnet, NETCONF, synchronous and asynchronous operation, and structured output. ### Source excerpt If you've spent any time in the Python network automation world, you'll have bumped into both Scrapli and Nornir. They come up in the same conversations, the same blog posts and the same job specs, so it's natural to line them up and ask: which one should I use? It's a fair question, but it's built on a slightly ... ## What are the best platforms for network automation? DevFeed: [What are the best platforms for network automation?]() Original publisher: [Read original article]() Author: Roger Perkin Published: 2026-07-24T08:25:02Z Content type: article Language: en Sources: [Roger Perkin Network Automation Consultant]() Topics: [Network](), [Automation](), [Ansible](), [Orchestration](), [awx](), [Low code]() Tags: [ansible](), [automation](), [awx](), [faq](), [low-code](), [nautobot](), [network](), [network-automation](), [orchestration](), [red-hat](), [source-of-truth]() ### AI overview The article lists Nautobot, Itential, Ansible, AWX, and Red Hat Ansible Automation Platform as network automation platforms. It states that they serve different purposes, including configuration, orchestration, source of truth and inventory, and enterprise low-code use cases. ### Source excerpt The best platforms for network automation include Nautobot, Itential, Ansible, AWX, Red Hat Ansible Automation Platform to name a few. Each one serves a different purpose including configuration and orchestration, source of truth and inventory and enterprise low code. Check out my dedicated post on network automation platforms ## Network Automation Platforms: Nautobot, Itential, Cisco NSO, and Juniper Apstra DevFeed: [Network Automation Platforms: Nautobot, Itential, Cisco NSO, and Juniper Apstra]() Original publisher: [Read original article]() Author: Roger Perkin Published: 2026-07-23T12:26:21Z Content type: comparison Language: en Sources: [Roger Perkin Network Automation Consultant]() Topics: [Automation](), [Network](), [Software](), [configuration](), [Open Source](), [Orchestration](), [Provisioning]() Tags: [2026](), [configuration](), [nautobot](), [network](), [network-automation](), [open-source](), [orchestration](), [platforms](), [provisioning]() ### AI overview This comparison describes network automation platforms for configuring, deploying, and managing network infrastructure. It presents Nautobot as an open-source source-of-truth and automation platform, followed by commercial offerings including Itential, Cisco NSO, and Juniper Apstra. ### Source excerpt Network Automation Platforms are software systems that automate and orchestrate the configuration, deployment, and management of network infrastructure. Unlike network automation tools which are software applications that automate specific tasks. Free Network Automation Platforms 1. Nautobot Nautobot is an open-source Network Source of Truth (NSoT) and Automation Platform. It provides a flexible data model to ... ## How AI Is Changing DevOps Without Replacing It DevFeed: [How AI Is Changing DevOps Without Replacing It]() Original publisher: [Read original article]() Author: Roger Perkin Published: 2026-07-15T22:15:13Z Content type: opinion Language: en Sources: [Roger Perkin Network Automation Consultant]() Topics: [DevOps](), [Artificial Intelligence](), [Automation](), [Network]() Tags: [ai](), [automation](), [devops](), [engineering](), [faq](), [network-automation](), [testing]() ### AI overview The article argues that AI is changing DevOps by accelerating tasks, assisting with code and content generation, and improving efficiency, while the discipline's core needs remain. It presents AI as an assistant for network automation teams rather than a replacement for design, implementation, testing, and engineering judgment. ### Source excerpt No, DevOps is not dead because of AI. If anything, AI is changing how DevOps teams work by speeding up tasks, assisting with code and content generation, and improving efficiency. The core DevOps problems still exist: teams need reliable delivery, good collaboration, strong automation, and clear operational ownership. AI can help with some of those ... ## No Lab, No Problem: Record CML2 Devices into pyATS Mocks for CI DevFeed: [No Lab, No Problem: Record CML2 Devices into pyATS Mocks for CI]() Original publisher: [Read original article]() Author: Brent Leekley Published: 2026-06-27T00:00:00Z Content type: tutorial Language: en Sources: [brent.leekley.me blog]() Topics: [GitHub Actions](), [Testing](), [GitHub](), [Network]() Tags: [ci](), [ci-cd](), [cisco](), [cisco-modeling-labs](), [cml](), [cml2](), [genie](), [github-actions](), [mock-devices](), [network-automation](), [network-testing](), [ospf](), [playback](), [pyats](), [record-and-replay](), [testing](), [unicon]() ### AI overview This tutorial explains how to record responses from real Cisco Modeling Labs 2 devices with pyATS and unicon, commit the recordings, and replay the same test suite in GitHub Actions. Replay allows the tests to run offline without booting or connecting to the lab. ### Source excerpt Develop against the live CML2 lab, then record it once with unicon playback and replay the exact same pyATS suite in GitHub Actions with no lab to license or reach. Point the testbed at an unreachable address and the suite still passes, because replay never opens a socket. Includes a real companion repo with a green Actions run. Fourth in a pyATS + CML2 network programmability series. ## The Snapshot Machine: genie learn and diff as a Change-Validation Safety Net on CML2 DevFeed: [The Snapshot Machine: genie learn and diff as a Change-Validation Safety Net on CML2]() Original publisher: [Read original article]() Author: Brent Leekley Published: 2026-06-22T00:00:00Z Content type: tutorial Language: en Sources: [brent.leekley.me blog]() Topics: [networking](), [Cisco](), [Routing (disambiguation)](), [Structured-data](), [Command-line interface]() Tags: [change-validation](), [cisco](), [cisco-modeling-labs](), [cli](), [cml2](), [genie](), [genie-diff](), [genie-learn](), [maintenance-window](), [network-automation](), [network-testing](), [ospf](), [pyats](), [routing-table](), [snapshot](), [structured](), [validation]() ### AI overview This tutorial demonstrates using Cisco Modeling Labs 2 with Genie learn and diff to validate network changes. It snapshots structured operational state before and after a maintenance change, then compares the snapshots to reveal side effects that routine show commands may miss. The source summary reports that a changed OSPF cost reroutes three destinations while adjacencies remain FULL. ### Source excerpt Snapshot a CML2 fabric with genie learn before and after a maintenance change, then genie diff the structured state. One fat-fingered OSPF cost quietly reroutes three destinations while every adjacency stays FULL. Structured before-and-after diffs catch the side effects that show commands miss. ## Structure Network Operations Around Teams, Not Heroes DevFeed: [Structure Network Operations Around Teams, Not Heroes]() Original publisher: [Read original article]() Published: 2026-06-16T06:06:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Networks](), [Network](), [Automation]() Tags: [article](), [automation](), [network](), [network-automation](), [networks](), [operations](), [teams](), [worth-reading]() ### AI overview An article argues that network operations should be structured around teams rather than individual heroes, suggesting that hero-dependent cultures can make network automation harder to deploy. ### Source excerpt Chris Grundemann wrote an interesting article arguing that you should structure your network operations around teams, not heroes. Even if you feel you're perfectly OK with your network being held together by exhausted heroes (and duct tape), it could be a bit harder to deploy network automation in an always-busy hero culture. However, the choice, as they say, is yours. ## From Intent to Reality: Driving pyATS Tests from NetBox Against a CML2 Fabric DevFeed: [From Intent to Reality: Driving pyATS Tests from NetBox Against a CML2 Fabric]() Original publisher: [Read original article]() Author: Brent Leekley Published: 2026-06-15T00:00:00Z Content type: tutorial Language: en Sources: [brent.leekley.me blog]() Topics: [NetBox](), [Network](), [Cisco](), [data](), [Structured-data]() Tags: [cisco-modeling-labs](), [cml](), [cml2](), [custom-fields](), [genie](), [ids](), [intent-based-networking](), [netbox](), [network](), [network-automation](), [network-testing](), [ospf](), [pyats](), [pynetbox](), [router-id](), [source-of-truth](), [spine-leaf](), [structured](), [testbed]() ### AI overview This tutorial shows how to store declared OSPF router-IDs in NetBox and use Cisco pyATS to compare them with the router-IDs on a live CML2 spine-leaf fabric. The comparison turns network intent validation into a pass-or-fail test. ### Source excerpt NetBox holds the intent (declared OSPF router-IDs), a CML2 spine-leaf is the network under test, and pyATS is the judge. Close the loop and prove the live network matches what you said it should be, with real pass and fail output. ## Build the Lab Once, Test It Forever: A CML2 Spine-Leaf Wired for pyATS DevFeed: [Build the Lab Once, Test It Forever: A CML2 Spine-Leaf Wired for pyATS]() Original publisher: [Read original article]() Author: Brent Leekley Published: 2026-06-14T00:00:00Z Content type: tutorial Language: en Sources: [brent.leekley.me blog]() Topics: [Network](), [Testing](), [Cisco](), [Code](), [API](), [Parser]() Tags: [api](), [cisco](), [cisco-modeling-labs](), [cml](), [cml2](), [code](), [genie](), [iol-xe](), [network-automation](), [network-testing](), [ospf](), [parsing](), [pyats](), [spine-leaf](), [testbed](), [virl2-client]() ### AI overview This tutorial describes a four-node spine-leaf lab in Cisco Modeling Labs 2 (CML2) that generates a Cisco pyATS testbed from the CML API. The approach treats the lab definition as the source of truth so regenerated inventories remain aligned with topology changes, and uses an OSPF underlay with a management network. ### Source excerpt Stop hand-maintaining your pyATS testbed. Build a four-node spine-leaf in CML2 as code, then generate the testbed straight from the CML API so it never drifts from the lab, with live Genie-parsed proof over a System Bridge management network. ## Using an AI Agent and MCP to Build and Verify Cisco Modeling Labs Network Labs DevFeed: [Using an AI Agent and MCP to Build and Verify Cisco Modeling Labs Network Labs]() Original publisher: [Read original article]() Author: Brent Leekley Published: 2026-06-10T00:00:00Z Content type: tutorial Language: en Sources: [brent.leekley.me blog]() Topics: [AI Agent](), [Model Context Protocol](), [Cisco](), [Claude](), [Network](), [API]() Tags: [agent](), [ai-agents](), [api](), [cat9000v](), [cisco-modeling-labs](), [claude](), [cml](), [cml-mcp](), [mcp](), [mcp-server](), [model-context-protocol](), [network](), [network-automation](), [pyats]() ### AI overview This article explains how to use an AI agent through the Model Context Protocol to build and verify network labs in Cisco Modeling Labs. It discusses CML 2.10's first-party MCP server, natural-language lab creation, and verification workflows that observe network state and retry until OSPF adjacency converges. ### Source excerpt CML 2.10 ships a first-party MCP server, and Claude can now build and verify network labs. Field lessons from running an AI agent against Cisco Modeling Labs: dataplane readiness gates, the cat9000v interface trap, SSH host-key rotation, and guardrails that live in docstrings. ## SwiNOG 41: It Was Nice to Be Back DevFeed: [SwiNOG 41: It Was Nice to Be Back]() Original publisher: [Read original article]() Published: 2026-05-04T05:09:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [evpn](), [Artificial Intelligence](), [Automation](), [Testing]() Tags: [ai](), [conferences](), [e2e-testing](), [evpn](), [llms](), [network-automation](), [networking](), [pytest]() ### AI overview A personal recap of SwiNOG 41 in Switzerland, highlighting discussions and presentations on networking topics including transceiver power, shared spectrum, AI and LLMs in networking, EVPN gateways, network automation, and end-to-end testing with Netlab and pytest. ### Source excerpt Last week's SwiNOG was (as expected) great fun at a phenomenal location, starting with the first slide of the first presentation: "6 Stages of Network De-sh*tification". I particularly loved the "talk less, chat more" schedule. The longer breaks gave us plenty of time to catch up with old friends and discuss interesting, sometimes completely unexpected, topics. For example, I learned that SIP MESSAGE is used to carry SMS messages these days. As much as I loved chatting with fellow networking engineers, I also found these presentations highly interesting: 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 ... ## Talking About Pulumi and Network Automation DevFeed: [Talking About Pulumi and Network Automation]() Original publisher: [Read original article]() Author: Scott Lowe Published: 2026-03-24T14:00:00Z Content type: opinion Language: en Sources: [Scott's Weblog]() Topics: [Infrastructure as code](), [Network](), [Automation](), [Python]() Tags: [aws](), [cilium](), [cli](), [cloud](), [cni](), [containers](), [cri-o](), [devops](), [docker](), [go](), [iac](), [k8s](), [kubernetes](), [linux](), [network-automation](), [networking](), [oci](), [podcast](), [pulumi](), [python](), [security]() ### AI overview The article introduces a Network Automagic podcast episode about Pulumi, its infrastructure-as-code model using general-purpose programming languages, and its potential role in network automation. It specifically discusses using Pulumi with Python for network automation tasks. ### Source excerpt Heard about Pulumi, but aren't sure what it is? Maybe you know a little bit about Pulumi--like that it does infrastructure as code (IaC), but using general purpose programming languages--and you're wondering where it fits in a larger automation framework? Or maybe you're a network engineer just starting to dabble in network automation, and you're wondering if this Pulumi thing is something you should check out. If any of these apply to you, then the latest Network Automagic podcast episode is right up your alley. I recently had the opportunity to join Steinn Bjarnarson and Urs Baumann for an episode of Network Automagic. The focus of our discussion--although I will say we diverged a bit here and there--was on Pulumi, what it is, and whether it fits into a larger network automation framework. After all, if you can use general purpose programming languages like Python with Pulumi, why not just use Pulumi in a Python program that also does network automation stuff? All in all, recording the podcast with Steinn and Urs was great fun, and I hope that the final product ends up being helpful for folks. There's a variety of ways to listen in on the episode: Via the Network Automagic web site Via the Network Automagic channel on YouTube (here is a link to the specific episode) Via Spotify Via Apple Podcasts As you can see, there are plenty of options to listen (and a few that I didn't include--check the Network Automagic web site for more!). Thanks to Steinn and Urs for having me on the show! ## Presentation: netlab Overview and Use Cases (NetBCN) DevFeed: [Presentation: netlab Overview and Use Cases (NetBCN)]() Original publisher: [Read original article]() Published: 2026-03-05T08:24:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Network](), [Automation](), [Testing]() Tags: [automation](), [event](), [netlab](), [network-automation](), [presentation](), [prototyping](), [use-cases]() ### AI overview The article announces a presentation on netlab use cases delivered at the NetBCN event. The presentation covers examples involving rapid prototyping, testing network automation software, and working with vendor technical assistance. ### Source excerpt Yesterday, I had a short presentation on netlab use cases during the NetBCN event. It covered a dozen examples, from rapid prototyping to testing network automation software and arguing with vendor TAC. I added the "use cases" part of the presentation to the standard netlab presentation; you can view the results on ipSpace.net (no account or registration required). Explore ## Technology Short Take 191 DevFeed: [Technology Short Take 191]() Original publisher: [Read original article]() Author: Scott Lowe Published: 2026-02-27T14:00:00Z Content type: article Language: en Sources: [Scott's Weblog]() Topics: [networking](), [Ansible](), [Security](), [Infrastructure as code](), [Artificial Intelligence](), [Large Language Model](), [Containers](), [VXLAN]() Tags: [ai](), [ansible](), [aws](), [blog](), [cilium](), [cli](), [cloud](), [cni](), [containers](), [cri-o](), [devops](), [docker](), [go](), [gre](), [iac](), [k8s](), [kubernetes](), [linux](), [llm](), [network-automation](), [networking](), [oci](), [security](), [vxlan]() ### AI overview Technology Short Take 191 is a curated collection of commentary and links covering networking, network automation, security, cloud management, containers, operating systems, applications, AI adoption, and software vulnerabilities. ### Source excerpt Welcome to Technology Short Take #191! This is my semi-regular collection of links related to technology disciplines, including networking, security, cloud computing, storage, and programming/development. I hope that I've managed to curate an interesting and useful set of links for readers. Enjoy! Networking I learned a new acronym from Ivan Pepelnjak in his article on "not so passive" OPSFv2 interfaces in Cisco IOS/XR: QDS (Quick and Dirty Solution). I am totally using that from now on. Via Ivan (hat tip to my colleague Russ for pointing me in this direction), I also learned that all is not well in network automation land with Ansible. Although some parts of it are apparently now resolved, this does raise questions about the viability of Ansible for network automation. Doug Dawson talks about the new Amazon Eero Signal, a cellular backup to a primary broadband connection for users using their Eero mesh systems. I agree with Doug--the pricing seems high to me. I generally like the Eero devices, although there have been times when I really could use a bit more control over the settings. Security The APNIC blog features a guest article discussing the use of tunneling protocols to infiltrate networks. The article specifically discusses Generic Routing Encapsulation (GRE) and Virtual Extensible LAN (VXLAN). It's worth a read if your network uses either of these technologies. Cloud Computing/Cloud Management Somewhere along the way I missed the CDK deprecation announcement. If I am not mistaken, this leaves Pulumi as the only cloud-independent IaC tool that lets you use a general purpose programming language. Managing dependencies between containers can be difficult at times; this blog post by Nicolas Fränkel introduced me to wait4x, a tool one can use to help simplify these types of situations. Operating Systems/Applications I appreciated reading Mitchell Hashimoto's AI adoption journey. I feel it does provide a more realistic approach to how someone in a role like his m ## Why netlab uses its own device configuration templates DevFeed: [Why netlab uses its own device configuration templates]() Original publisher: [Read original article]() Published: 2026-01-22T07:14:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Automation](), [Network](), [configuration](), [gRPC]() Tags: [configuration](), [netlab](), [network](), [network-automation]() ### AI overview The article explains netlab's approach to device configuration generation. It describes transforming a high-level lab-topology model into device-level data and configurations, and discusses why the project uses a simpler model and Jinja2-based templates rather than relying on broader vendor or standards-based models. ### Source excerpt Petr Ankudinov made an interesting remark when I complained about how much time I wasted waiting for Cisco 8000v to boot when developing netlab device configuration templates: For Arista part - just use AVD with all templates included and ANTA for testing. I was always wondering why netlab is not doing that. Like any other decent network automation platform, netlab uses a high-level data model (lab topology) to describe the network. That data model is then transformed into a device-level data model, and the device-level data structures are used to generate device configurations. 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 ## Using netlab to Set Up Demos DevFeed: [Using netlab to Set Up Demos]() Original publisher: [Read original article]() Published: 2026-01-15T07:15:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Network](), [Automation](), [Containers](), [Ubuntu]() Tags: [apple](), [automation](), [containers](), [go](), [netlab](), [network-automation](), [ubuntu]() ### AI overview The article describes using netlab in an Ubuntu virtual machine to orchestrate Arista cEOS containers on an Apple Silicon laptop for quickly setting up a demo network. It also includes positive feedback about netlab's ability to create a functional automated network lab quickly. ### Source excerpt David Gee was time-pressed to set up a demo network to showcase his network automation solution and found that a Ubuntu VM running netlab to orchestrate Arista cEOS containers on his Apple Silicon laptop was exactly what he needed. I fixed a few blog posts based on his feedback (I can't tell you how much I appreciate receiving a detailed "you should fix this stuff" message, and how rare it is, so thanks a million!), and David was kind enough to add a delightful cherry on top of that cake with this wonderful blurb: Read more ... ## Ansible network configuration modules still fail to process Jinja2 templates DevFeed: [Ansible network configuration modules still fail to process Jinja2 templates]() Original publisher: [Read original article]() Published: 2025-12-16T07:28:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Ansible](), [Network Configuration](), [bug](), [networking]() Tags: [2025](), [ansible](), [bug](), [configuration](), [network-automation](), [networking](), [ubuntu]() ### AI overview The article argues that Ansible's network device configuration modules continued failing to process templated configurations after several releases. It also reports that templated configuration support in the network configuration modules is scheduled to disappear in January 2028, and that netlab now generates device configurations outside Ansible. ### Source excerpt A month ago, I described how Ansible release 12 broke the network device configuration modules, the little engines (that could) that brought us from the dark days of copy-and-paste into the more-survivable land of configuration templates. In the meantime, the Ansible networking team fixed the ansible.netcommon collection, but (according to that PR) the ability to process templated configurations directly in the network configuration modules is scheduled to disappear in January 2028 (more details). I moved on; netlab is now generating device configurations outside of Ansible. Three releases later (they just released 13.1), the same bug is still there (at least it was on a fresh Python virtual environment install I made on a Ubuntu 24.04 server on December 13th, 2025), making all device_config modules unusable (without changing your Ansible playbooks) for configuration templating. Even worse: Read more ... ## Network Automation Reality Check with William Collins DevFeed: [Network Automation Reality Check with William Collins]() Original publisher: [Read original article]() Published: 2025-08-28T06:20:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Network](), [Automation](), [Tool]() Tags: [automation](), [network](), [network-automation](), [podcast]() ### AI overview A podcast conversation with William Collins examines recurring network automation problems, including excessive focus on tools, narrow point solutions, and reliance on vendor-delivered outcomes without a broader perspective. ### Source excerpt In early August, William Collins invited me to chat about a sarcastic comment I made about a specific automation tool I have a love-hate relationship with on LinkedIn. We quickly agreed not to go (too deep) into tool-bashing. Instead, we discussed the eternal problems of network automation, from unhealthy obsession with tools to focus on point solutions while lacking the bigger picture or believing in vendor-delivered nirvana. Listen to the podcast ## SwiNOG 40: Trustworthy Network Automation DevFeed: [SwiNOG 40: Trustworthy Network Automation]() Original publisher: [Read original article]() Published: 2025-08-20T05:53:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Network](), [Automation](), [Testing]() Tags: [automation](), [declarative](), [network](), [network-automation](), [testing](), [version-control]() ### AI overview A SwiNOG 40 presentation by Damien Garros discusses principles for building trustworthy network automation, including idempotency, dry runs, transactional changes, declarative design, version control, and testing. ### Source excerpt The SwiNOG 40 event started with an interesting presentation on Building Trustworthy Network Automation (video) by Damien Garros (now CEO @ OpsMill) who discussed the principles one can use to build a trustworthy network automation solution, including idempotency, dry runs, and transactional changes. He also covered the crucial roles of the declarative approach, version control, and testing. If you have ever watched any of my network automation materials, you won't be surprised by anything he said, but if you're just starting your network automation journey, you MUST watch this presentation to get your bearings straight. ## Where Are the NETCONF/YANG Tools? DevFeed: [Where Are the NETCONF/YANG Tools?]() Original publisher: [Read original article]() Published: 2025-06-04T05:38:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [NETCONF](), [Tooling](), [Network](), [Automation](), [XML]() Tags: [netconf](), [network](), [network-automation](), [tooling](), [xml]() ### AI overview The article examines difficulties finding reliable, current tooling for NETCONF/YANG network-device configuration and model inspection. It discusses ncclient's incomplete documentation, abandoned or outdated YANG tools, installation problems on modern Python versions, and the challenges of using Docker-based tooling. It mentions pyang as a possible tool and asks readers to recommend maintained alternatives. ### Source excerpt Jo attempted to follow the vendor Kool-Aid recommendations and use NETCONF/YANG to configure network devices. Here's what he found (slightly edited): IMHO, the whole NETCONF ecosystem primarily suffers from a tooling problem. Or I haven't found the right tools yet. ncclient is (as you mentioned somewhere else) an underdocumented mess. And that undocumented part is not even up to date. The commit hash at the bottom of the docs page is from 2020... I am amazed how so many people got it working well enough to depend on it in their applications. Read more ... ## Transitioning into Networking, 2025 Edition DevFeed: [Transitioning into Networking, 2025 Edition]() Original publisher: [Read original article]() Published: 2025-04-04T06:20:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [systems](), [Cloud Networking](), [Automation]() Tags: [architecture](), [certifications](), [cloud-networking](), [network-automation](), [networking](), [systems]() ### AI overview A systems engineer asks how to transition into network engineering or architecture. The article recommends building on networking fundamentals, learning cloud networking and automation, researching target organizations, using certifications strategically, and practicing with free or open-source labs and tools. ### Source excerpt Elmer sent me the following question: I've been working in systems engineering (Linux, virtualization, infrastructure ops) and am considering shifting toward network engineering or architecture. I got my CCNA years ago and started CCNP but didn't continue. I'd really appreciate any thoughts you might have on how someone with my background could best make that transition today, especially with how things are evolving around automation and the cloud. I keep answering a variant of this question every other year or so (2019, 2021, 2023, 2024). I guess it's time for another answer, so here we go. Read more ... [Next page]()