I know this might be better implemented as a TPA-RFC, logically, but
i feel we already have rough consensus on this.

The last request for a VM that came in (#40070) really demonstrated to
me the reason for this deprecation: `tekesicola` is certainly a
nice-looking name, but I have no idea what it means or why it was
picked. So it would make someone unfamiliar with the history of that
machine to actually know what it's for.

doc/naming-scheme.md

@@ -32,9 +32,17 @@ There are multiple naming schemes in use:
  * role-based
  * location-based
 
+We are trying to phase out the onion-based names, in favor of more
+*descriptive* names. It kind of takes the soul out of the
+infrastructure, but it makes things much easier to figure out for
+newcomers. It also scales better.
+
 Onion species
 -------------
 
+Note that this naming scheme is deprecated. Favor role-based or
+location-based names, see below.
+
 [Wikipedia list of onion species][], preferably picking a first letter
 matching purpose (e.g. "m" for monitoring, "b" for backups, "p" for
 puppet) and ideally not overlapping with [existing machines at