<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Provisioning on At the Edge</title><link>https://attheedge.dev/tags/provisioning/</link><description>Recent content in Provisioning on At the Edge</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 10 Nov 2026 10:00:00 +0100</lastBuildDate><atom:link href="https://attheedge.dev/tags/provisioning/index.xml" rel="self" type="application/rss+xml"/><item><title>Installing Robots Over the Network</title><link>https://attheedge.dev/post/provisioning-edge-servers-with-pxe/</link><pubDate>Tue, 10 Nov 2026 10:00:00 +0100</pubDate><guid>https://attheedge.dev/post/provisioning-edge-servers-with-pxe/</guid><description>&lt;p&gt;A new robot on the bench has an empty disk. It has no name and no operating system, so the fleet can&amp;rsquo;t reach it. Someone has to put an image on it, and every way of doing that by hand leaves the result depending on who stood at the machine.&lt;/p&gt;
&lt;p&gt;In the field I see three answers. Someone types a hostname at an installer prompt. Someone keeps a user-data file per box. Someone builds a USB image per site and carries it over. In all three, the person at the machine decides, and nothing reviewable records it.&lt;/p&gt;</description></item></channel></rss>