<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Renaming Hosts on Deevnet Infrastructure Platform</title><link>https://deevnet.github.io/deevnet-docs/docs/runbook/lifecycle/host-rename/</link><description>Recent content in Renaming Hosts on Deevnet Infrastructure Platform</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://deevnet.github.io/deevnet-docs/docs/runbook/lifecycle/host-rename/index.xml" rel="self" type="application/rss+xml"/><item><title>Rename a Proxmox Node</title><link>https://deevnet.github.io/deevnet-docs/docs/runbook/lifecycle/host-rename/pve-node-rename/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deevnet.github.io/deevnet-docs/docs/runbook/lifecycle/host-rename/pve-node-rename/</guid><description>&lt;h1 id="rename-a-proxmox-node">
 Rename a Proxmox Node
 &lt;a class="anchor" href="#rename-a-proxmox-node">#&lt;/a>
&lt;/h1>
&lt;p>Bringing a PVE node&amp;rsquo;s name into agreement with its inventory name, on a standalone node,
without restarting its guests.&lt;/p>
&lt;p>This is a standing procedure rather than a one-off. A hypervisor installed from the Proxmox
ISO arrives called &lt;code>pve&lt;/code>, because that is the installer&amp;rsquo;s default, so any node built that way
needs this — and the node name cannot be changed by any supported path afterwards. The

 &lt;a href="#do-not-create-this-problem-again">last section&lt;/a> is how to avoid needing it at all.&lt;/p></description></item></channel></rss>