What are the naming conventions for QA servers?

What naming convention should be used when creating a new QA server?

Comments

• I believe that in the past qa servers were named after fictional cities (Isengard), production servers were named after real cities (Portland), but I don't think that holds true any longer now that we use cloud server exclusively. Related to this question: https://stackoverflowteams.com/c/blend-interactive/questions/14?rq=1

Additional Posts

AFAIK we don't yet have a set standard. What I generally see is the pattern: client-funciton-environment. So the QA Web server for Acme would be acme-web-qa. A production database for Acme would be acme-sql-prod. For load balanced environments, we tack on a number for each server acme-web-prod-1. If "web" is too general for a client (if they have multiple web-like services or servers), we may use a more specific term, such as acme-episerver-web-prod-1.

Comments

• In general, I've been putting the number on the penultimate, rather than last, segment of the name, so that server would be named acme-episerver-web-1-prod instead.  This ensures that the name always ends with the environment, so it's easy to glob all prod servers like *-prod$ when querying servers.