Difference between revisions of "Renaming a PVE node"
(Created page with "= Work in progress = Quick notes gathered from various other places including the forum: To rename a standalone PVE host, you need to edit: * /etc/hosts * /etc/hostname * /e...") |
(→Change Hostname: pvelocalhost is not used anymore) |
||
| (7 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| − | = | + | == Introduction == |
| − | + | Proxmox VE uses the ''hostname'' as a nodes name, so changing it works similar to changing the host name. | |
| + | This must be done on a empty node. | ||
| − | + | == Change Hostname == | |
| + | |||
| + | Rename a standalone PVE host, you '''need''' to edit: | ||
* /etc/hosts | * /etc/hosts | ||
* /etc/hostname | * /etc/hostname | ||
| + | |||
| + | In the above files replace all occurrences of the ''old name'' with the '''new one'''. Ensure that <tt>/etc/hosts</tt> has an entry with the hostname mapped to the IP you want to use as main IP address for this node. | ||
| + | |||
| + | There are other files which you may want to edit, they are not important for the functions of Proxmox VE itself. | ||
* /etc/mailname | * /etc/mailname | ||
* /etc/postfix/main.cf | * /etc/postfix/main.cf | ||
| − | + | If your node is in a cluster, where it is not recommended to change its name, adapt <tt>/etc/pve/corosync.conf</tt> so that the nodes name is changed also there. | |
| + | See https://pve.proxmox.com/pve-docs/chapter-pvecm.html#edit-corosync-conf | ||
| + | |||
| + | == Cleanup == | ||
| + | |||
| + | The SSH keys don't need to be edited unless you really want to (and if you do, make sure you make the corresponding change on every other machine that SSH public key appears on). | ||
| + | |||
| + | Now move the configuration files, as the ''pmxcfs'' has a few restrictions to ensure consistency you cannot rename non empty folders. Thus if you have VMs or Containers on the node, which is not recommended when changing a nodes name, you have to recreate the folder structure and copy files per folder level. | ||
| + | |||
| + | Also copy the contents of <tt>/var/lib/rrdcached/db/pve2-{node,storage}/''old-hostname''</tt> to <tt>/var/lib/rrdcached/db/pve2-{node,storage}/''new-hostname''</tt> and remove the old directory. | ||
| + | |||
| + | == References == | ||
| + | |||
| + | * [https://forum.proxmox.com/threads/proxmox-node-name-change.14327/ Forum Post] | ||
| − | [[ | + | [[Category: HOWTO]] |
Revision as of 06:00, 7 September 2018
Introduction
Proxmox VE uses the hostname as a nodes name, so changing it works similar to changing the host name. This must be done on a empty node.
Change Hostname
Rename a standalone PVE host, you need to edit:
- /etc/hosts
- /etc/hostname
In the above files replace all occurrences of the old name with the new one. Ensure that /etc/hosts has an entry with the hostname mapped to the IP you want to use as main IP address for this node.
There are other files which you may want to edit, they are not important for the functions of Proxmox VE itself.
- /etc/mailname
- /etc/postfix/main.cf
If your node is in a cluster, where it is not recommended to change its name, adapt /etc/pve/corosync.conf so that the nodes name is changed also there. See https://pve.proxmox.com/pve-docs/chapter-pvecm.html#edit-corosync-conf
Cleanup
The SSH keys don't need to be edited unless you really want to (and if you do, make sure you make the corresponding change on every other machine that SSH public key appears on).
Now move the configuration files, as the pmxcfs has a few restrictions to ensure consistency you cannot rename non empty folders. Thus if you have VMs or Containers on the node, which is not recommended when changing a nodes name, you have to recreate the folder structure and copy files per folder level.
Also copy the contents of /var/lib/rrdcached/db/pve2-{node,storage}/old-hostname to /var/lib/rrdcached/db/pve2-{node,storage}/new-hostname and remove the old directory.