I’ve got asked this question a couple of times already! The process is straight forward now but it didn’t always have been!
At first I named my servers according with their purpose: “HOMESERVER”, “UTORRENT”, etc. This turned out not to work very well when I started to fiddle with virtualization. I needed to give them proper names that were not tied to the main software they were running so I could switch eventually, as I did when I decided to go with FreeNAS instead of Microsoft Windows Home Server.
The solution I took from watching the news about the US tornado season. They always have female names given alphabetically. My wife suggested to use stars since several analogies could be made: Constellations could hold servers that have a common purpose, the size of the star could be related to the given server’s processing power, there are several galaxies or groups of “stars” and the list goes on and on.
Right now I have the following names being actively used:
- Andromeda – this is my low-power, always on, Proxmox Virtualization box.
- Betelgeuse – this is my uTorrent-based downloader.
- Capella – my FreeNAS 4x2TB ZFS Raid-Z file server.
- Deneb – my cloud backup virtualized box: every hour it takes a snapshot of the websites I manage and also downloads and archives all gmail messages locally, these backups are all sent to Capella for long-term storage when it comes online.
- Elnath – my git code server virtualized box.
- Smokeping – this is a virtualized network test machine that constantly pings several addresses to keep track of when and where network failures occur, and yes, it needs a new name.
- Puppetmaster – this is the puppet master virtualized machine I use to coordinate puppet settings, I also need a new name for it.