<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl" href="/feed.xsl"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ansible · Darren Qu</title><link>https://darrenqu.net/tags/ansible/</link><description>Technical writing on network engineering: campus and WAN, hybrid cloud interconnect, automation and observability, and the data center fabrics — InfiniBand, RoCE, Spectrum-X — underneath GPU clusters.</description><generator>Hugo</generator><language>en-US</language><managingEditor>Darren Qu</managingEditor><webMaster>Darren Qu</webMaster><copyright>2026 Darren Qu</copyright><atom:link href="https://darrenqu.net/tags/ansible/index.xml" rel="self" type="application/rss+xml"/><lastBuildDate>Wed, 30 Sep 2026 00:00:00 +0000</lastBuildDate><item><title>Adopting a Brownfield Network into Ansible: What the Lab Caught</title><link>https://darrenqu.net/automation/brownfield-network-iac-three-vendors/</link><pubDate>Wed, 30 Sep 2026 00:00:00 +0000</pubDate><guid isPermaLink="true">https://darrenqu.net/automation/brownfield-network-iac-three-vendors/</guid><category>Automation</category><category>ansible</category><description>Three vendors, one config domain, no rewrite. Collect, model, diff offline, remediate, and re-collect: what failed and where it showed up.</description></item></channel></rss>