<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Network-Automation on Gene Reader</title><link>https://blog.gereader.xyz/categories/network-automation/</link><description>Recent content in Network-Automation on Gene Reader</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><managingEditor>eugene.reader@gmail.com (Gene Reader)</managingEditor><webMaster>eugene.reader@gmail.com (Gene Reader)</webMaster><lastBuildDate>Sat, 22 Nov 2025 16:52:05 -0800</lastBuildDate><atom:link href="https://blog.gereader.xyz/categories/network-automation/index.xml" rel="self" type="application/rss+xml"/><item><title>Nautocon and AutoCon4 Session Notes (Unofficial)</title><link>https://blog.gereader.xyz/posts/autocon4-notes/</link><pubDate>Sat, 22 Nov 2025 16:52:05 -0800</pubDate><author>eugene.reader@gmail.com (Gene Reader)</author><guid>https://blog.gereader.xyz/posts/autocon4-notes/</guid><description>&lt;p&gt;These are my personal reflection notes from the AutoCon4 and Nautocon sessions I attended. I took notes during the sessions and expanded them the same day while everything was still fresh, trying to pull out the high-level concepts I wanted to remember.&lt;/p&gt;
&lt;p&gt;I wrote most of this in fast shorthand during the talks, then turned those notes into fuller summaries later. That means there is always a chance I captured something imperfectly or interpreted a point differently than the speaker intended. &lt;b&gt;Any mistakes are mine.&lt;/b&gt;&lt;/p&gt;</description></item><item><title>What AutoCon4 Taught Me</title><link>https://blog.gereader.xyz/posts/autocon4/</link><pubDate>Sat, 22 Nov 2025 14:17:51 -0800</pubDate><author>eugene.reader@gmail.com (Gene Reader)</author><guid>https://blog.gereader.xyz/posts/autocon4/</guid><description>&lt;p&gt;I went into AutoCon4 expecting to hear new tooling ideas, clever automation tricks, and maybe a few case studies to bring home. I walked out with something very different.&lt;/p&gt;
&lt;p&gt;Instead of focusing on the latest frameworks or features, almost every speaker pushed a much deeper point.&lt;/p&gt;
&lt;p&gt;If you want to go deeper in what I learned at Nautocon and AutoCon4, I have also published my expanded session notes:
&lt;a href="https://blog.gereader.xyz/posts/autocon4-notes/"&gt;Nautocon &amp;amp; AutoCon4 Session Notes (Unofficial)&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Building a Network Automation Lab: Containerlab + NetBox on macOS</title><link>https://blog.gereader.xyz/posts/intro-to-clab/</link><pubDate>Sun, 28 Sep 2025 14:00:00 -0700</pubDate><author>eugene.reader@gmail.com (Gene Reader)</author><guid>https://blog.gereader.xyz/posts/intro-to-clab/</guid><description>&lt;h1 id="building-a-network-automation-lab-containerlab--netbox-on-macos"&gt;Building a Network Automation Lab: Containerlab + NetBox on macOS&lt;/h1&gt;
&lt;p&gt;&lt;em&gt;Building a foundation for network automation testing and development on a Mac from 2018&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="the-challenge"&gt;The Challenge&lt;/h2&gt;
&lt;p&gt;I needed a reliable local lab environment for testing network automation scripts and prototyping configurations. My 2018 MacBook Pro with 16GB RAM isn&amp;rsquo;t exactly cutting-edge anymore, so I had to be smart about how I used my resources.&lt;/p&gt;
&lt;p&gt;My goal was to build something that could handle real routing protocols and integrate with modern automation tools, but wouldn&amp;rsquo;t require enterprise hardware or cloud resources.&lt;/p&gt;</description></item></channel></rss>