(I'm curious as to what seemed so out-of-place in a serious action report. Mythological gods seem like they'd be OK... but maybe Seven Dwarves or Deadly Sins or Slang Drug Terms would be embarrassing?)
Even if you want "safe" sanitized names though, I can't understand why people create these elaborate multi-part naming conventions for servers. Seriously, if the hostname is harder to remember and type than the IP address, YOUR NAMING CONVENTION IS BROKEN!
Somehow I just don't have that much respect for people who've gotten where they are by duping professors and wowing everyone with some impressive degree or family pedigree. It's not the same.
For any manager to be worth their salt to me, they have to demonstrate that they've had a lot of good old-fashioned practice in thinking. And the management fast-track just doesn't portend that to me. And I think that's why most companies > 50 employees slowly crumble as their engineers and other thinkers are crowded out by MBAs.
In the course of the after-action report some screen dumps were shown to the executives in which the "whimsical" server names appeared.They were (understandably) in a rather agitated and non-whimsical mood, and incorrectly (in my opinion) correlated the seriousness of the problem which the perceived lack of seriousness of the naming scheme.
They could not see that the naming scheme was not whimsical - it was in fact quite methodical and conveyed more meaning to the engineers who lived with the machines everyday than the strict, sanitized names we eventually ended up with.