我们向沉闷（服务器）主机名的渐进转变

文章背景与核心概要

多年来，许多IT基础设施团队都在不断演进其服务器命名约定。本文探讨了一种逐渐抛弃富有创意的主题式命名方案（例如多伦多街道、神话人物和城市名称），转向纯粹实用、趋于“沉闷”的主机名的过程。尽管充满想象力的名字具有历史魅力，但在实际的日常管理、减少认知摩擦以及提供直观清晰性方面，fs1、apps0 和 san1 这种直截了当的命名惯例具有绝对的优势。

本文通过多伦多大学计算机科学系的实际案例，剖析了文件服务器以及多用户系统在命名演变过程中的经验。文章指出，将物理主机名与功能别名直接对齐能够有效消除运维过程中的心智负担和排障摩擦。同时，富有创意的命名并没有完全消失，而是被保留在了普通用户很少接触、管理开销较低的特定基础设施中。

🏙️ 命名方案的演进

🏙️ The Evolution of Naming Schemes

就像许多组织一样，多伦多大学计算机科学系多年来也在几种服务器命名方案之间进行过多次迭代。

Like many organizations, the Department of Computer Science at the University of Toronto has cycled through several server-naming schemes over the years.

• 街道名称时代： 很久以前，服务器是以地理位置命名的——具体来说是多伦多主要的南北向街道（产生了诸如 yonge 和 bay 这样的名字），而其他机器则采用东西向街道的名字。

  • The Street Names Era: Long ago, servers were named after geographic locations—specifically major north-south streets in Toronto (yielding names like yonge and bay), while other machines took the names of east-west streets.

• 功能命名时代： 随着时间的推移，这些富有创意的命名主题大体上被放弃了，取而代之的是功能性、可预测的描述符，例如 comps1 和 apps0。

  • The Functional Era: Over time, these creative themes were largely abandoned in favor of functional, predictable descriptors like comps1 and apps0.[^1]

📁 案例研究：文件服务器名称的演进

📁 Case Study: The Evolution of Fileserver Names

我们的文件服务器的历史完美地说明了这一转变背后的实际驱动力。

The history of our fileservers perfectly illustrates the practical drivers behind this transition.

按照惯例，这些服务器总是以 san 前缀开头（甚至在最近几代中并不存在物理存储区域网络时也是如此，cf）。在好几个世代中，它们一直使用以城市为主题的名字：

Conventionally, these servers always started with the prefix san (even in recent generations where no physical Storage Area Network exists, cf). For several generations, city-themed names were used: * santafe * santafe * sanjavier * sanjavier * sanandreas（用于测试文件服务器） * sanandreas (used for the test fileserver)

消除运维摩擦

Eliminating Operational Friction

有趣的是，这些富有创意的主机名从未在 NFS 挂载中暴露过。相反，NFS 文件系统是通过诸如 fs1 和 fs3 这样直截了当的别名来挂载的。从历史上看，这允许管理员在物理硬件之间透明地进行这些名称及其底层文件系统的故障转移（fail over）——这种习惯在硬件更新换代很久之后依然保留了下来。

Interestingly, these creative host names were never exposed in NFS mounts. Instead, NFS filesystems were mounted using straightforward aliases like fs1 and fs3. Historically, this allowed administrators to fail over these names and their underlying filesystems between physical hardware transparently—a habit that persisted long after.

然而，物理服务器的主机名与其功能性挂载点之间的这种脱节带来了一些轻微的运维摩擦：

However, this disconnect between the physical server's host name and its functional mount point introduced minor operational friction: 1. 对 fs1 背后的硬件进行故障排查，需要记住该特定硬件世代所对应的 san<whatever> 主机名。 1. Troubleshooting the hardware behind fs1 required remembering its corresponding san<whatever> host name for that specific hardware generation. 2. 收到关于 sanjavier 的警报时，需要进行心智转换，才能弄清楚它托管的是哪个虚拟的 fsN 文件服务器。 2. Receiving an alert about sanjavier required mental translation to figure out which virtual fsN fileserver it hosted.

为了消除这种烦恼，当前一代的文件服务器采用了沉闷且直接的映射方式。物理主机名现在直接与它们的虚拟身份保持一致——例如 san1 和 san4。虽然这种改变不那么富有诗意，但它极大地简化了日常管理。

To eliminate this annoyance, the current generation of fileservers adopted boring, direct mappings. Physical host names now align directly with their virtual identities—such as san1 and san4. While less poetic, this change drastically simplifies day-to-day administration.

👤 用户体验与多用户系统

👤 User Experience and Multi-User Systems

追求这种实用简洁性，也是为什么在从 Solaris 迁移到 Linux 的过程中，通用的多用户服务器从多伦多街道名称过渡到 apps0 和 comps0 等直观标签的原因。

This pursuit of practical simplicity is also why general multi-user servers transitioned from Toronto street names to intuitive labels like apps0 and comps0 during the migration from Solaris to Linux.

这种清晰的命名法帮助用户立即识别机器的预定用途——区分通用登录服务器和重型计算服务器，从而打消在登录节点上运行资源密集型计算的念头。

This clear nomenclature helps users instantly recognize the intended purpose of a machine—distinguishing general-purpose login servers from heavy compute servers, thereby discouraging resource-heavy computations on login nodes.

🏛️ 创意名称依然存活的地方

🏛️ Where Creative Names Still Survive

富有创意的名字并没有完全消失；它们只是被保留给了普通用户很少接触、且管理开销仍然很低的基础设施：

Creative names have not vanished entirely; they are simply reserved for infrastructure that normal users rarely interact with, where administrative overhead remains low:

• alkyone： 我们的外部邮件网关，以 alcyone 命名，已经持续使用了大约二十年。

  • alkyone: Our external mail gateway, named after alcyone, has persisted for roughly twenty years.

• rspamd： 配套的垃圾邮件过滤服务器，以其运行的主要软件命名，而不是 keyx（上一代反垃圾邮件的遗留名称；阅读更多关于可见产品名称的内容）。

  • rspamd: The companion spam filtering server, named after the primary software it runs, rather than keyx (the legacy name of the previous anti-spam generation; read more about visible product names).

• aviary： 我们唯一的 IMAP 服务器，因其运行 Dovecot 而得名。

  • aviary: Our solitary IMAP server, so named because it runs Dovecot.

神话顾问

The Mythological Consultants

由于我个人的命名倾向于世俗化（例如，将一个临时的备份 MX 服务器命名为 sponge，因为它旨在临时“吸收”传入的电子邮件），因此拥有古典文学和北欧神话背景的同事们便接管了富有创意的命名工作。多亏了他们，像特定 DNS 解析器这样的小众专用基础设施，才得以拥有像 argos 这样具有历史分量的名字。

Because my personal naming sense leans toward the mundane (for instance, naming a temporary backup MX server sponge because it was meant to "soak up" incoming email temporarily), colleagues with backgrounds in Classics and Norse mythology handle the creative nomenclature. Thanks to them, specialized infrastructure—like a specific DNS resolver—gets names with historical weight, such as argos.

（查看原帖上的 4 条评论。）

(View 4 comments on the original post.)